Add Buderus AM200 Support

[OlliHein]

Requirement:
Im using GB172 together with SM200, RC310 and AM200. Currently AM200 is not available and cannot be detected.

System:
EMS-ESP Version: v3.4.1
Device (Platform / SDK): ESP32 / v3.3.5-1-g85c43024c
Heap (Free / Max Alloc): 118.816 / 62.172 bytes
Flash Chip (Size / Speed): 4.194.304 bytes / 40 MHz
File System (Used / Total): 20.480 / 327.680 bytes (307.200 bytes free)

Devices and Sensors:
Type;Description;;Entries
Boiler;GBx72/Trendline/Cerapur/Greenstar Si/27i;67
Thermostat;RC300/RC310/Moduline 3000/1010H/CW400/Sense II;34
Solar;SM200/MS200;42
Gateway;KM200/MB LAN 2;0
Unknown;unknown;0
Sensors;Attached EMS-ESP Sensors;0

As you can see there is an unknown device detected, should be AM200

Environment:
Im using picture 23 from Buderus "Installation instructions for contractors". If you need PDF, I can give you a attachment. But I think you already have it or can download it.
As you can see in picture 23 I am using following sensors, pumps and valves:
Sensors: TA1, TR1, TR2, TB4, TB1, TB3
Valves: VR1, VB1
Pump: PR1

I can give you all the data and values of the running system to better identify the devices.

At first I attached the current logfile of EMS-PSP32:
log_AM200.txt

with more data:
log2_AM200.txt

and also picture 23 from Buderus installation guide:

Hope that will you give a first overview of my running system.

It will be great if AM200 can be integrated in your system, thanks for dooing that ;)

Thanks
Oliver

[MichaelDvP]

Please go to help-page and download the debug info (not settings/customizations), and post it here. We need the product-id and telegrams.
The log shows 3 telegrams from device 0x60.
0x054D seems to be Temperatures

00F5 00F7 8000 00D5 010F 01E5 8000 01DD 0000 8000
24.5 24.7      21.3 27.1 48.5      47.7

0x054E could be a status message, all valves off: 00 00 00 00 00 00
0x0550 could be settings: 00 FF 00 FF FF 00 0D 00 01 00 00 00 00 01 03 01 00 03 00 2D 19 C8 02 94 00 00 FF FF

For the temperatures note the temperatures shown in thermostat monitor screen and in terminal type read 60 54d
For the status telegrams you can use disgnostic menu, switch valves and check if and how telegram 0x54e changes.

For settings you have to change every setting for AM200 on the thermostat and check what changes in telegram 0x550.

With all this info we can add values/settings to emsesp.

@proddy : What device type? It is a special case of additional heating device, or in pos 10, as boiler replacement. I think best to add it as boiler and check for device-id 0x60? Like 0x70... for cascaded boilers.

PS:
@proddy Could you make the debug info on help page with a large button? Nobody uses it. And maybe move the settings/customization-download to system->upload (rename tab to up/download) to avoid confusion on the help page?

[proddy]

@proddy : What device type? It is a special case of additional heating device, or in pos 10, as boiler replacement. I think best to add it as boiler and check for device-id 0x60? Like 0x70... for cascaded boilers.

Agree, let's add it to boiler

PS: @proddy Could you make the debug info on help page with a large button? Nobody uses it. And maybe move the settings/customization-download to system->upload (rename tab to up/download) to avoid confusion on the help page?

Both good ideas. I'll try and think of a name for the up/download tab

[OlliHein]

@MichaelDvP
At first I attached debug info file. You are right, it is hard to find.
BTW: I also put it into a zip file because .json is not supported as an attachment here ;)

emsesp_info.zip

Tomorrow I will investigate more time to find out values and status informations as you descibed. Thanks for such fast support ;)

[MichaelDvP]

BTW: I also put it into a zip file because .json is not supported as an attachment here ;)

Good point, we should rename to emsesp_info.json.txt.

[OlliHein]

@MichaelDvP
Here are the temperature definitions:

[telegram] Rx: 60 00 FF 00 04 4D 0103 0108 8000 00C6 0127 0205 8000 0200 0000 8000 6C
                                 TB4  TR2       TA1  TR1  TB1  TB2* TB3

There are two 0x8000 I do not have connected. Should be TF1 and T1
*TB2 should be between TB1 and TB3 but it is also not connected in my installation

Pump detection is following in % (I used 0x55 to test)

[telegram] Rx: 60 00 FF 00 04 4E 55 01 C6
                                 PR1
[emsesp] No telegram type handler found for ID 0x54E (src 0x60)

Values of valves are not so easy to detect. I can only set On or Off in test mode. AM200 will adjust to any valve position depending on temperatures.

Let us start with temperatures and pump. What do you think?

[MichaelDvP]

Ok, first test here: https://github.com/MichaelDvP/EMS-ESP32/releases
We can do some iterations and renames and if all works i'll do a PR.

[OlliHein]

Wow, that's fast. I will try it. ;) @MichaelDvP: I uploaded EMS-ESP version 3.4.2b3 but there is no change. Device is still "unknown" and no sensors detected.

…

________________________________ From: MichaelDvP ***@***.***> Sent: Monday, July 18, 2022 8:14:02 PM To: emsesp/EMS-ESP32 ***@***.***> Cc: OlliHein ***@***.***>; Author ***@***.***> Subject: Re: [emsesp/EMS-ESP32] Add Buderus AM200 Support (Issue #573) Ok, first test here: https://github.com/MichaelDvP/EMS-ESP32/releases We can do some iterations and renames and if all works i'll do a PR. — Reply to this email directly, view it on GitHub<#573 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2C5WZ6GACPGJA2LYFZCVILVUWNGVANCNFSM53YSD72A>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[MichaelDvP]

Ups, forgot that boilers have a special handling when detecting. Hopefully it works now.

[OlliHein]

Great,
It works and I can read temperatures. I will try to check pump and values later.
Where did you get the informations about valves?

Current device Data:

The MQTT topics are not unique:

• curflowtemp
• currettemp

I think it must be:

• altcurflowtemp
• altcurrettemp

@MichaelDvP Can you check it please - thanks ;)

[proddy]

@OlliHein did you mark all those entries as favourites via the Customization page, or could this possibly be a new undiscovered bug?

[OlliHein]

I mark all needed entries as favourites and enable it for MQTT. I have curflowtemp twice in both boilers available but with different temperature values

@MichaelDvP I think the parent topic must be another one. The AM200 items are located at the default boiler not to the new alternative one.

[MichaelDvP]

The valves are not correct at the moment, i expect them in telegram 54E like pump in offset 0, and read offset 1,2,3 as bool. But i think some are mixing valves an use percent-states. You have to ckeck the right values/positions.

The flow temp is TB4/TR2, the en-manual says "system flow temp" and "system return temp", i thought it is the same as main boiler curflowtemp, but it seems they are different. I'll rename and take the names from the manual.

For mqtt it we can use a tag "hsa" (heating source alternative) like cascaded boilers (hs1-hs16) and heating circuits (hc1-hc4).
This shows as json-nest in "boiler"-topic, or, if you choose non-nested format, as extra "boiler_hsa"-topic.

If it helps we can add the input to names i.e. "system flow temperature (TB4)", and/or use the input as mqtt-shortname: "tb4" instead of "sysflowtemp"?

I thought telegram 550 is settings, but it is broadcasted (uncommon for settings) and there are some values in manual like "set temp return" (65°C), "Set flow temp AHS" (75°C) ,etc i can not see. Try in terminal read 60 54F, maybe there are some values. (try also 551).

I've updated my build.

[OlliHein]

TB4 and TR2 are the temperatures to control the VB1 valve as puffer bypass. TB4 should be the same as "system return temp".

The mqtt tag "hsa" is a good seperator to make the mqtt topic unique. See picture from mqtt explorer with the new EMS-ESP version you created. It works fine:

If it helps we can add the input to names i.e. "system flow temperature (TB4)", and/or use the input as mqtt-shortname: "tb4" instead of "sysflowtemp"?
-> I think it is not nessessary

The valves are not correct at the moment, i expect them in telegram 54E like pump in offset 0, and read offset 1,2,3 as bool. But i think some are mixing valves an use percent-states. You have to ckeck the right values/positions.
-> ok, I will check it next weekend

I thought telegram 550 is settings, but it is broadcasted (uncommon for settings) and there are some values in manual like "set temp return" (65°C), "Set flow temp AHS" (75°C) ,etc i can not see. Try in terminal read 60 54F, maybe there are some values. (try also 551).
-> also next weekend