Help build binding for Paradox Alarm Panel with IP150


I have been working on trying to control my Paradox Alarm panel with an IP150. We have made some progress reverse engineering the web interface and [tracstarr] has made some excellent progress at github and I want to know if someone can help create a binding for Openhab. I unfortunately cannot program properly, but can help as much as I can. Or if someone can point me in the right direction of how to do this? I did see that one can call javascript from Java, so I assume that would be the best way forward.

We have a thread running on the project at Micasaverde Vera Forum. The issues at the moment is that it is Windows based (I’m running Linux and Mac) and needs a bit of background processes (servicestack, selenium webdriver and phantomJS ).

The process basically logs into the IP150 modules web interface, populates some variables, and the requests the current status every second with javascript. We can’t get the official API, but perhaps the DSC binding could be tweaked to handle this.

Could any help?

1 Like

I seem to have found that there is a serial communication protocol that is available on the IP150. It seems it speaks on port 10 000. The protocol doc is here:

Wow, glad to see someone else also needs this! I also need a binding for Paradox, using the IP150 on an MG5050 module. I configured the alarm remote so one of the buttons opens my gate, but having this on OpenHab will open a big world for me. I also run Mac client with a Linux server, but did the configuration of the MG5050 via IP150 using my wife’s PC.

Would love to see progress on this topic (but sadly cannot programme to assist 8-(

Jéan. (my first post here on OpenHab!)

I did get an SDK from Paradox, but it is windows .NET based which limits me a lot. If anyone wants to have a look at it, let me know.

hi, I would love to have a look at the SDK. I have Java background and don’t think .NET would be a problem if the source code is available.


Sent you a message with the link. I don’t have a windows machine to test anything on. Let me know how you get on.

Hi mkent, I’m also interested in the same SDK. Could you please send me the link?


Hi mKent, I’d also love a peek at the SDK. For nothing else that wanting to be able to generate notifications when events happen on my alarm.

Hello, I would love to get the SDK, can you help, I am planning on reverse engineering in node-red

Soooooooooo, I’m making the switch from SmartThings to Openhab and started looking for paradox bindings only do find myself here. I’ve looked at the SDK and unfortunately I can’t even try playing with it as my alarm is a Paradox 192 (which i suspect many people have) and isnt “compatible” with the SDK. Looks like I’ll have to try and take what i’ve learned and have on my github project (posted above) and learn to create an openhab binding.

That being said, at least with what I did in .net I’ve had issues over the past few months in using it. I won’t bother to bring them up here as it looks like a re-implementation will have to be worked out for openhab as I’d rather have a binding rather than going through the api I created. If that’s even possible.

However, I’ve only been running OH2 for a day now and haven’t gotten into setting up a dev environment etc. I’m still learning the terminology and how to set things up. However, if anyone can help I’d love to get this started.

I’m using Openhab 1 and haven’t tested OH2 yet, but I can help with any Openhab questions you have.

So at least for me right now it doesn’t look like a native connection via their sdk is possible given the hardware I have to work with.

That said, for now I think I have a simple solution given the work I’ve already done. It’s not optimal, but should get me (and maybe others) up and running. I’m going to modify the current rest api service in the github project to write to MQTT broker. Since openhab already has the ability to read inputs from MQTT it seems like a simple logical step. It can also write out, so I can read from MQTT as well in the services. Now this is all untested and just an idea right now. Hopefully it can bridge the gap while dealing with the learning curve of openhab.

I use MQTT for some things with Openhab and find it works very well. I’ll check if they have an update, but I do think it’s stupid to need a Windows machine running just to interface to an alarm panel. Hopefully they are developing something a little more cross platform.

yep. I agree. However, the service I do have now for the panel can run on linux. That’s where I run it now. You need mono installed though. Having issues with mqtt right now that I’m trying to unwind first.

Well, with very little code change to my current service I got mqtt integrated. I can publish any zone/partition change and have some items defined for each as subscribers. Works quite well. Since the arming functions are just rest calls, that’s pretty easy too.

I still have some testing to do and some additional changes I want to add (like a heartbeat publish). It’s not the perfect solution, but it’s one that is working and hopefully can hold up well. Only time and testing will tell. I’ll try to push my updates by early next week with some examples.

I’m going to have to try the MONO thing on a Banana PI. Any hints?

Looking forward for your progress.

I would love to have a look at the Paradox SDK. I have .NET background, so I hope that I can help. Can I get a link to the SDK?

@tracstarr OK, so I have installed mono and phantomjs on my Banana Pi. I installed a precompiled version of PhantomJS which is 1.9.8 I think. Is that OK? I’m doing a walkthrough as I go so we can add that to the Readme on your github and I can at least contribute some documentation.

Also, have you added your MQTT adjustments to Github yet?

Sent you a message with the link.

So I can’t confirm if the latest phantomJS will work or not. In the readme of my code I noted that the nugget package wasn’t updated to latest phantom yet so I had to use older. I’ll try to check if that has changed. However, I am away this weekend and won’t get anything done until Monday at the earliest.

I have also found that the MQTT library I used requires it’s own build for mono and thus the nugget package won’t work. I have to investigate that in more detail. So as of now the MQTT only works on windows. If I can’t figure it out i’ll just have to find a different library.