Digiplex Evo

0 views

Skip to first unread message

Carlee Members

unread,

Aug 3, 2024, 4:59:39 PM8/3/24

to beitratabid

I already developed some integration which is confirmed to work in production (in my environment). It is available here:
GitHub rmichalak/openhab2-addonsAdd-ons for openHAB 2.x. Contribute to rmichalak/openhab2-addons development by creating an account on GitHub.

Communication protocol is quite extensive and I currently only implemented part of it (but the most important part, which should handle 90% of your requirements). I do have plans to implement the rest, but I would really appreciate your feedback and help, If there is anyone willing to participate in testing in their environment or on a different type of Digiplex/EVO alarm system, or just sharing their thoughts about the idea/code/whatever.

Hi, all you need to start playing with the binding is described in a README.md file which is a part of my github repository (see the link in the first post). If you have any specific question or problem that is not covered there, please ask here. I would be happy to help.

My log shows the following error:
2018-12-31 15:52:28.235 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.digiplex-2.3.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.digiplex [213]
2018-12-31 15:53:32.034 [ERROR] [org.openhab.binding.digiplex ] - FrameworkEvent ERROR - org.openhab.binding.digiplex

You should double check if serial port configuration (name, baud rate) in binding configuration is correct.
Baud rate should be in line with Paradox configuration, as described in your alarm system manual.

if serial communication works and binding configuration is correct, you should check the steps described here:
openhab.org Serial - BindingsThe Serial binding allows openHAB to communicate in ASCII over serial ports attached to the openHAB server.

I have to mention that in the README file. I suppose the problem will gone once my binding is integrated with official repository and installed in a standard way, as all dependencies will be installed automatically.

I used ser2net/socat for development of this binding and it worked flawlessly. I recall different kind of communication problem though. My version of PRT3 module has both usb and serial connectors, and my first try was to use usbusb cable to connect to RPi, by I found it very unstable. For the reasons unknown to me PRT3 module just stopped responding to my messages after a while. This is why I put reconnect mechanism into the binding, but even then I had to physically reconnect the cable from time to time to restore communication.

My second attempt was to use serial port of PTR3 module and connect it to USB port of RPi - and it worked (and is working till now) flawlessly. No lost messages, no stuck responses. So I wonder if your problem may also be related?

Looking forward to see your changes (once I rebase my changes - still remember that!) but please make sure that your communication problems are not related to the problem described above before you go too far with your implementation.