Los controladores diseñados específicamente cubren los tipos de dispositivos inteligentes Tuya más habituales, desde aires acondicionados, enchufes inteligentes y luces hasta puertas de garaje, bombas de calor y motores de cortinas. Cada controlador detecta automáticamente los puntos de datos del dispositivo durante el emparejamiento y los asigna a las capacidades correctas de Homey, por lo que la mayoría de los dispositivos están listos para utilizarse directamente. Se incluye un controlador genérico para cualquier tipo de dispositivo que no esté cubierto por los controladores específicos.
![[Imagen: large.png]](https://apps.homeycdn.net/app/com.tuyalocal/152/d2d1ade2-74d6-42ea-9935-c1638d321868/assets/images/large.png)
Toda la comunicación se realiza directamente a través de tu red Wi-Fi local. Los dispositivos responden al instante a los comandos de Homey y envían los cambios de estado en tiempo real, incluso sin conexión a Internet. Cada controlador incluye un conjunto completo de tarjetas de Flow —disparadores, condiciones y acciones— adaptadas a su tipo de dispositivo, por lo que puedes crear automatizaciones en cuanto añadas tu dispositivo.
Asistencia
¿Tienes algún problema con esta aplicación? Contacta con el desarrollador aquí.
Novedades
Versión 1.0.215 — When protocol rotation finds the version a device actually speaks, the app now writes it into "Protocol Version" instead of only advising you to. It had been rediscovering the same answer on every reconnect and starting from the configured version again — on a device that closes the connection every few minutes, that meant a 15-second handshake timeout before every single reconnect, for hours. Your setting is left alone if you have locked the protocol. Parse errors from discarded packets no longer carry the packet as hex: each line was unique, so repeat-suppression could never collapse them, and a burst could push everything else out of the log — support bundles came back with nothing but hex dumps. And a device that is connected but answers no status request now says so; that case used to produce no log line at all. The support bundle got better at its job. It now carries the connection history per device — how many connections, how long they lasted, how many packets arrived and whether any data ever did — instead of leaving that to be worked out by hand from dozens of log lines. Repeated log messages are folded into one line with a count and a time span, so a single chatty fault can no longer crowd everything else out of the report, and connection events are included even though they are not warnings. The report also reaches further back: when the log buffer fills, routine lines are dropped before warnings, so its history now extends as far as there were warnings rather than as far as there was chatter. The header carries the app start time and how long it has been running, without which the per-device connection counters — which start there — read like a contradiction. And settings that merely begin with "dp_" but hold a switch rather than a number no longer appear under the DP mapping. The "Create support bundle" button now also sits at the top of the Fix It tab. It was only under Help, which is not where anyone with a device that will not work goes looking. Two corrections to that report: it was reading the saved copy of the log rather than the running one, so whatever had just happened — the very reason for pressing the button — was missing from it. And a handful of repeated events now list their times instead of only a count, which is what makes a connection history readable.
Fuente: homey.app
Toda la comunicación se realiza directamente a través de tu red Wi-Fi local. Los dispositivos responden al instante a los comandos de Homey y envían los cambios de estado en tiempo real, incluso sin conexión a Internet. Cada controlador incluye un conjunto completo de tarjetas de Flow —disparadores, condiciones y acciones— adaptadas a su tipo de dispositivo, por lo que puedes crear automatizaciones en cuanto añadas tu dispositivo.
Asistencia
¿Tienes algún problema con esta aplicación? Contacta con el desarrollador aquí.
Novedades
Versión 1.0.215 — When protocol rotation finds the version a device actually speaks, the app now writes it into "Protocol Version" instead of only advising you to. It had been rediscovering the same answer on every reconnect and starting from the configured version again — on a device that closes the connection every few minutes, that meant a 15-second handshake timeout before every single reconnect, for hours. Your setting is left alone if you have locked the protocol. Parse errors from discarded packets no longer carry the packet as hex: each line was unique, so repeat-suppression could never collapse them, and a burst could push everything else out of the log — support bundles came back with nothing but hex dumps. And a device that is connected but answers no status request now says so; that case used to produce no log line at all. The support bundle got better at its job. It now carries the connection history per device — how many connections, how long they lasted, how many packets arrived and whether any data ever did — instead of leaving that to be worked out by hand from dozens of log lines. Repeated log messages are folded into one line with a count and a time span, so a single chatty fault can no longer crowd everything else out of the report, and connection events are included even though they are not warnings. The report also reaches further back: when the log buffer fills, routine lines are dropped before warnings, so its history now extends as far as there were warnings rather than as far as there was chatter. The header carries the app start time and how long it has been running, without which the per-device connection counters — which start there — read like a contradiction. And settings that merely begin with "dp_" but hold a switch rather than a number no longer appear under the DP mapping. The "Create support bundle" button now also sits at the top of the Fix It tab. It was only under Help, which is not where anyone with a device that will not work goes looking. Two corrections to that report: it was reading the saved copy of the log rather than the running one, so whatever had just happened — the very reason for pressing the button — was missing from it. And a handful of repeated events now list their times instead of only a count, which is what makes a connection history readable.
Fuente: homey.app