I enquired about that and the fronted guys pointed me to this
It works the other way round - generally the panel just displays the alarm’s state and specifically, when one tries to set the alarm, the panel checks for open sensors (asking for override/cancel if needed) and then calls a service to arm. The only feedback is a change of the alarm’s state.
I’ve been able to somewhat replicate this using node red.
When I attempt to arm using my tileboard interface a “call_service” event with “alarm_arm_[mode]” is sent to the HA event bus. I am then monitoring for this in node red and if following this the alarm is still in the disarmed state it will then show a popup alert on tileboard.
Now for the next piece of the puzzle. What do I send to the “alarm_set_ignore_open_sensors” service to set true/false?
Can you please also confirm that if I activate this and arm with open sensors if they are closed and re-opened it will trigger as normal?
You need to call this service to change ignore_open_sensors configuration variable. It’s documented here
However, it is not available if you use this integration. It is only available with that one.
Its discussion topic is here
it should. roughly, the alarm reacts on any registered sensor’s state change from ‘off’ to ‘on’
Perfect, thank you for your help. I am using the other component…just got the wrong topic here
I’m migrating from an old HA instance (which wouldn’t upgrade, so I’m having to do it manually 
). Getting a few errors in the logs
[init_variables] persistence: path "/config/resources/bwalarm" does not exist
[load_yaml] Error loading file "/config/resources/bwalarm/bwalarm.yaml": [Errno 2] No such file or directory: '/config/resources/bwalarm/bwalarm.yaml'
Any ideas why this might be? I’ve deleted the old Alarm custom component and reinstalled with HACS
EDIT: Actually looks like as soon as some logs get generated that error might go away? The current problem is this:
EDIT 2 For some reason I don’t even appear to have a config/resources folder.
Thanks
The issue is these two components are not the same, you’ve installed a diffrent component (and it has a different file structure).
This topic relates to the former component that is currently not supported.
The latter one lives there.
To report issues with it you need to go there.
To read more about it check out the Github docs and an appropriate topic (but please use Github if you have issues and don’t post them in the topic).
Hello,
After following your guide for install I get an error stating the integration bwalarm not available. Am I missing a step somewhere? I checked permissions and such, but no luck. I am setup on HA in a VENV.
This forum is abandoned and there is no reason to ask here for anything (especially if you have an issue - Github is the right place).
Please read this.
