Alarmo stops sending notification after longer Arm Away status #778
Comments
|
Thanks for the bug report. |
|
Could you give some clarity about whether the alarm does not get triggered (i.e. the alarm entity not going to triggered state) or only the notification not being executed? |
|
@nielsfaber The PIR sensor is activating i can see the events in the history. But the alarm state stays Away all the time. Please note that i have two Areas. Main House and Garage. Here is a graph showing exactly what happens. 
I dont know how Alarmo is coded, maybe it uses event, maybe cron jobs. Sorry for guessing out, but my guess is that maybe something at midnight is causing this behavior to detach events or crons. I double checked that i dont have any automations active since maybe HA installation is pretty new and i dont have not a single automation active at the moment that can be causing this. And also shouldnt the master state be returned to Away when the garage area also returns to away? |
|
Thanks for sharing this info. Are you certain this sensor is assigned to the garage area? Am I correctly assuming you configured the alarm to return to armed state after the trigger time has expired?
This depends on the states of the other areas. I will setup some test which enables a dummy sensor for a short moment every ~12 hours, and link it to an area. |
|
@nielsfaber while browsing in the history i noted that most of the time this happens there is throttling in the PIR caused by higih movement. 
Also disabled notification and disarmed/armed again to see if maybe huge movement combined with notifications is causing the issue. |
|
I have the same problem, although it triggered the alarm two times as expected until day 4 in away mode. On day 6, three motion sensors in a sensor group fired, but Alarmo stayed in armed mode. Manually disarming Alarmo and arming it again, solves the issue temporarily. 
|
|
@nielsfaber @sec4563 i am almost positive that this happens because of notifications. I disabled notifications in the actions tab and it looks like it is triggering fine now though only 24 hours passed. I will wait another 24-48 and post the results. |
|
No, it's not the notifications, it happened again even with notifications turned off. It may be because there is high amount of movement. 
|
|
In my own test which activates a sensor every day around 18:00 I have not encountered any failure of triggering the alarm (it runs now for 5 days). The issue seems not very easy to reproduce, at least not as easy as described in the initial bug report. There could be a relation with the amount of sensor activity and of course also with other things happening in HA. I appreciate the effort you spend into this, let's keep gathering statistics and hopefully pinpoint to the issue. logger:
default: warning
logs:
custom_components.alarmo: debugThis will add quite some spam to your HA logs (be warned), but it should also print a line every time a sensor changes:
It would be very helpful to have the loggings around the time whenever the alarm fails to trigger. |
|
@nielsfaber it happened again. The Debug was printing states of the sensor and alarm in the log, but after the problem happened the log is empty i cannot see the PIRs being active or any problem/exception. Though in history i can see the PIRs continue to be active. 
|
|
A small update from my side. I think we can conclude that the issue is not related to a 'longer arm away status' as the initial bug report states. The logging you shared suggests that either:
In order to pinpoint which scenario occurred some extra logging info is required. Thanks in advance for your willingness to help with this issue. |
|
I have got the same behavior but it's not due to long Arm Away rather to when it goes from Armed Away to Triggered and then when it comes back to Armed Away no trigger is detected any more. I "hot fix" it at my system in the way that when it comes from Triggered to Armed Away state that I disarm it and arm it again in Armed Away state and no problems since. For me it seems that when it comes from Triggered back to Armed Away that it don't detect any states or it cannot go to Triggering state again. It is not connected with the time spent in initial Armed Away state. |
|
@deadly667 Are you able to reproduce this in your setup, or is this not always the case? |
|
Hello, I have the same issue. It seems it doesn't related to the type of arming (home, night, away).
|
|
Hello, it seems the reason why the motion sensor doesn't trigger alarm is that for some reason it is absent in the list when alarmo changes state from triggered to armed. The sequence of events:
|
|
@froloffw7 Thanks a lot for helping out with this! Some important remark to be made here: This is done since it otherwise the arming would fail and the alarm becomes disarmed. From your logging and the previous screenshot of the history, I assume that this has happened for the motion sensor.
@sokarovski @deadly667 Could you confirm whether the automatic bypassing behaviour when returning to armed state may explain your observations? If so, how would you expect Alarmo to perform the re-arming? |
@nielsfaber yes, it does explain. I did a test where i went to the garage and left immediately. Doing only one trigger per day. Alarmo was working flawlessly for more than two weeks. So this tells me it is not time constraint. This only happens when i am into the garage working for hours. I am guessing that it is happening when the PIR sensor is still triggered but Alarmo tries to go in armed state after the triggered state. Although that is very strange scenario caused by me being lazy to disarm the alarm. I can see a scenario for example when a thief would be constantly moving in your house and you will receive only one notification. My suggested scenario will be if Alarmo want to go into Armed state and finds out that all sensors are not clear, it should stay for another "Trigger Time" in the triggered state, and agian, and agian, until all sensors are clear. Or maybe it should re-enter the triggered state and send you another notification. |
|
Sorry, I don't understand the meaning of bypassed_sensors property. Can you please point me how and were to check this? Attaching screenshot with motion sensor Alarmo settings. Is it possible to implement the similar algorithm like "Allow open initially: Open state while arming is ignored (subsequent sensor activation will trigger alarm)" to return to armed state instead of iteration with "Trigger Time" delay, as iteration may create some other issues which will be difficult to catch and debug. |
Thanks for the idea.
The bypassed sensors will be listed here (if any): It is clear to me now that the user may not be aware of this property, and assumes all sensors are working OK when the system is armed.
Yes, this should be already in place. But you will need to enable this setting: This gives Alarmo permission to ignore the initial state, so the arming (and also re-arming after triggering) would not fail, and the sensor will still activate the alarm after a next off-on state transition. I am now planning to remove the automatic bypassing. |
|
Sorry, for the delay. I did some more tests with different settings. It seems that enabling "Allow open initially" doesn't work in this case, as I still have events missed with Alarmo. If you plan to do some related changes, I have a proposal: PS I just got an idea, whether the reason of this malfunction is that motion sensors require enabling "Allow exit delay" to enable "Allow open initially"? |
|
I just made the aforementioned change of not bypassing open sensors when re-arming after triggering. |
|
v1.9.11 is released which no longer bypasses the sensors when re-arming the alarm. |
Alarmo Version
v1.9.10
HA Version
2023.7
Bug description
I have setup a separate zone of Alarmo in my garage with only one PIR sensor. Usually that zone is always armed since i bearly go to the garage. Even if i go it is only for short period of time. In that short periods I dont bother to disarm the alarm and it sends me a notifiocation that there is trigger in the Garage. But after one day of staying in armed state I stop receiving any notifications. If i disarm and arm the alarm again it continues to work.
Steps to reproduce
(i think that is optional i think the main problem is longer period of time that is causing the issue)
Relevant log output
No response
The text was updated successfully, but these errors were encountered: