Your section 3.3.3. regarding the Alarmo-card is not correct, your screenshots show the Lovelace Alarm Panel Card (which is not my work).
Its fine to use that card, but Alarmo comes with its own flavour with some extra functions.
A small warning: things might change in the future, especially regarding the setting up of actions/notifications Iâm planning to make some modifications. Hope this will not bother you.
Perhaps we can merge your guide in the readme of Alarmo, such that it can be found by more people, and I could help maintaining it when things change?
I would love some help with extending the instructions, especially written from the perspective of the user rather than me (some things might be intuitive to me but not to others).
I expect that one area fails which causes the master to abort the arming for all areas.
The best way to troubleshoot this is by creating a lovelace view with all areas + the master, as I did here.
If you use the âalarmo-cardâ for this view, you should be able to get all info to see whatâs going on.
If this doesnât help, maybe the HA logs will be able to show more.
As a last resort you can enable the debug logging for Alarmo by adding this to configuration.yaml and restart HA:
Please let me know if you need assistance
Consider to create an issue in github to discuss it more.
You mean to use the gateway as a siren?
From what I heard, the siren of the Xiaomi gateway can only be turned on/off by a specific service, and it is not available as a switch (or similar) entity.
I suppose a custom automation is needed to target the specific service, this is easier to do outside of Alarmo.
I use Alarmo and two Xiaomi gateways. I have writen automations for flashing them on the exit delays, entry delay, fixed orange when armed_night, red when armed_away, green for some time when disarmed and custom beeps on the delays.
The main alarm siren I have is a zwave one.
Good choice. I managed to get my gateway to ring but it stops after a few seconds. It does not reflect the settings entered in Alarmo of course and in the automation too⊠any ideas?
@jasonshearer
I just released an update which allows you to scale the buttons.
There are definitely more things to be done for improving the card, but itâs a start.
And I would like the different modes to use the areas like so:
Armed_Home: Only Arm Area 1 (Outdoor Camera Sensors)
Armed Night: Arm Area 1 (Outdoof Camera Sensors) & Area 3 (Door Sensors)
Armed Away: Arm All Areas (Outdood Camera Sensors, Indoor Camera Sensors and Door Sensors)
I was expecting my Master Panel (Home, Night and Away) to arm the areas like I described before but what I notices is that:
Master Arm Home fails to arm
Master Arm Night fails ti arm
Master Arm Away works perfectly
Please note that arming the different areas with their respetive Arm Button in their respective cards works fine.
Itâs only arming the night mode and the home mode in the Master Alarm card that doesnât work
There is probably something I didnât understand! Any one could enlight me?
Thanks again (Especially @neliss for the great work)
No problem for being new, this should make Alarmo a good tool for you actually.
First of all, consider to use alarmo-card.
Second, the master alarm can only arm the system in the modes that all areas have in common.
This is because the master alarm is meant to keep all areas in sync.
So if only 1 out of 3 areas are configured to be armed in ânightâ, you cannot arm in ânightâ via the master, but you will have to arm that area directly.
Maybe itâs easiest for you to set up the other 2 areas to do nothing in ânightâ mode, in that case the master will work OK for you.
Upgraded. What is the yaml for scaling the buttons?
EDIT: Found it in the card JS file.
button_scale:
Looking at the context the value is in the 1-2.5 range. The slider is not visible and manually adding the attribute does not change the button scaling.
@nellis
I have asked this in github issues, but I will also do it here, so this can help other users.
I have defined a notification that use a tts notify entity to tell that Alarmo could not be armed because of an open sensor.
It works. But the words I pass to he action are in spanish, plus the âopen sensorsâ variable. {{open_sensors}} contains the words of the name of the open sensors + âis openâ.
So, the result is a voice telling a mix of spanish and english words.
Is there any way to get only the name of the open sensor?
Thanks in advance.
Unfortunately HA uses a quite strict separation between the frontend and the backend side, meaning that it is quite difficult to have Alarmo use translated texts (in your local language) when sending push notifications.
But not impossible
If more users are bothered by the hardcoded english text, please let me know (by liking this post). I might take the effort to implement these translations.
I just come across as issue. I hope someone can help me. I have some Xiaomi vibration Sensors (
DJT11LM). These do not come up under sensors? How do I get them to recognized under Alarmo?
For the info, I have zigbee2mqtt setup. They are setup in zigbee2mqtt.
Do they provide a binary_sensor entity? If not, you would need to create a template sensor which toggles between on / off at some preset vibration level.
Hi
Thank you for your reply. There are no binary sensors. It creates a number of sensors but the interesting one is âactionâ, e.g. sensor.friendly_sensor_name_action. This has various angle, angle_x, angle_y, angle_z, angle_x_absolute, angle_y_absolute values. I donât know how I can use these values to calculate if it is a drop, tilt or vibration?
This is exactly the reason why Alarmo only handles binary_sensor entities.
I cannot judge which levels of vibrations are OK and which are a burglary attempt.