One of the nice things about Sengled bulbs is that they emit a kind of "last gasp" when they lose power, so that their state (...usually...) gets set to off when they lose power. That's particularly nice for lamps where someone might occasionally turn off the lamp instead of the bulb. When you restore power, though, they seem to do this strange little dance where they briefly illuminate at a low dimness, then turn back off. Worse, the events they emit during this flicker aren't always in consistent order, so the state can be inconsistent then.
This app does something utterly trivial: Whenever the target device sends that it's on, it responds by sending an on() command. 99.9% of the time, that's pointless and ignored. But if the message is because of that power-on flicker, receiving that command causes the bulb to go ahead and fully turn on, which was probably the intention of the person turning on the lamp.
So, if you have a Room Lighting set up to turn on at something less than 100%, will that also trigger it up to 100% then too?
I have bulbs that do the same thing after a power outage. I just hit the "on" button on the button controller I use and that usually sorts it. But, it would be nice to not have to do that. My issue is that at certain times, I don't want 100%. So, it may cause me more issues than it solves.
It doesn't send any level commands, just the on() command. What the bulb does with that is probably implementation-dependant. My bulbs seem to go back to what they were set to previously, but I suspect you'd just need to try it and see.
(Likely the same as going to the device page and clicking the On button, though it will respond a lot faster than you can click. And of course, you can look in logs to see whether your bulb is sending a switch.on event.)
