No, not that I am aware of.
One way is to take a door magnet wires and split it through normal close relay and you can trigger a let’s say esp relay through home assistant. You would simulate opened door which would trigger the alarm through HA.
What i have done is to have 2 seperate system, one inhouse (paradox) one my own for perimetr around the house. I have a 12V siren, esp wifi relay and it will be triggered when there is a person motion around the house. Works for over a year, perfectly. Once or so there was false positive but i changed the settings and it’s fine
I have Paradox and Alarmo configured in HA. Paradox has several motion sensors configured which can trigger the alarm and siren. I also have some contact sensors on the windows which are only visible via Alarmo. These can trigger Alarmo which will send me notification alerts but unfortunately no siren since Paradox doesn’t know about it.
I was hoping there might be something easy like an MQTT to trigger the Paradox alarm.
How to trigger an alarm: Wire a PGM output (12V) to a zone (putting a 1kOhm resistor between these should be safe and sufficient). Configure zone and PGM in the Babyware as you need. Toggle PGM via PAI. Zone should change states from open to closed and back. This way you can trigger an alarm.
1 Like
Is there any guide on how to do this?
Hey all , @yozik04 a serious thank you for maintaining this amazing piece of integration.
I’m trying to figure out how to filter out from hassio register the system time event that are pushed to mqtt every 10 second. My goal is to have the mqtt register as clean as possible to backrest my alarm sensors for any false alarm prior to deploy it in production .
While looking at the flooded register today I also noticed that system time sometimes didn’t update for few minutes. I believe this is an issue with the interface or network and not with the alarm system itself. Is that correct?
Looking forward hearing from you
Marco .
Hope someone out there can help me.
I recently purchased an IP150+ FW 5.6 and I am finding IP address can only be set through blueEye app, installer menu. I don’t have a Paradox installer account.
Fortunately by default is DHCP configured so I setup in my router IP150 MAC Address → IP address binding, but the password is the default one and I would like to change that.
How did you manage to setup ip address and password on FW5.6 modules?
Thank you.
Random question, since I installed a USB serial connector to home assistant for my inverter, I have been having issues with PAI.
It is intermittent, is there not a way to completely block the integration from looking at USB?
If PAI does not use serial for connection then that part of the code is not executed. So it can not interfere.
It is interesting. Between changing my inverter connection to USBtoSerial and updating home assistant the PAI add-on has been getting the following errors.
2023-10-14 07:56:47,073 - ERROR - PAI.paradox.lib.handlers - No handler for message 5
Detail: Container:
fields = Container:
data = b'R\x00\x80\x02\x00\x00\x00\x80\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36)
value = Container:
po = Container:
command = 5
status = Container:
reserved = False
alarm_reporting_pending = False
Winload_connected = True
NeWare_connected = False
validation = 128
address = 2
data = b'\x00\x00\x00\x80\x00\x00\x00\x00\x00\x00\x00\x00\x80\x01\x00\x00'... (truncated, total 32)
offset1 = 0
offset2 = 36
length = 36
checksum = b'\xd5' (total 1)
2023-10-14 07:56:47,192 - ERROR - PAI.paradox.lib.handlers - No handler for message 5
Detail: Container:
fields = Container:
data = b'R\x00\x80\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36)
value = Container:
po = Container:
command = 5
status = Container:
reserved = False
alarm_reporting_pending = False
Winload_connected = True
NeWare_connected = False
validation = 128
address = 3
data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 32)
offset1 = 0
offset2 = 36
length = 36
checksum = b'\xd5' (total 1)
2023-10-14 08:32:07,515 - ERROR - PAI.paradox.lib.handlers - No handler for message 5
Detail: Container:
fields = Container:
data = b'R\x00\x80\x05\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36)
value = Container:
po = Container:
command = 5
status = Container:
reserved = False
alarm_reporting_pending = False
Winload_connected = True
NeWare_connected = False
validation = 128
address = 5
data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 32)
offset1 = 0
offset2 = 36
length = 36
checksum = b'\xd7' (total 1)
2023-10-14 10:21:40,817 - ERROR - PAI.paradox.lib.handlers - No handler for message 5
Detail: Container:
fields = Container:
data = b'R\x00\x80\x04\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36)
value = Container:
po = Container:
command = 5
status = Container:
reserved = False
alarm_reporting_pending = False
Winload_connected = True
NeWare_connected = False
validation = 128
address = 4
data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 32)
offset1 = 0
offset2 = 36
length = 36
checksum = b'\xd6' (total 1)
2023-10-14 10:40:51,448 - ERROR - PAI.paradox.lib.handlers - No handler for message 5
Detail: Container:
fields = Container:
data = b'R\x00\x80\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36)
value = Container:
po = Container:
command = 5
status = Container:
reserved = False
alarm_reporting_pending = False
Winload_connected = True
NeWare_connected = False
validation = 128
address = 3
data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 32)
offset1 = 0
offset2 = 36
length = 36
checksum = b'\xd5' (total 1)
hello all, how to show the logbook of EVO192 entity (which includes all the sensors onto it) on the Lovelace logbook registry card? Otherwise if i do it only with the templace registry card, i need to input the entities one by one.
Hi, I need help.
I’m unable to connect and I’m constantly getting banned from retrying. I’m not sure how long this locking lasts but its been like 12 hours, I have armed / disarmed to try circumvent it but no luck.
Here is my log output:
2023-11-06 16:58:56,191 - INFO - PAI - Starting Paradox Alarm Interface 3.2.1
2023-11-06 16:58:56,191 - INFO - PAI - Config loaded from /data/options.json
2023-11-06 16:58:56,191 - INFO - PAI - Console Log level set to 20
2023-11-06 16:58:56,222 - INFO - PAI.paradox.interfaces - Starting BasicMQTTInterface Interface
2023-11-06 16:58:56,223 - INFO - PAI.paradox.interfaces.mqtt.core - MQTT loop started
2023-11-06 16:58:56,228 - INFO - PAI.paradox.interfaces - Starting HomeAssistantMQTTInterface Interface
2023-11-06 16:58:56,229 - INFO - PAI - Starting...
2023-11-06 16:58:56,229 - INFO - PAI.paradox.paradox - Connecting to interface
2023-11-06 16:58:56,229 - INFO - PAI.paradox.paradox - Using IP Connection
2023-11-06 16:58:56,322 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
2023-11-06 16:58:56,324 - INFO - PAI.paradox.connections.connection - Connection established
2023-11-06 16:58:56,324 - INFO - PAI.paradox.connections.ip.commands - Authenticating with IP Module
2023-11-06 16:58:56,330 - INFO - PAI.paradox.connections.ip.commands - Authentication Success. IP(114) Module version 20, firmware: 5.6, serial: 7201943e
2023-11-06 16:58:56,341 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module
2023-11-06 16:58:56,341 - INFO - PAI.paradox.paradox - Connecting to Panel
2023-11-06 16:58:56,441 - INFO - PAI.paradox.paradox - Panel Identified SP6000 version 7.14 build 2
2023-11-06 16:58:56,441 - INFO - PAI.paradox.paradox - Initiating panel connection
2023-11-06 16:58:56,542 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Installer login
2023-11-06 16:58:56,635 - ERROR - PAI.paradox.paradox - Got ERROR Message: Partition in code lockout (too many bad entries)
These are my settings:
LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
IP_CONNECTION_HOST: 192.168.1.120
IP_CONNECTION_PORT: 10000
IP_CONNECTION_PASSWORD: paradox
KEEP_ALIVE_INTERVAL: 10
LIMITS:
zone: auto
user: 1-10
door: ""
pgm: 1-5
partition: auto
module: ""
repeater: ""
keypad: ""
key-switch: ""
SYNC_TIME: true
SYNC_TIME_MIN_DRIFT: 120
PASSWORD: "0000"
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_KEEPALIVE: 60
MQTT_USERNAME: username
MQTT_PASSWORD: password
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true
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
HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS:
- live,alarm,-restore
- trouble,-clock
- live,tamper
HOMEASSISTANT_PUBLISH_PARTITION_PROPERTIES:
- target_state
- current_state
HOMEASSISTANT_PUBLISH_ZONE_PROPERTIES:
- open
- tamper
PUSHBULLET_CONTACTS: []
PUSHBULLET_EVENT_FILTERS:
- live,alarm,-restore
- trouble,-clock
- live,tamper
PUSHOVER_EVENT_FILTERS:
- live,alarm,-restore
- trouble,-clock
- live,tamper
PUSHOVER_BROADCAST_KEYS: []
SIGNAL_CONTACTS: []
SIGNAL_EVENT_FILTERS:
- live,alarm,-restore
- trouble,-clock
- live,tamper
GSM_CONTACTS: []
GSM_EVENT_FILTERS:
- live,alarm,-restore
- trouble,-clock
- live,tamper
IP_INTERFACE_ENABLE: false
IP_INTERFACE_PASSWORD: paradox
DUMMY_EVENT_FILTERS: []
I have replaced my pincode in PASSWORD field and the MQTT login.
Not sure why I am still locked out and what setting is incorrect?
Thank you
I got it working, I had to figure out the PC Password is 0000 and not my panel pin…
I have new issues now, unreliable connection. It connects, I get an OK response the connection is dropped immediately.
2023-11-07 13:47:03,240 - INFO - PAI.paradox.paradox - Connecting to Panel
2023-11-07 13:47:04,337 - INFO - PAI.paradox.paradox - Panel Identified SP6000 version 7.14 build 2
2023-11-07 13:47:04,337 - INFO - PAI.paradox.paradox - Initiating panel connection
2023-11-07 13:47:04,432 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Installer login
2023-11-07 13:47:04,529 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Authentication Success
2023-11-07 13:47:04,529 - INFO - PAI.paradox.paradox - Connection OK
2023-11-07 13:47:04,529 - INFO - PAI.paradox.paradox - Loading data from panel memory
2023-11-07 13:47:04,529 - INFO - PAI.paradox.hardware.panel - Loading definitions
2023-11-07 13:47:04,529 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel
2023-11-07 13:47:04,911 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (0.38s)
2023-11-07 13:47:04,977 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:06,883 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:08,597 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:09,919 - ERROR - PAI.paradox.paradox - Timeout while connecting to panel. Is an other connection active?
2023-11-07 13:47:09,919 - ERROR - PAI - Unable to connect to alarm
2023-11-07 13:47:10,513 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:13,399 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:15,230 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:16,942 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:18,858 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:21,506 - WARNING - PAI.paradox.paradox - Missing element with ID 5 in zone/Kazán
2023-11-07 13:47:21,922 - INFO - PAI - Starting...
2023-11-07 13:47:21,922 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2023-11-07 13:47:21,922 - INFO - PAI.paradox.paradox - Clean Session
2023-11-07 13:47:21,922 - INFO - PAI.paradox.paradox - Cleaning previous session. Closing connection
2023-11-07 13:47:21,923 - ERROR - PAI.paradox.connections.protocols - Connection was closed: None
2023-11-07 13:47:21,923 - ERROR - PAI.paradox.connections.connection - Connection was lost
2023-11-07 13:47:21,924 - INFO - PAI.paradox.paradox - Disconnected from the Alarm Panel
2023-11-07 13:47:21,924 - INFO - PAI.paradox.paradox - Connecting to interface
2023-11-07 13:47:21,924 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
2023-11-07 13:47:21,929 - INFO - PAI.paradox.connections.connection - Connection established
2023-11-07 13:47:21,929 - INFO - PAI.paradox.connections.ip.commands - Authenticating with IP Module
2023-11-07 13:47:21,935 - INFO - PAI.paradox.connections.ip.commands - Authentication Success. IP(114) Module version 20, firmware: 5.6, serial: 7201943e
2023-11-07 13:47:21,946 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module
2023-11-07 13:47:21,946 - INFO - PAI.paradox.paradox - Connecting to Panel
I managed to get a silent alarm triggered by creating a voice automation that switches the panic radio off, wait for 3 seconds, and then switch it on again. Hope this helps…
1 Like
You want to change the default “paradox” IP150 password? This was removed in latest firmware (my v1.36 IP150 I was able to change but lost it when upgrading to 5.xx)
You can set the IP addresses through the web interface (browser with IP of the module).
To actually modify any programming of the panel you must have the Panel ID and Code, which should nto bet left at default 0000/0000
So, for anyone on here, I think I got everything to work (brand new Hass user here just plugged in my Home Assistant Green few hours ago).
I re-took ownership of my SP6000 alarm with a hard reset and reprogram since the installer went out of business. At that moment I had no clue about Home Assistant integration so I upgraded my IP150 firmware with babyware to the latest 5.2 and was worried I had to buy a new IP150 based on comments here.
Well according to my log I think everything works ok?
Swan was disabled via the web interface of the IP150 and DHCP too. Not sure if that was needed.
2023-12-13 23:39:29,640 - INFO - PAI - Starting...
2023-12-13 23:39:29,641 - INFO - PAI.paradox.paradox - Connecting to interface
2023-12-13 23:39:29,641 - INFO - PAI.paradox.paradox - Using IP Connection
2023-12-13 23:39:30,065 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
2023-12-13 23:39:30,069 - INFO - PAI.paradox.connections.connection - Connection established
2023-12-13 23:39:30,070 - INFO - PAI.paradox.connections.ip.commands - Authenticating with IP Module
2023-12-13 23:39:30,081 - INFO - PAI.paradox.connections.ip.commands - **Authentication Success. IP(IP150) Module version 20, firmware: 5.2**, serial: (removed)
2023-12-13 23:39:30,105 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module
2023-12-13 23:39:30,106 - INFO - PAI.paradox.paradox - Connecting to Panel
2023-12-13 23:39:30,214 - INFO - PAI.paradox.paradox - Panel Identified SP6000 version 6.10 build 0
2023-12-13 23:39:30,214 - INFO - PAI.paradox.paradox - Initiating panel connection
2023-12-13 23:39:30,356 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Installer login
2023-12-13 23:39:30,483 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Authentication Success
2023-12-13 23:39:30,484 - INFO - PAI.paradox.paradox - Connection OK
2023-12-13 23:39:30,484 - INFO - PAI.paradox.paradox - Loading data from panel memory
2023-12-13 23:39:30,485 - INFO - PAI.paradox.hardware.panel - Loading definitions
2023-12-13 23:39:30,485 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel
2023-12-13 23:39:30,648 - INFO - PAI.paradox.interfaces.mqtt.core - MQTT Broker Connected
2023-12-13 23:39:31,921 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (1.43s)
2023-12-13 23:39:32,354 - INFO - PAI.paradox.hardware.panel - Pgm definitions loaded (0.43s)
2023-12-13 23:39:32,366 - INFO - PAI.paradox.hardware.panel - Loading labels
2023-12-13 23:39:32,366 - INFO - PAI.paradox.hardware.panel - Updating Labels from Panel
2023-12-13 23:39:32,864 - INFO - PAI.paradox.hardware.panel - Zone labels loaded (0.5s): Porte entree rdc, Patio gauche, Patio centre, Patio droite, IR sous-sol, Temperature, IR rdc, Porte entree s-s
2023-12-13 23:39:32,968 - INFO - PAI.paradox.hardware.panel - Pgm labels loaded (0.1s): Output 01, Output 02
2023-12-13 23:39:33,067 - INFO - PAI.paradox.hardware.panel - Partition labels loaded (0.1s): Residence, Area 2
2023-12-13 23:39:33,570 - INFO - PAI.paradox.hardware.panel - User labels loaded (0.5s): System Master, Master 1, Master 2, User 04, User 05, User 06, User 07, User 08, User 09, User 10
2023-12-13 23:39:33,571 - INFO - PAI.paradox.hardware.panel - Module labels loaded (0.0s):
2023-12-13 23:39:33,572 - INFO - PAI.paradox.hardware.panel - Repeater labels loaded (0.0s):
2023-12-13 23:39:33,573 - INFO - PAI.paradox.hardware.panel - Keypad labels loaded (0.0s):
2023-12-13 23:39:33,676 - INFO - PAI.paradox.hardware.panel - Site labels loaded (0.1s): Your Alarm Site
2023-12-13 23:39:33,885 - INFO - PAI.paradox.hardware.panel - Siren labels loaded (0.21s): Wireless Siren 1, Wireless Siren 2, Wireless Siren 3
2023-12-13 23:39:33,886 - INFO - PAI.paradox.paradox - Running
hello community!
I’m getting in the deep of HASS and now that my main installation become full of entity i need to start and make it worth on the HMI and user experience side.
I’m keeping my HASS behind a firewall, hence only accessing via VPN when needed to, so i found out that having a whatsapp integration to trigger notifications is the safest way.
Now i’m about to enable automations to send me messages on state changes and PAI is indeed one of the most important one!
I would like to obtain that, other then notifyinh when one of my partition is in alarm, also which zone triggered it . So my idea was to activate an automation to send me the open zone only in the event the partition is in alarm. What is the best way to do this knowing i will have something like 100 zones (PIR, TAMPER, windows sensor, volumetric)
I was thinking about making an entitiy with all the zones in series but that might not be the solution.
please let me know what are your thoughts!
thank you !
reading from mqtt seems to me the best way a bunch of info are there but i’m not getting it right…
i’m getting “Error rendering data template: UndefinedError: ‘trigger’ is undefined” trying to implement what i’ve found on github
action:
- service: notify.persistent_notification
data:
title: |
'Alarm Triggered'
message: >
The following zones are triggered: {{- '\n' -}} {% for state in states
if state.entity_id in
device_entities('85c3e68cb1afa155df178f17f8215efa') and state.domain ==
'binary_sensor' and state.state == 'on' -%}
* {{ state.entity_id|replace('binary_sensor.zone_','') }} sensor is {{ state.state }}
{% endfor %}
mode: single
but this is only triggering a message “the following zones are triggered:”
