Hello, I have a Paradox alarm system that I would like to integrate into my dashboard. To see the status, arm and disarm the system. There must be a way to do this knowing that the system is accessible through its IP150 module. Currently, I can control it using an Android application in which I have configured the ip address/port of the module.
Looking it over it might be possible to develop a custom driver for it, but you’ll either need to get some documentation on the API or reverse-engineer the data using a packet sniffer.
The Paradox Security IP150 modules don’t expose an API for public use (or at least they didn’t).
There used to be a few projects that would scrape the data from the IP150, to varying degrees of success. They may have progressed, so might be worth searching for those on GitHub.
If you have an EVO Panel, then the PRT3 COMBUS Module has a textual API with documentation. This is how I integrated mine, over an IP-Serial converter so the Hubitat can talk to it.
I have a Paradox system as well. For this one to integrate with Hubitat I am planning to use a rough hardware method such as adding one more remote ( very easy to do so, explained on YouTube) and wring the contacts within remote via a zigbee multi relay ( lots of them on Amazon or Aliexpress ) . That will allow me to arm and disarm via Hubitat without touching anything else.
1 Like
Oh, sound interesting. Please let me know your progress...
Hello, I'm about to transfer my Paradox System from Control4 to Hubitat. I have a Paradox EVO Sercurity Panel with Two - TM50 Touch Keypads and my Intergration Module is the PRT3. Can you advise me what I need to do to integrate my system onto Hubitat? Thank you in advance.
If you're familiar with the core setup of the PRT3 Adapter on the EVO, and have a RS-232 to Ethernet adapter (mine is a WIZ110SR), then it's just the Plugin code that you need. My Device driver runs entirely on the Hubitat, with only the RS-232 -> Ethernet adapter as the external-hardware requirement.
My [Hubitat] code to do this currently isn't published. I'll push it to github later this week. It's been 5yrs since I converted it from my original Vera codebase, which itself was old (c 2008), so no guarantees on the quality.
There's also no doc, since I wasn't planning to support it.
In the coming months, I plan to switch mine out for one that uses/exposes MQTT, via the Paradox IP150.
I had hoped to try out Paradox's IP150+MQ, or the IP180, but that seems to involve a hot-mess of [proprietary/installer-only] panel upgrades 
