Replies: 4 comments 1 reply
-
The log shows the offset in brackets if offset is a positive value. The 1A telegram in offset 0: flowtemp, offset1: burnpower, Writing these values is temporary, the boier resets to default setting after ~3 minutes. So you have to repeat the commands every minute. That is what EM10 or thermostats do. In the 3.6 beta we have a scheduler where you can define such values. Create scheduler value with timer 00:01 and command |
Beta Was this translation helpful? Give feedback.
-
Amazing answer! So thank you again for bringing some light into the whole thing and how the EM10 works (sending every minute, I verified it already by watching "0x1A"). |
Beta Was this translation helpful? Give feedback.
-
Hello, we have a Logano Plus gb312, which has an EM10 module, which is actually supposed to provide the external specification of the performance. I have to check if that ever worked. Now the EM10 module is recognized, but no values are transferred via MQTT and I can also see it under the web interface. Are the values exclusively set? In other words, you can't see anything in the web interface. Or I have to add “customize”? My goal is to check the EM10 is configured correctly... the installer says "everything is fine, I have no idea why it doesn't work..." Thanks |
Beta Was this translation helpful? Give feedback.
-
But there is no burner set power on the MC10 (boilder), the boiler always runs at full power and does not regulate at all. I would like to see why the burner always runs at 100% and not only runs at 50% when set to 5 volts to the EM10 for example. That's why I thought you could see the external setpoint here |
Beta Was this translation helpful? Give feedback.
-
Hi All,
I have a Buderus GB162 boiler which is connected to a EM10 module. The EM10 module is used for telling the boiler either the set value of the flow temperature (°C) or the set value of the burner power (%).
When I run "watch on" and connect 5 V to the EM10 this gives these values for the set flow temperature:
[emsesp] alert(0x12) -W-> boiler(0x08), UBASetPoints(0x1A), data: 32
(for setting it to 50 °C)[emsesp] alert(0x12) -W-> boiler(0x08), UBASetPoints(0x1A), data: 00
(for setting it to off)That looks exactly the same for the set burner power:
[emsesp] alert(0x12) -W-> boiler(0x08), UBASetPoints(0x1A), data: 32
(for setting it to 50 %)[emsesp] alert(0x12) -W-> boiler(0x08), UBASetPoints(0x1A), data: 00
(for setting it to 0 %)I thought there's no way that the boiler can understand if it is % or °C requested so I was checking the raw packets ("watch raw"):
[telegram] Rx: 12 08 1A 00 00 11
(for setting the set flow temperature to "off")[telegram] Rx: 12 08 1A 01 00 13
(for setting the set burner power to "0 %")So there is a different offset (as expected) but this is only shown when displaying raw bytes.
Many questions for this topic:
Sorry guys if any of these questions are stupid but I'm brand new to EMS-ESP and I couldn't find any of these answered and also I couldn't find anything related to EM10 which surprised me since to my knowledge that's the official way of controlling the boiler from external systems.
Beta Was this translation helpful? Give feedback.
All reactions