PLC with lots of DIO’s for pushbuttons and switches (old part of the initial system)
Openhab server
Hue hub with lamps, Gledopto dimmers and Icasa dimmers
Some other devices like kodi, Onkyo, …
The PLC have the logic, controls the scenes, lighting, heating etc.
Openhab is used for the remote control, is communicating with the PLC by modbus and is used as a many protocols to modbus translator.
As it is a rather complex setup I was thinking to simplify it, right now between the push of a button and the turning on of a light, there are a number of devices in between: the PLC, the openhab server, the Hue hub.
Ideal should be connecting all the buttons directly to the openhab server and controlling the zigbee devices without the Hue hub, but I have no idea how to accomplish this.
What hardware should I look out for?
The bit we’ve missed is, how are these buttons connected now?
I’m guessing wired to the PLC.
Some openHAB hosts like Pi will offer GPIO pins, but might be limited for a lot of remote buttons.
There aren’t a lot of good home market products for “many pushbuttons” interfacing.
I use “dumb” Modbus DIO modules for this myself.
But frankly you might just as well stick with the PLC and have openHAB continue to read its inputs, even if you move the control rules to OH.
Correct, IO’s are connected to the plc. AI’s also.
Right now, all the logic happens in the plc althoug some rules are needed to translate modbus to hue.
If I only could control the Hue’s from the plc.
The Deconz dongle is great, but not good for my setup as it needed a lot of sw to communicate with.
I gave up. I could get it running but then the openhab interface failed. And when I disabled it the OH interface came back alive. It’snow again connected to my synology through docker. However I still would like to bring all together on my oh box…
deCONZ/phoscon starts a web server on standard port 80. If you use that port for OH or nginx or anything else already it won’t work. Here’s where you can change the port: