Skip to content
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

Problem mit Buderus AM200 in Kodierung 10 #1161

Closed
Frank1451 opened this issue Apr 21, 2023 · 10 comments
Closed

Problem mit Buderus AM200 in Kodierung 10 #1161

Frank1451 opened this issue Apr 21, 2023 · 10 comments
Labels
enhancement New feature or request
Milestone

Comments

@Frank1451
Copy link

PROBLEM DESCRIPTION

The Buderus AM200 was switched from code 1 to code 10, after that no more parameters were indicated, even after restarting the EMS-ESP.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

  System information output here:
{
  "System Info": {
    "version": "3.6.0-dev.9",
    "platform": "ESP32",
    "uptime": "001+04:26:41.397",
    "uptime (seconds)": 102401,
    "free mem": 128,
    "max alloc": 77,
    "free app": 6147,
    "reset reason": "Power on reset / APP CPU reset by PRO CPU"
  },
  "Network Info": {
    "network": "WiFi",
    "hostname": "ems-esp",
    "RSSI": -77,
    "IPv4 address": "192.168.178.118/255.255.255.0",
    "IPv4 gateway": "192.168.178.1",
    "IPv4 nameserver": "192.168.178.1",
    "static ip config": false,
    "enable IPv6": false,
    "low bandwidth": false,
    "disable sleep": false,
    "enable MDNS": true,
    "enable CORS": false,
    "AP provision mode": "disconnected",
    "AP security": "wpa2",
    "AP ssid": "ems-esp"
  },
  "NTP Info": {
    "NTP status": "disconnected",
    "enabled": false,
    "server": "time.google.com",
    "tz label": "Europe/Amsterdam"
  },
  "OTA Info": {
    "enabled": false,
    "port": 8266
  },
  "MQTT Info": {
    "MQTT status": "connected",
    "MQTT publishes": 32426,
    "MQTT queued": 0,
    "MQTT publish fails": 0,
    "MQTT connects": 1,
    "enabled": true,
    "client id": "ems-esp",
    "keep alive": 60,
    "clean session": false,
    "entity format": 1,
    "base": "ems-esp",
    "discovery prefix": "homeassistant",
    "discovery type": 0,
    "nested format": 1,
    "ha enabled": false,
    "mqtt qos": 0,
    "mqtt retain": false,
    "publish time heartbeat": 60,
    "publish time boiler": 10,
    "publish time thermostat": 10,
    "publish time solar": 10,
    "publish time mixer": 10,
    "publish time other": 10,
    "publish time sensor": 10,
    "publish single": false,
    "publish2command": false,
    "send response": false
  },
  "Syslog Info": {
    "enabled": false
  },
  "Sensor Info": {
    "temperature sensors": 0,
    "temperature sensor reads": 0,
    "temperature sensor fails": 0,
    "analog sensors": 0,
    "analog sensor reads": 0,
    "analog sensor fails": 0
  },
  "API Info": {
    "API calls": 0,
    "API fails": 0
  },
  "Bus Info": {
    "bus status": "connected",
    "bus protocol": "Buderus",
    "bus telegrams received (rx)": 153284,
    "bus reads (tx)": 25630,
    "bus writes (tx)": 0,
    "bus incomplete telegrams": 1,
    "bus reads failed": 0,
    "bus writes failed": 0,
    "bus rx line quality": 100,
    "bus tx line quality": 100
  },
  "Settings": {
    "board profile": "S32",
    "locale": "de",
    "tx mode": 2,
    "ems bus id": 11,
    "shower timer": false,
    "shower alert": false,
    "hide led": false,
    "notoken api": false,
    "readonly mode": false,
    "fahrenheit": false,
    "dallas parasite": false,
    "bool format": 1,
    "bool dashboard": 1,
    "enum format": 1,
    "analog enabled": true,
    "telnet enabled": true,
    "max web log buffer": 50,
    "web log buffer": 19
  },
  "Devices": [
    {
      "type": "thermostat",
      "name": "RC300/RC310/Moduline 3000/1010H/CW400/Sense II/HPC410",
      "device id": "0x10",
      "product id": 158,
      "version": "18.06",
      "entities": 47,
      "handlers received": "0x06 0x02BA 0x02B0 0x029C 0x02BB 0x02B1 0x029D 0x02BC 0x02B2 0x029E 0x02BD 0x029F 0x02BE 0x02A0 0x02BF 0x02A1 0x02C0 0x02A2 0x031D 0x0267",
      "handlers fetched": "0x02A5 0x02B9 0x02AF 0x029B 0x02CC 0x02F5 0x023A 0x0240",
      "handlers pending": "0xA3 0xA2 0x12 0x13 0x0471 0x02A6 0x0472 0x02A7 0x0473 0x02A8 0x0474 0x02A9 0x02B3 0x0475 0x02AA 0x02B4 0x0476 0x02AB 0x02B5 0x0477 0x02AC 0x02B6 0x0478 0x02CE 0x02D0 0x02D2 0x031B 0x031E 0xBB 0x023E",
      "handlers ignored": "0xE6 0x0236 0xF7 0x0358 0xF6 0x033B 0x02F6 0x0291 0x0292 0x0293 0x0294 0x02E0 0x02EA 0x054C 0x0313 0x035A 0x0380 0x0295 0x0296 0x0297 0x0298 0x0426 0x0427 0x0428 0x0269 0x026B 0x026A 0x026D 0x026C 0x0422 0x043F 0x0440 0x0424 0x0441 0x0421 0x0442 0x02C3 0x0423 0x0449 0x0425 0x0683 0x068D 0x02FF 0x03"
    },
    {
      "type": "mixer",
      "name": "MM100",
      "device id": "0x28",
      "product id": 160,
      "version": "24.05",
      "entities": 8,
      "handlers received": "0x0331",
      "handlers fetched": "0x0313",
      "handlers ignored": "0xF6 0xD4 0x0255 0x03C7 0xF7 0xF9 0xBF"
    },
    {
      "type": "solar",
      "name": "SM100/MS100",
      "device id": "0x30",
      "product id": 163,
      "version": "21.04",
      "entities": 36,
      "handlers received": "0x0362 0x0363 0x0366 0x0364 0x036A",
      "handlers fetched": "0x0358 0x035A 0x0380 0x038E",
      "handlers pending": "0x035D 0x0391 0x035F 0x035C 0x0361",
      "handlers ignored": "0xF7 0x035B 0x035E 0x0360 0x0368 0x038A 0x038D 0xF6 0x0359 0x03DA 0xE8 0x0345 0x038B 0x038C 0xF9 0xBF"
    },
    {
      "type": "heatsource",
      "name": "AM200",
      "device id": "0x08",
      "product id": 228,
      "version": "03.03",
      "entities": 0,
      "handlers ignored": "0x04 0xE6 0xD1 0xEA 0xE4 0xE9 0xE3 0xF7 0xF9 0xF6 0x02CC 0x02D6 0xEF 0x054D 0x054E 0x0550 0x054C 0xBF"
    }
  ]
}

TO REPRODUCE

Steps to reproduce the behavior:

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

@MichaelDvP
Copy link
Contributor

MichaelDvP commented Apr 21, 2023

The AM200 uses the boiler device-id and sends out some boiler telegrams 0xE3... but also some AHS telegrams 0x054D...
Please make a full log of a few minutes to see if we can register as normal boiler or need some special additions.
What configuraton are us using? What sensors/valves are connected?
For testing i've added a AM200 to boiler for device-id 0x08. Try with this build: https://github.com/MichaelDvP/EMS-ESP32/releases/tag/latest

@Frank1451
Copy link
Author

Frank1451 commented Apr 22, 2023 via email

@Frank1451
Copy link
Author

Frank1451 commented Apr 22, 2023 via email

@Frank1451
Copy link
Author

Frank1451 commented Apr 22, 2023 via email

@Frank1451
Copy link
Author

SchemaNr51

@MichaelDvP
Copy link
Contributor

Thanks. As expected there are boiler telegrams and AM200 telegrams, but most of the values are published in both telegrams, like flowtemp, rettemp,...
We have to check if it more usefull to map as boiler and maybe add some values or as heatsource. The setting telegrams are not broadcasted, we have to read them.
Could you please open a telnet and post the output from these commands:
read 08 E6
read 08 EA
read 08 54C

@Frank1451
Copy link
Author

ems-esp:$ read 08 E6
000+22:57:37.369 I 3: [emsesp] heatsource(0x08) -W-> Me(0x0B), ?(0xE6), data: 01 50 00 00 64 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00 00 00
000+22:57:37.637 I 4: [emsesp] heatsource(0x08) -W-> Me(0x0B), ?(0xE6), data: (offset 26)

ems-esp:$ read 08 EA
000+22:58:06.842 I 5: [emsesp] heatsource(0x08) -W-> Me(0x0B), ?(0xEA), data: 01 3C 00 00 00 00 00 00 00 00 00 3C 00 2D 00 3C 00 00 00 00 00 00 0A (offset 5)

ems-esp:$ read 08 54C
000+22:58:24.255 I 6: [emsesp] heatsource(0x08) -W-> Me(0x0B), ?(0x054C), data: 02 00 01 00 00 00 3C 3C 00 78 00 3C 01 01 05 1E 01 00 5A 00 01 23 01 64 23
000+22:58:24.481 I 7: [emsesp] heatsource(0x08) -W-> Me(0x0B), ?(0x054C), data: 0F 05 (offset 25)

@Frank1451
Copy link
Author

maybe that will help too.
These were the data fields for coding 1:

<style> </style>
Entity Name value UoM
AHQ1 System Vorlauftemperatur 19,1 °C
AHQ1 System Rücklauftemperatur 19,2 °C
AHQ1 Alternativer WE Vorlauftemperatur 21 °C
AHQ1 Speichertemperatur Oben 40,7 °C
AHQ1 Speichertemperatur Unten 31,7 °C
AHQ1 Puffer-Ventil 0 %
AHQ1 Rückfluss-Ventil 50 %
AHQ1 Alternativer WE Pumpenmodulation 0 %
AHQ1 VR2 Konfiguration bypass  
AHQ1 Alt. Wärmeerzeuger aktiviert an  
AHQ1 Konfig. Hauptpumpe aus  
AHQ1 Ausgang Pumpe PR1 pwm  
AHQ1 Minimale Pumpenansteuerung 35 %
AHQ1 Rücklauf Temperaturerhöhung aus  
AHQ1 Soll-Rücklauftemperatur 60 °C
AHQ1 Mischer-Laufzeit 120 seconds
AHQ1 Sollwert Vorlauftemperatur 65 °C
AHQ1 Puffer-Bypass Konfig. mixer  
AHQ1 Speicher-Mischer-Laufzeit 60 seconds
AHQ1 Konfig. Warmwasserspeicher monovalent  
AHQ1 Konfig. Sperr-Modus aus  
AHQ1 Konfig. Sperrterminal n_o  
AHQ1 Hysterese Sperrmodus 5 °C
AHQ1 Wartezeit Kessel-Freigabe 30 minutes
AHQ1 Brenner aus  
AHQ1 Alternativer WE Pumpe aus  
AHQ1 Wärmeanforderung 0 %
AHQ1 verbleibende Blockzeit 0 minutes
AHQ1 verbleibende Blockzeit WW 0 minutes

@MichaelDvP
Copy link
Contributor

At first look it seems better to map as heatsource with the AM200 telegram. I'll need some time to check all values. For now i've updated my dev build to read/show the known AM200 values from switch position 1 also for switch 10. Try https://github.com/MichaelDvP/EMS-ESP32/releases/tag/latest

@Frank1451
Copy link
Author

Great, that works very well - thanks!

When I can still support, please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants