Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

Upstream daily, 2026-11-02

Previous run (01/11) was fine, so this is a normal incremental run.

Clones moved since 01/11: tuya-local dcb0d40→2931535 (lawn_mower stop action, Wi-Fi only, no Zigbee impact), Athom zigbee-clusters b859be7→2add8be, z2m docs a55fd7d→f2cc3d9b5 (zhc bump, new device pages, 32-bit deprecation notice), Tasmota 9107ce7→a470373. Unchanged: zhc c18c32d (npm 26.125.0 still latest), herdsman, ZHA quirks, deCONZ, Blakadder, tinytuya, localtuya, Johan, zigbee-OTA, SmartThings, Hubitat, ioBroker, Domoticz.

Coverage matrix (all sources)

branchabsentcompletewrong classpartialcompacted
master528→521680→6801→1161→1632208→2213
stable-v5547→546575→5769→9130→1292317→2318
bastien-home474→474630→6287→7142→1402325→2329

Gains come from the 01/11 work (P3190 iwn0gpzz to power_meter, P3191 wbhaespm to smart_breaker, xpq2rzhq now complete in presence_sensor_radar on all three branches, awepdiwi complete on stable and bastien via P3200) and from new TS0601 couples now present in source as universal_zigbee (HYT001ZB, APRM-04-005, 119710, SP107E, ZAS-01P, floor thermostat 0hhou4yj, ECD-ZB-REPEATER).

Lost to publish compaction (budget full, parked, not pinned)

The publish payload sits at the cap (master 15498/15500, bastien 15500/15500), so new pins pushed other couples out of the rebuilt payload. They are still in the source drivers. These couples went from complete to dropped since 01/11:

Pinning any of them needs freed budget (another P3057-style headroom step), since pins only displace other couples. Listed in data/leads/kb-compaction-losses-2026-11-02.json.

Lessons from upstream

Unknown commands

Nothing new. Issues #581/#584 are compaction losses handled by P3200; #559 and #550 are already answered. Mail diags were covered by the mails routine up to 01/11 23:10.

Forum

Covered by the GHA forum sweep, no new run needed here.

← Knowledge base index · source