De Dietrich/Diematic (Modbus) to MQTT Interface

you are right, I thought this image was a front view of the boiler-side connector


Thx for the help :grin:

Hello,
I am so happy that I found this solution for getting my DeDietrich Boiler connected to HA.
DeDietrich is very rare in Germany and not so well documented.

In my case, I would need to connect through WIFI. Was anyone able to achieve this?

When I compare the configuration of the USR-TCP232-306 to the manuals of the PUSR WIFI models, there are quite some differences.

  1. There is no dedicated Serial configuration section. Just something called WIFI-UART

  2. I found nothing to set it up with work-mode TCP Server. They only mention work-modes are Transparent, Serial Command Mode, HTTPD Client Mode & Modbus TCP <=> Modbus RTU

Has anyone a suggestion how to get the Boiler connected via WIFI?

Many thanks in advance,

Sebastian

Hello,
After you fix wiring - is it working ?
Im asking because Im at your stage - USR-TC232-306 send message that boiler is offline. I did your wiring mistake, after that I did it correct, but status is the same. I`m with MC45 with Diematic 3 with two modbus connectors.
also I want to ask you about your wiring - white and black are A nd B. Brown and red are ? because I did not see them in original manual.

Hello,
Have a look here:

Benoit

Bonjour Benoit,

thank you very much for guiding me to this. I will test it with the PW11 probably in december!

Hello,
First I wanna say that that your job is AWESOME! Thanks, thanks, thanks!!!

I manage to install all yesterday and it works fine for now.
I want to ask you is this normal and if it`s not
 do you have idea how to fix it:

  • there is some difference in sensors - According to MC45 boiler power is 8 or 11, but in HA shows 39%. when oit goes to 20+ on Diematic panel, HA show 45-55%
 How to caliberate HA to shows real power % ?
  • I cannot set target Temp from HA. it`s stays to 17.5 all the time. From Diematic III Panel I was set it to 24C day temp. If I change from 17.5 to 21 from HA
 after 20-30sec boiler stops (temp is below current). If I change baclk to 24C, after 20-30sec boiler starts
 As I see, I can control boiler, but in HA stays to 17.5 all time.

I don`t have Internal Temp Sensor (room temp) to circuit A for the moment. I will try to find and install some type temp probe these days (must see whitch will be compatible, If you have any suggestions it will be nice).

For info: I have only circuit A, I dont use for hot water, only for house heating.

Hello,

after reading W630s model doc, it should work with it with following settings:
-serial server transparent mode
-packet time of 50ms , packet length of 256

I think somebody have already done it with this kind of material but I didn’t found any forum message to confirm it.
Benoit

Hello,

Power is (to fast ?) extrapolated from fan speed when Ionisation current is above 0 here (Diematic.py / line 359) :
self.burnerPower=round((self.registers[DDREGISTER.FAN_SPEED] / FAN_SPEED_MAX)*100) if (self.ionizationCurrent>0) else 0;

Values can vary depending boiler. You can adapt FAN_SPEED_MAX.

For Zone A settings, they shoudn’t be displayed without Internal Sensor. Have you enable the force circuit A flag in the conf file? I don’t understand what behaviour could be waited from temp setting if you do not have internal temp sensor.

Regards,
Benoit

PS: the interface has been done with reverse engineering and testing on one kind of boiler (MC25), so it’s difficult to coer the wide range.

I Did not know that, will try to calibrate is to show correct power value. As I see its exact 25% difference (when its idle, HA report 25% power).

No, I did not enable this flag. I folow your manual and I did not see such thing/manual.
I totally new in this
 HA control over MC45 is from 24 hours
 for the moment looks very cool - this gave me all that I can need.
Last week I realized that I dont have internal Temp sensor... I ask why is installed like this 15 years ago... No reasonable explanation. It works, but maybe not optimal. Now Im searching for Temp probe/sensor that is compatible with MC45 boiler/Diematic III. Do you know is there any specs for that sensor ?

After your explanation about power %
 My only issue is Day/Night temp in HA
 it`s always 17.5C (you can see on my screenshot in previous post). Today, just before leave the house I change from HA from 24C day temp to 21C and 5min ago when I go to Boiler for last check it was set correct to 21C
 But in HA is still 17.5C


Also want to ask you - do you know why I have “mode zone A” - unknown status ?


As new User I cannot reply again (some limitation up to 3), so here is update:

I found here FM52 room control with temp sensor and just install it.
All problems disapiar at once!
Power/load is reported correctly !
I have internal room temperature
I can see Mode Zone A status
I can see what Temp i set now for day and night
I can see pump power (I really dont know how this is related to this room thermostat/control
)

So, sorry for my previous stupid questions and thanks again for your great work here.
I decide to tipe for update, because some of my ussues dont look to be related to this internal control that I was miss and I want to give info for other users to avoid my problems and mistakes.

Hi all,

I have succesfully implemented the Modbus communication to my De Dietrich boiler (Innovens MCA 15/25), using home assistant.
Everything is working fine for a few years.

However lately I have seen that the boiler restarts itself multiple times a day. There is no alarm logged in the alarmhistory (most recent alarm is from 2023). The water pressure is okay (1.7 bar) and I cannot see any reason why the boiler would restart itself.
I have made a small movie, where you can see on the display that the boiler suddenly restarts.

I would like to contact a technician, but they will surely start replacing boards and other stuff, without first knowing the root cause.
I couldn’t find any other forum with so much knowledge about De Dietrich. So I was hoping that anyone had some ideas, advice?

Home Assistant is polling the boiler very slow (I’ve slowed it down to 1 request per minute). However that doesn’t seem to help.

Thanks!
Thomas.

Hi Thomas,
Not sure if anybody can help in this forum but wish you luck in solving the issue

Does the boiler restart or it just loosing the connection with the controller? Do you hear that boiler stops and starts again?

In my Modulens G when I restart the boiler it takes few minutes it works again as the boiler starts the ventilation procedure every time (code M20). I can’t see similar behaviour in your movie, but maybe your boiler does not force the ventilation procedure. Did you try to restart it manually and see if the boiler starting procedure is different to what you recorded?

Regards,
Pawel

1 Like

Hi, thanks for your reply. There is most definitely a difference between a cold boot (me turning the mains off and on) and the ‘internal’ reboot that I am experiencing. When I do a cold reboot, the boiler starts indeed with te venting procedure. This doesn’t happen during an automatic restart. But during that automatic restart, I do hear each time that it (re)ignites the flame.

anyone? pls.

Hello,

Thanks to @BenoitS, I want to report another successful setup with HA integration.
Heater: HPI G Hybrid 200 ASL 8kW / Diematic4
(integrated Inverter 8 kW + gaz 25 + 200l ECS)
RS485 adapter : Eflin EW11 (very cheap ~10€, works very well)

For the time being, all basic info (boiler/zoneA/zoneB/water) are correctly reported to HA
I will dig now how to add more specific sensors (linked to inverter for example)

Hello @BenoitS,

I have started my work on getting my DeDietrich Boiler connected to HA.
First of all, I noticed that the described way to create a HA Add-On from the WIKI does not work anymore.
I found a way how to build it and I will post, once I get it all working.

For the connection, I am using the Protoss PW11 RS485 to Wifi adapter.

Suprisingly, I worked like a dream after fireing up the HA Addon. I was able to read and control everything. However, after a while it stopped working.

Now, I am getting the “ModBus Master Slave Synchro Error” message all the time.

Maybe you can help sorting it out.

Below you can find an extract of the log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2025-01-13 10:09:01,390 - __main__ - CRITICAL - Modbus interface address: 10.10.50.120 : 8899
2025-01-13 10:09:01,390 - __main__ - CRITICAL - Modbus regulator address: 0xa
2025-01-13 10:09:01,391 - __main__ - CRITICAL - Broker: 10.10.50.10 : 1883
2025-01-13 10:09:01,392 - __main__ - CRITICAL - Topic Root: home/heater/boiler
2025-01-13 10:09:01,392 - __main__ - CRITICAL - Hassio Discovery Enable: True
2025-01-13 10:09:01,393 - __main__ - CRITICAL - Hassio Discovery Prefix: homeassistant
2025-01-13 10:09:01,393 - __main__ - CRITICAL - Regulator type is Diematic3
2025-01-13 10:09:01,503 - Diematic - INFO - Using tzinfo ('CET') for Boiler time sync
2025-01-13 10:09:01,508 - Diematic - WARNING - Init Link with Regulator
2025-01-13 10:09:01,609 - __main__ - DEBUG - Paho MQTT version 2.XX or more detected, using callback API version2
2025-01-13 10:09:01,642 - __main__ - CRITICAL - Connected to MQTT broker
2025-01-13 10:09:01,645 - __main__ - INFO - Publish :home/heater/boiler/status Offline
2025-01-13 10:09:01,709 - __main__ - INFO - Sending HA discovery messages
2025-01-13 10:09:05,470 - DDModbus - DEBUG - Frame received: c3f2fe6afefaa62cfeff
2025-01-13 10:09:05,470 - Diematic - DEBUG - Bus status switched to SLAVE
2025-01-13 10:09:05,922 - DDModbus - DEBUG - Frame received: c1f2fe6afefaa2a4fcff
2025-01-13 10:09:06,164 - DDModbus - DEBUG - Frame received: bff2fe6afefab6dcfcff
2025-01-13 10:09:06,415 - DDModbus - DEBUG - Frame received: bdf2fe6afefab254feff
2025-01-13 10:09:06,818 - DDModbus - DEBUG - Frame received: bbf2fe6afefab2ccf9ff
2025-01-13 10:09:06,998 - DDModbus - DEBUG - Frame received: b9f2fe6afefab644fcff
2025-01-13 10:09:07,318 - DDModbus - DEBUG - Frame received: b7f2fe6afefab2fcfeff
2025-01-13 10:09:07,593 - DDModbus - DEBUG - Frame received: b5f2fe6afefab674ff
2025-01-13 10:09:07,777 - DDModbus - DEBUG - Frame received: b3f2fe6afefab6ecf8ff
2025-01-13 10:09:08,053 - DDModbus - DEBUG - Frame received: b1f2fe6afefab264feff
2025-01-13 10:09:08,320 - DDModbus - DEBUG - Frame received: d7f2fe6afefaa67cf8ff
2025-01-13 10:09:08,551 - DDModbus - DEBUG - Frame received: d5f2fe6afefaa2f4feff
2025-01-13 10:09:08,803 - DDModbus - DEBUG - Frame received: d3f2fe6afefaa26cfeff
2025-01-13 10:09:09,066 - DDModbus - DEBUG - Frame received: d1f2fe6afefaa6e4ff
2025-01-13 10:09:09,308 - DDModbus - DEBUG - Frame received: cff2fe6afefaa61cfeff
2025-01-13 10:09:09,561 - DDModbus - DEBUG - Frame received: cdf2fe6afefaa294f8ff
2025-01-13 10:09:09,834 - DDModbus - DEBUG - Frame received: cbf2fe6afefaa20cff
2025-01-13 10:09:10,089 - DDModbus - DEBUG - Frame received: c9f2fe6afefaa684feff
2025-01-13 10:09:10,591 - Diematic - DEBUG - Bus status switched to MASTER after 5.120495080947876
2025-01-13 10:09:10,591 - Diematic - INFO - ModBus Master Slave Synchro OK
2025-01-13 10:09:15,574 - DDModbus - DEBUG - Frame received: e9befa2efcfaf6fefeb28fff
2025-01-13 10:09:15,575 - Diematic - DEBUG - Bus status switched to SLAVE
2025-01-13 10:09:15,840 - DDModbus - DEBUG - Frame received: e9befa2efcfaf6fefeb28fff
2025-01-13 10:09:16,276 - DDModbus - DEBUG - Frame received: e7befa2efcfaf6fefe2a89ff
2025-01-13 10:09:16,500 - DDModbus - DEBUG - Frame received: e7befa2efcfaf6fefe2a89ff
2025-01-13 10:09:16,963 - DDModbus - DEBUG - Frame received: cabefa2efcfaf6fefe1e9bff
2025-01-13 10:09:17,235 - DDModbus - DEBUG - Frame received: e5befa2efcfaf6fefe1e9bff
2025-01-13 10:09:17,743 - DDModbus - DEBUG - Frame received: e3befa2efcfaf6fefe4e85ff
2025-01-13 10:09:17,925 - DDModbus - DEBUG - Frame received: e3befa2efcfaf6fefe4e85ff
2025-01-13 10:09:18,369 - DDModbus - DEBUG - Frame received: e1befa2efcfaf6fefe7a97ff
2025-01-13 10:09:18,609 - DDModbus - DEBUG - Frame received: e1befa2efcfaf6fefe7a97ff
2025-01-13 10:09:19,155 - DDModbus - DEBUG - Frame received: dfbefa2efcfaf6fefe4a2efeff
2025-01-13 10:09:19,378 - DDModbus - DEBUG - Frame received: bebefa2efcfaf6fefe4a2efeff
2025-01-13 10:09:19,855 - DDModbus - DEBUG - Frame received: ddbefa2efcfaf6fefe7e6eff
2025-01-13 10:09:20,041 - DDModbus - DEBUG - Frame received: ddbefa2efcfaf6fefe7e6eff
2025-01-13 10:09:21,043 - Diematic - DEBUG - Bus status switched to MASTER after 5.468306064605713
2025-01-13 10:09:25,444 - DDModbus - DEBUG - Frame received: c7f2fe6afefaa23cfcff
2025-01-13 10:09:25,445 - Diematic - DEBUG - Bus status switched to SLAVE
2025-01-13 10:09:25,710 - DDModbus - DEBUG - Frame received: c5f2fe6afefaa6b4f9ff
2025-01-13 10:09:25,979 - DDModbus - DEBUG - Frame received: c3f2fe6afefaa62cfeff
2025-01-13 10:09:26,225 - DDModbus - DEBUG - Frame received: c1f2fe6afefaa2a4fcff
2025-01-13 10:09:26,476 - DDModbus - DEBUG - Frame received: bff2fe6afefab6dcfcff
2025-01-13 10:09:26,761 - DDModbus - DEBUG - Frame received: bdf2fe6afefab254feff
2025-01-13 10:09:27,077 - DDModbus - DEBUG - Frame received: bbf2fe6afefab2ccf9ff
2025-01-13 10:09:27,401 - DDModbus - DEBUG - Frame received: b9f2fe6afefab644fcff
2025-01-13 10:09:27,676 - DDModbus - DEBUG - Frame received: b7f2fe6afefab2fcfeff
2025-01-13 10:09:27,958 - DDModbus - DEBUG - Frame received: b5f2fe6afefab674ff
2025-01-13 10:09:28,431 - DDModbus - DEBUG - Frame received: b3f2fe6afefab6ecf8ff
2025-01-13 10:09:28,666 - DDModbus - DEBUG - Frame received: b1f2fe6afefab264feff
2025-01-13 10:09:28,911 - DDModbus - DEBUG - Frame received: d7f2fe6afefaa67cf8ff
2025-01-13 10:09:29,201 - DDModbus - DEBUG - Frame received: d5f2fe6afefaa2f4feff
2025-01-13 10:09:29,525 - DDModbus - DEBUG - Frame received: a6f2fe6afefaa26cfeff
2025-01-13 10:09:29,844 - DDModbus - DEBUG - Frame received: d1f2fe6afefaa6e4ff
2025-01-13 10:09:30,124 - DDModbus - DEBUG - Frame received: cff2fe6afefaa61cfeff
2025-01-13 10:09:30,625 - Diematic - DEBUG - Bus status switched to MASTER after 5.180644512176514
2025-01-13 10:09:35,612 - DDModbus - DEBUG - Frame received: dbbefa2efcfaf6fefe2eaefeff
2025-01-13 10:09:35,613 - Diematic - DEBUG - Bus status switched to SLAVE
2025-01-13 10:09:35,871 - DDModbus - DEBUG - Frame received: dbbefa2efcfaf6fefe2eaefeff
2025-01-13 10:09:36,354 - DDModbus - DEBUG - Frame received: d9befa2efcfaf6fefe1aeefcff
2025-01-13 10:09:36,537 - DDModbus - DEBUG - Frame received: d9befa2efcfaf6fefe1aeefcff
2025-01-13 10:09:37,024 - DDModbus - DEBUG - Frame received: 9bbefaf2dab6fefef6d6fa827f18fefeb6fed2fefefaca20c2ff
2025-01-13 10:09:37,276 - DDModbus - DEBUG - Frame received: 9bbefaf2dab6fefef6dafa867f18fefeb6fed2fefefaca00caff
2025-01-13 10:09:37,534 - DDModbus - DEBUG - Frame received: 9bbefaf2dab6fefef6dafa867f18fefeb6fed2fefefaca00caff
2025-01-13 10:09:37,782 - DDModbus - DEBUG - Frame received: 36befaf2dab6fefef6dafa7e7f18fefeb6fed2fefefac60b6cff
2025-01-13 10:09:38,163 - DDModbus - DEBUG - Frame received: e9befa2efcfaf6fefeb28fff
2025-01-13 10:09:38,401 - DDModbus - DEBUG - Frame received: e9befa2efcfaf6fefeb28fff
2025-01-13 10:09:38,882 - DDModbus - DEBUG - Frame received: e7befa2efcfaf6fefe2a89ff
2025-01-13 10:09:39,145 - DDModbus - DEBUG - Frame received: e7befa2efcfaf6fefe2a89ff
2025-01-13 10:09:39,643 - DDModbus - DEBUG - Frame received: e5befa2efcfaf6fefe1e9bff
2025-01-13 10:09:39,829 - DDModbus - DEBUG - Frame received: e5befa2efcfaf6fefe1e9bff
2025-01-13 10:09:40,262 - DDModbus - DEBUG - Frame received: e3befa2efcfaf6fefe4e85ff
2025-01-13 10:09:40,501 - DDModbus - DEBUG - Frame received: e3befa2efcfaf6fefe4e85ff
2025-01-13 10:09:41,004 - Diematic - DEBUG - Bus status switched to MASTER after 5.390854597091675
2025-01-13 10:09:45,570 - DDModbus - DEBUG - Frame received: cdf2fe6afefaa294f8ff
2025-01-13 10:09:45,570 - Diematic - DEBUG - Bus status switched to SLAVE
2025-01-13 10:09:45,851 - DDModbus - DEBUG - Frame received: cbf2fe6afefaa20cff
2025-01-13 10:09:46,213 - DDModbus - DEBUG - Frame received: c9f2fe6afefaa684feff
2025-01-13 10:09:46,462 - DDModbus - DEBUG - Frame received: c7f2fe6afefaa23cfcff
2025-01-13 10:09:46,715 - DDModbus - DEBUG - Frame received: c5f2fe6afefaa6b4f9ff
2025-01-13 10:09:46,976 - DDModbus - DEBUG - Frame received: c3f2fe6afefaa62cfeff
2025-01-13 10:09:47,213 - DDModbus - DEBUG - Frame received: c1f2fe6afefaa2a4fcff
2025-01-13 10:09:47,494 - DDModbus - DEBUG - Frame received: bff2fe6afefab6dcfcff
2025-01-13 10:09:47,763 - DDModbus - DEBUG - Frame received: 7af2fe6afefab254feff
2025-01-13 10:09:48,066 - DDModbus - DEBUG - Frame received: bbf2fe6afefab2ccf9ff
2025-01-13 10:09:48,280 - DDModbus - DEBUG - Frame received: b9f2fe6afefab644fcff
2025-01-13 10:09:48,602 - DDModbus - DEBUG - Frame received: b7f2fe6afefab2fcfeff
2025-01-13 10:09:48,843 - DDModbus - DEBUG - Frame received: b5f2fe6afefab674ff
2025-01-13 10:09:49,094 - DDModbus - DEBUG - Frame received: b3f2fe6afefab6ecf8ff
2025-01-13 10:09:49,367 - DDModbus - DEBUG - Frame received: 62f2fe6afefab264feff
2025-01-13 10:09:49,602 - DDModbus - DEBUG - Frame received: d7f2fe6afefaa67cf8ff
2025-01-13 10:09:49,911 - DDModbus - DEBUG - Frame received: d5f2fe6afefaa2f4feff
2025-01-13 10:09:50,179 - DDModbus - DEBUG - Frame received: d3f2fe6afefaa26cfeff
2025-01-13 10:09:50,411 - DDModbus - DEBUG - Frame received: d1f2fe6afefaa6e4ff
2025-01-13 10:09:50,912 - Diematic - DEBUG - Bus status switched to MASTER after 5.342122793197632
2025-01-13 10:09:56,109 - DDModbus - DEBUG - Frame received: e1befa2efcfaf6fefe7a97ff
2025-01-13 10:09:56,109 - Diematic - DEBUG - Bus status switched to SLAVE
2025-01-13 10:09:56,333 - DDModbus - DEBUG - Frame received: e1befa2efcfaf6fefe7a97ff
2025-01-13 10:09:56,778 - DDModbus - DEBUG - Frame received: dfbefa2efcfaf6fefe4a2efeff
2025-01-13 10:09:56,972 - DDModbus - DEBUG - Frame received: dfbefa2efcfaf6fefe4a2efeff
2025-01-13 10:09:57,503 - DDModbus - DEBUG - Frame received: ddbefa2efcfaf6fefe7e6eff
2025-01-13 10:09:57,749 - DDModbus - DEBUG - Frame received: ddbefa2efcfaf6fefe7e6eff
2025-01-13 10:09:58,194 - DDModbus - DEBUG - Frame received: dbbefa2efcfaf6fefe2eaefeff
2025-01-13 10:09:58,416 - DDModbus - DEBUG - Frame received: dbbefa2efcfaf6fefe2eaefeff
2025-01-13 10:09:58,877 - DDModbus - DEBUG - Frame received: d9befa2efcfaf6fefe1aeefcff
2025-01-13 10:09:59,142 - DDModbus - DEBUG - Frame received: d9befa2efcfaf6fefe1aeefcff
2025-01-13 10:09:59,653 - DDModbus - DEBUG - Frame received: 9bbefaf2dab6fefefa1a7f0f7f1afefeb6fed2fefefac64746ff
2025-01-13 10:09:59,859 - DDModbus - DEBUG - Frame received: 9bbefaf2dab6fefefa1a7f0f7f1afefeb6fed2fefefac64746ff
2025-01-13 10:10:00,081 - DDModbus - DEBUG - Frame received: 9bbefaf2dab6fefefa1a7f0f7f1afefeb6fed2fefefac64746ff
2025-01-13 10:10:00,278 - DDModbus - DEBUG - Frame received: 9bbefaf2dab6fefefa1e7f0f7f1afefeb6fed2fefefaca60e4ff
2025-01-13 10:10:01,280 - Diematic - DEBUG - Bus status switched to MASTER after 5.170348405838013
2025-01-13 10:10:01,280 - DDModbus - DEBUG - Send read request: 0a030001003f556100
2025-01-13 10:10:03,784 - DDModbus - WARNING - No answer to masterReadAnalog
2025-01-13 10:10:03,784 - Diematic - WARNING - ModBus Master Slave Synchro Error
2025-01-13 10:10:06,232 - DDModbus - DEBUG - Frame received: cff2fe6afefaa61cfeff
2025-01-13 10:10:06,233 - Diematic - DEBUG - Bus status switched to SLAVE
2025-01-13 10:10:06,504 - DDModbus - DEBUG - Frame received: cdf2fe6afefaa294f8ff
2025-01-13 10:10:06,792 - DDModbus - DEBUG - Frame received: cbf2fe6afefaa20cff
2025-01-13 10:10:07,248 - DDModbus - DEBUG - Frame received: c9f2fe6afefaa684feff
2025-01-13 10:10:07,475 - DDModbus - DEBUG - Frame received: c7f2fe6afefaa23cfcff
2025-01-13 10:10:07,726 - DDModbus - DEBUG - Frame received: c5f2fe6afefaa6b4f9ff
2025-01-13 10:10:08,008 - DDModbus - DEBUG - Frame received: c3f2fe6afefaa62cfeff
2025-01-13 10:10:08,248 - DDModbus - DEBUG - Frame received: c1f2fe6afefaa2a4fcff
2025-01-13 10:10:08,530 - DDModbus - DEBUG - Frame received: bff2fe6afefab6dcfcff
2025-01-13 10:10:08,807 - DDModbus - DEBUG - Frame received: bdf2fe6afefab254feff
2025-01-13 10:10:09,043 - DDModbus - DEBUG - Frame received: bbf2fe6afefab2ccf9ff
2025-01-13 10:10:09,310 - DDModbus - DEBUG - Frame received: b9f2fe6afefab644fcff
2025-01-13 10:10:09,640 - DDModbus - DEBUG - Frame received: b7f2fe6afefab2fcfeff
2025-01-13 10:10:09,956 - DDModbus - DEBUG - Frame received: b5f2fe6afefab674ff
2025-01-13 10:10:10,264 - DDModbus - DEBUG - Frame received: b3f2fe6afefab6ecf8ff
2025-01-13 10:10:10,533 - DDModbus - DEBUG - Frame received: b1f2fe6afefab264feff
2025-01-13 10:10:10,825 - DDModbus - DEBUG - Frame received: d7f2fe6afefaa67cf8ff
2025-01-13 10:10:11,326 - Diematic - DEBUG - Bus status switched to MASTER after 5.093903064727783
2025-01-13 10:10:11,327 - Diematic - INFO - ModBus Master Slave Synchro OK
2025-01-13 10:10:11,327 - DDModbus - DEBUG - Send read request: 0a030001003f556100
2025-01-13 10:10:13,831 - DDModbus - WARNING - No answer to masterReadAnalog
2025-01-13 10:10:13,831 - Diematic - WARNING - ModBus Master Slave Synchro Error

Any help would be very much appriciated!

Greetings from Germany,
Sebastian

Hi, I think a build of HA broke it. I fixed it by updating the Dockerfile as follows

Every now and then I get a message in the logs about a frame too long error, is there anything I can do about it?

2025-01-14 12:49:46,323 - DDModbus - DEBUG - Frame received: 001001d6000102000ca8f300001001b40001020064a15f00001001d20001020000a97200001002da000408000000000000ffffab2e000b0301d9000154a7000b0301d9000154a7000b0301d9000154a70000100004000306ff0cff31ff020030000010006c000306ff0eff01ff19bba000001001d6000102000ca8f300001001b40001020064a15f00001001d20001020000a97200001002da000408000000000000ffffab2e000b0301d9000154a7000b0301d9000154a7000b0301d9000154a70000100004000306ff0cff31ff020030000010006c000306ff0eff01ff19bba000001001d6000102000ca8f300001001b40001020064a15f00001001d20001020000a972003c10033e00091200000000000000000000000000000000000253ba00140300010001d70f00
2025-01-14 12:49:46,325 - DDModbus - WARNING - Received Frame Length Error

Hi champ4210.
After applying your change I get the same message as before:

2025-01-16 11:48:34.210 ERROR (MainThread) [supervisor.docker.addon] Invalid build environment, can't build this add-on!

Have you encountered this before?.

Becareful that the Dockerfile is named “Dockerfile” case sensitive and not “DockerFile”.

That did the trick for me.

Brilliant!!!
I didn’t think of that, no one paid attention to it, the file with that name was original.

Now I’m stuck on.:
The command '/bin/ash -o pipefail -c pip install pytz' returned a non-zero code: 127
Changing to pip3 doesn’t help