sparkydave1981

As a previous commercial alarm installer I just thought I'd put a note about naming conventions. What you are explaining to is as stated above referred to as "areas". What...

The areas can be armed and disarmed independently as of they were two (or more) seperate alarm systems. Zones (inputs) can be in either or both. Entry and exit time...

Zones are individual inputs, it's purely a naming convention. I agree that any non-alarm logic (turning lights on etc) is not needed in the component as we can already do...

I currently use this custom component in HA to communicate with a hard wired "Paradox" alarm system in my house using [this](https://github.com/maragelis/ParadoxRs232toMqtt) interface. It would be awesome if I can...

> As `fail` is not a valid state, I'm not happy with sending it to the `state` topic, it'd rather go to `information` one and my question is would you...

> create a script in Home Assistant and assign that script to a button, so that will be your custom short press... Ah ok thanks. I just assumed (wrongly) that...

I tested this work-around and it does do the job however 'natively' being able to enter the code within the Blueprint would definitely be nicer. Also, since the button now...

> Call the Service `_send_command_printf` and set cmd to `home.left_bt_pic.val=1` to enable the blue bar. 0 to turn it off. Just seeing this now, but the issue will remain when...

> Or you add a single automation to call that service when the light turns on... ...sure, but this is still a work-around for something that should be simple to...

I had this same problem, tried again 2 days later and all was good.