Paradox Alarm MQTT Hassio addon

djacid · July 19, 2020, 4:54pm

Hello to everyone, dp you know if this addon is compatible with ip150+?

csula · August 9, 2020, 6:02pm

Hi There,

First of all, I’m using this modul for a half a year now without any problem, thank you so much!
Today, I had a mistery and can’t solve it alone. So, I armed the house via HA lovalace panel. Forgot something, went back and disarmed. And after that, the HA constantly shows the system disabled, even if I send directly from developer panel any command. I looked into the MQTT, and as I see the alarm/state topic is not refreshing at all. Every other topic is ok, I see the motion detectors, opening sensors. Just this little alarm/state topic. Restarted HA, IPmodul, HA Paradox modul, everything what I can. If the modul started, I can reach the website of ipmodul which is fine. In the module log is empty.
I didn’t instralled, added or even modified anything in HA after the last successfull opening/closeing.

Please help!

Thanks,
g

csula · August 9, 2020, 6:15pm

Modifying. Only if is send disarm than in the cmnd topic is set to DISARM but the state topic not changing. (The IP modul got the disarm correctly)

alfredo · August 15, 2020, 10:01pm

Hi All!

I’m dropping a note here to inform you that I’ve just released v1.1 of the addon. This is a very minor release, that distinguishes between the ‘arming’ state when the alarm is in its grace time going to be armed (i.e. the transition from ‘disarmed’ to ‘armed’), and the ‘pending’ state when the alarm is in its grace time going to trigger (the transition from ‘armed’ to ‘triggered’). Previously, both states where reported as ‘pending’ so it was harder to distinguish each case programmatically.

To update, simply hit refresh in your Add-on Store and enjoy the smooth update process

Enjoy!

Shaad · August 17, 2020, 7:12pm

Hello !

I’ve just decided to buy a Paradox alarm, an EVO HD more specifically.
I’m trying to figure out which would be the best integration with Home Assistant and using which interface in order to get all individual sensor status updated in real-time in Home Assisstant without any latency.

Looks like I can use (at least) :

an IP150 IP module with your integration : https://github.com/maisken/Paradox_IP150
a PRT3 module with DaveOke ParadoxHassMQTT : https://github.com/DaveOke/ParadoxHassMQTT
serial connection, IP150 or even Serial Over IP (ESP32) with ParadoxAlarmInterface (PAI) : https://github.com/ParadoxAlarmInterface/pai

Which solution would you recommand me as the most reliable ?
Thanks.

scstraus · August 18, 2020, 1:19am

My IP150S with 1.40 firmware is rock solid. I have literally never had an issue with the integration from the moment I first set it up a year ago.

Shaad · August 18, 2020, 7:46am

With which alarm model for information ?

carels · October 14, 2020, 6:30am

Hi,

I keep getting the following error:
Could not login, wrong credentials provided

I’m not 100% sure I have the correct details, could you confirm the following configuration settings?

PANEL_CODE: '1234'   <- would this be the same code to disarm the alarm (i.e. the same code when logging in via the web interface onto the IP150 module)?
PANEL_PASSWORD: 'aabbccdd' <- is this the serial number printed on the circuit board of the alarm?

Eventually too many logins will cause the IP150 module to lock everyone out, is there a way to get the addon to automatically stop if it gets an invalid login response?

Thanks,
Carel

scstraus · October 14, 2020, 10:30am

IIRC, one is the code for the alarm, the other is the credential used to log into the IP150S using a web browser.

J-P1 · October 20, 2020, 3:00pm

Hello,

I have 2 Alarm Systems which both have their own IP150. What would be the best way to integrate them both within the same Home Assistant? Can we install this add-on “twice”?

Thank you for the great work!

scstraus · October 20, 2020, 3:52pm

I don’t think you can have 2 instances of hass.io addons on the same hass instance, but you could use another IP150 to mqtt gateway like https://github.com/Tertiush/ParadoxIP150v2 for the second one. Or you could get a Pi 2 and install hass.io and this addon on that and just subscribe to the MQTT messages from there. I’ve had to do things like this for some bluetooth devices in the past, works great.

J-P1 · October 22, 2020, 3:51pm

Hello, I have a quick question. Regarding this add-on, one of the benefit is that it uses the “web” port so that it frees up the “software” port. I am able to use the iOS iParadox application successfully while this add-on is running, which is great in case I need “backup access”.

However, I couldn’t connect with Babyware at all, which I believe is supposed to use the “software” port as well. Is this normal behaviour? I had to program new user codes and I just couldn’t connect. So, maybe there’s a setting, or I need a different version… I often need to program codes and it would be convenient to maintain Babyware access.

Thank you!

Babyware

tilentravnik · October 22, 2020, 4:20pm

Babyware can not connect to the panel if PAI add-on is running. I don’t think there is a way around this.

mihaim · November 2, 2020, 4:29pm

Hello,

I’m trying to setup the addon on a IP150+ module, however it doesn’t require a password when connecting via the web interface, but only the panel code, so I don’t really know what to do with PANEL_PASSWORD config. I’ve tried to leave it empty but the config file becomes invalid.

Any ideas?

Thanks,
Mihai

scstraus · November 2, 2020, 7:30pm

Did you try setting it to an empty string like “”?

mihaim · November 3, 2020, 8:10am

Yes, I’ve tried different variations of empty ("", ‘’, null) but the addon would crash at start.
What seems to work instead is the default password (i.e. paradox).

The reason I say “it seems to work” is because the addon doesn’t crash anymore, however in the Entities section it shows up Unavailable, so I’m not really sure it does work indeed. Any thoughts on how can I check that?

The addon log looks clean:

[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.

Thanks,
Mihai

scstraus · November 3, 2020, 10:59am

In my experience, if the log is completely empty, the addon is working. Doesn’t give much confidence.

You won’t get sensors until your MQTT sensors are correctly set up. Best is to go browse for your topics on your MQTT server using a tool like MQTTlens and see if the integration is publishing data when you open windows that are monitored by the alarm.

mihaim · November 3, 2020, 11:44am

Thanks @scstraus, I’ll try do that, although I believe the integration doesn’t connect to the IP150+ as it shows Unavailable.
paradox

mihaim · November 3, 2020, 12:13pm

Ok, done the test, and as expected nothing shows up in the mqtt broker. Perhaps the integration doesn’t connect to the IP150+ module, but no error in the log file.

Shaad · November 3, 2020, 3:48pm

I guess you could create a custom addon with this addon sources and run both of them in parrallel, one for each of your IP150 modules.