I have successfully used MC’s “Driver/work of art” to slow change the colour of a Sengled/Lightify A19 bulb…, but I am unable to reproduce the same effect on my GardenSpots… they are both listed in the driver fingerprint file… double checked using MC’s “thing” driver as well.
Admittedly, there are a lot of settings crammed into the controls… but I only can achieve immediate changes between colours…not the smooth transition that I know they are capable of from within the Lightify app… which still works of course… but I finally want them controlled with automations. And I have become used to their slow colour transitions for over three years now
Any and all help appreciated. I am using the same settings I used on the A19 bulb that achieved the slow colour changes.
PS - Now I wonder if there will ever a be the possibility to be able to “choose” the colours that are being transitioned…ie: themed for halloween or Christmas …MC ignore this PS… its kind of obnoxious considering the amazing amount of volunteer work you have already put into supporting, us, the SmartThings community. THANKYOU!
Thanks Mariano for putting all the work into your driver(s), I really appreciate it. You single-handedly made my move from DTH to Edge much less painful than I had anticipated!
About the pesky Gledopto bulb, it almost works perfectly now. I do see a few glitches still, but they are not “mission critical”:
When I switch on the bulb through the color or dimmer slider, it does not understand the status change in the app, and the on/off button there remains in “off”.
When I change the dimmer and then switch the bulb off, the bulb goes to the old setting for a split-second before actually turning off.
I will try to see if the “progressive on” works, and let you know. I will also test whether the new driver also works on the related Gledopto bulb that was in your driver’s fingerprints before (GL-B-008ZS), but had the same problems with the on/off switch as my GL-B-008Z bulb. I have a couple of those, too, but I haven’t moved them to edge drivers yet, so I didn’t notice the problem before (sorry).
Since you said that turning on with the level or color temperature worked well, I thought that I would also update the app
Try with this version
───────────────────────────────────────────────────
Name Zigbee Light Multifunction Mc
Version 2022-12-07T10:59:35.177118646
───────────────────────────────────────────────────
I tried it, and it is in fact much much better now; thanks for taking care of this. The app is now updated (although with a delay of one to two seconds) when the bulb is switched on with the dimmer setting. Strangely, I first tried with a dimmer value of 10 to not wake up the whole family and the bulb did not switch on. With higher dimmer settings it works. Also when trying to reduce the dimmer to 10 through an Alexa voice command the bulb switches off. Dimmer 20 and higher apparently work. That’s not critical for me, but I wanted to give feedback anyway.
Regarding the “progressive on”, I have tried it a few times and it seems to work. I haven’t used this in the past, so I did not know what exactly to expect (other than what the name says…). In my hands, yes, the progressive on works with this bulb, although it is not smooth but the brightness increases in noticable steps. If that’s how it is supposed to be, it works flawlessly. Is there anything in particular to check for?
That update delay in the app is normal in ZLL bulbs, since the command is sent, to ensure that the command has been executed, it waits 1 or 2 seconds to read the state of the device attribute and emit the event. This is also the case in the stock driver.
Non-ZLL bulbs, normally zigbee 3.0, the device sends the status after executing the command without needing to read the attribute and it is much faster.
The effect shown depends on the configuration you have in preferences, the difference between the level Start with the End and the Time to reach it.
The number of steps to increase to the End level is calculated with the entered Time and End level - Start level. The minimum increase that the app shows is 1%
The time range is between 6 sec and 45 minutes.
If you put a little time for a lot of level increase the effect will be staggered.
In these cases it is better to use preferences On-Off transition times ranging from 1sec to 10sec, as long as your device supports it.
Thanks Mariano for the clarifications. I didn’t know about the differences in the protocol between ZLL and Zigbee 3.0. That’s very informative indeed.
Regarding the progressive on, I will try with different times and level increases - I don’t need this setting for my bulbs at this time, but it is great to have the option and know how to use it best. I will also try out the on-off transition times to see if my bulb supports it.
Do you have an idea why often when I switch the bulb off (some time after changing the level), it comes on with the previous level for a split second before it switches off)?
Yes, I saw this and used it. But I feel it should be part of official documentation on Smartthings website and Samsung should provide software directly.
But no worries. I installed the driver and the strip works very well. Thank you!
Mario, thanks for all of the work. I recently purchased a PAUTIX COB LED Strip Light White CCT Tunable 3200LEDs,CRI90+ 16.4ft/5m Dimmable 2700K-6500K 24V LED Tape Lights Kit (3 wires → V+, WW & CW). It comes with a 24 volt power supply and controller/remote. However, I want to control it with my Smartthings system, so I purchased a GLEDOPTO GL-C-006P controller which you have already added a fingerprint for. I can get the controller to function, but it doesn’t seem to control the color as well as the supplied controller/remote because the voltage range for the GLEDOPTO controller is much narrower. For example, if I use the original controller/remote to command full “warm” the voltages are 21.6 volts for WW and 9.1 volts for CW channels and I get a very warm/orangy white, but with the GLEDOPTO controller using your version 6.0 driver they only go to 21.0 and 19.4 volts respectively and the resulting light is very blue. I’m trying to figure out if this is a driver issue or a problem with the GLEDOPTO controller. Any ideas?
I don’t know why that happens.
The driver only understands the color temperature that it sends to the device and displays the color temperature response set by the device.
How the device converts the color temperature in volts for the LEDs has nothing to do with the driver.
It can be the device or the strip itself.
When you set a color temperature with the remote control, what color temperature does the app show?
The GL-C-006P device is in the 2700k-6500k profile
