I already made a pull request, but it hasn’t been accepted yet… I also wouldn’t mind to make a little howto for the github page, but first we need @alfredo to come back and pay us a visit so he can update the github repository…
Thanks for doign the pull request scstraus. 
As for the howto, I am sure it will benefit others since this addon requires a bit of tech knowledge to get it working.
Hi all,
Sorry for the delayed reply, as I found some spare time to look into this. I’ve now released v0.6 of the add-on, with the arch issue fixed. I take it was a (not-so-well documented?) breaking change in hassio at some point, that made that configuration parameter mandatory.
Thanks @scstraus for proactively proposing a pull request. Much appreciated!
I totally welcome a decent readme for the github repository, it’s very much needed. If anyone has time and willingness to help, please go ahead and I’ll try to review in a decently short lapse of time! Thanks all for the support!
Cool, I’ve only just gotten the addon working myself as I tried to order the IP150S 1.40 from Megateh as recommended here but they sent me the IP150 with 4.40 firmware instead (despite my having specifically ordered the other one) . They don’t have any 1.40 IP150S’s left. So don’t order from them…
I sent it back and got a real IP150S with 1.40 from eBay… @digieurope still has his, and these guys claim to still have 5 left (I emailed them to confirm), if anyone else is looking for one.
So, I just got the addon finally working a couple days ago… So far I’ve only played with the sensors (which are working perfectly). I haven’t played with arming it or getting the alarm panel working in lovelace yet… Once I get it all going, I will try to put together a comprehensive readme for the github repo and open a pull request against it.
Can somebody suggest a way to troubleshoot this addon?
I’m trying to follow other people’s posts as closely as possible, but I see no messages in any log - Paradox add-on, Mosquitto, home-assistant.log - no error nowhere - yet all defined entities are in unknown state.
I tried setting SSL on and off on the IP150s, at one point I got a flood of warnings that the certificated can’t be verified but then this also stopped.
The only way to tell that the addon is connected to the IP150s module is when I get the ‘userX already logged in’ message.
For completeness:
IP150s fw 1.40.00
Hardware 020
Panel SP65
FW 5.18
Hassio 0.91.4/RPi3B
In my experience, if there’s no log than the addon is working correctly. A couple things to try:
-
Can you correctly see all your zones and alarm state when you log directly into your IP150S?
-
Using this addon, use the webUI to subscribe to the topics you have defined and see if there’s any activity. If there is, then you defined your sensors wrong… If there’s not then you have a problem with the addon.
Thanks for the suggestions.
Connecting to the web interface of IP150s (provided that I stop the add-on) works correctly.
I’m using the Chrome extension MQTTLens to connect to Mosquitto and I’ve subscribed to all defined topics:
“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”
however I can only see one message in total for them - “Connected” on paradox/ctrl/state.
Did you put a # after the topics to ensure it grabs the subtopics?
1 Like
Hi @scstraus,
Thanks for your involvement. It indeed seems time is coming for this add-on to finally get a README. I recently received a contribution on github for a base README, which is now live. Please feel free to propose further edits as you experiment with setting up the add-on.
right. that was it. so this add-on is successfully pushing messages to the broker. I’ll try to redefine the sensors.
Hello, I am not running Hassio but I am using Docker for Windows with containers for home-assistant, portainer, mosquitto mqtt. If anyone is using this setup, I managed to get this addon working by using the following Dockerfile:
FROM python:alpine3.7
COPY . /app
WORKDIR /app
RUN pip install -r requirements.txt
CMD python3 ip150_mqtt.py options.json
configuration.yaml looks like this:
alarm_control_panel:
- platform: mqtt
state_topic: 'paradox/alarm/state/1'
command_topic: 'paradox/alarm/cmnd/1'
name: alarm_house
payload_disarm: 'DISARM'
payload_arm_home: 'ARM_HOME'
payload_arm_away: 'ARM_AWAY'
qos: 1
binary_sensor:
- platform: mqtt
state_topic: "paradox/zone/state/1"
name: "x1"
payload_on: "on"
payload_off: "off"
device_class: motion
- platform: mqtt
state_topic: "paradox/zone/state/3"
name: "x2"
payload_on: "on"
payload_off: "off"
device_class: motion
- platform: mqtt
state_topic: "paradox/zone/state/4"
name: "x3"
payload_on: "on"
payload_off: "off"
device_class: motion
- platform: mqtt
state_topic: "paradox/zone/state/5"
name: "x5"
payload_on: "on"
payload_off: "off"
device_class: motion
Lovelace card:
type: alarm-panel
states:
- arm_home
- arm_away
entity: alarm_control_panel.alarm_house
name: Alarm
All it’s working as expected, stay arming, full arming and disarming, also the binary sensors seem ok. I will play more when I will have time, because it needs automations, when the alarm is triggered, notifications, etc.
!Important IP150 INFO
I had v4.4 on my IP150 with Insite Gold and managed to downgrade to 1.39. Here is the link with information about downgrading. I will gladly help you if you encounter issues.
1 Like
Hi @renzorlive,
Thanks for sharing this! I’ve added your lovelace config snippet to the main project README, as documentation is building up.
I’d also like to add information about running this as an isolated Docker addon. However, have you considered taking inspiration from the current Dockerfile? Specifically, you could try with the following Dockerfile:
FROM python:alpine3.7
# Copy data for add-on
COPY run.sh ip150.py ip150_mqtt.py requirements.txt options.json /
RUN apk add --no-cache python3 &&\
python3 -m ensurepip &&\
pip3 install -r requirements.txt
RUN chmod a+x /run.sh
CMD [ "/run.sh" ]Then, have run.sh be something like
while true
do
python3 ip150_mqtt.py options.json
# 20 seconds should be enough to ensure the session expired on the server
sleep 20
doneThe above should do a couple of things:
- Only copy the necessary files in the Docker image
- use a small wrapper around the app that automatically restarts it if it crashes. Hopefully this will never be needed
but there used to be times when this addon was quite less stable than today!
If you could let me know your mileage, I’d be happy to add instructions (or somewhat add this alternative Dockerfile to the source, for quickest reuse).
Thanks!
This is working on my setup with the following changes:
Dockerfile:
FROM python:alpine3.7
# Copy data for add-on
COPY run.sh ip150.py ip150_mqtt.py requirements.txt options.json /
RUN apk add --no-cache python3 &&\
python3 -m ensurepip &&\
pip3 install -r requirements.txt
#RUN chmod a+x /run.sh**This line is not needed for windows hosts because all files are copied with x permission**
CMD [ "/run.sh" ]
run.sh
#!/bin/sh
# Shebang needs to be here, else it returns: standard_init_linux.go:207: exec user process caused "exec format error"
while true
do
python3 ip150_mqtt.py options.json
# 20 seconds should be enough to ensure the session expired on the server
sleep 20
done
Thank you for your work!
Finally I got my sp5500 working. Anyway to setup a panic button?
I still have trouble setting this up.
Deleted ver.0.5, started from scratch, copy-pasted config from readme and replaced passwords/addresses.
No errors in log (which I assume means add-on connects both to mosquitto brocker and to the IP150s).
I can see the updates in the respective topics via MQTTLens.
alarm entity is in unknown state and pirs are constantly off 
try typing them not copy and past. They format stuff up all my config.
1 Like
My problems are definitely connected with the Mosquitto add-on I’m using.
I reinstalled the add-on from scratch last night, messing up the config with my sleepy fingers.
Today I found an error message per every IP150 PIR event.
I managed to fix the Mosquitto logging following instructions in this discussion, however I’m back to all PIR sensors being off.
Can you share which MQTT broker you guys are using?
I’m using this one:
MQTT Server & Web client
Mosquitto MQTT Server bundled with Hivemq’s web client
Works good. I’m having a problem with the MQTT alarm panel not sending the appropriate messages, but the sensors work fine and I’ve verified I can arm/disarm by sending the requisite MQTT message manually to the MQTT server, so the MQTT server itself appears to be working perfectly…
mosquitto addon as well
{
“logins”: [
{
“username”: “XXXXX”,
“password”: “XXXXX”
}
],
“anonymous”: false,
“quiet_logs”: true,
“customize”: {
“active”: false,
“folder”: “mosquitto”
},
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}
I replaced my broker with ‘MQTT Server & Web client’, re-configured from scratch.
I can currently subscribe to the paradox/zone/state/# topic from HiveMQ web client or mosquitto_sub and I can see the updates happening … off status for all (32) PIRs, on when something is triggered, etc.
None of this is reflected in the UI - I’m using the Lovelace GUI interface to seup my sensors.
I can manually flip one of the sensors publishing the ‘on’ msg to the broker and only then is the status change visible in the GUI…
What else can I try?