thank you, I’ve switched over to Alarmo and so far it seems rock solid. I have my wall-mounted tablet speaking the status. It also turns my semi-retired DSC alarm on & off via envislink.
thanks again @neliss
Hello everything works fine except one thing. If the mqtt alarm pad is setting the mode but alarmi failed because is sensor is not ready the pad stays in away mode but alarmo is disarmed.
Did I do something wrong or is there any solution?
I would expect that Alarmo sends disarmed state when the arming fails due to a sensor not being ready.
This should notify your alarm pad to go to disarmed as well.
Could you listen what happens on the MQTT interface in this situation?
E.g. using: mosquitto_sub -t 'alarmo/#' -v
I will try it today. I wasn’t at the laptop because I wanted to leave the house.
I will update this post this evening.
Here is the picture.
The Alarmpad stayed in the Armed state on the Display
I don’t understand much from the picture you’re sharing.
Please filter out only the Alarmo command/state topics, and explain your config (single or multiple areas? master alarm enabled?)
I dont really get your question but I try to clearify it.
The red one is the topic from the alarm panel as configured in alarmo mqtt: home/alarm
The blue one is the topic from alarmo. “Haus” is the area I specified:
Is there a way to have the alarm trigger after x amount of failed attempts?
I have been using Alarmo for a month or so and it is generally working great. I had an issue recently where I accidentally set up two instances and caused issues ( open ticket ), so I removed the integration and started over.
Now, I am noticing that any time home assistant is restarted, it often comes up in an armed state even though the alarm was disarmed at the time of the restart. Has anyone else seen this or any ideas why? I would say it happens about 80% of the time.
Are you using zwave.js? I had this working when the integration was lock-manager, but since changing to zwave.js and keymaster I haven’t been able to figure out how to pull the keypad disarm.
I use zwavejs2mqtt with gateway enabled. At least until keymaster is updated.
Thanks for the great integration. As bwalarm is not really maintained any more, I am considering changing for alarmo.
I have however a question. I have a few Fibaro eyes in my house.
For some of them, I would like them to trigger immediately the alarm (they are in rooms where nobody should be when alarm is on). However, when leaving the house they still might be on for a few moment if I was in that room just before leaving.
I have identified them as motion.
Then in advanced settings, two options:
Immediate: Activating this sensor will trigger the alarm directly instead of after entry delay.
Allow open while arming: Allow this sensor to be active shortly after leaving such that it will not block arming.
Based on my scenario, I would like for these sensors to be Immediate and Allow open while arming unfortunately these two options are mutually exclusive. Is there a good reason for that? Am I missing something in the configuration?
Thank you fo any tip!
1 Like
Good question… 
Looking at the code I don’t see a reason why both options cannot be combined.
I will remove this restriction in a next update.
1 Like
If the alarm fail to arm, then if i restart homeassistant more later when is restart try to arm the alarm again, the previous state is disarm because is fail
I have made some tests to see if I could make an “Alarmo card”, for the arming/disarming of the alarm through Lovelace.
My test proved that I can include a card to the Alarmo integration “package” and make it show up automatically as an extra available card, making installation and updates very easy.
The next question ofcourse is:
Are there any users who use Alarmo in combination with the alarm panel Lovelace card?
If so, which functionality would you like to see added?
I currently made a “copy” of the HA card as a baseline.
Some useful features I was thinking of myself:
- Countdown timer while leaving and entering (so for states arming + pending).
- error notifications such as: “wrong pin entered” or “could not arm due to Bedroom Window being open”
Anything other suggestions?
2 Likes
I am definitely using the HA lovelace alarm panel card. It just showed up on my default dashboard as soon as I added Alarmo.
I would definitely love to have a timer that showed how long until arming or until triggering.
I would also love to option to make the panel card larger so that it filled more of the screen ( maybe only while armed? ). I often struggle to enter the pin correctly at its current size even on a 10" tablet on the wall
I am not yet using alarmo. I will switch soon though:) I don’t use the lovelace card at the moment and I won’t after I switch. So, no need for me.
Thanks anyhow.
I won’t be using any specific Alarmo card either. As long as it works over the normal HA alarm service and MQTT, that’s all I need. Everything else, like count down timers and whatnot, are just gimmicks as far as I see it. The perfect alarm system does not have any UI, except for emergency cases. And the normal HA alarm panel card is well suited for that.
For those who need a fancy alarm UI, it can all be done outside of Alarmo using automations or with MQTT (like the MQTT alarm panel from the guy who made Wallpanel).
Alarmo is really great because it is simple, efficient and focuses on what it’s supposed to do - being a logic controller for an alarm system and nothing more. If it ends up becoming more and more bloated with secondary and collateral functionality, then I will stop using it (or maybe fork an older version for my own personal use).
Would definitely use a card with a countdown timer.
If also a sound cold be added as s countdown that would bee awesome!
I think you could implement an “override” button to arm, knowing that you have a door or window open.
We have security doors, and sometimes I’m happy to leave the internal door open, knowing the security door is locked, but I have to wait to arm first, wait for the delay, and then press override.
Might be useful for some.
May be it could have that functionality and you do not use it?