Automoli not turning light off if motion sensor unavailable

[thundergreen]

I just got kicked in my little ass because a light was burning 3 hours without turning off. I checked all motion entities configured for this automation and say F** on sensor became unavailable. Like this automoli did not turn off the light. Is it possible to handle unavailable motion sensor as Off state? Would save my ass :P

😒 Expected behavior
A clear and concise description of what you expected to happen.

Is it possible to handle unavailable motion sensor as Off state? Would save my ass :P

[benleb]

Hm that's not defined but should be, right! On is obviously a stupid idea but off seems a good choice.

Can anybody imagine a case where treating an unavailable sensor as off would be "bad" in some way? 🤔 Or has a third variant that would be cool? 😄

[oscfor]

I have seen the same happening with an illumination sensor.

[oscfor]

Hm that's not defined but should be, right! On is obviously a stupid idea but off seems a good choice.

Can anybody imagine a case where treating an unavailable sensor as off would be "bad" in some way? 🤔 Or has a third variant that would be cool? 😄

What du you think about a switch for following sunlight? Only use illumination setting if sun is up? Or +/-x hours from sunset/sunrise? This would fixe my problem with Aquara Motions sensors which only sends updated illumination measurement if motion is detected.

[thundergreen]

O like idea using sun entity .. below horizon would work fine in 80% of the cases I guess

[lpt2007]

I have same happening with motion and illumination sensor. Any solution?