I am having many issues with my ZHA/Zigbee network using a Nortek stick and all Sengled devices. The issues range from lag to turn on/off, color swapping without being set, and even some light groups coming on without an automation (0430 this morning in the bedroom).
I would like to have all lights be Zigbee in my house and controlled via ZWave switches so they are never actually powered off and are controlled through adaptive lighting such that they are the right color and brightness throughout the day.
Currently I have 83 ZHA devices, a Nortek stick (coordinator), 10x Sengled E1C-NB7’s (routers), 23x Sengled E21-N1EA bulbs, and 49x E21-N1E floods. This is all via a Raspberry Pi. At one point I thought it was the SD card so I migrated to a brand new A2 rated card.
I started with a handful of lights in Light Groups but realized that flooded the network so I converted to ZHA groups which allows lights to be in sync for turn off/on. I updated my Nortek stick to the latest recommended firmware, and re-paired all of the coordinators afterward. I then shut down my Pi and forced all devices to re-compute routes.
Currently my network map looks like:
As a benchmark I am trying to toggle all lights on and then off and looking for near real time responsiveness. What I observe is a handful of groups turn on, some toggle on but then retoggle off within seconds to minutes, re-toggling causes failures such as EZSP not running. I have seen issues with Adaptive lighting where states are poorly synced and it causes a turned off light to turn back on and that is being fixed in v2 however what I really need is my lights to be responsive purely under ZHA.
I am sort of stuck with where to go from this point and have turned on pertinent logging. Here are some of the errors I see:
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for None None (00:0d:6f:00:17:36:c5:0a)
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {11, 13} {1}
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Found custom device replacement for 00:0d:6f:00:17:36:c5:0a: <class 'bellows.zigbee.application.EZSPCoordinator'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for sengled E12-N1E (b0:ce:18:14:03:53:16:bb)
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
2022-02-13 08:35:06 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {11, 13} {1}
2022-02-13 08:37:30 DEBUG (MainThread) [zigpy.device] [0x65e1] Delivery error for seq # 0x6f, on endpoint id 1 cluster 0x0702: message send failure
2022-02-13 08:37:30 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x65E1:1:0x0702]: failed to get attributes '['instantaneous_demand', 'current_summ_delivered', 'status']' on 'smartenergy_metering' cluster: [0x65e1:1:0x0702]: Message send failure
2022-02-13 08:37:30 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x65E1:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('[0x65e1:1:0x0702]: Message send failure'), DeliveryError('[0x65e1:1:0x0702]: Message send failure'), DeliveryError('[0x65e1:1:0x0702]: Message send failure'), DeliveryError('[0x65e1:1:0x0702]: Message send failure')]
Failed to call service light.turn_on
2022-02-13 10:38:21 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendMulticast: (EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=13, sequence=63), 0, 3, 64, b'\x01?\x01')
2022-02-13 10:38:21 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendMulticast: (EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=9, sequence=65), 0, 3, 66, b'\x01A\x01')
2022-02-13 10:38:21 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendMulticast: (EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=14, sequence=67), 0, 3, 68, b'\x01C\x01')
2022-02-13 10:38:21 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendMulticast: (EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=15, sequence=69), 0, 3, 70, b'\x01E\x01')
2022-02-13 10:38:23 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0xA365:1:0x0300]: failed to get attributes '['color_mode', 'color_temperature', 'current_x', 'current_y', 'color_loop_active']' on 'light_color' cluster:
2022-02-13 10:38:23 DEBUG (MainThread) [bellows.ezsp.protocol] Send command setExtendedTimeout: (b0:ce:18:14:03:52:e5:be, True)
2022-02-13 10:38:23 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendMulticast: (EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=16, sequence=71), 0, 3, 72, b'\x01G\x01')
2022-02-13 10:38:23 DEBUG (MainThread) [bellows.ezsp.protocol] Send command readCounters: ()
2022-02-13 10:38:23 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendMulticast: (EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=17, sequence=73), 0, 3, 74, b'\x01I\x01')
Its almost like the broadcast floods the network and takes forever to process then the controller times out before zigbee devices respond. Very hard to explain. I have not yet updated the firmware on the Sengled devices because I haven’t yet figured out how to do it without tearing down the network and pairing it all to a Sengled hub. Any thoughts on how to further troubleshoot would be very welcomed.
THanks!