Any updates from the community on zigbee bulbs that can be set to NOT turn on automatically after power is restored using this driver? Thanks.
Added this ledvance rgbw bulb
I´m using many things from Gledopto:
- Led controllers: http://www.gledopto.com/h-col-435.html and http://www.gledopto.com/h-col-416.html
- Filament Bulbs: http://www.gledopto.com/h-col-387.html
- GU10 Lights: http://www.gledopto.com/h-col-402.html
- Triac AC Dimmer: http://www.gledopto.com/h-col-380.html
Working very well and maintaining last state when power is restored.
It seems LEDVANCE is not availible in canada. Any other suggestions? Thanks.
Have you tried with this driver and adjusting the settings of all transition times to between 1-5 seconds? 1 second transition fixed the issue I had with lack of dimming and color temperature control on some of my innr bulbs.
UPDATE: I don’t even have that setting. I should have stuck with Sengled bulbs.
I’ll give it a shot. Thank you.
Posting here but in no way suggesting this driver is the issue … I’m just looking for any guidance.
I am using this driver on multiple Osram/Sylvania LED strips. Operationally, everything seems to work well and always has. I do, however, get a temporary message pop up on the device page in the app (iOS) when I first open the device. I have seen this message many times before on different devices, but it usually corrects itself. In this case it is not. Furthermore, it does not show up on every one of the other Osrams using the same driver.
I also get this message on another, different device that is NOT using this driver. But I do see they both have the Level By External Steps feature. I am not sure if that’s relevant in any way.
Thoughts?
According the screenshot, In this case the reason could be, the capability Hue by external steps without value received.
It may be that the driver does not initialize it correctly with a value when the driver is initialized or the device is installed, I will look into that.
If you send it a value with a routine, the error should disappear.
Thank you. That resolved it.
I’ve been using this driver for a long while now (≈ 2 years) and for several different brands of Zigbee bulb devices. About 6-8 months ago, many (but not all) Zigbee devices started to become unresponsive - sometimes getting a “network” error or sometimes the command finally executes several minutes later. Sometimes commands work but most of the time they didn’t. I didn’t have much time to look into it, but I was trying basic troubleshooting like add/remove device, restart the hub, changing the Zigbee channel, disabling automations, but all to no avail. I just learned to deal with it until I finally had enough and submitted a ticket to Smartthings. They’ve been no help and I feel like I’m going in circles with them but then it all of a sudden hit me to check which driver these problem devices were using. Lo and behold they were all this driver - Zigbee Light Multifunction Mc. So to test my theory, I changed the driver back to the default Smartthings Zigbee switch and the device responds immediately. I change it back to Mariano’s, unresponsive. I try this with several devices all with the same result. So for my (and my wife’s) sanity, for now I am using the Smartthings Zigbee Switch driver.
So what gives? Has anyone else run into this issue? Is there anything I can do to “fix” it?
I have not had any problems using this driver on the 5 devices I use.
This is the latest version released.
Zigbee Light Multifunction Mc
bb1b3fd4-dcba-4d55-8d85-58ed7f1979fb
2024-12-08T09:45:01.460678797
The delays you describe seem more likely due to saturation of your zigbee network or the Hub due to memory limits or excess of messages to process.
The driver only processes and emits the messages that the hub sends to it and does not decide on the flow control priorities and resource use of the Hub
You can try to delete and reinstall the driver.
If it works fine with the stock driver, do not hesitate, use it.
Smartthings optimizes the Hub firmware resources for its stocks drivers and is implementing message handling flows directly through the firmware (On/Off, Level, ColorTemperature), without re-sending them to the driver handlers. Not all devices in stock drivers can use this, ZLL devices cannot use that function.
My driver cannot use that firmware function because the driver needs to control all the commands in custom handlers, to perform all the custom functions that the driver has.
If there are many devices on the network that use these resources from the Hub firmware, the drivers that need to handle the messages that the Hub has to re-send to them may be penalized somewhat in latency, but there would not be delays like the ones you mention.
I use mariano’s drivers in +10 devices without any problems.
Hello, could I get this driver for matter bulbs like philips wiz, too? I wanna use dimming fumction for my flicker free wiz, but I cannot find the driver for it…
Your Wiz bulbs will use the Stock “Matter Switch” Driver. You don’t need install any drivers, it will be automatically added if it is not already on your hub.
@Mariano_Colmenarejo , any way to modify the order of the device details, for exemple, send this fields to the end of the device screen and the level/hue controls first?
Hi,
Sorry, we are no longer allowed to choose the order in which the capabilities of a profile are displayed.
Only the first capability, which will be the one displayed on the tile, can be chosen, as long as it is one that they allow, for example battery cannot be chosen.
Now they choose in which order they are displayed and we have to obey.
why am I not at all surprised by this idiotic platform impossibility
I bought Aqara E1 3switch device.
Added to Samsung Smartthings as Zigbee Multi Switch and Child Mc:
I can see all 3 switches on ST:
But when I try to add a routine then it doesn’t let me choose from 3 switches. there is no selection at all. and when I test the routine it works but it doesn’t work after I save it and try by pressing the physical button.
help will be very appreciated.
Go into the settings for the Aqara relay and select “Create single device for Switch 2” and do the same for switch 3.
it worked! Thank you very much!