Junkers Cerapur TOP 30-3 ZWB is recognised as Generic Boiler

[marcselis]

DESCRIPTION

My Junkers Cerapur TOP 30-3 ZWB is not recognized and is reported as a Generic Boiler.
The log says to report this on Github, so here I am ;-)

The relevant log line reads like this:

2025-10-10 10:51:32.759 WARNING 330: [emsesp] Unknown EMS boiler. Using generic profile. Please report on GitHub.

The log is also showing a lot of read errors. I don't know whether these are related, or whether these are due to the OpenTherm adapter that is also connected. See additional context below.

log.txt

REQUESTED INFORMATION

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

• Searched the issue in issues
• Searched the issue in discussions
  Added my info in improve EMS brand detection #2482
• Searched the issue in the docs
• Searched the issue in the chat
  Got invitation is expired
• Provide the System information in the area below, taken from http://<IP>/api/system

{"system":{"version":"3.7.2","uptime":"000+00:55:43.630","uptimeSec":3343,"platform":"ESP32S3","cpuType":"ESP32-S3","arduino":"ESP32 Arduino v2.0.17","sdk":"v4.4.7-dirty","freeMem":198,"maxAlloc":171,"freeCaps":8341,"usedApp":2148,"freeApp":2524,"partition":"app0","flash_chip_size":16384,"resetReason":"Software reset CPU / Software reset CPU","psram":true,"psramSize":8189,"freePsram":8144,"model":"","temperature":39.5},"network":{"network":"WiFi","hostname":"ems-gateway","RSSI":-66,"WIFIReconnects":0,"TxPowerSetting":0,"staticIP":false,"lowBandwidth":false,"disableSleep":true,"enableMDNS":true,"enableCORS":false,"APProvisionMode":"disconnected","APSecurity":"wpa2","APSSID":"ems-esp"},"ntp":{"NTPStatus":"connected","enabled":true,"server":"be.pool.ntp.org","tzLabel":"Europe/Brussels"},"mqtt":{"MQTTStatus":"connected","MQTTPublishes":462,"MQTTQueued":0,"MQTTPublishFails":0,"MQTTReconnects":0,"enabled":true,"clientID":"esp32-9ebd4d74","keepAlive":60,"cleanSession":false,"entityFormat":3,"base":"ems-esp","discoveryPrefix":"homeassistant","discoveryType":0,"nestedFormat":1,"haEnabled":true,"mqttQos":0,"mqttRetain":false,"publishTimeHeartbeat":60,"publishTimeBoiler":10,"publishTimeThermostat":10,"publishTimeSolar":10,"publishTimeMixer":10,"publishTimeWater":10,"publishTimeOther":60,"publishTimeSensor":10,"publishSingle":false,"publish2command":false,"sendResponse":false},"syslog":{"enabled":false},"sensor":{"temperatureSensors":0,"temperatureSensorReads":0,"temperatureSensorFails":0},"api":{"APICalls":0,"APIFails":0},"bus":{"busStatus":"connected","busProtocol":"HT3","busTelegramsReceived":23181,"busReads":55,"busWrites":0,"busIncompleteTelegrams":240,"busReadsFailed":278,"busWritesFailed":0,"busRxLineQuality":100,"busTxLineQuality":17},"settings":{"boardProfile":"S32S3","locale":"en","txMode":3,"emsBusID":11,"showerTimer":true,"showerMinDuration":180,"showerAlert":false,"hideLed":false,"noTokenApi":false,"readonlyMode":false,"fahrenheit":false,"dallasParasite":false,"boolFormat":1,"boolDashboard":1,"enumFormat":1,"analogEnabled":false,"telnetEnabled":true,"maxWebLogBuffer":100,"modbusEnabled":false,"forceHeatingOff":false,"developerMode":true},"devices":[{"type":"boiler","name":"Generic Boiler","deviceID":"0x08","productID":0,"brand":"","version":"00.00","entities":50,"handlersReceived":"0x18 0x19 0x34","handlersFetched":"0x14 0x16 0x33","handlersPending":"0xBF 0x10 0x11 0xC2 0x15 0x1C 0x1A 0x35 0x26 0x2A 0xD1 0xE3 0xE4 0xE5 0xE6 0xE9 0xEA 0x28 0x0494 0x0495 0x048D 0x048F 0x048A 0x04A2 0x0485 0x0486 0x0492 0x0488 0x0484 0x048B 0x0491 0x0499 0x049C 0x049D 0x04AE 0x04AF 0x02CC 0x04A5 0x04AA 0x04A7 0x02D6"},{"type":"controller","name":"HT3","deviceID":"0x09","productID":95,"brand":"","version":"18.04","entities":0},{"type":"connect","name":"OpenTherm Converter","deviceID":"0x18","productID":171,"brand":"","version":"01.02","entities":0,"handlersIgnored":"0x18 0x19 0x34 0x04 0x16"}]}

TO REPRODUCE

Start EMS-ESP an check the log for the detected devices

EXPECTED BEHAVIOUR

Boiler is identified correctly

SCREENSHOTS

2025-10-10 10:51:32.759 WARNING 330: [emsesp] Unknown EMS boiler. Using generic profile. Please report on GitHub.

ADDITIONAL CONTEXT

I also see a lot of warnings and errors in the logs about failed TX Read operations and incomplete Rx.

000+00:50:10.251 E 175: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 16 00 FF
000+00:50:11.884 E 176: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 33 00 FF
000+00:50:21.070 W 177: [telegram] Incomplete Rx: 98 88 18 01 02 14 3C
000+00:50:24.186 W 178: [telegram] Incomplete Rx: 8B 00 88 00 18 00 00 01 6C 00 00 00 02 00 C0 01 31 80 00 80 00 FF FF FF 00 00 00 00 00 00 00 24
000+00:50:33.968 W 179: [telegram] Incomplete Rx: 8B 00 88 13 05 22 00 80
000+00:50:37.076 W 180: [telegram] Incomplete Rx: 98 88 16 01 00 17
000+00:50:41.062 W 181: [telegram] Incomplete Rx: 98 88 04 00 00 68
000+00:50:43.055 W 182: [telegram] Incomplete Rx: 98 88 18 09 02 04 19
000+00:50:44.088 W 183: [telegram] Incomplete Rx: 90 88 13 05 22 00 80
000+00:50:51.556 W 184: [telegram] Incomplete Rx: 98 08 1A 00 00 00 F0 0E
000+00:51:04.048 W 185: [telegram] Incomplete Rx: 8B 00 88 13 05 22 00 80
000+00:51:08.838 E 186: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 14 00 FF
000+00:51:11.765 E 187: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 33 00 FF
000+00:51:53.778 W 188: [telegram] Incomplete Rx: 8B 00 88 13 05 22 00 80
000+00:52:08.875 E 189: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 14 00 FF
000+00:52:10.556 E 190: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 16 00 FF
000+00:52:12.207 E 191: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 33 00 FF
000+00:52:53.566 W 192: [telegram] Incomplete Rx: 8B 00 88 13 05 22 00 80
000+00:52:59.601 W 193: [telegram] Incomplete Rx: 98 88 18 0D 02 0C 17
000+00:53:03.593 W 194: [telegram] Incomplete Rx: 8B 00 88 13 05 22 00 80
000+00:53:09.022 E 195: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 14 00 FF
000+00:53:10.672 E 196: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 16 00 FF
000+00:53:12.306 E 197: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 33 00 FF
000+00:53:15.115 W 198: [telegram] Incomplete Rx: 98 88 04 00 00 3D
000+00:53:18.104 W 199: [telegram] Incomplete Rx: 98 88 18 14 02 3E 21
000+00:53:30.615 W 200: [telegram] Incomplete Rx: 98 88 16 01 00 4A
000+00:53:56.119 W 201: [telegram] Incomplete Rx: 98 08 1A 00 00 00 F0 48
000+00:53:57.116 W 202: [telegram] Incomplete Rx: 98 88 16 01 00 0D
000+00:54:09.042 E 203: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 14 00 FF
000+00:54:10.709 E 204: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 16 00 FF
000+00:54:12.374 E 205: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 33 00 FF

[MichaelDvP]

Tx quality is very low, please check the bus connections, cables, servicekey connectors plugged in fully, etc. Also try different tx-modes. If tx-quality is better, restart ems-esp to detect the boiler. If this is a unknown boiler you'll get a message "Unrecognized EMS device " with it's product-ID.

[marcselis]

I shortened the cable to the thermostat with more than a meter and that helped a lot, but still some Last Tx Read operation failed errors. After switching the tx-mode to EMS+ these are gone.
The boiler is now recognized as a Condens, Logamax/Logomatic, Cerapur Top, Greenstar, Generic HT3

The Incomplete Rx errors remain. Maybe these are related to the OpenTherm Converter?
I'd love to help to make that recognized as a thermostat, but I don't know how I can collect bigger logs. I now use the Export function from the System Log page and that has a limited capacity.

[proddy]

For more logging there are some ideas on https://docs.emsesp.org/Troubleshooting/#changing-a-value-on-an-ems-device-doesnt-work