I've got 2 of these bulbs already working, but this third one seems to be acting up. I run discovery and it actually finds the bulb multiple times. I've tried factory resetting the bulb and adding and removing it from the hub.
For some reason, when it discovers these bulbs it just discovers as a "Device" and I have to manually change it to a zigbee rgbw light. This one for some reason after being discovered, it never gets any more info from the bulb itself. It discovers and adds, but it will not respond to any commands and there's never any info showing from it.
Yeah, looking at the box, its saying Zigbee 3.0. The odd thing is I bought 2 of them at the same time, they're the same model Zigbee 3.0. One worked fine, still originally added as a device instead of bulb, but I changed it to "Sengled Element Color Plus" custom driver and it worked. The data on that bulb is:
The other one is able to be discovered, but then it never gathers any info or can take any commands, I tried using the same sengled driver and the generic zigbee rgbw light driver. The data that shows on that one is:
It has not paired completely. I suggest resetting the bulb and pairing again close to the Hubitat. There is no need to delete the Hubitat device created already - the bulb will pair back as that device.
Alternatively, change the driver to the Sengled driver and click configure. That might do the trick. Definitely try this first
I've got it set to Sengled Element Color Plus as the type. I hit configure and I can see in the logs it shows a configure but nothing ever comes after it.
You can see it discovers multiple times. I've noticed that it works and can accept commands when the first time it discovers works. I was able to change the hue/level/saturation. Discovery was still running and each time it was "discovered" it would flash colors showing its been discovered. After discovery stops, it just stops working all together.
I just went through the same rigamarole with the same Sengled Element Color Plus bulb E21-N1EA. Same multiple pairings popping up at discovery, right from the get go.
I think I deleted it from HE once after "failure to behave" like you outlined. Then the second time I left it in HE, made sure the driver was the Sengled Element Color Plus (had tried Advanced RGBW too) then reset and re-paired the bulb. Repeated that two or so times and plenty of CONFIGURES. I was getting that CT color mode coming up unchangeable just as you showed.
On the third attempt it finally came in and started responding to color commands, I was hopping between drivers a couple times to see if that mattered. It operates as expected so far on the Sengled Element Color Plus driver.
So i think there are some quirky attitudes here at configuration time that some of these bulbs get into.
There just seems to be some funky things that can happen in the initial discovery/pairing of the odd bulb sometimes. Also, I've found not everything works using HE's Advanced RGBW driver, like I changed to that for the flash capability and then couldn't get color changes to work. Changed back to the Singled driver. Think i have seen elsewhere folk discussing which of these drivers worked best for them. Could be some nuance with the bulb, the configure success/failure, or firmware.
I think that's been my experience as well.. I just checked and 14 out 16 Sengled color bulbs are on the Sengled driver.. 2 of my office table lamp bulbs are on advanced and seem to work okay while a 3rd is the sengled driver which also seems to work. I wonder if I actually hit configure for those 2 don't remember.
also I just realized I have like 18 smart bulbs in production? When the heck did THAT happen?
Yeah, my unexpected nightmare is all the battery hungry devices that are the-engine-to-all-this-working now ruling a portion of my subconscious where I am afraid to leave them for too long.
I didn't have this concern with my battery device'd Visonic Alarm System...
