Been given an invitation code? Use it here.
Enter the code you were given.
Back to signing in · Sign out and use another account
A building reaches you one of two ways: you commission a gateway yourself, or somebody who owns one invites you to theirs.
Plug it in and open its setup page on the building's own network. It shows a short code. Type it here and the gateway becomes yours.
The app lost its connection to the building. Controls are unavailable until it comes back.
Rooms and names are yours to arrange. Group addresses come from the installation and are only changed by an ETS import.
Give this to them. It works once, and it will not be shown again.
Across every building you have a role in, newest first. Gateway outages appear once they have lasted five minutes, so a flickering line does not fill this list.
Your own language. It follows you to any device you sign in on.
What everyone here sees if they have not chosen for themselves — the family, not you. Your own language is above, and this does not change it.
No site file loaded.
Importing runs on the server and replaces the project for this device id. Rooms and names you have arranged are kept.
Uploading…
Every address in the project: what it is called, what it drives, and a button to test it against the real bus. The outcome is what the actuator did, not what was asked.
Nothing imported yet.
Changes take effect on the next command; the relay re-reads the installation within half a minute. What you set here outranks anything the import guessed.
Start a session and walk the building pressing switches. Each one appears here as it is heard, newest first, and can be added to the project without an ETS file. Nothing is sent to the bus — this only listens.
Heard on this bus and not in the project. Collected continuously; existence only, never values.
Or ask every address already in the project to report what it is. Useful straight after changing something in ETS. It reads only — nothing is switched, moved or written.
Optional. With these set, the app talks straight to the gateway over the local network — faster, and it keeps working when the line is out. Leave them blank and everything goes through the cloud.
Not normally needed. The server answers all of this after you sign in. These matter only when this page is served by a gateway itself, or opened from a file, where there is no server to ask.
These run on the gateway itself, so they keep working with the internet down and with nobody's app open. Saved here, delivered to the device, and kept for it if it is offline right now.
This session only, newest first. Cleared when the page reloads.