Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

Homey firmware & Zigbee stack: research notes (2026-10-10)

Public, unmodified sources only. No firmware image was downloaded, unpacked or decompiled. Athom does not publish Homey Pro firmware images for download; updates go through the app (Settings → Updates).

See REA_TOOL.md for the rea evaluation.

2. Node.js per firmware (official)

Source: https://apps.developer.homey.app/the-basics/app#node.js

3. Zigbee stack (EmberZNet NCP)

4. Open-source libraries (npm, as of 2026-10-10)

5. Memory and app lifecycle

6. Build processing (Athom)

7. Additive proposals for the app

  1. Handle memwarn: drop caches (DP maps, logs), log the count to diagnostics, and run a heap-budget test in CI.
  2. Rebinding after an NCP update: at init, compare the stored "last bound" stamp with the time since the last reporting. If a device has been silent longer than N times its report interval, re-run bind and configureReporting once, with backoff. Add a "Re-bind / reconfigure reporting" maintenance action.
  3. Rely on end-to-end APS ACK: keep a single retry, with jitter, for writes; do not stack app retries on top of the stack's retries (avoids bursts that freeze Tuya MCUs, e.g. Gledopto).
  4. Sleepy end devices: queue writes until the next check-in instead of failing; mark as unavailable only after 2–3 reporting intervals (generalises the #550 fix).
  5. Store ieeeAddress (≥12.3.0) in diagnostics, guarded for older firmware.
  6. Use Node 22 as the runtime target: add a CI job that runs the tests on Node 22 as well as Node 24 for the CLI. Set compatibility to >=12.9.0 only if Node 22 APIs are really used.
  7. Optional OTA manifest entries, only for vendor-published images whose licence allows redistribution (do not host Tuya images).
  8. A weekly workflow watches the npm versions in §4 and the Silabs release notes, and opens an issue when something changes.

Credits

← Knowledge base index · source