@Mariano_Colmenarejo, All seems to be fine now as I checked my running the colour changing mode for 5 min but no idea what happened yesterday when I ran the colour changing mode to 30 min.
I also wanted to turn on the bulb and start the color changing mode straightaway but then realised that I need to write one routine to set the colour changing mode to active first and then another routine to turn on the bulb.
It works, but I cant get a 2700K color that works right. It looks totally blue when I use the driver slider to and drag it to 2700. Do I have to do a custom Hue and Saturation too? If so, what are people using for soft white? Left side off this image is the color produced when using the slider to 2700K.
Hi @Mariano_Colmenarejo, I was using this driver with my GLEDOPTO LED controller. It was working fine. But yesterday I was not able to change colors using the app. So I removed the device and added it back on. I had to re-install the driver but now I donβt see any options to change the colors. All the options are new which look very different. Can you please help with this?
@Mariano_Colmenarejo, Just checking if this driver will support this Neon strip (link below) in case someone else has requested this or something like this before?
@Mariano_Colmenarejo, I have been using his driver for my Zigbee bulbs and it turns on when the door is opened and turns off when the door is closed. I have noticed twice now that the bulb does not turn off when the door is closed though it has worked perfectly in the last few months. Now itβs working but I had to take the bulb off and put it back in for it to start working normally. Previously when the bulb did not turn off, I looked at the app and the status was βoffβ and then I tried to turn it back on but was not able to as it threw a server or network error so I had to take the bulb out and put it back in after which it started working. Any advice what could have gone wrong? All other bulbs are working normally.
The driver hasnβt changed in a long time and so I donβt think itβs the driverβs fault.
What has changed is the hub firmware to 53.19 and I had a similar problem with 3 devices, smoke sensor and 2 remote controls.
I sent the hub logs to @nayelyz and the smartthings team analyzed them.
The conclusion was that the 3 devices had a common device as a zigbee route to the hub.
This device did a rejoint and changed ID and the 3 devices that werenβt working were left orphaned, with no route to connect to the hub.
I had to remove the battery and reinstall it, so that they would relink via a new route to the hub.
The route should have been redone by itself, but after more than a day it didnβt happen.
maybe the new zigbee stack of firmware 53.19 doesnβt work correctly in these cases. It hasnβt happened to me again since the beginning of July.
I donβt know if this is your case, but it seems similar to me.
Hello,
In case anyone is interested, I have added the RGBW Bulb LEDVANCE, Classic 60 E27 Multicolor, it works very well and is cheap 13 Eur on Amazon.
This bulb supports the adjustment of the settings after a power loss, with the options:
Turn Off
Turn On
Restore Previous State
When you choose Turn On or Restore Previous State, the bulb turns on with the same values ββof level, color Temperature and color used before the power outage.
Transition times for off, level, color temperature commands works fine too
These are the fingerprints of the bulb.
- id: "LEDVANCE/A60 RGBW T"
deviceLabel: LEDVANCE Classis A60 RGBW
manufacturer: LEDVANCE
model: A60 RGBW T
deviceProfileName: rgbw-level-colortemp-2000-6500