Homey SDK rules & pitfalls (our words)
- Driver match is on exact zigbee.manufacturerName + productId arrays in driver.compose.json; endpoints/clusters must match the interview. Source: Homey Apps SDK.
- Flow card ids must exist in app.json or triggers throw (invalid_flow_card_id).
- Large app.json slows/destroys Athom processing; keep drivers lean.
- Settings changes arrive via onSettings; never block it on a sleepy device.
- Use BoundCluster for incoming commands; register listeners once (memory leaks otherwise).
Related notes:
- Athom / Homey publish limits — what we know (2026-10-10, Paris)
- P2929 — Bastien app: crashes and failing Flow cards/buttons (21/10/2026, Paris)
- Button event router (P2926) — 2026-10-21
- Disabled workflows (P2916, 20/10/2026)
- Homey forum — Apps category + zigbee tag digest (2026-10)
- Forum Homey — fils clés (10/10/2026)
- Diagnostics et crashs Homey reçus par Gmail (01/08 → 10/10/2026)
- Homey firmware & Zigbee stack: research notes (2026-10-10)
- Homey news 2025-2026: what it means for this app (queue #101-#106)
- Homey SDK, CLI and developer news — October 2026 (our summary)
- Homey SDK v3 rules — sourced, tested, automated (P2964)
- Homey tooling watch
- Homey versions strictly incremental — all apps (rule from dlnraja, 2026-10-10)
- P2933 / P2934 — Homey diag reports via Gmail + Aqara DJT11LM (2026-10-21)
- Battery multi-button remotes — TS0041 / TS0042 / TS0043 / TS0044 / TS004F
- [Homey forum 154077 — "[APP][Pro] Tuya Local" (read 2026-10-11)](https://github.com/dlnraja/com.tuya.zigbee/blob/master/docs/knowledge/TUYA_LOCAL_THREAD_154077.md)
- Homey SDK / upstream watch — zigbee-clusters 3.9.0 and tuya-local (24/10/2026)
- Z2M generic device options → ideas for Homey (ideas only, nothing implemented)