The documentation describes the current MQTT implementation.
It is very minimal, so let me know if you miss something.
Alarmo doesn’t arm itself.
You can choose to arm only when everyone left the house, or even make an automation for it.
If you want the arming to fail when there are people in the house, perhaps you could create a template binary_sensor for that condition and add it to Alarmo.
Thank you for great work, love it!
1 Like
Hi @neliss,
Firstly, great component. Makes managing the alarm setup very easy.
I’ve got a question regarding the bypass/force arm mode. Is it possible to do this from the UI/service call? Or only via push notification?
Would it be possible to allow an override code when arming to force arm? Say I arm with my normal code and it won’t allow it due to open sensors but if I arm with a special bypass code then it will force arm
Interesting integration. Unfortunately most of my sensors are not recognized and don’t appear on the Add Sensors tab. In fact, only four of my camera intrusion sensors appear (from the hikvision integration), but none of my zwave door and motion sensors (yes, they’re binary).
Any ideas ?
To announce state changes via Alexa use the yaml editor after creating a new notification.
name: Disarmed Home Echo Dot
modes: []
triggers:
- state: disarmed
actions:
- service: notify.alexa_media
service_data:
data:
type: tts
message: The security system is now DISARMED
target:
- media_player.living_room_echo_dot
1 Like
Make sure the binary sensor has a correct device class
This is just a starting point.
I mentioned here already that I was doubting between a couple of different implementations for the force arm option.
Everyone has their own preference, so I want to roll out support for different flavours.
I’m not really picturing yet now to do it via service call, since the default Lovelace alarm panel card doesn’t offer an option for setting this.
Ofcourse I could introduce an alternative service that you could call by clicking a button or something, but I don’t see it ideal yet.
Perhaps I will just make a branch of the Lovelace alarm panel card with extra whistles and bells.
This is a good idea. I will add a checkbox in the ‘create user’ form, where you can mark a code as override/force mode.
I added quite strict requirement on the sensors (got more complaints about this). They have to be of type binary_sensor but also have a device_class from this list.
Ofcourse this is open for debate. I don’t want to impose limitations, but in my own HA setup I noticed that the ‘candidates’ list was quite long if I would allow any binary sensor.
Hi guys
Newbie here, I had manually installed the zip file and then tried to use the HACS method for automatically getting new updates. The integration seems to install without glitches but when I try to reach the Alarmo configuration page I get a blank page. Needless to say how many times I repeated the process. I’ve even tried to return to manual installation but again I have the same problem. Anyone more experienced knowing what I’ve done wrong ? I love this application and and want it to become my main home alarm system.
Thank you all
Try clearing browser cache
1 Like
Maybe clear the browser cache ?
1 Like
Thank you both for the quick reply. What if I’m using the companion app ?
In app configuration you can also clear the cache.
I will try to install Alarmo with a ‘virgin’ browser, see if i see the white screen as you do.
Caching issues are out of my control unfortunately…
1 Like
Thank you all again, it worked like a charm. That was an idiotic problem so my apologies for spending your time.
I see. Well that explains it. I’m not sure you can modify the device class for zwave sensors ? I will have to look it up. I might have to add a template sensor for each. Or I’ll just modify the source of your component to skip the class test, that’s probably the easiest way to solve this short term 
I’ll try a few things when I get home from work.
Yeah I understand. But it’s never a good idea to hard code these kind of restrictions, because it’s bound to fail at some point. People just have so many different and sometimes obscure configurations. Why not add a checkbox along the lines of “show all sensors” ? It would be unchecked by default.
You can do this via customize.
I also use Z-wave (OZW integration), in my case all motion / door sensors were automatically discovered with their correct device_class. Maybe your devices are not fully supported (yet)?
Its preferrable to have the device_class set correctly, so (when things are in place), you can could receive push notification’back door is open’, instead of ‘backdoor is on’.
Alarmo also applies some default settings for doors, motion sensors, windows etc. so perhaps it worth it to have them set correctly.
Correct. I use mostly Sensative strips, Aeotec Door sensor 7 and Fibaro motion sensors. As far as I remember, none of those were natively supported by the old OZW 1.4 integration. I had to manually add them to the xml. So the device classes were not set either. I never cared much, since I don’t use Lovelace other than for configuration.
Makes sense. When given device classes, everything works as expected. Thanks.
Oh and while testing I stumbled over this bug. I should probably post this on Github, but don’t have my login around. So I’ll dump it here I guess.
When a sensor that is not marked as immediate triggers, this error shows up:
2020-11-23 22:51:38 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/home/hast/.homeassistant/custom_components/alarmo/sensors.py", line 182, in async_sensor_state_changed
if not res and sensor_config[ATTR_IMMEDIATE]:
UnboundLocalError: local variable 'res' referenced before assignment
I’m setting this up to communicte with my commercial alarm system via MQTT but don’t see where I can set the payload.
I need to be able to send subcommands and password for arming / disarming etc. Where can this be set?