Can you post your config? In my experience the addon will tell you if it has any problem but won’t say anything if it’s working. You sure it started right? Have you checked your MQTT logs?
Ok, good call to check the config - the mqtt user was wrong. Corrected that and now I can see one topic only: paradox/ctrl/state. Pair messages are coming onto that topic Connected/Disconnected every second.
Same info can find in the mqtt logs:
1604494750: New client connected from 172.30.33.1 as auto-A473775A-7A06-0E4C-77AA-A7035D5BEE80 (p2, c1, k60, u'xxxx').
1604494751: Client auto-A473775A-7A06-0E4C-77AA-A7035D5BEE80 disconnected.
No errors in the adapter logs.
I’ve seen connect/disconnect situations like that arise from a mismatch in SSL settings.
I guess I’m not using ssl at all.
Adapter config:
IP150_ADDRESS: 'http://192.168.1.107'
PANEL_CODE: 'xxxx'
PANEL_PASSWORD: xxxxx
MQTT_ADDRESS: 'mqtt://core-mosquitto'
MQTT_USERNAME: xxxxx
MQTT_PASSWORD: xxxxxx
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
Mosquitto config:
logins: []
anonymous: false
customize:
active: false
folder: mosquitto
certfile: fullchain.pem
keyfile: privkey.pem
require_certificate: false
I use the IP address for my mosquitto server.
MQTT_ADDRESS: 'mqtt://10.0.0.222'
and this is my moquitto config (also not using ssl)
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
broker: true
allow_anonymous: false
mqttusers:
- username: homeassistant
password: password
readonly: false
topics:
- '#'
log_level: info
I’m guessing it’s your mosquitto config. Try like the above and if it doesn’t work, send mosquitto logs.
What seems to work instead is the default password (i.e. paradox).
Thanks @milhaim, that has been useful for me to figure out why the addon couldn’t connect and the correct value for panel password
@alfredo Is it possible to perhaps add a note to the installation documentation to use “paradox” as PANEL_PASSWORD if the web interface only ask for a panel code and no password?
I now have the addon able to connect to the paradox IP150 module, however, it seems to be requesting a statuslive.html page, which returns a 404. I’ve seen earlier in the post a reference to this file, however, when I log into the IP150 module there’s no page that actually provides a statuslive.html page or anything for that matter that can be used to get an indication of the statusses of various zones / sensors.
The only thing I can do when I manually log into the IP150 web interface is configure various settings. My options under main menu are:
Receiver Configuration
System Information
I/O Configuration
IP150 Configuration
Email configuration
Event Log
Any idea why I’m not seeing any of the other info?
My guess would be that it’s just an incompatible version. Generally this module works with IP150S around 1.4 version…
Here’s the current version I’m running:
IP module
Firmware version - 4.42.02
Hardware - 020
ECO - S079
Serial boot - N/A
IP boot - 2.14
Probably worth adding I’m also running Insite Gold - would that interfere with the addon?
No idea whatsoever. Best to read the docs for the addon.
I can confirm : PAI workfs perfectly, stable and fast with latest IP150 firmwares.
1 Like
HI All
I’ve looked at the pai github project about the paradox alarm interface.
It’s really a good work!!
I’m planning to remove my “CLOSE” tecnoalarm alarm system (proprietary bus / no documentation / closed for only installer) and i’m planning to use one of the paradox panels to interface with my homeassistant installation.
I need a minimum of a 16 wired zones and the cheapest option is a spectra SP7000 with 16 zones built in (no need to buy a expansion).
I see that the serial speed for spectra is only 9600baud, is this a problem?
Also i wish to built a esp32 tcp serial bridge. There are incompatibility or problems with SP7000?
Could i avoid buying sp150 and use babywire connecting to serial bridge? Also for firmware updates?
And a last, have someone interfaced a SIM900 module with SP/EVO panels? (avoiding buying gsm interfaces?)
I know, a lot of questions 
Thanks to all and thanks to all developers for this brilliant work!
Bye
P.
Hi all,
Do you have any idea if this works with 5.x.x firmware(eg. 5.2.19)?
Thanks!
Hello,
That is a quite long post with a lot of different issues.
I installed the paradox add-on and I’m pretty sure that the mqtt settings are wrong. Could you support me?
I successfully connect though 192.168.1.51:20002
My mosquitto broker is running
Do y have to adapt the user and ports?
My paradox add-on is running with paradox settings and mqtt admin credentials
Best regards
Ludo
Hi, as soon as I start the add-on, I get the following in the logfile:
[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 <module>
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: <!DOCTYPE HTML PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html>
<head>
<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='langue.js'></script><script type='text/javascript' src='commun.js'></script></head><body><div id = 'ERROR' style='margin-top:60px;'></div><title>redacted</title><script type='text/javascript'>;var sre = "<table><tr><td align='middle'><div class='box' style='width:460px;margin:80px;'><div class='box-title strips'>" + top.ln_cant[1] + "</div><div class='box-content'><div class='msg' id='MESSAGE'></div></div></div></td></tr></table>";document.getElementById('ERROR').innerHTML = sre; document.getElementById('MESSAGE').innerHTML = top.cant('System Master');</script></body></html>
When I view the source code of the IP150 login page it’s the exact same as the above HTML:
<!DOCTYPE HTML PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html>
<head>
<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='langue.js'></script><script type='text/javascript' src='commun.js'></script></head><body><div id = 'ERROR' style='margin-top:60px;'></div><title>redacted</title><script type='text/javascript'>;var sre = "<table><tr><td align='middle'><div class='box' style='width:460px;margin:80px;'><div class='box-title strips'>" + top.ln_cant[1] + "</div><div class='box-content'><div class='msg' id='MESSAGE'></div></div></div></td></tr></table>";document.getElementById('ERROR').innerHTML = sre; document.getElementById('MESSAGE').innerHTML = top.cant('System Master');</script></body></html>
What I have noticed when accessing the IP150 via a browser is that it only asks for my panel code not the password. I also managed to pick up last night after the whole rabbit hole of trying to actually get hold of Babyware that my firmware is on 5.02.019. Is there a way to disable the password part so that it only authenticates using the panel code?
Nvm, found PAI seems to be the de-facto route to go now.