-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to arm not showing up as a notification anymore #20
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
I will take a look. This is not intentional. |
I saw that a bug that causes no notification to be sent if:
This is a special case since such sensors are evaluated at the start of the arming process, where others are evaluated at the end of the arming process (so when leave delay has expired). I also added some logging for these scenario's. I'm assuming that this scenario is what you were encountering. |
This is fixed in release v1.2.0. |
I tested with different scenarios and they are now all working as expected now, @nielsfaber , thanks! |
I'm using the latest 1.1.2, just wondering if there was any change on notifications (on purpose or not) as I haven't been able to see the failed to arm notifications anymore, other notifications look ok ie: If I try to arm the alarm with a sensor open, it doesn't work and it also doesn't show me anything even though I have a notification set.
The text was updated successfully, but these errors were encountered: