search

emsesp / EMS-ESP32

ESP32 firmware to read and control EMS and Heatronic compatible equipment such as boilers, thermostats, solar modules, and heat pumps
https://emsesp.github.io/docs
GNU Lesser General Public License v3.0
538 stars 96 forks source link

Unrecognized EMS device (device ID 0x10, no product ID). Please report on GitHub. #1531

Closed Lizzard44 closed 6 months ago

Lizzard44 commented 6 months ago

Unrecognized EMS device (device ID 0x10, no product ID). Please report on GitHub.

A clear and concise description of what the problem is.

000+00:55:28.640 E 28: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 90 02 00 1B

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

{ "System Info": { "version": "3.6.5-dev.7", "uptime": "000+00:57:48.855", "uptime (seconds)": 3468, "platform": "Tasmota Arduino v2.0.14", "sdk": "4.4.6", "free mem": 161, "max alloc": 107, "used app": 1597, "free app": 387, "partition": "app0", "reset reason": "Power on reset / APP CPU reset by PRO CPU" }, "Network Info": { "network": "WiFi", "hostname": "ems-esp", "RSSI": -45, "IPv4 address": "192.168.178.136/255.255.255.0", "IPv4 gateway": "192.168.178.2", "IPv4 nameserver": "253.0.0.0", "BSSID": "set", "static ip config": false, "enable IPv6": true, "low bandwidth": false, "disable sleep": false, "enable MDNS": true, "enable CORS": false, "AP provision mode": "disconnected", "AP security": "wpa2", "AP ssid": "ems-esp" }, "NTP Info": { "NTP status": "connected", "enabled": true, "server": "192.168.178.2", "tz label": "Europe/Berlin" }, "OTA Info": { "enabled": false, "port": 8266 }, "MQTT Info": { "MQTT status": "connected", "MQTT publishes": 545, "MQTT queued": 0, "MQTT publish fails": 0, "MQTT connects": 1, "enabled": true, "client id": "ems-esp", "keep alive": 60, "clean session": false, "entity format": 1, "base": "ems-esp", "discovery prefix": "homeassistant", "discovery type": 0, "nested format": 2, "ha enabled": true, "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": true }, "Syslog Info": { "enabled": true, "syslog started": true, "syslog level": "notice", "syslog ip": "192.168.178.3", "syslog queue": 0 }, "Sensor Info": { "analog sensors": 0, "analog sensor reads": 0, "analog sensor fails": 0 }, "API Info": { "API calls": 2, "API fails": 0 }, "Bus Info": { "bus status": "connected, tx issues - try a different Tx Mode", "bus protocol": "HT3", "bus telegrams received (rx)": 841, "bus reads (tx)": 0, "bus writes (tx)": 0, "bus incomplete telegrams": 12, "bus reads failed": 85, "bus writes failed": 0, "bus rx line quality": 100, "bus tx line quality": 0 }, "Settings": { "board profile": "CUSTOM", "locale": "de", "tx mode": 1, "ems bus id": 11, "shower timer": false, "shower alert": false, "phy type": 0, "rx gpio": 23, "tx gpio": 5, "dallas gpio": 0, "pbutton gpio": 0, "led gpio": 2, "hide led": false, "notoken api": false, "readonly mode": true, "fahrenheit": false, "dallas parasite": false, "bool format": 2, "bool dashboard": 2, "enum format": 1, "analog enabled": true, "telnet enabled": true, "max web log buffer": 50, "web log buffer": 50 }, "Devices": [ { "type": "boiler", "name": "Condens 2500/Logamax/Logomatic/Cerapur Top/Greenstar/Generic HT3", "device id": "0x08", "product id": 95, "version": "18.04", "entities": 67, "handlers received": "0x14 0x1C 0x18 0x19 0x34 0x2A 0x04", "handlers fetched": "0x16 0x33", "handlers pending": "0xBF 0x10 0x11 0xC2 0x15 0x1A 0x35", "handlers ignored": "0x03 0x05" }, { "type": "controller", "name": "Generic Controller", "device id": "0x09", "product id": 0, "version": "00.00", "entities": 0 } ] }


every 10 Sec.

_Steps to reproduce the behavior:_

start device
proddy commented 6 months ago

the version and product info from EMS devices are fetched by a read command. It looks like your Tx is not working - either faulty hardware or cables. I would check that first.

Lizzard44 commented 6 months ago

I swapped cables & GPIO ports and tested them. The error never changes. I think the newly purchased interface board https://bbqkees-electronics.nl/product/ems-interface-board-v3-1/ is broken. :( Data is being read. I can't say what else doesn't work. It's the first time I'm using the ESM-ESP.

proddy commented 6 months ago

if it's a standard BBQKees board try choosing the board profile that matches (in your config it shows as CUSTOM). Also as the message says try different EMS TxModes depending if you have Buderus or Worcester/Junkers

Lizzard44 commented 6 months ago

it is a board that is not listed "AZ-Delivery D1 R32" with an "ESP32 WROOM-32"

It is a Junkers Cerapur ZSBE 16-3 and an FR120 is also attached to the BUS.

I've now tried all the settings. The error remains and does not change.

2024-01-01 15:46:08.219 W 6149: [emsesp] Unrecognized EMS device (device ID 0x10, no product ID). Please report on GitHub. 2024-01-01 15:46:31.160 E 6150: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 07 00 1B 2024-01-01 15:46:51,754 W 6151: [telegram] Incomplete Rx: 88 00 18 00 3C 02 2B 50 30 09 33 65 C0 80 00 80 00 02 0D FF FF 18 00 00 00 00 00 02 1 8 2024-01-01 15:46:55.714 E 6152: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 88 14 00 1B

bbqkees commented 6 months ago

Can you show us a clear picture of how exactly you have connected the EMS interface board to your ESP32 board? Most mistakes are due to wiring the wrong pins.

image

According to your custom board profile info you gave above RX of the EMS interface board should go to GPIO23 and TX of the board should go to GPIO05.

You also need to connect GND and 3V3 of the ESP32 board to the EMS interface board.

Also the info is not showing the thermostat, check if it connected to the BB terminal or to the 3 wire older bus next to it. If so, you are rewire it the the BB terminal so it can be seen on the EMS bus.

Lizzard44 commented 6 months ago

Yes, I connected the EMS as described. RX to GPIO23 and TX to GPIO05. I also tried other GPIOs (e.g. GPIO19) for TX. But I'll check it again carefully (not what I mixed up). The EMS bus, like the FR100, is connected to BB (27).

image

Does it make sense to connect the FR100 to 1-2-4 (analog) an the EMS at BB (only)?

bbqkees commented 6 months ago

Can you check if you have read only mode on by mistake? image

Then TX is not active.

In your config it is set to true: "readonly mode": true

Lizzard44 commented 6 months ago

oh a smartass.....

there is an "EMS Reads (Tx)" and an "EMS Writes (Tx)". Only the “EMS Writes (Tx)” is switched off. "EMS Reads (Tx)" should still work.

Of course I also tried to activate "EMS Writes (Tx)". The error remains.

I now think that the thermal baths are not properly supported.

Regardless, I can read values and will ignore the error messages. I only reported here because it says so "[emsesp] Unrecognized EMS device (device ID 0x10, no product ID). Please report on GitHub."

proddy commented 6 months ago

"read" will just listen, but EMS-ESP can't poll for values, including details of the EMS devices. So basically EMS-ESP goes into dumb mode. The option was there for a fail-safe when testing for those panicking EMS-ESP would corrupt their EMS devices.

Lizzard44 commented 5 months ago

I downgrade to a ESP8266 version and now it works perfekt. I think the ""AZ-Delivery D1 R32" with an "ESP32 WROOM-32"" ist not kompatibel.