Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

Field notes — X/Twitter scan (2026-10-04)

Our own summaries of posts the maintainer shared, with what matters for this app. Sources and authors are credited in CREDITS.md. No code was copied.

Mesh and reliability (for the FAQ)

Device identity and values

DIY firmware worth knowing

Somfy TaHoma / Overkiz — inspiration for covers

How TaHoma works (from Somfy's developer-mode docs, pyoverkiz and the Home Assistant Overkiz integration):

Applied here (P2799): "Open", "Close", "Stop" and "Go to favorite position" flow actions on curtain_motor, curtain_motor_shutter and curtain_motor_wall were log-only placeholders. They now drive the device's own capability listeners, and a favorite_position setting (default 50 %) acts like TaHoma's "My" position.

Ideas kept for later (not implemented): combined position+tilt action with sequencing; staggering commands when a flow moves many covers; optional Identify (cluster 0x0003) action for covers.

Applied (P2801/P2802, all three apps):

Flow cards that never fire (P2803)

The Bastien flow audit found driver triggers that are never fired and conditions without a run listener. Their English titles are clear, but their ids are hashed, so generic emitters miss them. tools/flow/build-dead-flow-autowire.js maps a card only when its title is unambiguous, the driver really has the capability, and the id is not already used literally in JS. Triggers then fire on capability change for that driver only. Conditions return false (never throw) without data, and a driver's own listener still wins.

Ecosystem status checks

Workflow / AI tooling notes

← Knowledge base index · source