Tilez Hub and Tilez Cloud
A Tilez server keeps dashboards, so that every device can use the same one. There are three, for different places:
| Where it runs | What it does | |
|---|---|---|
| Tilez Hub | At home, on a Raspberry Pi or any other machine with Docker | Keeps dashboards, has an admin page, and lets browsers at home show Tilez (it is their bridge to your devices). Devices at home are paired without a code; others with a code, or by signing in with a user |
| Tilez Cloud | On the internet | Keeps dashboards for the Tilez apps, and gives them services of its own: the weather and energy prices. An app starts a home there, joins one with a code from a device of that home, or signs in with an account. No bridge: the apps reach your devices themselves, and a browser gets no dashboards there |
| tilez-pico | At home, on a small board such as a Raspberry Pi Pico W | Keeps dashboards, and nothing else. Being built |
You need none of them to use Tilez on one device. Choose:
- Tilez Hub if you want Tilez in a browser, or one place at home for the dashboards of all your devices.
- Tilez Cloud for the Tilez weather and energy prices connections, or dashboards reachable from anywhere.
How devices get in to Tilez Hub
Section titled “How devices get in to Tilez Hub”- Pairing: a device on your home network is paired the first time it opens the hub. From anywhere else, it enters a one-time code. Either way it is remembered from then on, and you can take it away again on the admin page.
- Users: with users switched on, devices sign in with a name and a password instead.
- Roles: an admin device can change dashboards and other devices; a reader, such as a wall tablet, only shows them.
Every paired device can read the dashboards the hub keeps, with the passwords and keys of their connections in them. Pair only devices of people who may have them.