New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Buderus AM200 Support #573
Comments
Please go to help-page and download the debug info (not settings/customizations), and post it here. We need the product-id and telegrams.
0x054E could be a status message, all valves off: For the temperatures note the temperatures shown in thermostat monitor screen and in terminal type 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: |
Agree, let's add it to boiler
Both good ideas. I'll try and think of a name for the up/download tab |
@MichaelDvP Tomorrow I will investigate more time to find out values and status informations as you descibed. Thanks for such fast support ;) |
Good point, we should rename to |
@MichaelDvP
There are two 0x8000 I do not have connected. Should be TF1 and T1 Pump detection is following in % (I used 0x55 to test)
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? |
Ok, first test here: https://github.com/MichaelDvP/EMS-ESP32/releases |
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: ***@***.***>
|
Ups, forgot that boilers have a special handling when detecting. Hopefully it works now. |
Great, The MQTT topics are not unique:
I think it must be:
@MichaelDvP Can you check it please - thanks ;) |
@OlliHein did you mark all those entries as favourites via the Customization page, or could this possibly be a new undiscovered bug? |
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. |
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). 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 I've updated my build. |
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:
|
@MichaelDvP Currently it is hard to find out changes of status information in logfile. You already have a great method to post status information with MQTT available in EMS-ESP. I mean it should be easy to write telegram data from bus depending of the devices (i.e. 0x60) to MQTT as a topic. The value should be the hex stream. If we have this, it will be easy to change data on a terminal and I can be seen directly as changes in MQTT explorer. Wat do you think? |
Emsesp has already a lot of tools to examine the bus, remember that emsesp is based on reverse engineering the bus. |
Yes, you are right, I hat to read documentation first. The terminal watch is a good way to examine bus data. |
@MichaelDvP Here are the values of both valves: I set buffer bypass (VB1) to off in diagnostic menu:
I set buffer bypass (VB1) to open in diagnostic menu:
I set buffer bypass (VB1) to close in diagnostic menu:
I set AVE Valve (VR1) off in diagnostic menu
I set AVE Valve (VR1) open in diagnostic menu
I set AVE Valve (VR1) close in diagnostic menu
|
Thx, so we have a telgram 0x54F for settings, please use In statusMessage 0x54E we have now in offset: and in 0x54F commands for I think the main information to show in ems-esp are the percent values for pump and valves. Is it usefull also to add entities for opening/closing and pump on/off? |
I think also the percent values are enought. 0=close; >1-99 = opening; 100=open
I don't think so and I do not need it, AM200 should control valves. Did you add the new valves informations to the new boiler device? I miss the data in last update v3.4.2b4? |
I have not updated yet, i'm waiting for the complete 54F telegram.
Strange, these are from solar class, don't know howthey came to boiler, maybe something from browser cache? |
@MichaelDvP
ems-esp:$ read 60 54f and there is another telegram 54C for configuration settings:
AA=Alternate heat source activation: No(00),Yes(01) Buffer primary pump (PR1) Mixer return AHS (VR1) Buffer Blocking mode Have fun implementing it ;)
|
Nice findings, good work. So 54F is only testing mode and 54C are settings. It will take some days to implement all with commands. |
First implementation with the mentioned assumptions is on my GH. Please check. |
Hi @MichaelDvP ,
-> I corrected settings of HH, KK and OO. I did a mistake. Yes, my setting of (HH and KK) are both 90s I updated my ems-esp with new version and it look nice with your current implementation ;)
Let us coninue - thx |
Now you have marked HH to (8/)9 and KK to (10/)11, Check which is first. |
Yes KK is pos 8/9 and HH is pos 10/11 I cheked it twice. It was a mistake in my first documentation. |
@MichaelDvP I updated following post with lager data to show the overflow of a 255s value |
@MichaelDvP Do you have enough information to bring AM200 running? If you need more data I can update you. |
@OlliHein I've merged Michael's AM200 additions to the latest dev branch/release. |
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
The text was updated successfully, but these errors were encountered: