# \[APP\]\[Pro\] Modbus - Connect every Modbus devices

**URL:** <https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497>\
**Category:** Apps\
**Tags:** app, homey-pro, advancedflow\
**Created:** [February 20, 2024, 7:13pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497 "2024-02-20T19:13:05Z")\
**Posts on this page:** 20\
**Page:** 24

<div class="post-metadata">

**Author:** ![Andreas\_Wichmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andreas_wichmann/32/79081_2.png) [@Andreas\_Wichmann](https://community.homey.app/u/Andreas_Wichmann)\
**Post date:** [May 20, 2025, 5:53pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/462 "2025-05-20T17:53:27Z")

</div>

Hello, after a bit of trial and error I was able to read the values from my E3DC home power station without any problems. It works perfectly.

 ![screenshot_238](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/f/af07636bf52a232acff93f8ef5ffb8bec63d8383.jpeg)

Now I am trying to read values from the Lamda heat pump. I have tried everything possible, but unfortunately I always get the error message “A Modbus Exception Occurred - See Response Body [ILLEGAL DATA ADDRESS]”. Here are a few examples:

 ![screenshot_240](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/0/0083fac4478ae9ace36d7d41ecdcc20b5fcbeedd.png)  
 ![screenshot_241](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/9/5935b5b56dac6be7e012f79145f133d55d80adff.png)  
 ![screenshot_242](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/5/656a87788772418a71b04e861933ebbd8867424d.png)

What could be the problem?  
Does something else need to be set on the heat pump side?  
Does anyone have a working example?

BR  
Andreas

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [May 20, 2025, 6:39pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/463 "2025-05-20T18:39:25Z")

</div>

Looks good so far.  
Do you know if the numbers are address or Register? You can try the flow card option “Register, beginnend mit #1”.

---

<div class="post-metadata">

**Author:** ![Andreas\_Wichmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andreas_wichmann/32/79081_2.png) [@Andreas\_Wichmann](https://community.homey.app/u/Andreas_Wichmann)\
**Post date:** [May 20, 2025, 8:01pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/464 "2025-05-20T20:01:57Z")

</div>

… it seems the address.

 ![screenshot_243](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/9/295d80bb87d31f040001c3d8454c3456406b93fc.png)

but how can I find the Register?

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [May 20, 2025, 8:08pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/465 "2025-05-20T20:08:21Z")

</div>

Register and address is the same, just with a offset of 1.  
Address numbers are starting at 0, registers at 1. That means reqister 1 = address 0.  
It depends, what kind of representation the manufacturer is using.

The flow card option only makes it easier to use the numbers from the manual and just select if it’s a register or address representation.

---

<div class="post-metadata">

**Author:** ![Andreas\_Wichmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andreas_wichmann/32/79081_2.png) [@Andreas\_Wichmann](https://community.homey.app/u/Andreas_Wichmann)\
**Post date:** [May 20, 2025, 8:17pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/466 "2025-05-20T20:17:00Z")

</div>

my Values are from this GITHUB-Site: [modbus-templates/Heizungsanlagen/Lambda-WP/holding-registers.tsv at fd3b6a9fd690d0fee70835b9fba0d22e52dcb4bd · ioBroker/modbus-templates · GitHub](https://github.com/ioBroker/modbus-templates/blob/fd3b6a9fd690d0fee70835b9fba0d22e52dcb4bd/Heizungsanlagen/Lambda-WP/holding-registers.tsv)

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [May 21, 2025, 5:36am UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/467 "2025-05-21T05:36:58Z")

</div>

Your flow card settings are correct

- holding register
- address number
- type is also right.

Is your dehice perhaps not the main device (master) and connected to another modbus device? In this case you have to check which Modbus ID the device is using. If you are using IP/port and default ID, you are perhaps requesting the master in your Modbus network.

---

<div class="post-metadata">

**Author:** ![CaptainVoni](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/captainvoni/32/3549_2.png) [@CaptainVoni](https://community.homey.app/u/CaptainVoni)\
**Post date:** [May 22, 2025, 6:53am UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/468 "2025-05-22T06:53:00Z")

</div>

Would it be possible to get When-flowcards for the connection (established and lost) and some tag for the current connection status?

My use-case would be to react on the restart of my inverter, which goes offline every evening for some minutes.

---

<div class="post-metadata">

**Author:** ![Andreas\_Wichmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andreas_wichmann/32/79081_2.png) [@Andreas\_Wichmann](https://community.homey.app/u/Andreas_Wichmann)\
**Post date:** [May 22, 2025, 9:31pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/469 "2025-05-22T21:31:39Z")

</div>

the Lamda heat pump and the heating controller are separate devices. That’s why I didn’t get any values for the buffer tank. All values for the heat pump are correct.

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

Thank you for your quick support

---

<div class="post-metadata">

**Author:** ![Peter\_H69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_h69/32/120855_2.png) [@Peter\_H69](https://community.homey.app/u/Peter_H69)\
**Post date:** [August 1, 2025, 1:53pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/470 "2025-08-01T13:53:51Z")

</div>

Hello all,

I need some help.

I have a sma solar system with a home manager2.0 and two inverters.

If the hourprice go’s below zero I want to reduce power to zero export.

With sma you can do this by writing value 0 in register 40016.

I already have put in a grid guard code to be able to write registers.

If I test the flow below in test mode, all works fine, no alarms.

But when I activate the flow, nothing happends, the inverters keep feeding the grid.

What am I doing wrong?

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

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 1, 2025, 2:09pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/471 "2025-08-01T14:09:55Z")

</div>

Try the flow card option “Register, starting at #1”

Some manufacturers are using addresses, some registers

Tje difference is only, that one starts to count at 0 and tho other at 1.

---

<div class="post-metadata">

**Author:** ![Peter\_H69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_h69/32/120855_2.png) [@Peter\_H69](https://community.homey.app/u/Peter_H69)\
**Post date:** [August 1, 2025, 2:13pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/472 "2025-08-01T14:13:05Z")

</div>

Thanks for the fast replay,

I already tryed this, no result.

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 1, 2025, 2:27pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/473 "2025-08-01T14:27:23Z")

</div>

If you connect with flow card, please disconnect, too. Or set ‘auto connect’ in device settings. Not that an open connection blocks another call.

Do you get an error from the flow card (error output at the bottom, should get red if you test your flow).

You got the register from manufacturers manual?

---

<div class="post-metadata">

**Author:** ![Peter\_H69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_h69/32/120855_2.png) [@Peter\_H69](https://community.homey.app/u/Peter_H69)\
**Post date:** [August 1, 2025, 5:25pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/474 "2025-08-01T17:25:16Z")

</div>

I made a new flow with disconnect also.

No errors while testing.

The register 40016 is the one witch sets the homemanager to zero, always taking selfconsumption in account.

I’m going to dig further into unlocking with the grid guard code, maybe I made a mistake there.

I let you know later

---

<div class="post-metadata">

**Author:** ![Peter\_H69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_h69/32/120855_2.png) [@Peter\_H69](https://community.homey.app/u/Peter_H69)\
**Post date:** [August 5, 2025, 5:57pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/475 "2025-08-05T17:57:06Z")

</div>

Hi Ronny,

I think i need more help.

> **[HM-20-Modbus-NSD-TI-en-12.pdf](https://files.sma.de/downloads/HM-20-Modbus-NSD-TI-en-12.pdf)**
>
> 1062.78 KB

 ![Flow](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/9/89188f759ddf86939e88119912bb153e2474b35d.png)

 ![error1](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/6/862fbe8d7b9d1dc0e2a3867d24a33873e0c8fd01.png) ![error2](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/0/60f91f633d56aef4d1540803854c75f9a06d1c22.png)

All the settings in sma looks fine.

When I test in testmode no erros, if I test in livemode this error appeers.

I made the connection manualy, so I connect and disconnect everey time.

---

<div class="post-metadata">

**Author:** ![Peter\_H69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_h69/32/120855_2.png) [@Peter\_H69](https://community.homey.app/u/Peter_H69)\
**Post date:** [August 5, 2025, 6:03pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/476 "2025-08-05T18:03:53Z")

</div>

![hm2.0setup](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/e/7e52bf25f1463dd4d5bb4166dc8ef024573905ad.png)

I don’t know if this means somethig? Device works fine but cannot be controlled

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 5, 2025, 6:35pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/477 "2025-08-05T18:35:36Z")

</div>

> [@Peter\_H69](#):
>
> I don’t know if this means somethig? Device works fine but cannot be controlled

Yes, that’s ok. The device itself has no controls, only flows.

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 5, 2025, 6:42pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/478 "2025-08-05T18:42:40Z")

</div>

> [@Peter\_H69](#):
>
> All the settings in sma looks fine.

Based on the error I would say you set Unit-ID =1?  
Try ID=2 in device settings - based on page 20 in the manual.

---

<div class="post-metadata">

**Author:** ![Peter\_H69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_h69/32/120855_2.png) [@Peter\_H69](https://community.homey.app/u/Peter_H69)\
**Post date:** [August 5, 2025, 6:49pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/479 "2025-08-05T18:49:20Z")

</div>

I changed id to 2 and no error in livemode.

The sun is almost down here, but maybe it looks working now.

Tomorrow I let you know.

---

<div class="post-metadata">

**Author:** ![Peter\_H69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_h69/32/120855_2.png) [@Peter\_H69](https://community.homey.app/u/Peter_H69)\
**Post date:** [August 6, 2025, 4:43pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/480 "2025-08-06T16:43:24Z")

</div>

Hi Ronny

A small update,

This morning it was not working,

I tried much different settings, no result.

Now I tried registertype INT32 and it looks to be working.

Leds see if it keeps doing this tomorrow on automatic.

---

<div class="post-metadata">

**Author:** ![Peter\_H69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_h69/32/120855_2.png) [@Peter\_H69](https://community.homey.app/u/Peter_H69)\
**Post date:** [August 7, 2025, 7:22pm UTC](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497/481 "2025-08-07T19:22:53Z")

</div>

Everything Worked fine today.

I only have to modify the flow because sma falls back to 100% every hour, but that’s not going to be a problem.

Thank you very much Ronny for this great app.

[Previous page](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497.md?page=23)

[Next page](https://community.homey.app/t/app-pro-modbus-connect-every-modbus-devices/104497.md?page=25)
