Problem with system with more than 4 mixers.

[Shmul1]

Good afternoon.

My heating system has the following equipment:

1. 1 x Junkers CerapurMaxx ZBR 100-3
2. 1 x Gateway MB LAN 2
3. 1 x CW400 Thermostat
4. 7 x MM100 Mixing modules

I use 5 MM100 modules for heating, 1 MM100 module for hot water and 1 MM100 module for heating the pool. If I control the system via the Thermostat CW400, then everything works fine for me. Now I decided to connect the heating system to the Home Assistant via MQTT and I bought BBQKees Gateway E32. I can see all my equipment perfectly in the EMS-ESP web interface, but there is one problem. Mixer with 1-4 are shown as h1-h4, 5 becomes wwc1 Mixer, Mixer 6 becomes wwc2, but the mixer 7 (id8 for hot water) is wwc1!!! Thus in EMS-ESP got two mixer wwc1, MQTT and considers them as one and constantly reads the information for sensors from one to the other mixer!!! Is it possible to rename the mixer so that they are displayed correctly via MQTT? Is it possible, if there are more than 4 mixers in the system, then, for example, mixers 1-8 should be assigned the values h1-h8, and mixers 9 - wwc1, 10 - wwc2 (for CW800 users, for example)?

[proddy]

wow, that's one hell of a system. Could you send over the devices you have? http://ems-esp.local/api/system

[proddy]

I'm also thinking of extending the customization service we have in v3.4 so that each device can be renamed

[Shmul1]

{ "System": { "version": "3.3.1b1", "uptime": "000+01:42:37.927", "uptime (seconds)": 6157, "freemem": 111, "reset reason": "Power on reset / APP CPU reseted by PRO CPU", "Dallas sensors": 0 }, "Network": { "connection": "WiFi", "hostname": "ems-esp", "SSID": "HomeNet", "BSSID": "74:4D:28:F6:F4:64", "RSSI": -66, "MAC": "8C:CE:4E:95:14:84", "IPv4 address": "192.168.10.25/255.255.255.0", "IPv4 gateway": "192.168.10.1", "IPv4 nameserver": "8.8.8.8" }, "Status": { "bus status": "connected", "bus protocol": "HT3", "telegrams received": 20836, "read requests sent": 3504, "write requests sent": 0, "incomplete telegrams": 42, "tx fails": 0, "rx line quality": 100, "tx line quality": 100, "MQTT": "connected", "MQTT publishes": 8899, "MQTT publish fails": 0, "Dallas reads": 0, "Dallas fails": 0 }, "Devices": [ { "type": "Boiler", "name": "Junkers Topline/GB162 (DeviceID:0x08 ProductID:115, Version:05.09)", "handlers": "0x10 0x11 0xC2 0x14 0x15 0x1C 0x18 0x19 0x1A 0x35 0x16 0x33 0x34 0x26 0x2A 0xD1 0xE3 0xE4 0xE5 0xE6 0xE9 0xEA" }, { "type": "Thermostat", "name": "RC300/RC310/Moduline 3000/1010H/CW400/Sense II (DeviceID:0x10, ProductID:158, Version:18.05)", "handlers": "0xA3 0x06 0xA2 0x12 0x2A5 0x2B9 0x2AF 0x29B 0x471 0x2A6 0x2BA 0x2B0 0x29C 0x472 0x2A7 0x2BB 0x2B1 0x29D 0x473 0x2A8 0x2BC 0x2B2 0x29E 0x474 0x2F5 0x31B 0x31D 0x31E 0x23A 0x267 0x240" }, { "type": "Mixer", "name": "MM100 (DeviceID:0x20, ProductID:160, Version:24.05)", "handlers": "0x2D7" }, { "type": "Mixer", "name": "MM100 (DeviceID:0x28, ProductID:160, Version:24.05)", "handlers": "0x331" }, { "type": "Mixer", "name": "MM100 (DeviceID:0x23, ProductID:160, Version:24.05)", "handlers": "0x2DA" }, { "type": "Mixer", "name": "MM100 (DeviceID:0x22, ProductID:160, Version:24.05)", "handlers": "0x2D9" }, { "type": "Mixer", "name": "MM100 (DeviceID:0x21, ProductID:160, Version:24.05)", "handlers": "0x2D8" }, { "type": "Mixer", "name": "MM100 (DeviceID:0x24, ProductID:160, Version:24.05)", "handlers": "0x2DB" }, { "type": "Mixer", "name": "MM100 (DeviceID:0x25, ProductID:160, Version:24.05)", "handlers": "0x2DC" }, { "type": "Gateway", "name": "KM200/MB LAN 2 (DeviceID:0x48, ProductID:189, Version:04.07)" }, { "type": "Controller", "name": "BC10 (DeviceID:0x09, ProductID:114, Version:02.01)" } ] }

[MichaelDvP]

One thing is a simple naming issue, we have only names for h1-hc4, as the thermostats only have 4 heatingcircuits. (we need to insert TAG_HC5, -TAG_HC8) The mixers device ID 0x20-0x27 are already assigned as heating, 0x28 and 0x29 as warm water. Now it's interesting what your mixers 0x24 and 0x25 sends, can you make a log from the telegrams (more than a minute). I think ID 0x24 (mixer 5 is wrongly named wwc1 but shows right values. ID 0x25 (named wwc2) is the pool? Then the handler 0x2DC is not right.

[Shmul1]

can you make a log from the telegrams (more than a minute).

Can you tell me please, what should I do exactly, Iam first day user :)))

[Shmul1]

2022-01-15 19:09:34.935 D 256: [telegram] Sending read Tx [#108], telegram: 8B 90 FF 00 20 01 9C 2022-01-15 19:09:34.992 D 257: [emsesp] Last Tx read successful 2022-01-15 19:09:35.685 D 258: [telegram] Sending read Tx [#109], telegram: 8B 90 FF 00 20 01 A7 2022-01-15 19:09:35.781 D 259: [emsesp] Last Tx read successful 2022-01-15 19:09:36.585 D 260: [telegram] Sending read Tx [#129], telegram: 8B 90 FF 19 20 01 A7 2022-01-15 19:09:36.661 D 261: [emsesp] Last Tx read successful 2022-01-15 19:09:37.661 D 262: [telegram] Sending read Tx [#110], telegram: 8B 90 FF 00 20 01 BB 2022-01-15 19:09:37.746 D 263: [emsesp] Last Tx read successful 2022-01-15 19:09:38.385 D 264: [telegram] Sending read Tx [#111], telegram: 8B 90 FF 00 20 01 B1 2022-01-15 19:09:38.452 D 265: [emsesp] Last Tx read successful 2022-01-15 19:09:39.035 D 266: [telegram] Sending read Tx [#112], telegram: 8B 90 FF 00 20 01 9D 2022-01-15 19:09:39.095 D 267: [emsesp] Last Tx read successful 2022-01-15 19:09:39.735 D 268: [telegram] Sending read Tx [#113], telegram: 8B 90 FF 00 20 01 A8 2022-01-15 19:09:39.836 D 269: [emsesp] Last Tx read successful 2022-01-15 19:09:40.409 D 270: [telegram] Sending read Tx [#130], telegram: 8B 90 FF 19 20 01 A8 2022-01-15 19:09:40.484 D 271: [emsesp] Last Tx read successful 2022-01-15 19:09:41.185 D 272: [telegram] Sending read Tx [#114], telegram: 8B 90 FF 00 20 01 BC 2022-01-15 19:09:41.273 D 273: [emsesp] Last Tx read successful 2022-01-15 19:09:41.885 D 274: [telegram] Sending read Tx [#115], telegram: 8B 90 FF 00 20 01 B2 2022-01-15 19:09:41.947 D 275: [emsesp] Last Tx read successful 2022-01-15 19:09:42.536 D 276: [telegram] Sending read Tx [#116], telegram: 8B 90 FF 00 20 01 9E 2022-01-15 19:09:42.598 D 277: [emsesp] Last Tx read successful 2022-01-15 19:09:43.067 D 278: [mqtt] Publishing topic ems-esp/boiler_data (#10911, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:09:43.168 D 279: [mqtt] Publishing topic ems-esp/boiler_data_ww (#10912, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:09:43.235 D 280: [telegram] Sending read Tx [#117], telegram: 8B 90 FF 00 20 01 F5 2022-01-15 19:09:43.269 D 281: [mqtt] Publishing topic ems-esp/thermostat_data (#10913, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:09:43.320 D 282: [emsesp] Last Tx read successful 2022-01-15 19:09:43.370 D 283: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#10914, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:09:43.471 D 284: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#10915, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:09:43.572 D 285: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#10916, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:09:43.673 D 286: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#10917, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:09:43.774 D 287: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#10918, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:09:43.875 D 288: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10919, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:09:43.910 D 289: [telegram] Sending read Tx [#118], telegram: 8B 90 FF 00 20 02 1B 2022-01-15 19:09:43.959 D 290: [emsesp] Last Tx read successful 2022-01-15 19:09:43.976 D 291: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#10920, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:09:44.077 D 292: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#10921, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:09:44.178 D 293: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#10922, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:09:44.279 D 294: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10923, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:09:44.380 D 295: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#10924, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:09:44.610 D 296: [telegram] Sending read Tx [#119], telegram: 8B 90 FF 00 20 01 3A 2022-01-15 19:09:44.655 D 297: [emsesp] Last Tx read successful 2022-01-15 19:09:45.235 D 298: [telegram] Sending read Tx [#120], telegram: 8B 90 FF 00 20 01 40 2022-01-15 19:09:45.315 D 299: [emsesp] Last Tx read successful 2022-01-15 19:09:46.011 D 300: [telegram] Sending read Tx [#121], telegram: 8B A8 FF 00 20 02 31 2022-01-15 19:09:46.083 D 301: [emsesp] Last Tx read successful 2022-01-15 19:09:47.085 D 302: [telegram] Sending read Tx [#122], telegram: 8B A3 FF 00 20 01 DA 2022-01-15 19:09:47.147 D 303: [emsesp] Last Tx read successful 2022-01-15 19:09:47.735 D 304: [telegram] Sending read Tx [#123], telegram: 8B A2 FF 00 20 01 D9 2022-01-15 19:09:47.796 D 305: [emsesp] Last Tx read successful 2022-01-15 19:09:48.435 D 306: [telegram] Sending read Tx [#124], telegram: 8B A1 FF 00 20 01 D8 2022-01-15 19:09:48.497 D 307: [emsesp] Last Tx read successful 2022-01-15 19:09:49.085 D 308: [telegram] Sending read Tx [#125], telegram: 8B A4 FF 00 20 01 DB 2022-01-15 19:09:49.147 D 309: [emsesp] Last Tx read successful 2022-01-15 19:09:49.604 D 310: [emsesp] No telegram type handler found for ID 0x255 (src 0x23) 2022-01-15 19:09:50.335 D 311: [telegram] Sending read Tx [#126], telegram: 8B A5 FF 00 20 01 DC 2022-01-15 19:09:50.397 D 312: [emsesp] Last Tx read successful 2022-01-15 19:09:53.086 D 313: [mqtt] Publishing topic ems-esp/boiler_data (#10925, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:09:53.187 D 314: [mqtt] Publishing topic ems-esp/boiler_data_ww (#10926, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:09:53.288 D 315: [mqtt] Publishing topic ems-esp/thermostat_data (#10927, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:09:53.389 D 316: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#10928, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:09:53.490 D 317: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#10929, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:09:53.591 D 318: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#10930, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:09:53.692 D 319: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#10931, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:09:53.793 D 320: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#10932, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:09:53.894 D 321: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10933, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:09:53.995 D 322: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#10934, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:09:54.096 D 323: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#10935, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:09:54.197 D 324: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#10936, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:09:54.298 D 325: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10937, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:09:54.399 D 326: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#10938, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:09:58.053 D 327: [emsesp] No telegram type handler found for ID 0x255 (src 0x22) 2022-01-15 19:10:03.085 D 328: [mqtt] Publishing topic ems-esp/boiler_data (#10939, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:10:03.186 D 329: [mqtt] Publishing topic ems-esp/boiler_data_ww (#10940, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:10:03.287 D 330: [mqtt] Publishing topic ems-esp/thermostat_data (#10941, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:10:03.388 D 331: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#10942, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:03.489 D 332: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#10943, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:03.590 D 333: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#10944, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:03.691 D 334: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#10945, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:03.792 D 335: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#10946, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:03.893 D 336: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10947, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:10:03.994 D 337: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#10948, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:04.095 D 338: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#10949, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:04.196 D 339: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#10950, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:04.297 D 340: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10951, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:04.398 D 341: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#10952, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:07.303 D 342: [emsesp] No telegram type handler found for ID 0x255 (src 0x21) 2022-01-15 19:10:09.035 W 343: [telegram] Incomplete Rx: C8 90 F9 00 11 2022-01-15 19:10:13.084 D 344: [mqtt] Publishing topic ems-esp/boiler_data (#10953, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:10:13.185 D 345: [mqtt] Publishing topic ems-esp/boiler_data_ww (#10954, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:10:13.286 D 346: [mqtt] Publishing topic ems-esp/thermostat_data (#10955, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:10:13.388 D 347: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#10956, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:13.489 D 348: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#10957, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:13.590 D 349: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#10958, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:13.691 D 350: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#10959, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:13.792 D 351: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#10960, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:13.893 D 352: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10961, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:10:13.994 D 353: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#10962, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:14.095 D 354: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#10963, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:14.196 D 355: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#10964, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:14.297 D 356: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10965, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:14.398 D 357: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#10966, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:17.631 D 358: [emsesp] No telegram type handler found for ID 0x255 (src 0x20) 2022-01-15 19:10:23.084 D 359: [mqtt] Publishing topic ems-esp/boiler_data (#10967, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:10:23.144 D 360: [emsesp] Fetching values for device ID 0x20 2022-01-15 19:10:23.144 D 361: [telegram] Tx read request to device 0x20 for type ID 0x2D7 2022-01-15 19:10:23.144 D 362: [emsesp] Fetching values for device ID 0x08 2022-01-15 19:10:23.144 D 363: [telegram] Tx read request to device 0x08 for type ID 0x14 2022-01-15 19:10:23.144 D 364: [telegram] Tx read request to device 0x08 for type ID 0x16 2022-01-15 19:10:23.144 D 365: [telegram] Tx read request to device 0x08 for type ID 0x33 2022-01-15 19:10:23.144 D 366: [emsesp] Fetching values for device ID 0x10 2022-01-15 19:10:23.144 D 367: [telegram] Tx read request to device 0x10 for type ID 0x2A5 2022-01-15 19:10:23.144 D 368: [telegram] Tx read request to device 0x10 for type ID 0x2B9 2022-01-15 19:10:23.144 D 369: [telegram] Tx read request to device 0x10 for type ID 0x2AF 2022-01-15 19:10:23.144 D 370: [telegram] Tx read request to device 0x10 for type ID 0x29B 2022-01-15 19:10:23.144 D 371: [telegram] Tx read request to device 0x10 for type ID 0x2A6 2022-01-15 19:10:23.144 D 372: [telegram] Tx read request to device 0x10 for type ID 0x2BA 2022-01-15 19:10:23.144 D 373: [telegram] Tx read request to device 0x10 for type ID 0x2B0 2022-01-15 19:10:23.144 D 374: [telegram] Tx read request to device 0x10 for type ID 0x29C 2022-01-15 19:10:23.144 D 375: [telegram] Tx read request to device 0x10 for type ID 0x2A7 2022-01-15 19:10:23.144 D 376: [telegram] Tx read request to device 0x10 for type ID 0x2BB 2022-01-15 19:10:23.144 D 377: [telegram] Tx read request to device 0x10 for type ID 0x2B1 2022-01-15 19:10:23.144 D 378: [telegram] Tx read request to device 0x10 for type ID 0x29D 2022-01-15 19:10:23.144 D 379: [telegram] Tx read request to device 0x10 for type ID 0x2A8 2022-01-15 19:10:23.144 D 380: [telegram] Tx read request to device 0x10 for type ID 0x2BC 2022-01-15 19:10:23.144 D 381: [telegram] Tx read request to device 0x10 for type ID 0x2B2 2022-01-15 19:10:23.144 D 382: [telegram] Tx read request to device 0x10 for type ID 0x29E 2022-01-15 19:10:23.144 D 383: [telegram] Tx read request to device 0x10 for type ID 0x2F5 2022-01-15 19:10:23.144 D 384: [telegram] Tx read request to device 0x10 for type ID 0x31B 2022-01-15 19:10:23.144 D 385: [telegram] Tx read request to device 0x10 for type ID 0x23A 2022-01-15 19:10:23.144 D 386: [telegram] Tx read request to device 0x10 for type ID 0x240 2022-01-15 19:10:23.144 D 387: [emsesp] Fetching values for device ID 0x48 2022-01-15 19:10:23.144 D 388: [emsesp] Fetching values for device ID 0x09 2022-01-15 19:10:23.144 D 389: [emsesp] Fetching values for device ID 0x28 2022-01-15 19:10:23.144 D 390: [telegram] Tx read request to device 0x28 for type ID 0x331 2022-01-15 19:10:23.144 D 391: [emsesp] Fetching values for device ID 0x23 2022-01-15 19:10:23.144 D 392: [telegram] Tx read request to device 0x23 for type ID 0x2DA 2022-01-15 19:10:23.144 D 393: [emsesp] Fetching values for device ID 0x22 2022-01-15 19:10:23.144 D 394: [telegram] Tx read request to device 0x22 for type ID 0x2D9 2022-01-15 19:10:23.144 D 395: [emsesp] Fetching values for device ID 0x21 2022-01-15 19:10:23.144 D 396: [telegram] Tx read request to device 0x21 for type ID 0x2D8 2022-01-15 19:10:23.144 D 397: [emsesp] Fetching values for device ID 0x24 2022-01-15 19:10:23.144 D 398: [telegram] Tx read request to device 0x24 for type ID 0x2DB 2022-01-15 19:10:23.144 D 399: [emsesp] Fetching values for device ID 0x25 2022-01-15 19:10:23.144 D 400: [telegram] Tx read request to device 0x25 for type ID 0x2DC 2022-01-15 19:10:23.185 D 401: [mqtt] Publishing topic ems-esp/boiler_data_ww (#10968, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:10:23.286 D 402: [mqtt] Publishing topic ems-esp/thermostat_data (#10969, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:10:23.387 D 403: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#10970, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:23.488 D 404: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#10971, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:23.589 D 405: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#10972, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:23.690 D 406: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#10973, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:23.760 D 407: [telegram] Sending read Tx [#131], telegram: 8B A0 FF 00 20 01 D7 2022-01-15 19:10:23.791 D 408: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#10974, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:23.822 D 409: [emsesp] Last Tx read successful 2022-01-15 19:10:23.892 D 410: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10975, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:10:23.993 D 411: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#10976, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:24.094 D 412: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#10977, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:24.195 D 413: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#10978, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:24.296 D 414: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10979, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:24.397 D 415: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#10980, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:24.460 D 416: [telegram] Sending read Tx [#132], telegram: 8B 88 14 00 20 2022-01-15 19:10:24.492 D 417: [emsesp] Last Tx read successful 2022-01-15 19:10:24.498 D 418: [mqtt] Publishing topic ems-esp/heartbeat (#10981, retain=0, retry=1, size=215, pid=1) 2022-01-15 19:10:25.060 D 419: [telegram] Sending read Tx [#133], telegram: 8B 88 16 00 20 2022-01-15 19:10:25.102 D 420: [emsesp] Last Tx read successful 2022-01-15 19:10:25.785 D 421: [telegram] Sending read Tx [#134], telegram: 8B 88 33 00 20 2022-01-15 19:10:25.825 D 422: [emsesp] Last Tx read successful 2022-01-15 19:10:26.635 D 423: [telegram] Sending read Tx [#135], telegram: 8B 90 FF 00 20 01 A5 2022-01-15 19:10:26.735 D 424: [emsesp] Last Tx read successful 2022-01-15 19:10:27.981 D 425: [emsesp] No telegram type handler found for ID 0x255 (src 0x28) 2022-01-15 19:10:28.510 D 426: [telegram] Sending read Tx [#161], telegram: 8B 90 FF 19 20 01 A5 2022-01-15 19:10:28.583 D 427: [emsesp] Last Tx read successful 2022-01-15 19:10:29.235 D 428: [telegram] Sending read Tx [#136], telegram: 8B 90 FF 00 20 01 B9 2022-01-15 19:10:29.324 D 429: [emsesp] Last Tx read successful 2022-01-15 19:10:29.935 W 430: [telegram] Incomplete Rx: 04 FA 00 2022-01-15 19:10:30.160 D 431: [telegram] Sending read Tx [#137], telegram: 8B 90 FF 00 20 01 AF 2022-01-15 19:10:30.221 D 432: [emsesp] Last Tx read successful 2022-01-15 19:10:30.581 D 433: [emsesp] No telegram type handler found for ID 0x255 (src 0x24) 2022-01-15 19:10:31.235 D 434: [telegram] Sending read Tx [#138], telegram: 8B 90 FF 00 20 01 9B 2022-01-15 19:10:31.297 D 435: [emsesp] Last Tx read successful 2022-01-15 19:10:31.860 D 436: [telegram] Sending read Tx [#139], telegram: 8B 90 FF 00 20 01 A6 2022-01-15 19:10:31.957 D 437: [emsesp] Last Tx read successful 2022-01-15 19:10:33.010 W 438: [telegram] Incomplete Rx: C8 90 F9 00 2022-01-15 19:10:33.015 D 439: [mqtt] Publishing topic ems-esp/boiler_data (#10982, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:10:33.116 D 440: [mqtt] Publishing topic ems-esp/boiler_data_ww (#10983, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:10:33.217 D 441: [mqtt] Publishing topic ems-esp/thermostat_data (#10984, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:10:33.236 D 442: [telegram] Sending read Tx [#162], telegram: 8B 90 FF 19 20 01 A6 2022-01-15 19:10:33.310 D 443: [emsesp] Last Tx read successful 2022-01-15 19:10:33.318 D 444: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#10985, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:33.419 D 445: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#10986, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:33.520 D 446: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#10987, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:33.621 D 447: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#10988, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:33.722 D 448: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#10989, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:33.823 D 449: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10990, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:10:33.924 D 450: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#10991, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:34.010 D 451: [telegram] Sending read Tx [#140], telegram: 8B 90 FF 00 20 01 BA 2022-01-15 19:10:34.034 D 452: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#10992, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:34.099 D 453: [emsesp] Last Tx read successful 2022-01-15 19:10:34.135 D 454: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#10993, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:34.236 D 455: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#10994, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:34.337 D 456: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#10995, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:35.003 D 457: [emsesp] No telegram type handler found for ID 0x255 (src 0x25) 2022-01-15 19:10:35.610 D 458: [telegram] Sending read Tx [#141], telegram: 8B 90 FF 00 20 01 B0 2022-01-15 19:10:35.676 D 459: [emsesp] Last Tx read successful 2022-01-15 19:10:36.310 D 460: [telegram] Sending read Tx [#142], telegram: 8B 90 FF 00 20 01 9C 2022-01-15 19:10:36.367 D 461: [emsesp] Last Tx read successful 2022-01-15 19:10:37.335 D 462: [telegram] Sending read Tx [#143], telegram: 8B 90 FF 00 20 01 A7 2022-01-15 19:10:37.436 D 463: [emsesp] Last Tx read successful 2022-01-15 19:10:38.085 D 464: [telegram] Sending read Tx [#163], telegram: 8B 90 FF 19 20 01 A7 2022-01-15 19:10:38.155 D 465: [emsesp] Last Tx read successful 2022-01-15 19:10:38.935 D 466: [telegram] Sending read Tx [#144], telegram: 8B 90 FF 00 20 01 BB 2022-01-15 19:10:39.025 D 467: [emsesp] Last Tx read successful 2022-01-15 19:10:39.710 D 468: [telegram] Sending read Tx [#145], telegram: 8B 90 FF 00 20 01 B1 2022-01-15 19:10:39.779 D 469: [emsesp] Last Tx read successful 2022-01-15 19:10:40.410 D 470: [telegram] Sending read Tx [#146], telegram: 8B 90 FF 00 20 01 9D 2022-01-15 19:10:40.470 D 471: [emsesp] Last Tx read successful 2022-01-15 19:10:41.060 D 472: [telegram] Sending read Tx [#147], telegram: 8B 90 FF 00 20 01 A8 2022-01-15 19:10:41.154 D 473: [emsesp] Last Tx read successful 2022-01-15 19:10:41.810 D 474: [telegram] Sending read Tx [#164], telegram: 8B 90 FF 19 20 01 A8 2022-01-15 19:10:41.883 D 475: [emsesp] Last Tx read successful 2022-01-15 19:10:42.485 D 476: [telegram] Sending read Tx [#148], telegram: 8B 90 FF 00 20 01 BC 2022-01-15 19:10:42.568 D 477: [emsesp] Last Tx read successful 2022-01-15 19:10:43.046 D 478: [mqtt] Publishing topic ems-esp/boiler_data (#10996, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:10:43.147 D 479: [mqtt] Publishing topic ems-esp/boiler_data_ww (#10997, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:10:43.210 D 480: [telegram] Sending read Tx [#149], telegram: 8B 90 FF 00 20 01 B2 2022-01-15 19:10:43.248 D 481: [mqtt] Publishing topic ems-esp/thermostat_data (#10998, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:10:43.274 D 482: [emsesp] Last Tx read successful 2022-01-15 19:10:43.349 D 483: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#10999, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:43.450 D 484: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#11000, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:43.551 D 485: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#11001, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:43.652 D 486: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#11002, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:43.753 D 487: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#11003, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:43.835 D 488: [telegram] Sending read Tx [#150], telegram: 8B 90 FF 00 20 01 9E 2022-01-15 19:10:43.854 D 489: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#11004, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:10:43.893 D 490: [emsesp] Last Tx read successful 2022-01-15 19:10:43.957 D 491: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#11005, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:44.058 D 492: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#11006, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:44.159 D 493: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#11007, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:44.260 D 494: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#11008, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:44.361 D 495: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#11009, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:44.585 D 496: [telegram] Sending read Tx [#151], telegram: 8B 90 FF 00 20 01 F5 2022-01-15 19:10:44.671 D 497: [emsesp] Last Tx read successful 2022-01-15 19:10:45.285 D 498: [telegram] Sending read Tx [#152], telegram: 8B 90 FF 00 20 02 1B 2022-01-15 19:10:45.334 D 499: [emsesp] Last Tx read successful 2022-01-15 19:10:45.935 D 500: [telegram] Sending read Tx [#153], telegram: 8B 90 FF 00 20 01 3A 2022-01-15 19:10:45.982 D 501: [emsesp] Last Tx read successful 2022-01-15 19:10:47.010 D 502: [telegram] Sending read Tx [#154], telegram: 8B 90 FF 00 20 01 40 2022-01-15 19:10:47.090 D 503: [emsesp] Last Tx read successful 2022-01-15 19:10:47.685 D 504: [telegram] Sending read Tx [#155], telegram: 8B A8 FF 00 20 02 31 2022-01-15 19:10:47.757 D 505: [emsesp] Last Tx read successful 2022-01-15 19:10:48.410 D 506: [telegram] Sending read Tx [#156], telegram: 8B A3 FF 00 20 01 DA 2022-01-15 19:10:48.472 D 507: [emsesp] Last Tx read successful 2022-01-15 19:10:49.035 D 508: [telegram] Sending read Tx [#157], telegram: 8B A2 FF 00 20 01 D9 2022-01-15 19:10:49.097 D 509: [emsesp] Last Tx read successful 2022-01-15 19:10:49.456 D 510: [emsesp] No telegram type handler found for ID 0x255 (src 0x23) 2022-01-15 19:10:50.185 D 511: [telegram] Sending read Tx [#158], telegram: 8B A1 FF 00 20 01 D8 2022-01-15 19:10:50.247 D 512: [emsesp] Last Tx read successful 2022-01-15 19:10:50.860 D 513: [telegram] Sending read Tx [#159], telegram: 8B A4 FF 00 20 01 DB 2022-01-15 19:10:50.922 D 514: [emsesp] Last Tx read successful 2022-01-15 19:10:51.510 D 515: [telegram] Sending read Tx [#160], telegram: 8B A5 FF 00 20 01 DC 2022-01-15 19:10:51.572 D 516: [emsesp] Last Tx read successful 2022-01-15 19:10:53.005 D 517: [mqtt] Publishing topic ems-esp/boiler_data (#11010, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:10:53.106 D 518: [mqtt] Publishing topic ems-esp/boiler_data_ww (#11011, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:10:53.207 D 519: [mqtt] Publishing topic ems-esp/thermostat_data (#11012, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:10:53.308 D 520: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#11013, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:53.409 D 521: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#11014, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:53.510 D 522: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#11015, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:10:53.611 D 523: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#11016, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:10:53.712 D 524: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#11017, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:53.813 D 525: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#11018, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:10:53.914 D 526: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#11019, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:54.015 D 527: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#11020, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:54.116 D 528: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#11021, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:10:54.217 D 529: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#11022, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:54.318 D 530: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#11023, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:10:57.881 D 531: [emsesp] No telegram type handler found for ID 0x255 (src 0x22) 2022-01-15 19:11:03.005 D 532: [mqtt] Publishing topic ems-esp/boiler_data (#11024, retain=0, retry=1, size=608, pid=1) 2022-01-15 19:11:03.106 D 533: [mqtt] Publishing topic ems-esp/boiler_data_ww (#11025, retain=0, retry=1, size=234, pid=1) 2022-01-15 19:11:03.207 D 534: [mqtt] Publishing topic ems-esp/thermostat_data (#11026, retain=0, retry=1, size=145, pid=1) 2022-01-15 19:11:03.308 D 535: [mqtt] Publishing topic ems-esp/thermostat_data_hc1 (#11027, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:11:03.409 D 536: [mqtt] Publishing topic ems-esp/thermostat_data_hc2 (#11028, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:11:03.510 D 537: [mqtt] Publishing topic ems-esp/thermostat_data_hc3 (#11029, retain=0, retry=1, size=357, pid=1) 2022-01-15 19:11:03.611 D 538: [mqtt] Publishing topic ems-esp/thermostat_data_hc4 (#11030, retain=0, retry=1, size=350, pid=1) 2022-01-15 19:11:03.712 D 539: [mqtt] Publishing topic ems-esp/mixer_data_hc1 (#11031, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:11:03.813 D 540: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#11032, retain=0, retry=1, size=51, pid=1) 2022-01-15 19:11:03.914 D 541: [mqtt] Publishing topic ems-esp/mixer_data_hc4 (#11033, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:11:04.015 D 542: [mqtt] Publishing topic ems-esp/mixer_data_hc3 (#11034, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:11:04.116 D 543: [mqtt] Publishing topic ems-esp/mixer_data_hc2 (#11035, retain=0, retry=1, size=80, pid=1) 2022-01-15 19:11:04.217 D 544: [mqtt] Publishing topic ems-esp/mixer_data_wwc1 (#11036, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:11:04.318 D 545: [mqtt] Publishing topic ems-esp/mixer_data_wwc2 (#11037, retain=0, retry=1, size=79, pid=1) 2022-01-15 19:11:06.380 D 546: [emsesp] No telegram type handler found for ID 0x255 (src 0x21)

[MichaelDvP]

Good, but use log level ALL to see the telegrams, You can download to a text-file and drop the file here.

[Shmul1]

ok

[Shmul1]

log.txt

[Shmul1]

0x20-0x23 and 0x25 - hc 0x24 - pool 0x28 - wwc

[Shmul1]

EMS Devices screen: 0x24 & 0x28 - wwc1 0x25 - wwc2

[MichaelDvP]

Ok, looks like the pool behave like a normal heating circuit and telegram 0x2DB is right:

2022-01-15 19:13:50.658 T 1155: [emsesp] Me(0x0B) <- Mixer(0x24), MMPLUSStatusMessage_HC(0x2DB), data: 20
2022-01-15 19:13:50.720 D 1156: [emsesp] Last Tx read successful
2022-01-15 19:13:50.720 T 1157: [emsesp] Mixer(0x24) -> Me(0x0B), MMPLUSStatusMessage_HC(0x2DB), data: 01 00 00 80 00 46 08 00 08

Then we only need to add the names. The telegram contains no measured temperature, flow-setpoint is 70°C,

@proddy should i make a pr to 3.4, or dev-branch?

[Shmul1]

I have made a little video. First, the sensors receive data from 0x28, and then from 0x2

https://user-images.githubusercontent.com/51746237/149632083-16b32c5b-d03f-4cc3-8af5-60b1d4bed712.mp4

4

[MichaelDvP]

I've added to proddys v3.4alpha, please check if this solves the issue. After uploading the bin you need to refresh the page in your browser. EMS-ESP-3_4_0a13-ESP32.zip

[Shmul1]

thanks, uploading

[Shmul1]

Now I see all mixers in HA, thank you! This firmware is a very big progress in your work!

[proddy]

thanks @MichaelDvP for the quick fix

[MichaelDvP]

Next step is to add the heating circuits to the thermostat. I've found on NorbertS' list that this thermostat have 8 ciircuits in row. I'm curious if the buffers for web/mqtt are large enought for all these circuits. Please check dashboard for thermostat, mqtt and http://ems-esp.local/api/thermostat Here is the bin with more thermostat hcs. (Update with also single publish): EMS-ESP-3_4_0a13-ESP32.zip

[Shmul1]

{ "errorcode": "A35(3125)", "datetime": "10:46:55 16.01.2022", "floordry": 0, "dampedoutdoortemp": 0.9, "floordrytemp": 0, "building": 1, "minexttemp": -20, "wwsettemp": 60, "wwmode": 4, "wwsettemplow": 45, "wwcircmode": 3, "wwchargeduration": 60, "wwcharge": "off", "wwextra1": 0, "wwdisinfecting": "on", "wwdisinfectday": 1, "wwdisinfecttime": 120, "hc2": { "seltemp": 21, "mode": 1, "modetype": 1, "ecotemp": 29.5, "manualtemp": 21, "comforttemp": 30, "summertemp": 17, "designtemp": 45, "offsettemp": 0, "minflowtemp": 25, "maxflowtemp": 43, "roominfluence": 3, "curroominfl": 0, "nofrosttemp": 5, "targetflowtemp": 45, "heatingtype": 3, "summersetmode": 1, "summermode": "off", "controlmode": 6, "program": 0, "tempautotemp": -0.5, "fastheatup": 0 }, "hc4": { "seltemp": 21, "mode": 1, "modetype": 1, "ecotemp": 29.5, "manualtemp": 21, "comforttemp": 30, "summertemp": 17, "designtemp": 45, "offsettemp": 0, "minflowtemp": 25, "maxflowtemp": 43, "roominfluence": 3, "curroominfl": 0, "nofrosttemp": 5, "targetflowtemp": 45, "heatingtype": 3, "summersetmode": 1, "summermode": "off", "controlmode": 6, "program": 0, "tempautotemp": -0.5, "fastheatup": 0 }, "hc1": { "seltemp": 21, "mode": 1, "modetype": 1, "curroominfl": 0, "targetflowtemp": 45, "summermode": "off" }, "hc3": { "seltemp": 21, "mode": 1, "modetype": 1, "ecotemp": 29.5, "manualtemp": 21, "comforttemp": 30, "summertemp": 17, "designtemp": 45, "offsettemp": 0, "minflowtemp": 25, "maxflowtemp": 43, "roominfluence": 3, "curroominfl": 0, "nofrosttemp": 5, "targetflowtemp": 45, "heatingtype": 3, "summersetmode": 1, "summermode": "off", "controlmode": 6, "program": 0, "tempautotemp": -0.5, "fastheatup": 0 }, "hc5": { "seltemp": 21, "mode": 1, "modetype": 1, "ecotemp": 15, "manualtemp": 21, "comforttemp": 30, "summertemp": 17, "designtemp": 75, "offsettemp": 0, "minflowtemp": 25, "maxflowtemp": 75, "roominfluence": 3, "curroominfl": 0, "nofrosttemp": 5, "targetflowtemp": 70, "heatingtype": 1, "summersetmode": 1, "summermode": "off", "controlmode": 6, "program": 0, "tempautotemp": -0.5, "fastheatup": 0 }, "hc6": { "seltemp": 21, "mode": 1, "modetype": 1, "ecotemp": 29.5, "manualtemp": 21, "comforttemp": 30, "summertemp": 17, "designtemp": 45, "offsettemp": 0, "minflowtemp": 25, "maxflowtemp": 43, "roominfluence": 3, "curroominfl": 0, "nofrosttemp": 5, "targetflowtemp": 45, "heatingtype": 3, "summersetmode": 1, "summermode": "off", "controlmode": 6, "program": 0, "tempautotemp": -0.5, "fastheatup": 0 } }

[MichaelDvP]

Looks good, only hc1 have to few values, wait a minute to allow emsesp to read all values. Does web-dashboard also show all values for all hc? Also check Settings -> Customization for the thermostat.

[Shmul1]

Yes? dashboard shows all. Customization ok. I have restarted EMS-ESP but hc1 still have to few values, telegrams.txt .

[MichaelDvP]

I have restarted EMS-ESP but hc1 still have to few values,

After restart it always take some minutes to collect all data from bus. Do you use mqtt? Then check the mqtt-publish for thermostat and mixer, especially for (MQTT) nested formatting and (Settings) Enum-format Value. I think the 4k buffer for mqtt is to small for nested formatting.

[proddy]

the API call to http://ems-esp.local/api/thermostat uses a large buffer (EMSESP_JSON_SIZE_XXLARGE_DYN in WebAPIService.cpp) so I would expect to see all the hc1 values in that call

[Shmul1]

I have changed Enum-format from Index to Value and now I have: Boiler entities 43 (was 56), thermostat entities 133 (was 133). But http://ems-esp.local/api/thermostat now shows "null", customization is empty for all devices. I try to watch entities by tapping on device and the list of sensors do not appear. After that I changed Enum-format to Index back, Now I have: Boiler entities 42, thermostat entities 133. situation with API, sensor list and customization the same, it doesn't work

[Shmul1]

I do all these actions with a delay of more than 5 minutes

[Shmul1]

Now I have uploaded firmware and the problem with customization, API and entity list disappeared

[Shmul1]

Enum-format - Value thermostats.txt

[MichaelDvP]

I'm confused that hc1 is not sorted to front and it contains only values from the hc1-monitor telegram. @proddy any idea why? @Shmul1 Please make another >1 min log with loglevel ALL i like to see if the other telegrams are empty or not fetched.

@proddy what do you think about inserting in EMSESP::publish_device_values

        if (doc.overflowed()) {
            LOG_WARNING(F("buffer overflow, please use individual topics"));
        }

[Shmul1]

log (1).txt

[MichaelDvP]

Thanks, i see the problem.

1. @proddys new hextoa() cuts the high byte from type-id, but this is cosmetic.
2. the tx-queue overflows and the first messages are ignored, Maybe we should wait for empty queue before generating the messages for next device. Quick solution is to enlarge the queue.

[MichaelDvP]

This is the quick solution, i think now all values should be there. I've added the suggested warning for mqtt overflow. EMS-ESP-3_4_0a13-ESP32.zip

[proddy]

thanks @MichaelDvP for those fixes

[Shmul1]

Good job, thank you!

[Shmul1]

thermostats.txt

[MichaelDvP]

@Shmul1 Have you already checked the mqtt-output?

[Shmul1]

Yes, of course, I sent the log back on Sunday. The firmware works well, but there is one more thing. In your firmware, warm water is prepared only through a circuit in the boiler, and in my case through a separate circuit "wwc1", so the sensors associated with warm water do not work. Is it possible to fix this?

[MichaelDvP]

Is it possible to fix this?

It need some work, but i think it's possible. The wwc has two telegrams: Mixer(0x28) -> All(0x00), MMPLUSStatusMessage_WWC(0x331), data: 02 4E 00 3C 00 3C 3C 46 02 03 04 00 3C here we know only 024E as flowtemp, 00 as pumpstatus and offset 11: 00 as status. The other bytes are unknown, one of the 3C could be the settemp (60°C)? Thermostat(0x10) -> Mixer(0x28), ?(0x33B), data: 01 02 00 is a setting, but we do not know what is set by the thermostat. You have to log the telegrams and change the values you want to have on the thermostat, if we know the new value and find it in a telegram `Thermostat(0x10) -> Mixer(0x28), ..., we can add the value and the setting.

[Shmul1]

Ok, I will do it today

[Shmul1]

I have changed different settings and made the lo log (2).txt

[Shmul1]

Please check if this is enough

[MichaelDvP]

I see changing values in the unknown telegram 0x313 on offsets 4, 5, 10 but as written before i need a reference what value has changed and to what value is has changed. First change was offset 10 to 0x41, maybe a temperature to 65°C, or a bitfield bits 0 and 7 set?

[Shmul1]

Maybe it's better to make a video and make a log at the same time?

[Shmul1]

log (3).txt

https://user-images.githubusercontent.com/51746237/150002075-d7fe4a78-8a1c-42b4-a639-54342391ad82.mp4

[MichaelDvP]

Ok, here are some more values. Some settings (like disinfect day, etc. are already in thermostat. Some values you have skipped, and values you have shown on video but not changed are not logged. But it's a good idea with the video. EMS-ESP-3_4_0a16-ESP32.zip Please check the values and settings, i think we will need some more iterations to have all working.

[Shmul1]

Good afternoon. Unfortunately, I had to leave on a business trip before Saturday and now I can only do everything remotely. I'm ready to make more videos on Saturday and Sunday. I installed the firmware, there is integration in HA, but I can test it in more detail only at night. Thank you for your work log.txt .

[proddy]

I'm confused that hc1 is not sorted to front and it contains only values from the hc1-monitor telegram. @proddy any idea why?

@MichaelDvP this was a bug. I was sorting the vector but always returning the last hc in the list. It still needs to be fixed. https://github.com/emsesp/EMS-ESP32/blob/8c4e5e5185e967a719fc0f8ccc48679fba5af976/src/devices/thermostat.cpp#L335.

[proddy]

Hi @Shmul1, if you don't mind I'd like to use some of your data as test data for EMS-ESP. I don't have any mixers, gateways or even a thermostat than can support more than one heating circuit! When you have time would you mind sending over some data which I can re-use? http://ems-esp.local/api/thermostat http://ems-esp.local/api/thermostat/info http://ems-esp.local/api/mixer http://ems-esp.local/api/mixer/info

thanks

[Shmul1]

Hello, sure, no problem. I'm the only one who can't make a video yet, I'm still on a business trip, otherwise I'll do what I can do remotely.

[Shmul1]

mixer.txt mixer_info.txt thermostat.txt thermostat_info.txt