C8 Issues with Adding and Controlling Sengled Devices

[anthony4]

TLDR: New to C8 Sengled Bulbs not joining and Zigbee Radio keeps going offline until I reboot the hub. Sengled bulbs joined to c7 and migrated to C8 function fine. Same make/model.

I haven't had to pair anything since migrating from my c7, but I have 3 Sengled Element Color Plus Bulbs that I have just tried to pair. I was able to get the three of them to pair when I switched channels from 20 to 26, but they were unresponsive after pairing. I was also unable to get them to repair after removing them or factory resetting them multiple times. Brand new out of box. Placed them within 1 foot of the Hubitat.

Now I had an old, bad sylvannia bulb laying around. I was able to get that in and controllable without issue.

Went to the C-8 hoping that my zigbee light performance would improve. I did see some improvement, specifically with my smaller groups of 3-5 bulbs, but my larger groups made of nested groups that ultimately include ~30-40 bulbs total never really had 100% successful execution

Also worth noting, but not sure if expected behavior. Once the bulbs were "successfully joined" but not controllable, nothing with their ID appeared in the Zigbee logs when pressing Configure, On or Off.

Hub Info:
C-8
Platform 2.3.5.125
Running on wired ethernet
Zigbee Radio Channel:26 (originally 20 on 4/16/23)

Troubleshooting thus far:
Zigbee Power (have adjusted from lowest (4) to maximum
Performed a soft reset (no change)
Reboot Radio
Rebuild network (multiple)
Reboot Hubitat (multiple)
Updated Zigbee Channel
Changed device driver to legacy and advanced RGBCCT

My Setup Details
-Repeaters
Sonoff USB Repeaters (6)

-Power Outlets / Repeaters
Ikea Tradfri Outlets (serving primarily as Repeaters - 15)

-Motion Detectors (Battery)
Bosch ZPR1-WP13 Motion Sensors (4)

-Contact Sensors
Visonic Contact Sensor (1)
Sengled Contact Sensor (1)

-Bulbs / Lights
Sengled Element A19 Color Plus (11)
Sengled Element E12 Color Plus (4)
Sengled Element Plus (2)
Sengled LED strip (1)
Sengled Z01 A19 (1)
Gledopto RGBCCT 7W Garden Light (1)
Sylvania / Lightify LEDvance Bulb (9)
Ecosmart A19 CT Bulbs (13)
Ikea Tradfri E12 white bulbs (4)
Ikea Tradfri LED Driver (2)

Running Unifi backend. Access Points (5) are located on floors above hubitat with 2.4 Ghz transmit power set to low and channels used are 3, 6, 1, 11

[anthony4]

After I changed my channel to 25, I could pair the sengleds immediately, but I got the below error after about 2 minutes paired. I can not control the lights still, but they are showing up in Zigbee Logs...

dev:29002023-04-17 01:36:52.613 AMwarnskipped:[raw:catchall: 0000 0002 00 00 0040 00 63F1 00 00 0000 00 00 890000, profileId:0000, clusterId:0002, clusterInt:2, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:63F1, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[89, 00, 00]]

dev:29002023-04-17 01:36:52.610 AMdebugdescMap:[raw:catchall: 0000 0002 00 00 0040 00 63F1 00 00 0000 00 00 890000, profileId:0000, clusterId:0002, clusterInt:2, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:63F1, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[89, 00, 00]]

dev:29002023-04-17 01:36:52.516 AMdebugdescMap:[raw:catchall: 0104 0004 01 01 0040 00 63F1 01 00 0000 02 01 FF00, profileId:0104, clusterId:0004, clusterInt:4, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:63F1, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[FF, 00]]

dev:29002023-04-17 01:36:49.153 AMdebugdescMap:[raw:catchall: 0000 0013 00 00 0040 00 63F1 00 00 0000 00 00 88F16324F417001418CEB08C, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:63F1, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[88, F1, 63, 24, F4, 17, 00, 14, 18, CE, B0, 8C]]

dev:29002023-04-17 01:36:27.800 AMwarnskipped:[raw:catchall: 0000 0002 00 00 0040 00 10E6 00 00 0000 00 00 870000, profileId:0000, clusterId:0002, clusterInt:2, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:10E6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[87, 00, 00]]

dev:29002023-04-17 01:36:27.798 AMdebugdescMap:[raw:catchall: 0000 0002 00 00 0040 00 10E6 00 00 0000 00 00 870000, profileId:0000, clusterId:0002, clusterInt:2, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:10E6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[87, 00, 00]]

dev:29002023-04-17 01:36:27.628 AMdebugdescMap:[raw:catchall: 0104 0004 01 01 0040 00 10E6 01 00 0000 02 01 FF00, profileId:0104, clusterId:0004, clusterInt:4, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:10E6, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[FF, 00]]

dev:29002023-04-17 01:36:24.309 AMdebugdescMap:[raw:catchall: 0000 0013 00 00 0040 00 10E6 00 00 0000 00 00 86E61024F417001418CEB08C, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:10E6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[86, E6, 10, 24, F4, 17, 00, 14, 18, CE, B0, 8C]]

dev:29002023-04-17 01:36:24.135 AMdebugsetLevel(0, 0)

dev:29002023-04-17 01:36:24.133 AMdebugsetLevel(0)

dev:29002023-04-17 01:36:24.131 AMdebugoff()

dev:29002023-04-17 01:36:23.546 AMdebugsetLevel(0, 0)

dev:29002023-04-17 01:36:23.545 AMdebugsetLevel(0)

dev:29002023-04-17 01:36:23.543 AMdebugoff()

dev:29002023-04-17 01:36:21.123 AMdebugsetLevel(0, 0)

dev:29002023-04-17 01:36:21.121 AMdebugsetLevel(0)

dev:29002023-04-17 01:36:21.119 AMdebugoff()

[danabw]

What driver(s) are you using with the Sengled bulbs? Did you select the driver, or was is assigned by the hub?

[anthony4]

I've used a combination of the default element color plus, the legacy one, and the advanced RGB CCT. What gets me is that there is no activity in the zigbee log when I trigger an action. Additionally, all other bulbs of this make and model are running the default driver without any issue

[anthony4]

Another thing to note on this, My Zigbee Radio keeps failing and/or crashing. It is up for a couple of days, then all of a sudden I can't control any Zigbee devices. I log onto the Hubitat and find that the Radio is stuck on Initializing / Initialising. I try to rebuild, reboot the radio from the Hubitat, nothing restores it. The logs show that it flipps between offline and online a couple of times before I have logged on to troubleshoot. Only thing that restores the radio to functional is a software initiated reboot of the entire device. This has happened 3-4 times to me over the last 2 weeks. It has reoccurred even after doing a soft reset.

[FriedCheese2006]

I would stop using the rebuild option. Do you have "rebuild on reboot" enabled? If so, turn that off. Either way, shut the hub down without the rebuild and remove power for about 15 minutes. Boot it back up and see if that made a difference. If not, try re-pairing the repeaters.

[anthony4]

Repair the repeaters Even if they're responsive to commands and requests?

I have noticed some feedback on the rebuild on reboot. I did turn that off, but I have not done a shutdown with a cold start. Will try that out today.

[FriedCheese2006]

Yes to the repeaters. With my issue, devices were still responding through them and they were still checking in, but many devices dropped off and would not pair through the repeaters.

[danabw]

The recommended sequence if you use the Rebuild option is:

1. Reboot the hub (full shut down/restart is fine)
2. Reboot the Zigbee radio - this button:
   

Then continue...

[anthony4]

came home to an offline zigbee radio again. After rebooting the hub, I have rebooted the radio as suggested. Will see if it fails again.

[anthony4]

zigbee is failing on a daily basis. Hubitat support has weighed in and says this is a rare occurrence for the C8's and is likely related to custom drivers on my implementation. They directed me to my error logs. Thing is, no errors from a single Zigbee device. All are LAN connected devices/apps.

Out of 165 errors in a 10 hour period, 154 were from an implementation of the Orbit Bhyve Controller package out of Hubitat Package Manager forked from Kurtsanders by dcmeglio (GitHub - dcmeglio/hubitat-orbitbhyve: Provides integration with a Orbit™ Bhyve Timer and SmartThings)

I have uninstalled the app, will see if maybe it was causing the OS to fail maybe? I can't believe that this few errors would cause the OS to kill a zigbee radio, especially when the setup was stable on the C7, but hey, who knows.

[anthony4]

Interestingly, all of my zigbee devices are running on built in drivers.

My Setup Details
-Repeaters
Sonoff USB Repeaters (6)	Ikea TRADFRI Signal Repeater
-Power Outlets / Repeaters
Ikea Tradfri Outlets (serving primarily as Repeaters - 15)	Ikea TRADFRI Control Outlet
-Motion Detectors (Battery)
Bosch ZPR1-WP13 Motion Sensors (4)	Bosch Motion Detector
-Contact Sensors
Visonic Contact Sensor (1)	Generic Zigbee Contact Sensor
Sengled Contact Sensor (1)	Generic Zigbee Contact Sensor (no temp)
-Bulbs / Lights
Sengled Element A19 Color Plus (11)	Sengled Element Color Plus
Sengled Element E12 Color Plus (4)	Sengled Element Color Plus
Sengled Element Plus (2)	Sengled Element Plus
Sengled LED strip (1)	Sengled Element Color Plus
Sengled Z01 A19 (1)	Sengled Element Plus
Gledopto RGBCCT 7W Garden Light (1)	Advanced Zigbee RGBW Bulb
Sylvania / Lightify LEDvance Bulb (9)	Generic Zigbee Bulb
Ecosmart A19 CT Bulbs (13)	Advanced Zigbee CT Bulb
Ikea Tradfri E12 white bulbs (4)	Generic Zigbee Bulb
Ikea Tradfri LED Driver (2)	Advanced Zigbee Bulb

[anthony4]

There may be something to the bhyve app removal. The bulb I could not keep running more than a minute is now working 5 minutes later...

[anthony4]

was able to pair 2 more of them and join them to a group and keep them paired. Will update tomorrow if they stay online, then move to final location.

[anthony4]

So now my hub is having zigbee fail immediately after rebooting. 3 failures today. Going backwards.

[Ken_Fraleigh]

I am also seeing the 8 second Zigbee offline/online events, but not seeing any major consequences from it. Are you rebooting when it happens? I personally would not do that.

[anthony4]

Previously, when offline, I could not control zigbee devices. Now, the reboots are becoming less frequent, every 30 minutes, so I have not been able to catch and offline event and see if there was an effect.

[Ken_Fraleigh]

@anthony4

every 30 minutes

If you are having zigbee offline events every 30 minutes, have you shared this info with @gopher.ny ? I’m only seeing this happen every couple days now (currently it hasn’t happened since 4/25).

[anthony4]

Support replaced my hub at mine assistance. So far I've just moved over my zigbee lighting, with no reboot issues. Continuing to move over apps and devices slowly to see if something breaks the hub. Support felt that the reboot issue was being caused by an app or device.