I’ve an app submitted in the App-store for testing. This is an app for Duco ventilation products based on Modbus (TCP). [[Repo]
Initial beta release is meant for stability tests and for now it only supports the master box (focus, slient), but other products like valves and room modules will be added later on (incl auto discovery of the masters sub-devices).
it’s through modbus TCP and it should be compatible with any Duco ventilation system. Duco is very consistent in their modbus registers.
The app now only reads parameters but using the Holding registers you can control / override the devices.
I think the best way is using the lower level limit, this way the Duco ventilation system can always “overrule” your setting in case of high humidity, temperature or CO2 levels.
For the older duco ventilation boxes (focus, silent before 2017) there’s modbus rtu integrated. If I’m correct from 2017 there’s an additional TCP interface board required.
There is one version pending for acceptance, after acceptance I can release test versions.
There has to be done a lot before everything works. I’m still learning every day
New to homey DSK and javascript/NodeJS (I’m a realtime embedded systems developer).
But I’m very impressed how Homey build their platform. It works very nice (documentation could be better).
The app runs stable, I run longterm tests daily. It doesn’t crash and if communication fails, it recovers by itself. And using limitted resources, could add up to 100 nodes.
@Tjar Could you help me out a bit? I have a Focus with the communication print and fixed IP adress, but I am not able to add the device using the prefilled settings. Is there a modbus on/off setting hidden somewhere?
I’m not familiar with the communication board. If I’m correct the default settings are 9600baud, no parity and 1 stopbit, ID:1 and address offset 1.
I think the “address” field is the ID field.
I’ve a Moxa Mgate on my Duco focus. That works (set to higher baudrate).
the manual says it supports modbus tcp:
“02.F Can Modbus TCP be read by default on a DucoBox?
Yes, a Modbus converter is no longer needed as with Modbus RTU.”
I don’t really understand why you should configure the RTU, except when the communication board interfaces with the ventilation box using modbus RTU.
Yeah, to make things easy That is the ‘connectivity board’ (seems to be the newer version of the communication print, which I have). Checked with CAS modbus scanner to be sure, but no luck. Luckily there is sill the solution of the converter.