"dhw circulation pump mode" disappeared after v3.5.0b12 upgrade

[jrb80]

EMS-ESP Version: 3.5.0b12
Boiler detected by EMS: Worcester Greenstar Si/27i
Boiler installed: Worcester Greenstar Si/30
Bus protocol: HT3

---

Previously wWCircMode "warm water circulation pump frequency" or "dhw circulation pump mode" was published but since upgrading to the latest beta the topic is not published.

Previous output

{
  "~": "ems-esp",
  "uniq_id": "boiler_wwcircmode",
  "command_topic": "~/boiler/wwcircmode",
  "options": [
    "off",
    "1x3min",
    "2x3min",
    "3x3min",
    "4x3min",
    "5x3min",
    "6x3min",
    "continuous"
  ],
  "stat_t": "~/boiler_data_ww",
  "name": "dhw Circulation pump mode",
  "object_id": "boiler_dhw_circulation pump mode",
  "val_tpl": "{{value_json.wwcircmode}}",
  "dev": {
    "ids": [
      "ems-esp-boiler"
    ]
  }
}

Nothing reported in web portal, telnet or HA after.

[MichaelDvP]

EMS-ESP Version: 3.5.0b12

Why do you use a intermediate beta?

[jrb80]

No particular reason other than thinking the latest is the greatest, I down graded toEMS-ESP Version: 3.4.4 and the topic is now published again, must be a problem with the beta.

[MichaelDvP]

Sure, the latest is the greatest (maybe with some new issues) but the latest is 3.5.0dev-15. I can not remember if there was a issue in b12 and if this is fixed in dev-15. In my system (dev-15 with some extras) i see circ pump mode,

[proddy]

I can see it in show values from the Console, but then I'm using the latest dev branch

[jrb80]

Ok, thanks for the quick response. I'll close the issue as it can always be reopened if it appears on v3.5 stable (to be released).

[proddy]

let us do some more testing, it may be a bug. I keep creating more bugs everytime I touch something these days it seems

[MichaelDvP]

I think this is related to #727. I have removed the the 0-off option, because the tested boilers only support options 1-7 (also norberts1 and other docus says 1-7). If this boiler supports, and is set to, 0-Off the setting will be interpreted as -1 and the setting is removed. @jrb80 What is your setting?

[jrb80]

Yes that could be it. The current value is 0-Off and therefore must be an invalid value in the new v3.5 scheme. I have tried changing the mode (1x3min/2x3min) using the web UI and telnet call boiler wwcircmode 2 but it continues to fail, here is an extract from the log. This is probably a more general issue with sending telegrams to my Worcester Greenstar Si/30 boiler rather than specifically the wWCircMode mode.

My boiler is wrongly identified as Worcester Greenstar Si/27i rather than Si/30 but not sure whether that makes a difference as I can read all the values.

2023-01-11 12:06:08.991 D 2735: [mqtt] Publishing topic ems-esp/heartbeat (#1260, retain=1, retry=1, size=291, pid=1)
2023-01-11 12:06:13.031 D 2736: [mqtt] Publishing topic ems-esp/boiler_data_ww (#1261, retain=1, retry=1, size=499, pid=1)
2023-01-11 12:06:13.132 D 2737: [mqtt] Publishing topic ems-esp/boiler_data (#1262, retain=1, retry=1, size=679, pid=1)
2023-01-11 12:06:22.020 D 2738: [mqtt] Publishing topic ems-esp/heating_active (#1263, retain=1, retry=1, size=3, pid=1)
2023-01-11 12:06:23.030 D 2739: [mqtt] Publishing topic ems-esp/boiler_data_ww (#1264, retain=1, retry=1, size=499, pid=1)
2023-01-11 12:06:23.131 D 2740: [mqtt] Publishing topic ems-esp/boiler_data (#1265, retain=1, retry=1, size=679, pid=1)
2023-01-11 12:06:29.033 D 2741: [command] Calling command 'boiler/wwcircmode' (circulation pump mode) with value 1x3min
2023-01-11 12:06:29.035 D 2742: [emsesp] Write command successful
2023-01-11 12:06:29.092 D 2743: [telegram] Sending write Tx [#168], telegram: 8B 08 33 07 01
2023-01-11 12:06:29.108 D 2744: [emsesp] No telegram type handler found for ID 0x33 (src 0x0B)
2023-01-11 12:06:29.117 D 2745: [emsesp] Last Tx write successful
2023-01-11 12:06:29.117 D 2746: [telegram] Sending post validate read, type ID 0x33 to dest 0x08
2023-01-11 12:06:29.467 D 2747: [telegram] Sending read Tx [#169], telegram: 8B 88 33 00 1B
2023-01-11 12:06:29.510 D 2748: [emsesp] Last Tx read successful
2023-01-11 12:06:29.596 D 2749: [mqtt] Publishing topic ems-esp/boiler_data_ww (#1266, retain=1, retry=1, size=499, pid=1)
2023-01-11 12:06:29.697 D 2750: [mqtt] Publishing topic ems-esp/boiler_data (#1267, retain=1, retry=1, size=679, pid=1)
2023-01-11 12:06:33.030 D 2751: [mqtt] Publishing topic ems-esp/boiler_data_ww (#1268, retain=1, retry=1, size=499, pid=1)
2023-01-11 12:06:33.131 D 2752: [mqtt] Publishing topic ems-esp/boiler_data (#1269, retain=1, retry=1, size=679, pid=1)
2023-01-11 12:06:37.439 D 2753: [command] Calling command 'boiler/wwcircmode' (circulation pump mode) with value 2x3min
2023-01-11 12:06:37.440 D 2754: [emsesp] Write command successful
2023-01-11 12:06:37.492 D 2755: [telegram] Sending write Tx [#170], telegram: 8B 08 33 07 02
2023-01-11 12:06:37.508 D 2756: [emsesp] No telegram type handler found for ID 0x33 (src 0x0B)
2023-01-11 12:06:37.517 D 2757: [emsesp] Last Tx write successful
2023-01-11 12:06:37.517 D 2758: [telegram] Sending post validate read, type ID 0x33 to dest 0x08
2023-01-11 12:06:37.892 D 2759: [telegram] Sending read Tx [#171], telegram: 8B 88 33 00 1B
2023-01-11 12:06:37.935 D 2760: [emsesp] Last Tx read successful
2023-01-11 12:06:37.983 D 2761: [mqtt] Publishing topic ems-esp/boiler_data_ww (#1270, retain=1, retry=1, size=499, pid=1)
2023-01-11 12:06:38.084 D 2762: [mqtt] Publishing topic ems-esp/boiler_data (#1271, retain=1, retry=1, size=679, pid=1)
2023-01-11 12:06:43.033 D 2763: [mqtt] Publishing topic ems-esp/boiler_data_ww (#1272, retain=1, retry=1, size=499, pid=1)
2023-01-11 12:06:43.134 D 2764: [mqtt] Publishing topic ems-esp/boiler_data (#1273, retain=1, retry=1, size=679, pid=1)
2023-01-11 12:06:53.037 D 2765: [mqtt] Publishing topic ems-esp/boiler_data_ww (#1274, retain=1, retry=1, size=499, pid=1)
2023-01-11 12:06:53.138 D 2766: [mqtt] Publishing topic ems-esp/boiler_data (#1275, retain=1, retry=1, size=680, pid=1)

Here are my deep scan results

ems-esp:# scan devices deep
Performing a deep scan...
000+01:32:28.419 E 1: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B B8 02 00 1B
000+01:32:28.419 W 2: [emsesp] Unrecognized EMS device (device ID 0x38, no product ID). Please report on GitHub.
000+01:32:30.594 E 3: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B B0 02 00 1B
000+01:32:30.594 W 4: [emsesp] Unrecognized EMS device (device ID 0x30, no product ID). Please report on GitHub.
000+01:32:32.570 E 5: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 82 02 00 1B
000+01:32:32.570 W 6: [emsesp] Unrecognized EMS device (device ID 0x02, no product ID). Please report on GitHub.
000+01:32:34.095 E 7: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B C8 02 00 1B
000+01:32:34.095 W 8: [emsesp] Unrecognized EMS device (device ID 0x48, no product ID). Please report on GitHub.
000+01:32:35.719 E 9: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B A0 02 00 1B
000+01:32:35.719 W 10: [emsesp] Unrecognized EMS device (device ID 0x20, no product ID). Please report on GitHub.
000+01:32:37.320 E 11: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B A1 02 00 1B
000+01:32:37.320 W 12: [emsesp] Unrecognized EMS device (device ID 0x21, no product ID). Please report on GitHub.
000+01:32:39.494 E 13: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B A2 02 00 1B
000+01:32:39.496 W 14: [emsesp] Unrecognized EMS device (device ID 0x22, no product ID). Please report on GitHub.
000+01:32:41.045 E 15: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B A3 02 00 1B
000+01:32:41.045 W 16: [emsesp] Unrecognized EMS device (device ID 0x23, no product ID). Please report on GitHub.
000+01:32:42.670 E 17: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B A8 02 00 1B
000+01:32:42.671 W 18: [emsesp] Unrecognized EMS device (device ID 0x28, no product ID). Please report on GitHub.
000+01:32:44.245 E 19: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B A9 02 00 1B
000+01:32:44.245 W 20: [emsesp] Unrecognized EMS device (device ID 0x29, no product ID). Please report on GitHub.
000+01:32:45.770 E 21: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 90 02 00 1B
000+01:32:45.770 W 22: [emsesp] Unrecognized EMS device (device ID 0x10, no product ID). Please report on GitHub.
000+01:32:47.395 E 23: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 97 02 00 1B
000+01:32:47.395 I 24: [emsesp] Recognized new thermostat with deviceID 0x17
000+01:32:49.570 E 25: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 98 02 00 1B
000+01:32:49.570 W 26: [emsesp] Unrecognized EMS device (device ID 0x18, no product ID). Please report on GitHub.
000+01:32:51.170 E 27: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 99 02 00 1B
000+01:32:51.170 W 28: [emsesp] Unrecognized EMS device (device ID 0x19, no product ID). Please report on GitHub.
000+01:32:52.720 E 29: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 9A 02 00 1B
000+01:32:52.720 W 30: [emsesp] Unrecognized EMS device (device ID 0x1A, no product ID). Please report on GitHub.
000+01:32:54.345 E 31: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 9B 02 00 1B
000+01:32:54.345 W 32: [emsesp] Unrecognized EMS device (device ID 0x1B, no product ID). Please report on GitHub.
000+01:32:55.920 E 33: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 91 02 00 1B
000+01:32:55.920 W 34: [emsesp] Unrecognized EMS device (device ID 0x11, no product ID). Please report on GitHub.
000+01:32:57.445 E 35: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 97 B1 00 1B
000+01:33:00.063 E 36: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 97 B0 00 1B
000+01:33:01.820 E 37: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 97 06 00 1B
000+01:33:03.420 E 38: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 97 12 00 1B
000+01:33:04.971 E 39: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 97 A2 00 1B

[MichaelDvP]

Please attach the support info from help page. My crystal ball fails to show your system.
The write works, the boiler acknollages it, but seems not to change the off state. Can you change it on the thermostat?
Is the circulation pump configured?
The Si/27i is just a name for product id 123, the boiler electronic is identical when it have the same product-id.
Seems that boilers with active circulation mode can not set to off, and boilers with mode off, can not set to active.
Difficult to handle. I'll add back the off position, but we have to keep in mind that switching on->off and off-> on does not work, only changing the states 1-7 work.

[jrb80]

@MichaelDvP apologies, support file attached 20230111_info.json.txt

I am not using a Bosch smart thermostat (Sense II or similar), I am using Evohome. Previously it was set to 2x3min and now it is stuck in off mode. The strange situation is that the boiler circulation pump is running despite it reporting off.

[MichaelDvP]

I am using Evohome.

I don't know what this is. Seem not to be a ems device. Please try updating to https://github.com/MichaelDvP/EMS-ESP32/releases and post all values from terminal shòw command and make a full log (loglevel all). Maybe this helps to understand what this strange thermostat do.

[proddy]

wwcircmode in dev-16