Why use a separate OH instance? Because it’s a security device!! By using a dedicated instance for this interface I was able to lock this device down pretty tight. So I’ve basically turned the panel into a network device by mapping REST and MQTT to the various functions of the NX-586E. This OH instance consist of the serial, mqtt, ntp, mysql binding for persistence, one items file, and one rules file so it’s very simple and light weight. I’m using openhab to connect to the NX-586E and map the output to MQTT topics. I have a pre-existing VM infrastructure so I made my controller virtual but a raspberry pi would be perfect for this use and you can likely power it with the panel. What I did (and my suggestion), I basically created a software controller for the panel. Especially when the binding requires rules to function (looks like the binding in the last link posted uses rules). ![]() It’s so easy and reliable i’m not sure a dedicated binding is required. The NX-586E spits out status to a “coded” string also but it’s 1001% easier to decipher. ![]() You also have to format commands to the panel a certain way. My panel already had a serial port for home automation but it spits out what looks like random characters that you have to interpret to figure out what it’s saying. It’s basically a virtual keypad and it’s fairly cheap. ![]() I also have a NX-8E panel but I use the NX-586E module to connect to openhab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |