Paradox Alarm MQTT Hassio addon

KameDomotics · January 6, 2022, 2:10pm

hello guys, do you have any recommendations for this battery sensor? have there been any updates?
Thanks

sensor:
  - platform: mqtt
    state_topic: "paradox/states/system/power/battery"
    name: "Backup Battery"
    unit_of_measurement: "%"
    value_template: "{{ value_json.batt }}"

KameDomotics · January 6, 2022, 7:58pm

Queste informazioni sono presenti nel modulo IP, ho provato il mio pannello allarme con PAI, e ho queste informazioni:

pai

kirimeister · January 17, 2022, 8:06pm

I have a feeling that when I arm the system thru the HA panel it makes a forced arm. How can I configure the panel correctly not to allow forced arming? What should happen if a zone is open and thus the system cannot be armed? Can I see it on the panel?

yossi33 · January 19, 2022, 5:47pm

It looks like the panel states list in the MQTT interface WIKI is not accurate. For example to get the battery power I had to add the word “power” between system and battery. Is there an updated list of states or does any one have an idea where its possible to find one ?

poweredd · January 30, 2022, 11:51am

Good morning, my name is Marco I’m new to the forum recently

I looked at the spectacular world of home assistant…

I ask for kind help from you forum experts… it’s been months that I can not operate my anti-theft paradox… I attach to the post all the possible study material…

I warmly thank you for your help

error mqtt:
Mosquitto broker
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] mosquitto.sh: executing…
[12:23:09] INFO: Setting up user mqtt
[12:23:09] INFO: Certificates found: SSL is available
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing…
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[12:23:10] INFO: Starting NGINX for authentication handling…
[12:23:10] INFO: Starting mosquitto MQTT broker…
1643541790: mosquitto version 1.6.12 starting
1643541790: |-- *** auth-plug: startup
[12:23:11] INFO: Successfully send discovery information to Home Assistant.
[12:23:11] INFO: Successfully send service information to the Supervisor.
1643541790: Config loaded from /etc/mosquitto/mosquitto.conf.
1643541790: Loading plugin: /usr/share/mosquitto/auth-plug.so
1643541790: ├── Username/password checking enabled.
1643541790: ├── TLS-PSK checking enabled.
1643541790: └── Extended authentication not enabled.
1643541790: Opening ipv4 listen socket on port 1883.
1643541790: Opening ipv6 listen socket on port 1883.
1643541790: Opening websockets listen socket on port 1884.
1643541790: Opening ipv4 listen socket on port 8883.
1643541790: Opening ipv6 listen socket on port 8883.
1643541790: Opening websockets listen socket on port 8884.
1643541790: Warning: Mosquitto should not be run as root/administrator.
1643541790: mosquitto version 1.6.12 running
1643541790: New connection from 127.0.0.1 on port 1883.
1643541790: Socket error on client , disconnecting.
1643541791: New connection from 172.30.32.1 on port 1883.
1643541791: New client connected from 172.30.32.1 as 0PKcVhD1iN2MlM8FbMKcML (p2, c1, k60, u’homeassistant’).
1643541811: New connection from 172.30.33.5 on port 1883.
401: Unauthorized1643541812: Socket error on client , disconnecting.
1643541876: New connection from 172.30.33.5 on port 1883.
1643541876: Socket error on client , disconnecting.
1643541877: New connection from 172.30.32.2 on port 1883.
1643541877: Socket error on client , disconnecting.
1643541996: New connection from 172.30.33.5 on port 1883.
1643541996: Socket error on client , disconnecting.
1643541997: New connection from 172.30.32.2 on port 1883.
1643541997: Socket error on client , disconnecting.
1643542116: New connection from 172.30.33.5 on port 1883.
401: Unauthorized1643542116: Socket error on client , disconnecting.
1643542117: New connection from 172.30.32.2 on port 1883.
1643542117: Socket error on client , disconnecting.
1643542236: New connection from 172.30.33.5 on port 1883.
1643542236: Socket error on client , disconnecting.
1643542237: New connection from 172.30.32.2 on port 1883.
1643542237: Socket error on client , disconnecting.
1643542356: New connection from 172.30.33.5 on port 1883.
1643542356: Socket error on client , disconnecting.
1643542357: New connection from 172.30.32.2 on port 1883.
1643542357: Socket error on client , disconnecting.
1643542476: New connection from 172.30.33.5 on port 1883.
401: Unauthorized1643542477: Socket error on client , disconnecting.
1643542477: New connection from 172.30.32.2 on port 1883.
1643542477: Socket error on client , disconnecting.
1643542597: New connection from 172.30.32.2 on port 1883.
1643542597: Socket error on client , disconnecting.
1643542597: New connection from 172.30.33.5 on port 1883.
1643542597: Socket error on client , disconnecting.
1643542717: New connection from 172.30.32.2 on port 1883.
1643542717: Socket error on client , disconnecting.
1643542717: New connection from 172.30.33.5 on port 1883.
1643542717: Socket error on client , disconnecting.
1643542837: New connection from 172.30.32.2 on port 1883.
1643542837: Socket error on client , disconnecting.
1643542837: New connection from 172.30.33.5 on port 1883.
401: Unauthorized1643542837: Socket error on client , disconnecting.
1643542957: New connection from 172.30.32.2 on port 1883.
1643542957: Socket error on client , disconnecting.
1643542957: New connection from 172.30.33.5 on port 1883.
1643542957: Socket error on client , disconnecting.
1643543077: New connection from 172.30.32.2 on port 1883.
1643543077: Socket error on client , disconnecting.
1643543077: New connection from 172.30.33.5 on port 1883.
1643543077: Socket error on client , disconnecting.
1643543197: New connection from 172.30.32.2 on port 1883.
1643543197: Socket error on client , disconnecting.
1643543197: New connection from 172.30.33.5 on port 1883.
401: Unauthorized1643543198: Socket error on client , disconnecting.

conf.yaml:

MQTT

mqtt:
broker: 127.0.0.1
port: 1883
username: mqqt
password: …

Paradox alarm system

alarm_control_panel:

platform: mqtt
name: “…”
state_topic: “paradox/alarm/state/1”
command_topic: “paradox/alarm/cmnd/1”
qos: 1
availability_topic: “paradox/ctrl/state”
payload_available: “Connected”
payload_not_available: “Disconnected”
payload_disarm: “DISARM”
payload_arm_home: “Ins. Totale”
payload_arm_away: “Ins. Perim.”
payload_arm_night: “Ins.Notte”
#code: 1105

Load all binary sensors

binary_sensor:

platform: mqtt
state_topic: “paradox/zone/state/1”
0
qos: 1
payload_on: “on”
payload_off: “off”
availability_topic: “paradox/ctrl/state”
payload_available: “Connected”
payload_not_available: “Disconnected”
device_class: door
platform: mqtt
state_topic: “paradox/zone/state/2”
name: “IR SALONE”
qos: 1
payload_on: “on”
payload_off: “off”
availability_topic: “paradox/ctrl/state”
payload_available: “Connected”
payload_not_available: “Disconnected”
device_class: motion
platform: mqtt
state_topic: “paradox/zone/state/3”
name: “IR CORRIDOIO”
qos: 1
payload_on: “on”
payload_off: “off”
availability_topic: “paradox/ctrl/state”
payload_available: “Connected”
payload_not_available: “Disconnected”
device_class: motion

poweredd · January 31, 2022, 11:12am

I hope for an answer…
at least to know if fw versions.

and the sp6000 control panel both the ip150 module are compatible…??

thanks 1000

digieurope · February 21, 2022, 9:32am

Hello Marco,

Can you please check the FW of your IP150? I think you still need to have one below v.4 to use this addon, otherwise you need to use to other one (PAI out of memory) or downgrade your IP150 (not sure this is possible).

If the firmware is ok, you need to test your connection to the IP module through your local network.

If that wirks, it is most probably an MQTT issue and you need to restart the MQTT configuration from scratch.

Hope this helps,

KR

byronmorrison · March 7, 2022, 8:23am

Hey team,

I am getting the following error when trying to connect this addon, have read above but that has not solved my issue.

mqttuser and password are correct, double checked a few times

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Traceback (most recent call last):
File “ip150_mqtt.py”, line 140, in
ip_mqtt.loop_forever()
File “ip150_mqtt.py”, line 122, in loop_forever
self.ip.login(self._cfg[‘PANEL_CODE’], self._cfg[‘PANEL_PASSWORD’])
File “/ip150.py”, line 142, in login
raise Paradox_IP150_Error(
ip150.Paradox_IP150_Error: Wrong page fetcehd. Did you connect to the right server and port? Server returned:

Your Paradox System

Using the master password to login via the web no issues

Can login in with babyware and can confirm that panel password is correct also

Any help would be great.

scstraus · March 7, 2022, 10:19am

Are you on v1.5 or earlier firmware?

byronmorrison · March 7, 2022, 7:57pm

Hi Scstraus,

Panel Firmware is 4.90
Ip module firmware 4.40.04

scstraus · March 11, 2022, 2:02pm

Wrong integration. See countless other forum posts in this thread redirecting to correct one.

bitlisz · March 29, 2022, 12:37pm

PAI (Paradox Alarm Interface (Second Instance) 2.7.1) enabled (SP5500, IP150+ through local ip),
then Insite Gold cannot connect (SWAN, throught internet).

But almost instantly can connect, if PAI disabled.

Is this a known issue?

scstraus · March 30, 2022, 9:06am

This integration doesn’t do any of that. Find the one that does.

AunPixel · April 11, 2022, 6:21pm

Hi poweredd

Did you get your integration working ? I have a sp6000 and ip150 too.
I’m trying hard to get this up and running.

If so, can you help me ?

CharlesC · May 15, 2022, 3:38pm

Hi, firstly well done and thanks for this add-on… Working reasonably well but I have an issue which is that if a zone in a position is “open” and this the area shows as “not ready”… But on home assistant it appears to be “armed” even though it’s not. I traced this by inspecting the Mqtt messages and then eventually found the issue is in ip150_mqtt.py in the areas mapping there is no mapping for “Not Ready” so seems to be defaulting… I think of it goes to ready then back to not ready it might be okay but I can’t tell for certain. On one of my partitions/areas it seems to default this to disarmed and on partition 2 it is showing as armed home

wojcior1 · May 23, 2022, 6:40am

hi, after updating Home Assistant OS to version 8.1 the addon is unstable, do you have the same problem? I am using the installation on Oracle VirtualBox

ddppddpp · May 25, 2022, 12:02pm

I’m also noticing some instability after recent upgrades of HA OS. One of my PIR entities is reporting activity all the time (in HA) while the PIR itself is not being activated.
The add-on fails with different errors in irregular intervals.
Stoping the add-on and starting after a brief period fixes the issue temporarily
HA Core 2022.05.5, Supervisor 2022.05.3, HA OS 8.1 on odroid-n2

Specifically, I keep getting errors like in Paradox Alarm MQTT Hassio addon - #320 by Stewart_Clay

alfredo · May 27, 2022, 9:15pm

Hi All, I’m going to check my logs for anything relevant. The errors hinted by @ddppddpp (and reported by @Stewart_Clay ) seem to relate to some inner working of Paho (the MQTT library) – maybe related to the network, but not necessarily under my control.

If you get any further insights, or manage to make the errors more reliably reproducible let me know and we can look further into that.

Also, the changelog for hassOS 8.1 mostly hints to a kernel and other updates that, in principle, should not interfere with the plain networking we’re doing. (That is, if the new OS was breaking something this basic, I’d expect way more addons having similar issues, maybe?)

CharlesC · May 29, 2022, 9:35pm

Any chance someone could consider the below and if agreed maybe this is a simple fix??

In ip150_mqtt.py

Into the below I believe the following additional mapping is required:

'Not_ready' : 'disarmed',

_status_map = {
		'areas_status' : {
			'topic' : 'ALARM_PUBLISH_TOPIC',
			'map'   : {
				'Disarmed'   : 'disarmed',
				'Armed'      : 'armed_away',
				'Triggered'  : 'triggered',
				'Armed_sleep': 'armed_night',
				'Armed_stay' : 'armed_home',
				'Entry_delay': 'pending',
				'Exit_delay' : 'arming',
				'Ready'      : 'disarmed'
			}
		},

alfredo · May 29, 2022, 9:45pm

Hi @CharlesC I can try to have a look after the recent stability issues are sorted. What I’ll need to check before adding it, is whether a “Not_ready” start seems to be reported from the IP150 web app. If you are comfortable with broswer debgging tools and JS, you can find the list of all possible reported states. Also, I’m not sure what the “Not_ready” is for on a Paradox alarm, but if you know it maps to “disarmed” I’m happy to take that