Paradox Alarm MQTT Hassio addon

Installation Home Assistant OS
574

I’m using the plugin for the first time… and I’ve got this problem… I had to raise the ratio to 2 seconds, and user and pass are correct…
Does something happen to you?

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 192.168.44.115:80
DEBUG:urllib3.connectionpool:http://192.168.44.115:80 “GET /login_page.html HTTP/1.1” 200 None
Traceback (most recent call last):
File “//ip150_mqtt.py”, line 153, in
ip_mqtt.loop_forever()
File “//ip150_mqtt.py”, line 135, in loop_forever
self.ip.login(self._cfg[‘PANEL_CODE’], self._cfg[‘PANEL_PASSWORD’])
File “/ip150.py”, line 149, in login
raise Paradox_IP150_Error(
ip150.Paradox_IP150_Error: Wrong page fetcehd. Did you connect to the right server and port? Server returned: <!DOCTYPE HTML PUBLIC'-<meta http-equiv=“content-type"content=“text/html; charset=UTF-8”/><link rel=“stylesheet"type=“text/css"href=“webstyles.css”/><script type=“text/javascript"src=“commun.js”><script type=“text/javascript"src=“langue.js”><div id=“ERROR"style=“margin-top: 60px;”>

575

I also had a timeout problem.

  • I uninstalled the addon
  • deleted the repository,
  • HA reboot
  • Add repo
  • install the add-on

So far, I don’t have a problem.

The important thing is to set a static IP in paradox IP150. Earlier I had assigned via DHCP and reserved in the router, but for some reason it sometimes got a different IP.

576

Hello,

Paradox:
EVO192 256K 7.70.001
IP150 5.02.058

Home Assistant 2023.10.5
Supervisor 2023.10.0
Operating System 11.0
Frontend 20231005.0 - latest

seems some changes in PARADOX and need to change code. I provide debug log:

DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 192.168.11.13:80
DEBUG:urllib3.connectionpool:http://192.168.11.13:80 “GET /login_page.html HTTP/1.1” 200 None
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 192.168.11.13:80
DEBUG:urllib3.connectionpool:http://192.168.11.13:80 “GET /default.html?p=B57068F66A888120DA26CB1FD6D3D10C&u=D618828B HTTP/1.1” 200 None
INFO:root:Successfully logged into the Paradox web interface.
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 192.168.11.13:80
DEBUG:urllib3.connectionpool:http://192.168.11.13:80 “GET /statuslive.html HTTP/1.1” 404 None
WA

looks like statuslive.html is not available anymore.

now status is controlled via keepalives:
http://192.168.11.13/keep_alive.html?msgid=1&260926286441024

is it possible to modify a code base on ne version on firmware?

577

I had an alarm service tech come and do some work on my alarm. He opened up the admin ui with the special software they use, and it had tons of errors in the log. He cleared it out, and now it’s working fine again without the frequent disconnects, so it seems it’s accumulating a lot of errors and clogging up the system. For now it’s fine again.

The errors in the logs were as follows:

NE Ware ON
Software access
NeWare OFF
Entered User Code

Just repeating over and over all the messages a couple times per minute.

578

Hi, is there a way to read the control panel errors?
For example “low battery sensor” Etc
Thanks

579

Hi @KameDomotics,

I just had a couple of sensors with low battery. While I see some warnings appearing in the log, the zones in the “Area Status” don’t seem to report any “trouble”. Would you know of a reliable way of detecting this information from the web interface? In that case, I could possibly work something out to expose it via MQTT.

Going a bit technical, the source code of the web panel seems to have support for reporting “troubles”, including wireless low batteries. In the index.html file, there’s an array with all possible troubles to be reported:

tbl_troublename = new Array(“Clean smoke detector, fire zone trouble, or zone communication failure”,“Fire loop trouble”,“Module missing or failed to communicate”,“Module power failure (AC fail)”,“Module reporting via phone line failed”,“Module auxiliary power interrupted (aux limit)”,“Module battery low or disconnected”,“Module enclosure tampered”,“Module ROM memory corrupted”,“Printer module does not detect a printer”,“System cannot detect a phone line (TLM)”,“System communication with modules failed (combus)”,“System power failure (AC fail)”,“System reporting via phone failed”,“System auxiliary power interrupted (aux limit)”,“System battery low or disconnected”,“System bell/siren disconnected”,“System bell/siren power interrupted (bell limit)”,“System ROM memory corrupted”,“Loss of time and date”,“Too many modules connected to the system”,“Wireless zone low battery”,“Wireless zone supervision loss”,“Zone tampered”,“System RF interference”,“System reporting with receiver failed”,“Module missing or wireless module supervision loss”,“Zone antimask transparency trouble”,“Zone antimask proximity trouble”,“Zone antimask dirty lens trouble”,“Module direct light trouble”,“Module low bus voltage”,“Module selftest failed”,“IP150 lost communication with panel”,“IP150 receiver supervision”,“IP150 receiver unregistered”,“IP150 receiver registration failed”,“PCS module missing”,“PCS module tamper”,“PCS GPRS no service”,“PCS receiver supervision”,“PCS receiver unregistered”,“PCS receiver registration failed”,“System enclosure tampered”,“”);

(See “Wireless zone low battery”). However, in my setup, even with the wall panel showing 2 zones with low battery, and having that confirmed in the web panel log, the list of troubles, as reported by the web panel, is empty. In statuslive.html, where all the “live info” is reported, I see:

tbl_troubles = new Array()

which means an empty array, that is no troubles to show.

If anyone has a different behavior or setup, please let me know and we can take it from there. Thanks!

580

Hey @RKor sorry I completely missed this. Is the issue still present?

581

Hello,

I am new to Home Assistant and still in the process of migrating from Openhab (OH). In OH I was was able to use a Paradox interface, which I believe was based on a different approach. My panel is as follows:

Paradox:
EVO192 256K 7.01
IP150 5.02.58

My HA system is as follows:

  • Core: 2023.12.3
  • Supervisor: 2023.12.0
  • Operating System: 11.2
  • Interface utilisateur: 20231208.2

I installed the Paradox IP150 MQTT Adapter, version: 1.3. Upon trying to connect, I am getting the error message below, which is apparently the same as @B100d-BOb’s reported on October 23. Any advice for me?

Many thanks.

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 192.168.2.8:80
DEBUG:urllib3.connectionpool:http://192.168.2.8:80 "GET /login_page.html HTTP/1.1" 200 None
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 192.168.2.8:80
DEBUG:urllib3.connectionpool:http://192.168.2.8:80 "GET /default.html?p=2816066E540CB98B0B2F4911C6E66E2D&u=B7109187 HTTP/1.1" 200 None
INFO:root:Successfully logged into the Paradox web interface.
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 192.168.2.8:80
DEBUG:urllib3.connectionpool:http://192.168.2.8:80 "GET /statuslive.html HTTP/1.1" 404 None
WARNING:root:Error getting Paradox status update. Doing clean shutdown. Error details: Could not retrieve status information
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 192.168.2.8:80
DEBUG:urllib3.connectionpool:http://192.168.2.8:80 "GET /logout.html HTTP/1.1" 200 None
INFO:root:Logged out from the Paradox web interface.
582

Hey, just wondering if this error has come back for you in the time since the logs where cleared?

583

Hey everyone,

First of all, thank you for this awesome integration!

Questions regarding my situation

My paradox interface shows as of it hasnt started but I seem to getting all the inputs

My log also says that it has started.

Is there any reason why this would happen. Would this break anything for me?

Can I also amend users and change the pin. I was a master user when I had the paradox app.

584

Hello! Unfortunately, for some reason, your add-on cannot be installed. I get the following error message:

The command ‘/bin/ash -o pipefail -c apk add --no-cache python3 && python3 -m ensurepip && pip3 install -r requirements.txt’ returned a non-zero code: 1

What could be the problem?
Thanks!

585

Nope, it’s been running smoothly ever since the service guy came.

586

Do you happen to know what the service software was called? Mine is still disconnecting randomly making the alarm say unknown ive narrowed it down to being the IP 150 module so I am guessing I could have a similar issue as you did.

587

I believe it was babyware. Ask your tech to clear out the logs.

588

Hi all, this addon is still going strong for me. But as I am on a Supervised install, the fickle Hass gods will be forcing me to make the 4th forced migration. I’d like to go to a docker based install, but this addon is the one that’s stopping me from doing that. Is there any way to get this addon in a standard docker container flavor instead of an addon?

589

Did you ever find a working solution to that problem of “statuslive.html” missing? I have the same issue (using the same version of EVO and IP150).

590

Just using another plugin GitHub - ParadoxAlarmInterface/pai: Paradox Magellan, Spectra and EVO, with MQTT, Signal, Pushbullet, Pushover and others

591

Hello,
That is a quite long post with a lot of different issues.
I’m using this app for years to have an idea about my pir sensors. I just went in vacation ant thougt it could be usefull to know my alarm status and arm/disarm from HA (I’m currently still do it by phone).

  1. I copied the new mqtt sensors as follow:

sensor:

  • platform: mqtt
    state_topic: “paradox/alarm/state/1”
    name: “Alarm State”
  • platform: mqtt
    state_topic: “paradox/ctrl/state”
    name: “Connection Status”

the result is :

binary_sensor.connection_status: unknown
binary_sensor.alarm_state: unavailable

I still have, for example:

mqtt:
alarm_control_panel:
- state_topic: “Paradox/Events”
command_topic: “Paradox/C/P1”
payload_disarm: “Disarm”
payload_arm_home: “Sleep”
payload_arm_away: “Stay”
code: xxx
binary_sensor:
- state_topic: “paradox/zone/state/2”
name: “Paradox: Bureau”
qos: 1
payload_on: “on”
payload_off: “off”
availability_topic: “paradox/ctrl/state”
payload_available: “Connected”
payload_not_available: “Disconnected”
device_class: motion
unique_id: “paradox_002”

with
binary_sensor.paradox_bureau: off/on working fine for years
alarm_control_panel.mqtt_alarm: unknown

  1. How to arm/disarm?
    I guess it would be trough “alarm_control_panel” but the status is unknown

  2. how to know if the alarm is ringing?
    is there a sensor to configure?

I’m not using my alarm everyday but it chould be useful to add those 3 functions

Have a nice day,
Ludovic

image
image586×540 21.6 KB