So I have got my paradox alarm system hooked up to HA. Working great to arm and using sensors in automations. I have been using the burglary radio switch and Panic radio switch in automations thinking they will trigger an alarm but I tested it over the weekend but it does nothing when I turn on the switches. Question is how do I trigger the alarm to go off in my automations?
Also struggling to do this. The ‘trigger alarm’ function in Node Red doesn’t seem to do it. If I publish ‘disarm’ to paradox/control/partitions/Area_1 via mqtt, i can disarm. I’ve tried ‘trigger, trouble, triggered, alarm’ and a few others.
may be a little bit simple question, but any way: would someone help with configuration to get “paradox alarm” panel workable.
I see that some users have the following in the config:
ALARM_PUBLISH_TOPIC: paradox/alarm/state
ALARM_SUBSCRIBE_TOPIC: paradox/alarm/cmnd
ZONE_PUBLISH_TOPIC: paradox/zone/state
CTRL_PUBLISH_TOPIC: paradox/ctrl/state
CTRL_SUBSCRIBE_TOPIC: paradox/ctrl/cmnd
but my default config doesn’t have it. It contains smth like that:
COMMAND_ALIAS:
arm: partition all arm
disarm: partition all disarm
MQTT_COMMAND_ALIAS:
armed_home: arm_stay
armed_night: arm_sleep
armed_away: arm
disarmed: disarm
So far we figured out that it does not like multiple MQTT clients with same usernames.
Mosquitto Broker 6.x is also guilty but for an other yet unknown reason.
I’ve learnt that with core critical addins like Mosquitto, I always wait at least a few days before upgrading.
PAI still works like a charm for me with Mosquito version 5.
Yesterday night I rolled back my shnapshot when I figured out something is wrong. Hopefully I only updated the MQTT Broker, so the cause was easily sorted out But I’m using the dev version, which still don’t have update
Does anyone have good experience with SP6000 + IP150 gateway. I’m planning on a new installation with the above. In the past I only used the EVO boards. Hope it is the same. In some post I saw it was tested with the SP7000 but not the SP6000.
I have homeassist on rpi 3, MG5050 v6.81 IP150 v4.42. I have a PGM wired into PGM4 on the board and 1 2WayPGM (wireless door contact with PGM). For some reason, the autodiscover discovers the panic and burglar PGMs, but will not discover the PGM 4 and 2WayPGM. I know it works because a friend has the same setup and his works fine. I tried adding a switch to my general config yaml file but no success. Any ideas how I can force it to recognise the PGMs?
P.s. I also have 2 PGMs on an expansion board, but this isn’t supported as yet. If anyone knows how I can get those PGMs to work, too, that would be amazing.
I managed to get this integration working to some extent. I have a EVOHD panel. I’m getting this error in the logs after the PC password successfully authenticates.
PAI.paradox.paradox - Got ERROR Message: Invalid record type
From what I’ve read I have to tweak STATUS_REQUESTS in the config file. But there is no mention of how I should do it. Is it even the same config?
Would be awesome if this was documented.
Ps. I tried adding this to the config, which seems to be ignored.
I figured it out. In babyware, you need to ensure there is an “Activation” and “Deactivation” event linked in the PGM configuration in Babyware.
P.s. MG5050 with PGMs and zones on expnasion board work perfectly. Zones in the expansion board show up as binary.sensor.[name]_2. The “_2” must be the one you look at and use.
Thanks for the awesome Add-on. I have got it work with Sp6000 + IP150. I’m wondering is that possible to make a panic button in HA to trigger the alarm? I read someone mentioned it’s possible by wiring the PGM to a zone but i have no experience on this, can someone please help on how can this be done?
Hi, I have an SP6000 @ 5.18 and an IP150, and this connection worked for me since day1 - Problems only came up if I changed something (used as a process, then as a docker image, then as hassio plugin), or when there was a breaking change in PAI itself.
But I’m using the dev version, which still don’t have update 
