Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

AggregateError: the five "isolated" drivers have no common content defect (2026-11-15)

Question: the P3095 hold bisect "isolated" five never-published drivers that Athom refuses even when released alone (heiman_keyfob, heiman_siren, presence_radar_aoyan_ay204t, water_leak_aoyan_ay222z, siren_moes_mg_bjq002). Do they share a trait that the accepted ones (water_leak_blitzwolf_bw_is9, sauna_thermostat_ae5503) do not?

Verdict: no content trait found. The evidence points at the payload driver count, not at the drivers. Nothing in their source is changed by this note, and no couple is touched.

1. Content-identical twins, opposite results (decisive)

water_leak_aoyan_ay222z (refused alone, 9.0.1616) and water_leak_blitzwolf_bw_is9 (accepted alone, 9.0.1620) are the same driver apart from ids and names:

If a field, an asset, a pair view or a flow card were the trigger, both would fail or both would pass.

2. Payload driver count of every recorded upload since the 21/10 incident

Sources: publish-size-telemetry-<run> artifacts (current.json, field drivers) for runs from 9.0.1610 on, and the drivers field of athom-publish-outcomes.jsonl for 9.0.1596-9.0.1604.

VersionPayload driversReleased for the runAthom result
9.0.1596 / 1597347noneprocessing_failed, stateMeta socket hang up (not AggregateError)
9.0.16023619+ never-publishedAggregateError
9.0.16033536 never-publishedAggregateError
9.0.1604347noneTest
9.0.1610349heiman_keyfob, heiman_sirenAggregateError
9.0.1611348heiman_keyfobAggregateError
9.0.1612348heiman_sirenAggregateError
9.0.1613349presence_radar_aoyan_ay204t, water_leak_aoyan_ay222zAggregateError
9.0.1614348presence_radar_aoyan_ay204tAggregateError
9.0.1615347noneTest
9.0.1616348water_leak_aoyan_ay222zAggregateError
9.0.1617350blitzwolf, sauna, siren_moesAggregateError
9.0.1618348blitzwolf, saunaAggregateError
9.0.1620347blitzwolfTest
9.0.1621347sauna (blitzwolf held again by 1ccc123b7b)Test
9.0.1622348siren_moes_mg_bjq002AggregateError

This is the boundary measured in the current period, not an assumed constant: master shipped 446 drivers to Test on 2026-10-10 (ATHOM_NEW_DRIVER_REJECTION_2026-10-11.md), so the server-side limit, if it is one, changed around the 21/10 incident or depends on something that grows with the driver count. Athom does not document it and was not contacted.

3. Field-by-field comparison (source app.json, master dae8d0be77)

driverresult aloneclasscapscapOptssettings (energy_*)driver flow cardspair viewslearnmodebatteriesnamesmfr x pidfiles
heiman_keyfobrefused (348)other101 (0)0defaultyesCR2032en/fr/nl/de2x17
heiman_sirenrefused (348)other211 (0)0defaultyesOTHERen/fr/nl/de3x27
presence_radar_aoyan_ay204trefused (348)sensor4455 (0)0list>select_driver>addyes-en/fr/nl/de1x19
water_leak_aoyan_ay222zrefused (348)sensor4411 (0)0list>select_driver>addyesCR2032/CR2450/AAAen/fr/nl/de2x110
siren_moes_mg_bjq002refused (348)other314 (0)0list>select_driver>addyes-en/fr/nl/de2x110
water_leak_blitzwolf_bw_is9accepted (347)sensor4411 (0)0list>select_driver>addyesCR2032/CR2450/AAAen/fr/nl/de3x110
sauna_thermostat_ae5503accepted (347)thermostat427 (0)0defaultyes-en/fr/nl/de2x18

No column separates the refused rows from the accepted rows. Also checked and not discriminating:

4. Consequence for the P3095 bisect

While the base payload sits at 347, any released never-published driver brings the upload to 348 and gets refused, so the bisect splits every group down to single ids and records each one as "isolated". The current group of six (353 drivers, run 43706691200) is expected to follow the same path. The five "isolated" ids should be read as "refused at 348", not as defective drivers. Their hold entries stay as they are (they keep the upload on the accepted set); no couple moves.

Ways forward, each needing a decision before any upload:

  1. Release a held driver only together with an exact-couple fold that keeps the payload at 347 (fold its couples into an existing published driver, as done for SPI and WHD02 in October).
  2. A one-off diagnostic swap at a constant 347 (release one isolated id while another never-published id is held) would test the count reading directly; 9.0.1621 already did one such swap and passed.
  3. Pause the bisect: further singles at 348 add no information.

← Knowledge base index · source