Ok, it seems that customizing an autodiscovered alarm control panel doesn’t work.
So my solution is to disable autodiscover in pai.conf (MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE = False).
And create an MQTT Alarm Control Panel directly in HA config.
Does it work this way? If yes, then you need to create an issue that MQTT autodiscovered component attributes can not be overriden with customizations. It is definitely a bug then.
@jooka1978
Can you please tell me how to create the alarm panel for all partitions? I have 4 partitions but arming them one by one is not nice.
As far as i can understand, your alarm control panel is for a specific partion. I looked at the published topics in mqtt and i see all my 4 partitions, but no topic for the whole house.
Also, why when “arming home” the system starts a 30 sec countdown before arming if in babyware i set 0 seconds for stay arm ?
I dont think that you can arm all the partitions in HA with a single lovelace alarm panel card.
In my case the other partition is a basement so it is always armed, so I don’t arm and disarm it with the house.
In your case I would create an automation for that. Display only 1 alarm panel on frontend, and if you arm/disarm that partition it could trigger the other partitions.
I am just a user, yozik04 might be able to help you with MQTT and babyware.
And the countdown and siren beeps while home arming are hard coded somewhere? i would really like to be able to instant home arm wihtout any delay…
i arm some parts of the house when i go to sleep, after midnight and the 30 sec siren chirping is waking kids up Not to mention wife factor…
and this please: “And the countdown and siren beeps while home arming are hard coded somewhere? i would really like to be able to instant home arm wihtout any delay…” is it posible?
Cheers:) Bell squawk was already turned off. But i found out where the problem was coming from. It was the Special Arm Exit Delay which i have set to 0 in babyware. Apparently 0 does not work. Setting it to 1 sec works
So this is how I hacked this error:
serial.serialutil.SerialException: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Permission denied: ‘/dev/ttyUSB0’
Connect a screen and keybard to your Raspberry PI running HassOS.
Press Enter
You will see homeassistant login
Login as root
You will see ha >
Type in: login
You will see # (this means you are now on the HassOs Terminal as root)
Type in: vi /etc/udev/rules.dev/paradox.rules
Insert the following into the file by pressing i on your keyboard: SUBSYSTEMS==“usb”, ATTRS{idVendor}==“0403”, ATTRS{idProduct}==“6001”, SYMLINK+=“paradox”, MODE=“0666”
Press Esc
Type in (note the : in front of wq): :wq
Type in: cat paradox.rules
You should see SUBSYSTEMS==“usb”, ATTRS{idVendor}==“0403”, ATTRS{idProduct}==“6001”, SYMLINK+=“paradox”, MODE=“0666” being displayed
Reboot and your Paradox Addon should now be able to access /dev/ttyUSB0
Hi, first of I am new to HA and python. I installed PAI interfacing to an EVO192 version 6.9 and IP150 V4.4 connected to Paradox Gold site. It refused to connect with my IP 150 password, but was happy to connect using “paradox” ( I did change it.). I had something strange, It would load all the zones labels (64) and partition labels (4) but would only provide access to 43 zones in HA (and MQTT). I did get an error where it reported not recognizing an interface command but it did not stop processing. I had it running well up to a couple of days ago and now suddenly refuses to connect to the panel (via the SITE ID) Any ideas on these issues?
I have setup pai through the hassio add-on, everything works great and connection with IP150 (latest firmware, swan disabled) seems pretty stable.
The only issue I have is with the attributes that are being auto-discovered by home assistant.
For instance, in zones, I can only see the open state, but there are a bunch of other attributes (see below, i see them in mqtt explorer) that I can’t access (or don’t know how) through home assistant and that I need to trigger some automations. For example, some of my zones are wireless and I’d like to monitor the battery level so I can fire a notification when they are running low.
I have searched the web for hours and can’t seem to find anyone else who has the same issue, and from what I can recall (it was 4am and had been searching/trying settings non-stop since the day before…) some guys were able to see these attributes so I believe I have something wrong in my settings…
All of these lines break my configuration and addon will not connect to my Paradox.
Without it, no issue, apart from occasional " No handler for message 5" which according to Gitter is no biggie.
Can anyone please help me with correct formatting?
Any help will be greatly appreciated by virtual hugs and kisses.