I have 3 Sengled bulbs that have worked fine for the past 2 years or so. Recently, I noticed that one or more of the bulbs would not turn on or off via the automations that I have (all in Node-RED using MakerAPI). I also have the bulbs exposed to Apple Home via Homebridge.
Apple Home shows the bulb as being "on", but the bulbs are not actually on. HE logs show the bulbs being turned on but again, nothing is on. The bulbs can be turned on/off from Apple Home or HE device tab or using the physical switch on the lamp, so not sure what is going on.
The one thing that I can't figure out is why the bulb level is being set to "0%". That would explain why when the light comes on, it doesn't appear to be actually on but this is just a guess.
Any ideas on what may be going on? I noticed this in the past couple of days and there have been no changes to HE (Platform 2.3.9.200, C-8, Driver - Generic Zigbee Dimmer). Thanks for your help.
Switched the driver for the 3 bulbs to Sengled Element Classic. When I was changing the driver, I noticed that the "Device Name" was set to "Sengled Element Classic", so when I originally paired the bulb(s), it probably picked up that driver. Not sure how or why it got changed to "Generic Zigbee Dimmer", but I re-selected the driver you suggested.
I had a very similar issue with the same bulbs. They would not turn on with the on command in the UI but would turn off. The automations were working funky as well. I could switch drivers and get them to work but I liked the driver I was using better. What I found was the driver had the minimum level of 5%. The bulb somehow has gotten changed 1%. This had the controls out of sorts I guess because the unit didn't recognize what was going on. I changed the level back to above the 5%. Configured. Then set my level where I wanted it and they have worked correctly since without the bulb level changing mysteriously.
I am suspicious of how the level got changed and if I am right it has nothing to do with HE. I think someone hit the slider when turning them on in the favorites of the app.
How did you find this out? In my case, the "Level" attribute is set to 100% (from the device page) but somehow the device would set the level to 0% (from the logs). I don't use the slider in Apple Home and, as far as I know, no one at home does either.
I have been having these issues for a while. Both with Groups and Room Lighting.
I have had a few PMs with Mike and Gopher but I can't see any clear solutions.
I have cleared my issue in Groups by always sending a SetLevel first but in Room Lighting I found I can not have the same driver on 2 bulbs otherwise the RL commands don't work properly on both bulbs. I run 2 different supported driver, one for each bulb, everything works great.
I have tried all the supported drivers with no luck.
As with most of you I have run Sengleds for years independently without a single issue on any supported driver.
No sure where things went strange but defintely 6 months or more; all was stable before that.
I was just looking at the device page like I was betting my head against a wall and just happened to notice the level was at 1. I had clicked on several times without the switch status changing and it just hit me. That status isn't supposed to be 1.
Hmm - I don't use the built in apps (my automations are in Node-RED and use MakerAPI). After switching the driver, the lights did turn off automatically when they were supposed to, so and the level is still 100 on the device page
