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.

Sign up for GitHub

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

Jump to bottom

Buderus GB182 - HC1 mode change not work #1193

Closed
5 tasks done
ralf-koe opened this issue Jun 6, 2023 · 11 comments
Closed
5 tasks done

Buderus GB182 - HC1 mode change not work #1193

ralf-koe opened this issue Jun 6, 2023 · 11 comments
Labels
bug Something isn't working
Milestone
v3.6.0

Comments

@ralf-koe
Copy link

ralf-koe commented Jun 6, 2023

PROBLEM DESCRIPTION

GB182i.2 with MX300 and the EMS-ESP E32 adapter is running
Detected:
Condens 5000i/Greenstar 8000/GC9800IW
UI800
Wifi module

Unfortunately I can not switch the HC1 mode. In the EMS-ESP frontend the value is editable. Temperatures I can set. Via Buderus app and the MX300 I can change the mode and it also updates the values via MQTT.

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.12",
    "platform": "ESP32",
    "uptime": "001+02:08:16.075",
    "uptime (seconds)": 94096,
    "free mem": 117,
    "max alloc": 65,
    "free app": 14,
    "reset reason": "Software reset CPU / Software reset CPU"
  },
  "Network Info": {
    "network": "Ethernet",
    "hostname": "ems-esp",
    "IPv4 address": "172.16.100.191/255.255.255.0",
    "IPv4 gateway": "172.16.100.1",
    "IPv4 nameserver": "172.16.100.232",
    "static ip config": true,
    "enable IPv6": false,
    "low bandwidth": false,
    "disable sleep": false,
    "enable MDNS": false,
    "enable CORS": false,
    "AP provision mode": "disconnected",
    "AP security": "wpa2",
    "AP ssid": "ems-esp"
  },
  "NTP Info": {
    "NTP status": "connected",
    "enabled": true,
    "server": "172.16.100.1",
    "tz label": "Europe/Berlin"
  },
  "OTA Info": {
    "enabled": false,
    "port": 8266
  },
  "MQTT Info": {
    "MQTT status": "connected",
    "MQTT publishes": 29859,
    "MQTT queued": 0,
    "MQTT publish fails": 0,
    "MQTT connects": 1,
    "enabled": true,
    "client id": "ems-esp",
    "keep alive": 60,
    "clean session": false,
    "entity format": 0,
    "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
  },
  "API Info": {
    "API calls": 0,
    "API fails": 0
  },
  "Bus Info": {
    "bus status": "connected",
    "bus protocol": "Buderus",
    "bus telegrams received (rx)": 122191,
    "bus reads (tx)": 26405,
    "bus writes (tx)": 1,
    "bus incomplete telegrams": 0,
    "bus reads failed": 0,
    "bus writes failed": 0,
    "bus rx line quality": 100,
    "bus tx line quality": 100
  },
  "Settings": {
    "board profile": "E32",
    "locale": "en",
    "tx mode": 1,
    "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": 4,
    "bool dashboard": 1,
    "enum format": 1,
    "analog enabled": false,
    "telnet enabled": false,
    "max web log buffer": 75,
    "web log buffer": 75
  },
  "Devices": [
    {
      "type": "boiler",
      "name": "Condens 5000i/Greenstar 8000/GC9800IW",
      "device id": "0x08",
      "product id": 195,
      "version": "05.06",
      "entities": 64,
      "handlers received": "0xBF 0xC2 0x15 0xD1 0xE3 0xE4 0xE5 0xE9",
      "handlers fetched": "0x14 0xE6 0xEA",
      "handlers pending": "0x10 0x11 0x1C 0x18 0x19 0x1A 0x35 0x16 0x33 0x34 0x26 0x2A",
      "handlers ignored": "0xD7 0xD8 0x02D6 0x2E 0x3B 0xF9 0x17 0x36 0xF7"
    },
    {
      "type": "thermostat",
      "name": "UI800",
      "device id": "0x10",
      "product id": 4,
      "version": "49.03",
      "entities": 46,
      "handlers received": "0x06 0x02BA 0x02BB 0x02BC 0x031D 0x0267",
      "handlers fetched": "0x02A5 0x02B9 0x02AF 0x029B 0x02CC 0x02F5 0x023A 0x0240",
      "handlers pending": "0xA3 0xA2 0x12 0x13 0x0471 0x02A6 0x02B0 0x029C 0x0472 0x02A7 0x02B1 0x029D 0x0473 0x02A8 0x02B2 0x029E 0x0474 0x02A9 0x02BD 0x02B3 0x029F 0x0475 0x02AA 0x02BE 0x02B4 0x02A0 0x0476 0x02AB 0x02BF 0x02B5 0x02A1 0x0477 0x02AC 0x02C0 0x02B6 0x02A2 0x0478 0x02CE 0x02D0 0x02D2 0x031B 0x031E 0xBB 0x023E",
      "handlers ignored": "0xE7 0x02E0 0x02EA 0xC4 0xBF 0x3B 0xF9 0x05"
    },
    {
      "type": "gateway",
      "name": "WiFi module",
      "device id": "0x48",
      "product id": 252,
      "version": "03.01",
      "entities": 0,
      "handlers ignored": "0x0CBD"
    }
  ]
}

TO REPRODUCE

grafik

change hc1 mode to manual show

grafik

but finally mode and mode type did not change

EXPECTED BEHAVIOUR

If I use the MyBuderus App and switch "absence/Abwesend" to true, hc1 mode change to manual and hc1 mode type to eco.

Finally I want to use MQTT to switch the mode to eco if nobody is at home.

ADDITIONAL CONTEXT

log from change mode in EMS-ESP:

2023-06-05 17:02:44.986   TRACE 114:    [emsesp]     Me(0x0B) -W-> thermostat(0x10), RC300Set(0x02B9), data: 00
2023-06-05 17:02:45.039   TRACE 115:    [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 10 20 2D 2D 00 CB 00 01 23 00 00 00 02 01 38 00 00 00 FB 00 00 0F 00 01 23 00 00
2023-06-05 17:02:45.216   TRACE 116:    [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 00 00 00 00 99 00 00 (offset 35)
2023-06-05 17:02:45.689   TRACE 118:    [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorWWPlus(0xE9), data: 32 01 DD 01 DD 00 00 00 00 46 3C 00 00 02 00 01 C3 00 00 19 00 00 00 32 02 00
2023-06-05 17:02:47.118   TRACE 119:    [emsesp]     Me(0x0B) -R-> thermostat(0x10), RC300Monitor(0x02A5), length: 0x19
2023-06-05 17:02:47.197   TRACE 120:    [emsesp]     thermostat(0x10) -W-> Me(0x0B), RC300Monitor(0x02A5), data: 80 00 11 2A 00 00 2A 26 01 2A 03 03 01 01 2A 02 96 00 00 11 02 00 FF FF 00
2023-06-05 17:02:47.364   TRACE 121:    [emsesp]     Me(0x0B) -R-> thermostat(0x10), RC300Monitor(0x02A5), length: 0x19 (offset 25)
2023-06-05 17:02:47.453   TRACE 122:    [emsesp]     thermostat(0x10) -W-> Me(0x0B), RC300Monitor(0x02A5), data: 00 00 00 00 00 00 FF 00 41 00 3C 01 FF 01 02 00 00 00 00 58 (offset 25)
2023-06-05 17:02:55.020   TRACE 123:    [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 10 20 2D 2D 00 CB 00 01 23 00 00 00 02 01 37 00 00 00 FB 00 00 0F 00 01 23 00 00
2023-06-05 17:02:55.196   TRACE 124:    [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 00 00 00 00 99 00 00 (offset 35)
2023-06-05 17:02:55.387   TRACE 125:    [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorSlowPlus2(0xE3), data: 04 00 00 00 00 00 00 00 00 00 00 01 23 00 64 41 00 00 00 00
2023-06-05 17:02:55.591   TRACE 126:    [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorWWPlus(0xE9), data: 32 01 DC 01 DC 00 00 00 00 46 3C 00 00 02 00 01 C3 00 00 19 00 00 00 32

change within MyBuderus App bring the change also in EMS-ESP, MQTT and the following debug log

2023-06-05 17:16:34.412   TRACE 1179:   [emsesp]     gateway(0x48) -W-> thermostat(0x10), ?(0x016E), data: FF
2023-06-05 17:16:35.018   TRACE 1180:   [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 10 20 2D 2D 00 CB 00 01 1E 00 00 00 02 01 30 00 00 00 F8 00 00 0F 00 01 1E 00 00
2023-06-05 17:16:35.194   TRACE 1181:   [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 00 00 00 00 99 00 00 (offset 35)
2023-06-05 17:16:35.384   TRACE 1182:   [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorSlowPlus2(0xE3), data: 04 00 00 00 00 00 00 00 00 00 00 01 1E 00 64 41 00 00 00 00
2023-06-05 17:16:35.633   TRACE 1183:   [emsesp]     thermostat(0x10) -W-> boiler(0x08), ?(0xE7), data: 00 02 00
2023-06-05 17:16:35.714   TRACE 1184:   [emsesp]     thermostat(0x10) -B-> All(0x00), RC300Monitor(0x02A5), data: 80 00 11 22 00 00 22 22 05 A0 00 03 01 01 1C 02 A4 00 00 11 02 00 FF FF
2023-06-05 17:16:35.943   TRACE 1185:   [emsesp]     thermostat(0x10) -B-> All(0x00), RC300Monitor(0x02A5), data: 00 00 00 00 00 00 00 FF 00 41 00 3C 01 FF 01 02 00 00 00 00 58 (offset 24)
2023-06-05 17:16:36.161   TRACE 1186:   [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorWWPlus(0xE9), data: 32 01 D3 01 D3 00 00 00 00 46 3C 00 00 02 00 01 C3 00 00 19 00 00 00 32 02 00
2023-06-05 17:16:36.475   TRACE 1187:   [emsesp]     thermostat(0x10) -W-> boiler(0x08), ?(0x02E0), data: 01 00 00 00 01
2023-06-05 17:16:36.503   TRACE 1188:   [emsesp]     thermostat(0x10) -W-> boiler(0x08), ?(0x02EA), data: 00
2023-06-05 17:16:36.553   TRACE 1189:   [emsesp]     thermostat(0x10) -B-> All(0x00), RC300WWmode2(0x031D), data: 00 00 00 00 00 00 00 00 00 06 5C
2023-06-05 17:16:36.738   TRACE 1190:   [emsesp]     thermostat(0x10) -B-> All(0x00), RC300Floordry(0x0267), data: 00 00
2023-06-05 17:16:36.916   TRACE 1191:   [emsesp]     thermostat(0x10) -B-> All(0x00), ?(0xC4), data: 00
2023-06-05 17:16:37.278   TRACE 1192:   [emsesp]     thermostat(0x10) -B-> All(0x00), RC300Monitor(0x02A5), data: 22 00 00 22 22 05 A0 (offset 3)
2023-06-05 17:16:37.461   TRACE 1193:   [emsesp]     thermostat(0x10) -B-> All(0x00), ?(0x016E), data: FF
2023-06-05 17:16:37.983   TRACE 1194:   [emsesp]     thermostat(0x10) -W-> boiler(0x08), ?(0xE7), data: 00 00 00
2023-06-05 17:16:38.069   TRACE 1195:   [emsesp]     thermostat(0x10) -B-> All(0x00), RC300WWmode2(0x031D), data: 00 (offset 8)
2023-06-05 17:16:45.012   TRACE 1196:   [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 10 20 2D 2D 00 CB 00 01 1E 00 00 00 02 01 30 00 00 00 F8 00 00 0F 00 01 1E 00 00
2023-06-05 17:16:45.189   TRACE 1197:   [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 00 00 00 00 99 00 00 (offset 35)
2023-06-05 17:16:45.379   TRACE 1198:   [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorSlowPlus2(0xE3), data: 04 00 00 00 00 00 00 00 00 00 00 01 1E 00 64 41 00 00 00 00
2023-06-05 17:16:45.583   TRACE 1199:   [emsesp]     boiler(0x08) -B-> All(0x00), UBAMonitorWWPlus(0xE9), data: 05 01 D3 01 D3 00 00 00 00 46 3C 00 00 02 00 01 C3 00 00 19 00 00 00 05 02 00
@proddy proddy added the bug Something isn't working label Jun 6, 2023
@proddy
Copy link
Contributor

proddy commented Jun 6, 2023

Clear write-up, thanks. We'll look into it.

@MichaelDvP
Copy link
Contributor

I think absence is not the same as mode. The thermostats also sets a lot of dhw settings after receiving the command.
It is a bit strange, 0x16E is listed on Norberts list as Junkers hc10 settings with offset 0 the type of hc.

Could you read the telegram 2B9 (terminal read 10 2B9) and give us the values in different modes. Also read the 16E telegram.

Use the settings custom entities to add a entitiy absence: device 0x10, type 0x16E, offset 0, INT, writable.
Then you can test different values, use -1 to set 0xFF to absence mode.

@theFeverDog
Copy link

I have a GB192i.2, currently still without the MX300, which is detected as the same device. I can also test this if needed.

@ralf-koe
Copy link
Author

ralf-koe commented Jun 7, 2023

Read 10 2B9 with absence deactivated
000+00:03:32.877 I 1: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Set(0x02B9), data: 00 00 2A 00 26 01 00 00 FF 00 2A 01 E1 20 01 0F 05 2E 00 01 22 02 2A 00 01 000+00:03:33.132 I 2: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Set(0x02B9), data: 30 22 00 00 2E 00 00 (offset 25)
Read 10 2B9 with absence activated
000+00:05:28.872 I 3: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Set(0x02B9), data: 00 00 2A 00 26 01 00 00 FF 00 2A 01 E1 20 01 0F 05 2E 00 01 22 02 2A 00 01 000+00:05:29.829 I 4: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Set(0x02B9), data: 30 22 00 00 2E 00 00 (offset 25)
and the value change also
grafik

and back to 0, after switch in the app.

Changing in EMS-ESP to -1 seems to be sendet, but nothing change in the app or MQTT. Change to 0 is the same.

Is this correct?
grafik

Read 10 16E in auto mode
000+00:01:46.847 I 1: [emsesp] thermostat(0x10) -W-> Me(0x0B), ?(0x016E), data: 00
and after setting over the app to manual
000+00:03:05.715 I 2: [emsesp] thermostat(0x10) -W-> Me(0x0B), ?(0x016E), data: FF

Test directly with the UI800 within the heater show the same results.

@ralf-koe
Copy link
Author

ralf-koe commented Jun 7, 2023

@theFeverDog

without MX300 the app is not useable, but if you can check the User definied entity, possibly it works for you.

Use the settings custom entities to add a entitiy absence: device 0x10, type 0x16E, offset 0, INT, writable.
Then you can test different values, use -1 to set 0xFF to absence mode.

@theFeverDog
Copy link

theFeverDog commented Jun 7, 2023 •
edited
Loading

without MX300 the app is not useable

I know, but this way I can verify if the issue originates with the MX300 or not... and hopefully have everything ready and working for when my MX300 arrives ;-)

So after creating the custom entity, I also see the value change from 0 to -1 if I switch the from Present to Absent via my remote control*. However, changing the value in the EMS-ESP interface is sent correctly, but is not reflected in the value, or the remote control display

(*) In my setup I also have a Buderus RC220 (recognized as an RT800), but this only seems to be a fancy temperature sensor with a display to control the settings exposed by the BC400/UI800.

@MichaelDvP
Copy link
Contributor

There is a bug in the dashboard input field, sending text instead of number if UOM is empty. Please set a UOM to make writing work.

@ralf-koe
Copy link
Author

ralf-koe commented Jun 8, 2023

Very good hint and cool, it works now.

How I can use the "User definied entity" with MQTT?

It looks like the value is not send to the MQTT server.

@theFeverDog
Copy link

I can confirm that it works after setting the UoM.

In MQTT the custom device is shown under the EMS-ESP itself (not under the boiler or thermostat, at least in Home Assistant), and the status updates correctly. However it's only a sensor and cannot be edited.

@MichaelDvP
Copy link
Contributor

However it's only a sensor and cannot be edited.

Yes, the custom entities are new in v3.6 and not completly implemented/tested. Mqtt-publish is in /custom_data/.

@ralf-koe
Copy link
Author

ralf-koe commented Jun 8, 2023

Thanks again and sorry, I should have checked it before in MQTT Explorer, reading works, publishing I will check later.

@proddy proddy closed this as completed Jun 24, 2023
@proddy proddy added this to the v3.6.0 milestone Jun 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
v3.6.0
Development

No branches or pull requests
4 participants
@theFeverDog @proddy @ralf-koe @MichaelDvP