Alarm gets triggered if updating integrations while alarm is armed

[hajar97]

Checklist

• I am using the latest version of Alarmo (latest version can be found here)
• I checked for similar existing requests (both open and closed) before posting.

Alarmo Version

v1.10.7

HA Version

2025.1.2

Bug description

Have alarm armed with windows sensors to be allowed to be open when arming.
Then if an integration gets updated that is responsible for windows sensors, then those windows sensors go from open to unavailable while integration is updated and then when it i re-initialises from unavailable to open again. The don't go from closed to open. However, alarm gets still triggered as if someone opened a window, although that is not what is happening.

Steps to reproduce

Arm alarm with windows open, make them unavailable and then open again (e.g. through reload of a corresponding integration) and alarm will be triggered, although no window actually went from closed to open state.

Relevant log output

No response

[nielsfaber]

This is not a valid bug report.
You need to configure how alarmo needs to treat a sensor becoming unavailable, this is a setting that can be chosen per setting.

[hajar97]

Unless I am missing something, bug report is valid. Configuration for how to treat unavailable is a different thing. It is disabled for all those sensors. So those sensors becoming unavailable isn’t triggering the alarm. Alarm is triggered when they go back from unavailable to open again alarm gets triggered assuming a window was opened, while it wasn’t opened, it just went unavailable and then open again and it was open to begin with with “Allow open initially” setting enabled.

…

On 14 Jan 2025, at 12:50, Niels Faber ***@***.***> wrote: This is not a valid bug report. You need to configure how alarmo needs to treat a sensor becoming unavailable, this is a setting that can be chosen per setting. — Reply to this email directly, view it on GitHub <#1099 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2QG7QTSUS24NI4AEUBKHD2KT2W3AVCNFSM6AAAAABVEWLTV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBZG4YTANBTGU>. You are receiving this because you authored the thread.