Integración domótica Deako, gratuita y de código abierto
Deako smart light switches and dimmers on your network: on, off, brightness.
Publicado por LM1LC3N7
- Dispositivos
- Versión 0.1.1
- Requiere Gladys >=5.1.0
- ★ 0
La documentación de esta integración la escribe su autor y, por ahora, solo está disponible en inglés.
Brings Deako smart switches and dimmers into Gladys through the local API of the Deako Connect, without account nor cloud: on / off and brightness, and the changes made at the wall or in the Deako app shown at once.
Never tested with a real device: tell us on the forum how it goes. Not affiliated with Deako.
Before you start
- Your switches are set up with the Deako app and a Deako Connect (or a Deako switch serving as the bridge) is on your network. The newest Deako switches have no local API: they cannot be reached this way.
- Give the Connect a fixed IP address in your router. It announces itself on
the network as the service
local-integration(_telnet._tcp); your router shows its address too.
Configuration
- Address of the Deako Connect: its IP address (or name), with
:portonly if it is not 23. - Full read every: how often the whole list of devices is read again (60 s by default, 30 s at least). The changes come at once in between (the Connect pushes them).
- Save, then open Discover: each switch and dimmer is listed with its name in the Deako app. Add the ones you want.
Test the connection opens the connection if it is closed (at most every 10 s) and checks that the Connect answers.
Devices
| Deako device | Features |
|---|---|
| Switch | Power (0 / 1) |
| Dimmer | Power (0 / 1), brightness (0 to 100, 0 = off) |
How commands are sent
- One message at a time, 800 ms apart (as Deako asks). A command is done once the Connect shows the new state; otherwise its message says why ("sent, without confirmation", "refused by the Connect"…), and the devices are read again 5 s later.
- A scene on many lights sets every light: the commands wait in line (30 s at most), those of one device merged. Gladys gets its answer within 3.5 s: a command still in line then says "waiting in line" and still leaves.
Turning off (Off)
An Off (power 0, or brightness 0) needs no option and goes first: before the commands waiting (it cancels those of the same device), without the 800 ms gap, cutting a request that has had no answer for 1 s, even before the configuration is read (to the address of the last session).
In a scene of many Offs, each waits for its turn without the 800 ms gap (one at a time); one still in line after 4.3 s says so in its answer and still leaves.
When it cannot leave (the Connect does not answer, or another client holds its only connection), it is kept (also across a restart) and sent again every 10 s (one sent without an answer: 10 s after that send), at once when a connection opens for another command if it was never sent, and all at once when the Connect answers again. After connections closed at once or without a byte, the next automatic one (a resend, a reconnection) waits 1 s, then 2, 4, 8, up to 10 s; a click (an Off, a command, Test the connection) does not wait: its connection is tried at once (one per click, one per second at most), and an Off that still cannot leave is retried within about 1 s, then kept. Accepted by the Connect, it is checked by a read 5 s later and sent again 10 s after its last send if that read still shows the device on. It ends once the device shows it off, when the device is turned on again at the wall or in the app (never undone), when a newer command of that device leaves, or when the device is deleted.
An Off is refused only when the address of the Connect is not known (none typed and none from a previous session), or replaced by a newer click on the same device before it left. Once the Connect has answered it 4 times (accepted or refused, "busy" not counted) without the device showing it off, it is no longer sent again by itself: the status says so; click Off again.
Status
The Configuration page shows the connection, the number of devices, the devices to add, and every Off held.
Troubleshooting
- "unreachable": check the address and that the Connect is on the same network as Gladys; new tries after 5 or 15 s, then 30 s, 1, 2, then every 5 minutes.
- Nothing in Discover: check in the Deako app that the switches belong to the profile of this Connect.
Parámetros de configuración
Estos son los parámetros que Deako te pide en su pantalla de configuración en Gladys.
| Parámetro | Tipo | Obligatorio | Descripción |
|---|---|---|---|
| Your Deako lights | section | No | Brings Deako smart switches and dimmers (set up with the Deako app) into Gladys through the local API of the Deako Connect, without account nor cloud: on / off and brightness, the changes made at the wall or in the app shown at once. An Off (power 0, brightness 0) needs no option and goes first, even while the Connect does not answer: it is kept and sent again (every 10 s, 4 answered tries at most) until the device shows it, unless it is turned on again at the wall or in the app. The newest Deako switches have no local API: they cannot be reached this way. Never tested with a real device: tell us on the forum how it goes. Not affiliated with Deako. |
| Address of the Deako Connect | string | Sí | The IP address (or name) of the Deako Connect, or of the Deako switch that serves as the bridge, with :port only if not 23. Give it a fixed address in your router; it announces itself on the network as the service local-integration (_telnet._tcp). |
| Full read every (seconds) | number | No | How often the whole list of devices is read again: 60 s by default, 30 s at least. The changes come at once in between. |
| Language of the names | select | No | Used for the names of the devices and features added from now on. |
Cómo instalar Deako en Gladys
- En Gladys, abre Integraciones: Deako aparece en el catálogo junto a las integraciones nativas, con una insignia de comunidad.
- Haz clic en Instalar. Gladys descarga la imagen Docker (
ghcr.io/lm1lc3n7/gladys-deako:0.1.1), la ejecuta en un entorno aislado del núcleo y genera la interfaz de la integración (dispositivos, descubrimiento y configuración). - Abre la pantalla de Configuración de la integración, rellena los parámetros y guarda.
- También puedes instalarla directamente desde la URL de su repositorio: https://github.com/LM1LC3N7/gladys-deako.
Deako requiere Gladys >=5.1.0. El catálogo de Gladys se actualiza cada hora, así que una nueva versión está disponible como máximo una hora después de publicarse.
¿Todavía no usas Gladys? Es gratuito y de código abierto: sigue la guía de instalación para empezar.
Sobre las integraciones externas
Deako es una integración externa: una integración comunitaria empaquetada como contenedor Docker y publicada en GitHub. Gladys la instala con un clic y la ejecuta en un entorno aislado del núcleo. La publica y mantiene LM1LC3N7, no el equipo principal de Gladys.
- Explorar todas las integraciones, nativas y de la comunidad
- Crear y publicar tu propia integración externa
- Código fuente en GitHub — fuente de esta documentación