I was able to discover a Cree Connected bulb and it was setup as Generic Zigbee Bulb which is fine. However, it doesn't seem to be working. Not sure how to debug. I've tried to add two devices and both had issues. But I'm very patient so no worries.
Crees were the first things I added to my hub. I didn’t have any problems, but I did notice that they took a while to pass all of their information to the hub. After the confirmation flash from the bulb, I would wait about 30 seconds before saving.
Well something’s not right then, I have Cree bulbs that I used in development of this driver, they paired and configured within seconds the 5 or 6 times that I went through that process with them.
I don’t know what’s causing this. You might consider starting fresh. Delete the bulb from the hub, factory reset, and try discovery again.
To Reset a Cree Connected bulb to factory settings:
Turn ON the bulb.
Wait 2 seconds.
Turn OFF the bulb.
Wait 2 seconds.
Repeat steps 1-4 until the light blinks once to indicate it has been reset. This should happen after the third full ON-OFF cycle. In other words, it should blink the fourth time you turn ON the bulb.
Yes I did. I think … and I haven’t had time to confirm this yet, that for both my SmartSwitch and the Cree bulb I had to powerdown and restart the Hubitat in order for me to be able to control them. When I get a chance I will add a motion sensor I have and try to confirm that this action is what is making the new devices work. Or maybe I’ll try another Cree bulb.
I’ll post back when I have the time to do a little more.
Thanks for the follow up!!!
Has anyone experienced an issue with these when they go offline and continue to report as ON state? It would seem to make more sense that if they are offline to report as OFF since rules that look for the OFF state can them become frozen as the bulb is stuck in the on state as far as the rule machine is concerned.
Yup, any device that was on, then heads for the hills will still be reporting on whilst on holiday...
Well technically that's not true, the issue is that any device isn't going to report off if it can't reach the hub.
Over time here's what I discovered without offering any technical detail on why.
I personally believe the hub transmits better than it receives. This situation is seen in the world of radio receivers also. What happens in this case is that the hub can issue commands to the device and the device acts upon them, but the hub doesn't hear that acknowledgment and thus the status is incorrect. If I had any complaint coming from the ST hub is that I didn't have this issue as much on ST. The exact device that I have issues with (it's my furthest device) work okay with ST. And the hubs are in the same physical location.
I have other devices this occurs with also. Just not as often as my one light outside on the lamp post.
I do a crap ton of frame captures when writing zigbee drivers and ive not seen this unless an upstream router drops the frame...
If it's on the wire so to speak and destined for the hub the hub receives it.
Thanks Mike,
I have learned my lesson. Purchased a Sengled bulb (classic?) and it is superior to the Cree for only $8 (gotta love amazon same day shipments!) Lesson learned here. You get what you pay for. One note, I did find that setting the driver for a Cree to the Sengled driver that I can at least get the instant on and off and also forgo to stupid behavior of going on to 100% then dimming down to the desired value. That part makes me think it’s a function of the generic driver and not the bulb.