Simple Automation Rule Firing when restricted

Hi all,
Made a rule to keep my son's closet light off at night. Its a sengled smart bulb intended to function as a regular light bulb with dumb switch, except at night, when the hub senses it come online, it should turn it off at the bulb, causing it to flash on when power is restored, then turn off about a half a second later.
This works, but the first time every day that it is turned on outside of the rules hours, it also turns itself off. Today that was at 11, well outside of the 6AM end time for the rule.

If you bring up the Device page for the bulb what does the Events tab show at 11?

Thanks for the reply.
Here's the events

Since it's a simple rule delete it and set it up again maybe something got messed up that isn't showing up. :man_shrugging:

Occasionally when I mess around with rules, usually rule machine, they will look okay but do weird things. When I delete and set them back up then everything is fine.

Worth a quick try since it's a short rule.

What driver are you using? If it's not the sengled driver check to see if there is a setting in the driver that sets the bulb to off after a power failure (turning the switch off).

Not sure if it is related, but it is never a good idea to control a smart bulb with a dumb switch. It may actually be a bit related as it is messing with the mesh every time it is powered off and on.

Get a switch cover for the dumb switch and put a smart button or switch (like a hue) next to it. Then leave the power to the bulb on all the time.

2 Likes

Lots of activity, thank you all.
I am using the built in sengled driver. It does not have a "state after power failure" setting, but before any rules it would resume in the "on" state, regardless of the previous state. I don't think this is it. I can look for a different driver that may have more features.
I will try deleting and recreating the rule. Of note: I tried to replicate the issue by changing the exclude times, but it seems that changing the exclude times around the current time (as opposed to the current time naturally moving out of the exclude time) does not cause the issue. Also of note, I noticed in the device settings that under "in use by" was a half created rule with no trigger that I accidently made. I deleted that. Maybe that will fix it.
Regarding mesh issues, I did specifically research that this bulb will participate as an end device only, not a forwarding member of the mesh, but yes, cheaper devices will absolutely create issues with your mesh if they are not so configured and are constantly losing power. I did this research before I bought it and can't easily find it again, so I can't cite it, sorry.

Thanks all,
Will update tomorrow when it exits the exclude time again.

1 Like

The sengled bulbs I just purchased actually advertise on the box that you can use them as dumb bulbs and they won't bother the mesh because sengled doesn't repeat traffic on the mesh.

UPDATE: I see I just repeated what the OP said above. Oh well....

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.