# \[APP\]\[Pro\] Duco modbus

**URL:** <https://community.homey.app/t/app-pro-duco-modbus/98646>\
**Category:** Apps\
**Tags:** app, homey-pro\
**Created:** [December 22, 2023, 10:38am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646 "2023-12-22T10:38:49Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [December 22, 2023, 10:38am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/1 "2023-12-22T10:38:49Z")

</div>

Hi All,

I’ve an app submitted in the App-store for testing. This is an app for Duco ventilation products based on Modbus (TCP). [[[Repo](https://github.com/tjarb/duco.modbus/tree/main/drivers/master)]

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).

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/3/9310a35f67126270dff6f899b321f50e6f8e54a0.jpeg)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/d/8d7d5ef6fd1046b3afcebdf8676951e42d6324f6.png)

---

<div class="post-metadata">

**Author:** ![MarcoV](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcov/32/12410_2.png) [@MarcoV](https://community.homey.app/u/MarcoV)\
**Post date:** [December 22, 2023, 4:14pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/2 "2023-12-22T16:14:17Z")

</div>

How does homey connect with the ducobox ?  
With protocol is used.

Can only read the params or even controll the fan speed

Good work !

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [December 22, 2023, 5:39pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/3 "2023-12-22T17:39:56Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![MarcoV](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcov/32/12410_2.png) [@MarcoV](https://community.homey.app/u/MarcoV)\
**Post date:** [December 22, 2023, 5:52pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/4 "2023-12-22T17:52:29Z")

</div>

Connectivity Board is a additional board i will assume ?  
Quick googlr search learned this is 200 euro board something right ?

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [December 22, 2023, 6:21pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/5 "2023-12-22T18:21:16Z")

</div>

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.

I thought the price was around €180.

Best regards,

---

<div class="post-metadata">

**Author:** ![GijsP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gijsp/32/71130_2.png) [@GijsP](https://community.homey.app/u/GijsP)\
**Post date:** [December 24, 2023, 7:03am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/6 "2023-12-24T07:03:43Z")

</div>

This is great. 🙂 Let me know once the test version is available in the app store.

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [January 5, 2024, 7:01pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/7 "2024-01-05T19:01:43Z")

</div>

So, update from my side.  
Node (modbus) discovery is now integrated. Now implementing node (device) specific features.

 ![1000010378](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/3/039b4a4cd538b10fdbf2d16ba0f31c9f0f750c3e.jpeg)

 ![1000010380](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/e/ae825722c183a6b72fcab93cab5429cf6b70a04f.jpeg)

---

<div class="post-metadata">

**Author:** ![Nickk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nickk/32/81422_2.png) [@Nickk](https://community.homey.app/u/Nickk)\
**Post date:** [January 6, 2024, 7:49am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/8 "2024-01-06T07:49:48Z")

</div>

Nice! Can you post it already on the apps tore? Or wait a bit until everything is working stable?

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [January 6, 2024, 8:21am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/9 "2024-01-06T08:21:44Z")

</div>

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.

Step by step, we’ll get there.

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [January 9, 2024, 7:51am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/10 "2024-01-09T07:51:37Z")

</div>

@Nickk @MarcoV  
I’ve got a beta available in the store :

> **[Duco](https://homey.app/en-us/app/Ducofocus.modbus/Duco/)**
>
> World of Oxygen.

All read properties for now and Flow level is not the real flow level, Duco said it’s the valve position (not an actual flow measurement).

Best regads,

---

<div class="post-metadata">

**Author:** ![GijsP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gijsp/32/71130_2.png) [@GijsP](https://community.homey.app/u/GijsP)\
**Post date:** [January 10, 2024, 8:35am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/11 "2024-01-10T08:35:09Z")

</div>

@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?  
 ![1](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/4/c45420f6da794fb8fdbe00ad0c5f512b24d3c7ca.png)

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [January 10, 2024, 9:08am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/12 "2024-01-10T09:08:16Z")

</div>

Hi Gijs,

What kind of communication print do you use? it looks like it’s Modbus RTU setting.

You have partnr? Or URL?

Best regards,

---

<div class="post-metadata">

**Author:** ![GijsP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gijsp/32/71130_2.png) [@GijsP](https://community.homey.app/u/GijsP)\
**Post date:** [January 10, 2024, 9:15am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/13 "2024-01-10T09:15:14Z")

</div>

That will be this one: [DucoBox Communication print | Ventilatieland](https://www.ventilatieland.nl/nl_NL/p/ducobox-communication-print/9391/)

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [January 10, 2024, 10:09am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/14 "2024-01-10T10:09:27Z")

</div>

Hi Gijs, what kind of duco box do you have? silent, silent connect, focus, …?

---

<div class="post-metadata">

**Author:** ![GijsP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gijsp/32/71130_2.png) [@GijsP](https://community.homey.app/u/GijsP)\
**Post date:** [January 10, 2024, 11:10am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/15 "2024-01-10T11:10:27Z")

</div>

I have a DucoBox Focus.

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [January 10, 2024, 11:53am UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/16 "2024-01-10T11:53:04Z")

</div>

hi Gijs,

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).

Best regards,

---

<div class="post-metadata">

**Author:** ![GijsP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gijsp/32/71130_2.png) [@GijsP](https://community.homey.app/u/GijsP)\
**Post date:** [January 10, 2024, 12:10pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/17 "2024-01-10T12:10:19Z")

</div>

Ah, looks like the communication board doesn’t allow modbus TCP/IP. Well, I’ll get me a converter then. Thanks for your help! 🙂

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [January 10, 2024, 12:49pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/18 "2024-01-10T12:49:42Z")

</div>

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.

Best regards,

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [January 10, 2024, 1:09pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/19 "2024-01-10T13:09:44Z")

</div>

Gijs,

you may try CAS modbus scanner. Just try to connect to the IP and port 502, ID:1 and read the (single) address 10 (holding or input, doesn’t matter).

Best regards,

---

<div class="post-metadata">

**Author:** ![GijsP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gijsp/32/71130_2.png) [@GijsP](https://community.homey.app/u/GijsP)\
**Post date:** [January 10, 2024, 1:57pm UTC](https://community.homey.app/t/app-pro-duco-modbus/98646/20 "2024-01-10T13:57:55Z")

</div>

Yeah, to make things easy 😅 That is the ‘connectivity board’ (seems to be the newer version of the [communication print](https://data.duco.eu/dam/643A410E-B111-444E-BFC2-65B3749004E7/technische-fiche-Communication-Print-%28nl%29.pdf), which I have). Checked with CAS modbus scanner to be sure, but no luck. Luckily there is sill the solution of the converter.

[Next page](https://community.homey.app/t/app-pro-duco-modbus/98646.md?page=2)
