Skip to content

New Share your ideas with the AWTRIX community. Keep your creations together in your account.

Sign in

Terms of service

AWTRIX Hub is a free place to share automations and icons for AWTRIX displays and discuss them with their creators. It is operated by Stephan Mühl Softwareentwicklung (see the legal notice). These terms explain the rules for contributing and using content from the Hub.

1. Accounts and access

You can browse contributions, view enlarged icon previews and read discussions without an account. Sign in to publish flows or icons, post comments, like contributions, view or download flow code, or download original icon files and flow icon packs. Apps and devices need a Hub connection key to download originals, flow code and script sounds. Home Assistant blueprints are also published in our public GitHub repository.

Create an account with a sign-in provider offered on the login page, such as GitHub or Discord. We do not receive your password from those providers. The privacy policy explains the account data we use. Keep your sign-in details and Hub connection key private. You can replace or remove that key in your account settings.

Flows published before accounts existed are protected by a secret edit link, and those links keep working. Whoever holds one can change or delete its flow. We cannot restore a lost link because we store only its hash. If you have one, open it while signed in to attach the flow to your account. The edit link stops working permanently after you do this. No date is set for retiring the links that remain.

2. Sharing and discussion rules

Use the discussion below a flow or icon for questions, suggestions and requests about that contribution. Be constructive and respectful. A request does not oblige its creator to answer, change the contribution or provide support.

Do not publish:

Comments are public plain text, up to 3,000 characters. Your account display name and the posting time appear beside them. You can edit or delete your own comments. Replies written by others remain if you delete a comment; they are no longer linked to the deleted message. Moderators may remove comments that break these rules. Comments are not private messages, and the Hub does not send e-mail notifications for new comments or replies.

Contributions are not individually reviewed before publication. You remain responsible for what you submit. Automated bulk submissions and attempts to bypass access controls or rate limits are not permitted. Do not inflate likes, install or download counts, for example with several accounts or automated requests.

Official firmware only

Only content developed for the official, unmodified AWTRIX firmware for its selected platform may be uploaded. For AWTRIX NG, this means the official AWTRIX NG firmware maintained in that repository. This rule covers flows, on-device scripts and modules, icons, and all accompanying files, including sounds.

Content developed for firmware forks, modified builds or other unofficial firmware is prohibited, even if it also runs on official firmware. This applies to new uploads and all subsequent updates. Select the official firmware platform your contribution was developed for: AWTRIX NG or AWTRIX 3. These requirements help prevent compatibility problems for other users.

3. The rights you grant

You keep your copyright. By submitting content, you grant us a non-exclusive, worldwide, royalty-free licence to store, display and deliver it on the Hub and to devices, and make the technical copies needed to provide the service. For flows and icons, this includes downloads and installation on AWTRIX devices, resized and re-encoded versions of pictures, enlarged previews, thumbnails and link previews, delivering a script's sounds to signed-in users and their devices, and catalogue entries. Comments are displayed in their discussion.

Where enabled and described in the privacy policy, this also includes announcements of new flows in our Discord community and mirroring Home Assistant blueprints in our public GitHub repository for import into Home Assistant. Comments are not announced on Discord.

Signed-in users can open any published icon in the Studio, change it and publish the result on the Hub as a variation. The variation is shown as based on the original, with a link to it while the original is published, and it is used on the Hub like any other icon. By publishing an icon, you allow other users to do this and us to host and deliver their variations. This is part of the Hub as offered and also applies to icons published before this paragraph was added. Variations stay published if you later delete your icon. A variation does not transfer your copyright, and nobody may present your icon as their own work. If a variation of your icon breaks these terms, report it or write to flows@blueforcer.de.

You must have the rights needed to grant this permission and to allow the uses in section 4. A more specific licence supplied with a contribution takes precedence for that contribution; it must permit hosting and sharing here.

Deleting a contribution ends permission for its future public use on the Hub; icon variations that others have already published remain. Limited records may remain for moderation or legal claims as explained in the privacy policy. Copies already downloaded by others, installed on displays or present in public repository history cannot be recalled.

4. Using flows and icons

Earlier AWTRIX 3 community uploads

Icons marked as coming from the AWTRIX 3 community were uploaded to the earlier service for use by AWTRIX users. Those uploads did not record an account or identify the original creator. The Hub continues to make them available for that original community purpose; the importer is not presented as their creator. Like every published icon, they can be opened in the Studio and published as a variation that links to the original (see section 3). Rights remain with the respective creators. If you created an imported icon, contact flows@blueforcer.de for attribution, a rights clarification or a removal request, including for variations of it.

Other contributions

Unless the contribution provides a different licence:

Read a flow before running it (sign in to see its code), especially if it connects to other services. Do not publish your credentials when sharing a configuration. An author can update or remove a contribution. Installed icon copies keep their current version until you reload them; an icon ID is not a promise of permanent availability or unchanged contents.

5. Removing content and closing an account

You can manage your own published flows and icons from your account and your comments in their discussions or under My comments. The account view also lets you remove your comments when their flow or icon is no longer public. Removing a flow or icon also hides its discussion. Deleting your account removes your comments, likes and private server drafts. For published flows and icons, you choose whether to remove them from public view or leave them available under a deleted account. If you leave them online, the author name shown on your flows remains, your icons are shown as by "Deleted account", and you lose the ability to edit them yourself. You can still contact us about your privacy rights.

We may restrict or remove content that is unlawful or breaks these terms, and restrict accounts involved in serious or repeated abuse. We assess the context and severity, and aim to take proportionate action. Publication does not guarantee permanent storage. Keep your own copies of work you want to preserve.

6. Reporting content and reviewing decisions

Anyone can report a flow, icon or comment using the reporting form or by writing to flows@blueforcer.de. You do not need an account. Give the exact link and explain the issue. For a complete unlawful-content notice under Article 16 DSA, include your name and e-mail address and confirm that you believe the information is accurate and complete. The contact-detail exception for offences involving child sexual abuse remains applicable. We also consider anonymous or incomplete reports, but cannot send you an outcome without contact details.

The reporting procedure is intended to meet Article 16 of the Digital Services Act. We assess reports and decide whether to leave, restrict or remove the content. A person makes moderation decisions. Automated form checks and rate limits help prevent abuse; they do not decide whether a reported opinion is allowed. A report about a comment keeps a copy of its text, display name and link for moderation, even if the comment is later changed or deleted.

Where we have the necessary contact details, we provide the reporter with the outcome and the affected contributor with the reasons for a restriction and the available ways to contest it, as required by Articles 16 and 17 DSA. Accounts may have no e-mail address; legacy flows may have only an edit link. In those cases we may be unable to contact their authors directly.

If you disagree with a moderation decision, write to flows@blueforcer.de with the report reference or contribution link and explain why. We will review it. Your statutory rights, including access to the courts, remain unaffected.

7. Availability and liability

The Hub is free to use. We aim to keep it available but do not promise uninterrupted access, compatibility with every device or permanent storage. We may change or discontinue features.

We are liable without limitation for intentional or grossly negligent conduct and for culpable injury to life, body or health. For a slightly negligent breach of an essential contractual obligation, liability is limited to foreseeable damage typical of the agreement. Further liability is excluded to the extent permitted by law. Mandatory statutory liability remains unaffected.

8. Applicable law and changes

German law applies. Consumers retain the protection of mandatory provisions of the law of their country of residence. If any provision is invalid, the remaining terms continue to apply as provided by law.

We update these terms when the service or legal requirements change. We will inform users of significant changes. Changes requiring your agreement will be presented for acceptance; continuing to browse alone is not treated as acceptance of new contractual terms.

Last updated: 23 October 2026