incapacitater:
So I’ve encountered some weird behavior using the above devicetype/bulb and have no idea how to fix it. If I have it set to turn on with motion, that works just fine. However, if I have it set to turn off after motion stops, regardless of delay or no delay, it won’t even turn on. As soon as I remove the turning off when motion stops, it turns on just fine. I’d like it to do both, otherwise it’s kind of useless to me.
By any chance are you doing this with a Hello Home Action? The default time range for motion is bizarre, I had several unexpected results until I figured out that was the reason. Also, there’s an undocumented “feature”: a HHA won’t run at all if you’re already in the mode that HHA changes to. Both are discussed here:
Re: “When Things Start Happening” and “When Things Quiet Down” specifically: these two criteria require that you change mode when executing the action. Going further, these conditions are currently coded to not execute the phrase if the system is already in the mode being changed to by the phrase. Confusing enough? @Tyler is right, It’s been like this since it was introduced as an option, so I suspect the mode change was in your configuration previously. Not sure how else you could have done it. Off the top of my head, I don’t think you can set up the particular use case you’re looking for without…
If you’re not using a Hello Home Action, these don’t apply,but just in case…