Loosing devices - Buderus

[szymonzdziabek]

DESCRIPTION

EMS-ESP read my EMS bus when a heating system starts and then I see all devices. After few hours/days it looses devices and have only "Generic boiler" instead of Buderus GB152, MM10, WM10 and RC35.

The log:
2025-10-26 15:28:13.962 ERROR 488: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B A2 02 00 FF
2025-10-26 15:28:13.962 WARNING 489: [emsesp] Unrecognized EMS device (deviceID 0x22, no productID). Please report on GitHub.
2025-10-26 15:28:23.805 ERROR 490: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 90 02 00 FF
2025-10-26 15:28:23.805 WARNING 491: [emsesp] Unrecognized EMS device (deviceID 0x10, no productID). Please report on GitHub.
2025-10-26 15:28:33.867 ERROR 492: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 90 02 00 FF
2025-10-26 15:28:33.867 WARNING 493: [emsesp] Unrecognized EMS device (deviceID 0x10, no productID). Please report on GitHub.
2025-10-26 15:28:43.635 ERROR 494: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 90 02 00 FF
2025-10-26 15:28:43.635 WARNING 495: [emsesp] Unrecognized EMS device (deviceID 0x10, no productID). Please report on GitHub.
2025-10-26 15:28:53.652 ERROR 496: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 91 02 00 FF
2025-10-26 15:28:53.652 WARNING 497: [emsesp] Unrecognized EMS device (deviceID 0x11, no productID). Please report on GitHub.
2025-10-26 15:28:55.470 WARNING 498: [telegram] Tx queue overflow, skip one message
2025-10-26 15:29:00.729 WARNING 499: [telegram] Tx queue overflow, skip one message
2025-10-26 15:29:00.729 WARNING 500: [telegram] Tx queue overflow, skip one message
2025-10-26 15:29:00.729 WARNING 501: [telegram] Tx queue overflow, skip one message
2025-10-26 15:29:00.729 WARNING 502: [telegram] Tx queue overflow, skip one message
2025-10-26 15:29:04.588 ERROR 503: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 91 02 00 FF
2025-10-26 15:29:04.588 WARNING 504: [emsesp] Unrecognized EMS device (deviceID 0x11, no productID). Please report on GitHub.
2025-10-26 15:29:14.656 ERROR 505: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B A1 02 00 FF
2025-10-26 15:29:14.656 WARNING 506: [emsesp] Unrecognized EMS device (deviceID 0x21, no productID). Please report on GitHub.
2025-10-26 15:29:24.585 ERROR 507: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B A2 02 00 FF
2025-10-26 15:29:24.585 WARNING 508: [emsesp] Unrecognized EMS device (deviceID 0x22, no productID). Please report on GitHub.
2025-10-26 15:29:35.965 ERROR 509: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 90 02 00 FF
2025-10-26 15:29:35.965 WARNING 510: [emsesp] Unrecognized EMS device (deviceID 0x10, no productID). Please report on GitHub.
2025-10-26 15:29:46.304 ERROR 511: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 90 02 00 FF
2025-10-26 15:29:46.304 WARNING 512: [emsesp] Unrecognized EMS device (deviceID 0x10, no productID). Please report on GitHub.
2025-10-26 15:29:54.332 WARNING 513: [telegram] Tx queue overflow, skip one message
2025-10-26 15:29:55.972 WARNING 514: [telegram] Tx queue overflow, skip one message
2025-10-26 15:29:56.944 ERROR 515: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 90 02 00 FF
2025-10-26 15:29:56.944 WARNING 516: [emsesp] Unrecognized EMS device (deviceID 0x10, no productID). Please report on GitHub.
2025-10-26 15:30:00.515 WARNING 517: [telegram] Tx queue overflow, skip one message
2025-10-26 15:30:00.515 WARNING 518: [telegram] Tx queue overflow, skip one message
2025-10-26 15:30:00.515 WARNING 519: [telegram] Tx queue overflow, skip one message
2025-10-26 15:30:07.307 ERROR 520: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 91 02 00 FF
2025-10-26 15:30:07.307 WARNING 521: [emsesp] Unrecognized EMS device (deviceID 0x11, no productID). Please report on GitHub.
2025-10-26 15:30:19.863 ERROR 522: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B A1 02 00 FF
2025-10-26 15:30:19.863 WARNING 523: [emsesp] Unrecognized EMS device (deviceID 0x21, no productID). Please report on GitHub.
2025-10-26 15:30:29.012 WARNING 524: [telegram] Tx queue overflow, skip one message
2025-10-26 15:30:30.248 ERROR 525: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B 90 02 00 FF
2025-10-26 15:30:30.251 WARNING 526: [emsesp] Unrecognized EMS device (deviceID 0x10, no productID). Please report on GitHub.

REQUESTED INFORMATION

Similar issue:
#945

{"system":{"version":"3.7.2","uptime":"000+00:48:00.001","uptimeSec":2880,"platform":"ESP32","cpuType":"ESP32-D0WDQ6","arduino":"Tasmota Arduino v2.0.17","sdk":"4.4.8.240628","freeMem":144,"maxAlloc":91,"freeCaps":95,"usedApp":1650,"freeApp":334,"partition":"app1","flash_chip_size":4096,"resetReason":"Software reset CPU / Software reset CPU","psram":false,"model":""},"network":{"network":"WiFi","hostname":"ems-esp","RSSI":-84,"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":"192.168.1.1","tzLabel":"Europe/Warsaw"},"mqtt":{"MQTTStatus":"connected","MQTTPublishes":403,"MQTTQueued":0,"MQTTPublishFails":0,"MQTTReconnects":0,"enabled":true,"clientID":"esp32-a2286f24","keepAlive":60,"cleanSession":false,"entityFormat":0,"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,"analogSensors":0,"analogSensorReads":0,"analogSensorFails":0},"api":{"APICalls":0,"APIFails":0},"bus":{"busStatus":"connected, tx issues - try a different Tx Mode","busProtocol":"Buderus","busTelegramsReceived":2242,"busReads":0,"busWrites":0,"busIncompleteTelegrams":0,"busReadsFailed":423,"busWritesFailed":0,"busRxLineQuality":100,"busTxLineQuality":0},"settings":{"boardProfile":"S32","locale":"en","txMode":1,"emsBusID":11,"showerTimer":false,"showerMinDuration":180,"showerAlert":false,"hideLed":false,"noTokenApi":false,"readonlyMode":false,"fahrenheit":false,"dallasParasite":false,"boolFormat":1,"boolDashboard":1,"enumFormat":1,"analogEnabled":true,"telnetEnabled":true,"maxWebLogBuffer":25,"modbusEnabled":false,"forceHeatingOff":false,"developerMode":false},"devices":[{"type":"boiler","name":"Generic Boiler","deviceID":"0x08","productID":0,"brand":"","version":"00.00","entities":42,"handlersReceived":"0x10 0x11 0x1C 0x18 0x19 0x34","handlersFetched":"0x14","handlersPending":"0xBF 0xC2 0x15 0x1A 0x35 0x2A 0xD1 0xE3 0xE4 0xE5 0xE9 0x0494 0x0495 0x048F","handlersIgnored":"0x1E"},{"type":"controller","name":"Generic Controller","deviceID":"0x09","productID":0,"brand":"","version":"00.00","entities":0,"handlersIgnored":"0x29"}]}

TO REPRODUCE

It occurs without any user interaction.

EXPECTED BEHAVIOUR

To have all detected entities all the time.

SCREENSHOTS

After rebooting the boiler:

Devices on the bus:

ADDITIONAL CONTEXT

Add any other context about the issue here.

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

[MichaelDvP]

Please update to latest dev and check if you can position the ems-esp better to wifi AP, "RSSI":-84, is very bad signal, causing slow data transmisson and memory overflow in mqtt output queue.

[szymonzdziabek]

What I did - only changed EMS bus "polarity" and it seems it helped. It works for 5 days. I didn't even changed the ESP position to increase WiFi signal.