Just got a new CREE bulb and installed it using my iPhone. Turns on but doesn’t turn off fully (goes to about 10% brightness). So I assumed it was faulty and got another one; same problem. All my other CREE bulbs installed a while back work fine.
Looked in the IDE. Says Type=placeholder, No Zigbee ID.
Is this to be expected with the transition to Edge? I can return the bulbs but it may not be a CREE problem but a SmartThings one. If the latter, the transition is being handled in a piss-poor manner.
I installed the Zigbee Light Multifunctional Mc driver and rebooted the hub. Still no luck. I can change the brightness but the bulb will not go below about 10% illumination even when told to switch off.
I haven’t done anything fancy. Before I used the SmartThings app to install the bulbs and they work just fine. Now the two that I’ve tried say in the IDE “placeholder” for Type and there is a blank for the Zigbee Id. All previous bulbs say “Cree Bulb” for Type and have a Zigbee Id. Changing “placeholder” to “Cree Bulb” has no effect.
All the bulbs are the same make and model. The only difference is that I installed the earlier ones (8 or so) months ago and that went fine. The two I installed last week don’t work properly. Either I have two identically faulty bulbs (unlikely) or something has changed in the SmartThings installation. The older bulbs say “Cree Bulb” in the IDE Type, the new ones say “placeholder”.
I have a few really old Cree Smartbulbs that are working fine after I re-added to the Hub a month or so ago. They obviously where installed using the SmartThings Edge production driver since I see driver option on the Cree device’s menu.
Looking at the production Edge Zigbee Switch fingerprints file, I only see one entry for a Cree smartbulb so I presume that my Cree smartbulbs are using it since they are A-19 60W smartlights, but can’t say for sure.
Thanks for the tag, @Mariano_Colmenarejo.
Sorry for the delay, @bluebanana
So, currently, which driver is your device using (The one from SmartThings or Mariano’s)?
If it’s the one from ST, it makes sense it is picked by default as the device’s fingerprint is included in the production version.
In order to see what is happening we need to look at the driver’s logs. To do so, please help us by installing the CLI and running the command below:
You need to replace x.x.x.x with the actual Hub’s IP address which you can find in the IDE or your router’s configuration.
Then, execute the off command from the app to see the messages exchange between the Hub an the device.
Then, you can share those logs here, over DM or to email@example.com. Thanks!
I’m seeing different issues with the Cree bulbs with the stock driver, which registers as a Zigbee switch. (Using the 11/15/22 version.)
The dimmer slider is not working properly. Turn the bulb on at 100% reported. Open the device card and move the slider from 100% to 80% and the illumination stays the same. Back to 100%, no change. Down to 25% and it will dim. Back to 100% but the brightness doesn’t change.
Also, you can use the slider to set from 100% to 50% and close the card. When you re-open it, the brightness is still set at 100%.
So just general wonkiness with the slider setting the percentage of illumination.