Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

Athom / Homey publish limits — what we know (2026-10-10, Paris)

Measured facts (our bisects, publish.yml, same pipeline)

BuildChange vs last Test buildResult
#3482 v9.0.1364baseline (spi + whd02 held)Test
#3483 v9.0.1365+ deprecated: true on wall_remote_4_gang (+18 B)AggregateError
#3485 v9.0.1366deprecated reverted, ci/actions-optimization mergedTest
#3486 v9.0.1367 (K1)+ one it driver name (+38 B)Test
#3487 v9.0.1368 (K2)+ zigbee_rebind maintenance action on 319 drivers (~+70 KB app.json) + manifest.version readTest
J4 #3479 / J5 #3481I + one new driver (spi / whd02)AggregateError

Conclusion: it is not a byte-size threshold (K2 added ~70 KB and passed; +18 B deprecated failed). Every failure changes the set of pairable driver ids (a new driver, or a driver hidden via deprecated). Pure content changes inside existing drivers pass. Note: master already ships 12 deprecated drivers and passes, so deprecated itself is not forbidden; the trigger is a change in the set. Working hypothesis: Athom's server-side processing (store driver index / images / per-driver pages) fails when the driver list changes for this very large app. Not documented; to confirm with Athom.

Our app vs peers

Appapp.jsondriversmanufacturerName entries
ours (master)2.39 MB448 (446 published)19 199 (≈3 600 productId entries)
JohanBendz/com.tuya.zigbee (upstream)0.35 MB113650

Other peers (Xiaomi, Sonoff, Hue) raw app.json not fetchable at HEAD (built file not committed).

Official sources checked (in our words)

Audit (master)

Proposed solutions (not applied — need decision)

  1. (No Athom contact — user rule.) Keep bisecting from our side only.
  2. Change the driver set in one isolated build only (one new driver per build), never mixed with content.
  3. Shrink manifest: move the bulk of manufacturerName lists out of app.json is NOT possible for pairing (Homey matches on manifest), but case-variant duplicates (~3× per FP) could be removed if Homey matching is case-insensitive — must be verified first, else it breaks pairing.
  4. Split into satellite apps by family (lights / sensors / switches) — large migration, re-pair cost.
  5. Keep runtime data (fingerprints DB, dp registry) in lazy-loaded data files, never in app.json.

Update 21:50 Paris — K3 and payload forensics

| K3 #3489 v9.0.1370 | master #3488 content + switch_module_whd02 released only | AggregateError |

Confirms: one new driver alone, on current master, fails. Same for J4/J5.

Local reproduction of the publish payload (scripts/prepare-publish.js, auto-publish env 14000/1500/2, fresh .homeybuild each run — the script mutates .homeybuild, so reruns on the same dir are NOT comparable):

Open: the trigger is server-side and specific to driver-set changes; our pipeline and payload are clean. Next safe probes (bisect branch only): release whd02 with pair views copied from a passing socket driver; and a payload that adds a new driver id cloned 1:1 from a passing driver (rename only).

Correction 22:45 Paris — always read stateMeta

Probe P1 / R4 (2026-10-10 ~23:00 Paris)

Update 23:25 Paris — rename probe passes; fold ready

Athom failure kinds (read stateMeta, never just "processing_failed" or GHA green)

stateMetaMeaningAction
AggregateErrorAthom processing rejected the contentreal failure → bisect content; never auto-retry
socket hang upAthom transport dropped (#3490, #3492, #3494)transient → one retry with a NEW version
The specified key does not exist.upload/S3 side lost the archive (#3496 R5)transient → one retry with a NEW version

Pipeline: .github/scripts/transient-publish-retry.js + step "Transient Athom failure - single retry" in publish.yml re-dispatches publish.yml once (transient_retry=true, which disables a second retry). Both transient strings are in TRANSIENT_RE (processing-failure-republish-check) and build-error-diag-v2. The Auto-Fix doctrine (P139: no bump loops while an older Test is healthy) is unchanged.

Fold + R5 (2026-10-10 ~23:38 Paris)

Fold SUCCESS (2026-10-10 ~24:00 Paris)

Update 2026-10-25 (Paris) — P3024b combo cap vs pairing regression

Update 2026-10-25 (Paris) — P3036 measured combo ceiling and TS0601 top-up

P3201 (2026-11-02): where the combo budget goes, sourced pass

P3206 (2026-11-02 Paris): what actually limits a store publish, and baseline narrowing

P3330 (2026-11-15 Paris): driver-count ceiling enforced

348+ uploaded drivers: refused 12/12 (AggregateError). 347: accepted 6 times, refused once (#3706) with a package that differs from accepted #3705 only by version strings and 2.7 KB of JS. The pre-upload guard now blocks any upload above 347 drivers (master and stable); held drivers ship their couples through lib/drivers/held-driver-folds.json instead of new ids. Evidence and fold list: docs/knowledge/athom-driver-ceiling.md.

← Knowledge base index · source