Old or New Coordinator... ? Help!

Rofo · May 14, 2023, 7:11pm

HA release 2023.5.0 introduced a bug that supposedly only affected ‘older’ coordinators.
The bug caused certain zigbee devices to go offline earlier than they should:

github.com/zigpy/bellows

HUSBZB-1 config regression fix for Aqara devices

zigpy:dev ← puddly:puddly/husbzb1-config-fixes

opened 05:10AM - 12 May 23 UTC

puddly

+97 -24

#550 introduced a major regression for older coordinators. Below are the previou…s EZSP configurations: ```python v4 set CONFIG_ADDRESS_TABLE_SIZE = 16 v4 set CONFIG_APPLICATION_ZDO_FLAGS = 3 v4 set CONFIG_END_DEVICE_POLL_TIMEOUT = 60 v4 set CONFIG_END_DEVICE_POLL_TIMEOUT_SHIFT = 8 v4 set CONFIG_INDIRECT_TRANSMISSION_TIMEOUT = 7680 v4 set CONFIG_KEY_TABLE_SIZE = 4 v4 set CONFIG_MAX_END_DEVICE_CHILDREN = 32 v4 set CONFIG_MULTICAST_TABLE_SIZE = 16 v4 set CONFIG_PACKET_BUFFER_COUNT = 255 v4 set CONFIG_PAN_ID_CONFLICT_REPORT_THRESHOLD = 2 v4 set CONFIG_SECURITY_LEVEL = 5 v4 set CONFIG_SOURCE_ROUTE_TABLE_SIZE = 16 v4 set CONFIG_STACK_PROFILE = 2 v4 set CONFIG_SUPPORTED_NETWORKS = 1 v4 set CONFIG_TRUST_CENTER_ADDRESS_CACHE_SIZE = 2 v7 changed CONFIG_END_DEVICE_POLL_TIMEOUT = 8 (was 60) v7 changed CONFIG_KEY_TABLE_SIZE = 12 (was 4) v8 set CONFIG_TC_REJOINS_USING_WELL_KNOWN_KEY_TIMEOUT_S = 90 ``` EZSP v7 renamed `CONFIG_END_DEVICE_POLL_TIMEOUT_SHIFT` to `CONFIG_END_DEVICE_POLL_TIMEOUT` and changed the format. This unfortunately meant that the earlier PR made the new config backwards-incompatible with older coordinators (i.e. the HUSBZB-1) and that child devices that poll very infrequently (i.e. Aqara) will be aged out quickly by the coordinator. This only affected devices connected straight to the coordinator, not through an intermediate router. --- https://github.com/home-assistant/core/issues/92581

This has now been fixed in 2023.5.3 which is good news, but from what I can gather, my coordinator shouldn’t have been affected as its already running ezsp stack version 8. This is an extract from my ZHA debug info:

        "metadata": {
          "ezsp": {
            "manufacturer": "",
            "board": "",
            "version": "6.10.3.0 build 297",
            "stack_version": 8,
            "can_write_custom_eui64": true
          }

Is the wording in the bug fix just wrong and the problem is wider, or is there something else I should be investigating ?

I’m running a Sonoff Dongle-E (plus v2) as my coordinator. Firmware details etc are above.
If its affecting me, I curious as to why I dont hear more about the issues in the forum, as I believe that coordinator is not uncommon.

brad.trout · May 25, 2023, 8:14pm

I have a SkyConnect that is only a few months old, which also looks to be running the HUSBZB-1. I, too, am still experiencing issues on 2023.5.3 and am also surprised there is very little actual clarity around what is going on with this issue and when it might be fixed. VERY FRUSTRATING!

Rofo · May 26, 2023, 8:29am

I was initially confused because I misread this:

Thinking the HUSBZB-1 was a protocol, but its a physical device like this one on amazon:

All i can say is that since 2023.5.3 my ZHA network has been stable again. Did you have any issues prior to 2023.5.0 ? There are alot of threads about SkyConnect problems that pre-date this particular issue.

brad.trout · May 26, 2023, 9:38am

Thanks! I did have some SkyConnect issues previously but mostly got them resolved by replacing a few devices. This new issue all started since 2023.5.3. Oddly, for the first time ever, I upgraded from 4.6 to 2023.5.2 (skipping .0 and .1) because I was out of town. Then I upgraded to .3. I wonder if this had any impact?

brad.trout · May 28, 2023, 6:51pm

I just migrated back to Conbee II and everything is now working flawlessly again!