My problem isn’t new, but I am wondering if it’s a driver issue. I have noticed this more as my Osram bulbs have been replaced under warranty with the Sylvania ones made by Ledvance. The Osram bulbs work correctly with the driver. If you send. Setlevel command of 50 and turn the light off and on, it will come back on at 50. If you do the same thing with the newer bulbs it will set to 50, but when you turn it off and back on the device page will still say 50, but it won’t be at 50. It will only come on to whatever level it was last ramped up or down to, and if you refresh the device, the actual level it is at will then appear. I am wondering if @mike.maxwell has one of these bulbs and can help me with this. It still has the same model number, but has Sylvania Smart+ written on the bulb instead of Osram. I’m seeing this with the A19 RGBW, RT5/6 RGBW, and BR30 RGBW bulbs. They all are on the same firmware of 0102428. I also am having an issue with ramping up the lights. The problem is, if they are in a group of bulbs and you ramp them up with a button controller, they will start flashing on and off if you hold down the button to long, which is sometimes necessary to get all of them to 100. A couple times the lights flashed like this and reset themselves, flashing red, green, blue, and I had to rediscover them. I don’t know if these are driver related issues. I know these lights, unlike the Osrams, store there state in memory, so if you cut power to them, they come on to their previous level, which is usually 1% because I can only ramp down 
I hope these are issues that can be resolved with a different driver because I am really happy with the light they put out. The CT range is 1500 to 7000, which makes them great for circadian lighting, and the colors are really nice since the firmware updates.
Edit: fyi: I just tried the Sengled color plus driver and it seems to solve the issues with them. I can even prestage the level as an added bonus. I’m hoping that this won’t harm the bulbs.
Update: this driver works and I can prestage level and ct which is nice (would be nicer if there was an app to do that..hint). I can also send a setlevel to the device and it will come on at that level, unlike the generic rgbw drivers. The problem is with group messaging. It is a mess. I’m not going to delve into how messy, since this driver is for Sengled, but it ain’t great. I have a 9 bulb fixture that turns on and off very smooth, and transitions between levels and CT beautifully with the generic drivers. I’m hoping @mike.maxwell, or @bravenel can help. I have 50 of these bulbs in one to 9 bulb fixtures and obviously willing to be a guinea pig.
I haven't tackled the osram drivers yet, it will be a while before I do.
What physical button controller are you using that's resetting the bulbs?, in any event this issue isn't the driver.
Using the sengled driver?, a command is a command is a command, the device will accept it or it won't, but it won't hurt it.
Hue dimmer and Sylvania 2 button with set up as button controllers in RM. I think it happens when it gets the ramp up command when it’s already at 100%.
It seems that the setlevel for turning on/off a group works better than using on/off and smoothed out the group messaging issue I was having. I tried transitioning the group of 9 Bulbs through colors and color temperatures again and it is working well now, and actually much faster than with the generic driver. It was very out of sync initially, but seems fine a few hours later. So far this driver is working better than the generic one for my setup at least.
If you do get time to work on this, I’ll be happy to test it. Let me know.
If that's the case, it's an issue with the firmware on the bulb...
Thanks for letting me know. I’ll try to avoid doing that. That may explain why it doesn’t happen as often with the current firmware. It seems to only happen now with the 9 bulb group. Maybe it’s actually a feature 
BTW, these lights are so much faster now with the Sengled driver and using setlevel for on and off (groups), and the color transitions as well. Very happy with this. Even though it’s not perfect, it’s much better than the generic driver.
I discovered that the Sengled Element plus drivers fix the Osram CT bulbs not reporting back state on the device page. I had a couple of these that always seemed to be showing as "on" and figured I would try this out. It also seems that it has fixed the issues with state reporting for the rgbw bulbs as well. It seems that it is only the groups that I'm having any issue with as the individual lights work perfectly when commands are issued straight to the bulb. The main problem is if I send a setlevel to a zigbee group of bulbs and then turn off the group, I have to turn it back on with a setlevel for it to come back on at the previous level. If I turn it back on with just an on command (Alexa turn on the lights), then the lights come on to the level the individual bulbs were at previously. If I dim up or down the bulbs, since they are individually being dimmed then their level gets saved and this isn't an issue. So, I can just take care of level in the background with CT, but thought you might want to know.
Thanks for this. I narrowed it down to just a few bulbs that were still doing this and it turns out that I must have missed updating them to the latest firmware. They were still on 0102301 and when I updated them to 0102428 the issue ceased. They were in the group of 9 bulbs, which is now working perfect.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
