Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

New driver ids rejected by Athom (AggregateError) — offline analysis 2026-10-11 (Paris)

No upload was made for this analysis. Sources: git history of master (version commits), committed app.json at each version, config/publish-hold-drivers.json, docs/knowledge/ATHOM_LIMITS.md.

Builds compared

BuildDriver dirsHeldPublished driverscommitted app.jsonResult
9.0.14164482446—Test
9.0.1417 (#3536, valve_controller_5zone)44924474 448 892 BAggregateError
9.0.1418 (#3537, retry)4492447—AggregateError
9.0.1419 (valve held)4493446—Test
9.0.142044934464 448 172 BTest
9.0.1421 (#3540, remote_rgbcct_8zone)45034474 451 050 BAggregateError
9.0.1422 (#3541, retry)4503447—AggregateError

Over the whole history (v9.0.1300 → 1422) every build that reached Test published at most 446 drivers; 446 was first reached at 9.0.1330 (accepted). Every build publishing 447+ (1331..1361 with SPI, 1361 with spi held but whd02 in, 1417/1418, 1421/1422) failed with AggregateError.

What is NOT different between passing and failing builds

Interpretation

Decision

Ship new devices as exact-couple profiles inside existing drivers (fold), as already done for SPI → led_controller_rgb and WHD02 → switch_1gang:

The new driver folders stay in source, held from the payload.

Bug found while analysing

remote_rgbcct_8zone triggers used the same name zone for an argument and a token (P2746 rule: token ≠ arg). Fixed in the fold (zone_filter argument).

Update 14:32 Paris — the theory is weakened: AggregateError is (at least partly) flaky

← Knowledge base index · source