Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unrecognized devices on EMS-bus #882

Closed
cgeboers opened this issue Jan 2, 2023 · 9 comments
Closed

Unrecognized devices on EMS-bus #882

cgeboers opened this issue Jan 2, 2023 · 9 comments
Labels
question Question about something

Comments

@cgeboers
Copy link

cgeboers commented Jan 2, 2023 •
edited
Loading

After upgrading to 3.4.4 I see these errors in the EMS-ESP32 logs:

2023-01-02 10:26:00.736 W 44: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.
2023-01-02 10:26:58.337 E 45: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E8 02 00 1B
2023-01-02 10:26:58.337 W 46: [emsesp] Unrecognized EMS device (device ID 0x68, no product ID). Please report on GitHub.
2023-01-02 10:27:02.503 E 47: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E9 02 00 1B
2023-01-02 10:27:02.503 W 48: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.
2023-01-02 10:27:58.712 E 49: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E8 02 00 1B
2023-01-02 10:27:58.712 W 50: [emsesp] Unrecognized EMS device (device ID 0x68, no product ID). Please report on GitHub.
2023-01-02 10:28:01.144 E 51: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E9 02 00 1B
2023-01-02 10:28:01.144 W 52: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.
2023-01-02 10:28:15.476 W 53: [telegram] Incomplete Rx: 08 00 18 01 30 80 00 64 0F 09 01 A5 40 80 00 02 33 80 00 FF FF FF 2D 48 00 C8 00 02 00
2023-01-02 10:28:58.310 E 54: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E8 02 00 1B
2023-01-02 10:28:58.310 W 55: [emsesp] Unrecognized EMS device (device ID 0x68, no product ID). Please report on GitHub.
2023-01-02 10:29:00.745 E 56: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E9 02 00 1B
2023-01-02 10:29:00.745 W 57: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.
2023-01-02 10:29:58.621 E 58: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E8 02 00 1B
2023-01-02 10:29:58.621 W 59: [emsesp] Unrecognized EMS device (device ID 0x68, no product ID). Please report on GitHub.
2023-01-02 10:30:01.278 E 60: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E9 02 00 1B
2023-01-02 10:30:01.278 W 61: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.
2023-01-02 10:30:59.578 E 62: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E8 02 00 1B
2023-01-02 10:30:59.578 W 63: [emsesp] Unrecognized EMS device (device ID 0x68, no product ID). Please report on GitHub.
2023-01-02 10:31:04.065 E 64: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E9 02 00 1B
2023-01-02 10:31:04.065 W 65: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.
2023-01-02 10:31:59.349 E 66: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E8 02 00 1B
2023-01-02 10:31:59.349 W 67: [emsesp] Unrecognized EMS device (device ID 0x68, no product ID). Please report on GitHub.
2023-01-02 10:32:01.659 E 68: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E9 02 00 1B
2023-01-02 10:32:01.659 W 69: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.

I do know a little bit about ESP32, but I don't know anything about the EMS bus. This particuar system has two boilers, which are connected to each other via a device which in Home Assistant is visible as a "Switch", but it doesn't display a Product ID.

Any suggestions to what I can add for information, like system logs or anything?

When looking at debug messages I see this:

2023-01-02 10:39:03.077 WARNING 97: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.
2023-01-02 10:39:37.778 DEBUG 98: [emsesp] No telegram type handler found for ID 0x18 (src 0x08)
2023-01-02 10:39:38.075 DEBUG 99: [emsesp] No telegram type handler found for ID 0x08 (src 0x08)
2023-01-02 10:39:38.316 DEBUG 100: [emsesp] No telegram type handler found for ID 0x16 (src 0x08)
2023-01-02 10:39:39.049 DEBUG 101: [emsesp] No telegram type handler found for ID 0x1A (src 0x10)
2023-01-02 10:39:39.165 DEBUG 102: [emsesp] No telegram type handler found for ID 0x9D (src 0x10)
2023-01-02 10:39:39.261 WARNING 103: [telegram] Incomplete Rx: C1 00 08 00 33 00 0B FF 3C FB FF 28 FF 01 46 00 FF 00
2023-01-02 10:39:39.616 TRACE 104: [emsesp] Unknown(0x08) -> All(0x00), ?(0x15), data: 00 3C 01 01 09 00 00 00
2023-01-02 10:39:39.616 DEBUG 105: [emsesp] No telegram type handler found for ID 0x15 (src 0x08)
2023-01-02 10:39:44.033 TRACE 106: [emsesp] Switch(0x11) -> All(0x00), WM10MonitorMessage(0x9C), data: 01 9C 64 01 00
2023-01-02 10:39:44.324 TRACE 107: [emsesp] Switch(0x11) -> Unknown(0x08), WM10TempMessage(0x1E), data: 01 9C
2023-01-02 10:39:45.813 TRACE 108: [emsesp] Thermostat(0x10) -> All(0x00), RCTime(0x06), data: 17 01 0A 02 27 2D 00 02
2023-01-02 10:39:46.065 TRACE 109: [emsesp] Unknown(0x08) -> All(0x00), ?(0x16), data: FF 5A 64 00 06 FA 0A 01 05 64 00 02
2023-01-02 10:39:46.065 DEBUG 110: [emsesp] No telegram type handler found for ID 0x16 (src 0x08)
2023-01-02 10:39:46.341 TRACE 111: [emsesp] Unknown(0x08) -> All(0x00), ?(0x33), data: 0B FF 3C FB FF 28 FF 01 46 00 FF 00
2023-01-02 10:39:46.341 DEBUG 112: [emsesp] No telegram type handler found for ID 0x33 (src 0x08)
2023-01-02 10:39:46.563 TRACE 113: [emsesp] Unknown(0x08) -> All(0x00), ?(0x15), data: 00 3C 01 01 09 00 00 00
2023-01-02 10:39:46.563 DEBUG 114: [emsesp] No telegram type handler found for ID 0x15 (src 0x08)
2023-01-02 10:39:47.808 TRACE 115: [emsesp] Unknown(0x08) -> All(0x00), ?(0x18), data: 30 80 00 64 0F 09 01 A5 40 80 00 02 32 80 00 FF FF FF 2D 48 00 C8 00 02 00
2023-01-02 10:39:47.808 DEBUG 116: [emsesp] No telegram type handler found for ID 0x18 (src 0x08)
2023-01-02 10:39:48.029 TRACE 117: [emsesp] Unknown(0x08) -> All(0x00), ?(0x08), data: 30 48 00 CB 00 2D 48 00 C8 09 35 48 01 36 40 35 48 01 36 40
2023-01-02 10:39:48.029 DEBUG 118: [emsesp] No telegram type handler found for ID 0x08 (src 0x08)
2023-01-02 10:39:51.123 WARNING 119: [telegram] Incomplete Rx: 90 00 10 00
2023-01-02 10:39:52.577 TRACE 120: [emsesp] Thermostat(0x10) -> All(0x00), RCOutdoorTemp(0xA3), data: 0C 11 11 00 C4 00 CA 00 CA 7D 00 7D 00
2023-01-02 10:39:53.523 WARNING 121: [telegram] Incomplete Rx: 10 00 91 00 11 00
2023-01-02 10:39:55.151 WARNING 122: [telegram] Incomplete Rx: 08 1E 00 01 9C
2023-01-02 10:39:57.867 TRACE 123: [emsesp] Unknown(0x08) -> All(0x00), ?(0x18), data: 30 80 00 64 0F 09 01 A5 40 80 00 02 32 80 00 FF FF FF 2D 48 00 C8 00 02 00
2023-01-02 10:39:57.867 DEBUG 124: [emsesp] No telegram type handler found for ID 0x18 (src 0x08)
2023-01-02 10:39:58.094 TRACE 125: [emsesp] Unknown(0x08) -> All(0x00), ?(0x19), data: 00 76 00 00 00 00 00 00 00 64 01 32 CD 00 09 F5 00 00 00 FF AD D6 00 8C 5C 01 9C
2023-01-02 10:39:58.094 DEBUG 126: [emsesp] No telegram type handler found for ID 0x19 (src 0x08)
2023-01-02 10:39:58.325 TRACE 127: [emsesp] Unknown(0x08) -> All(0x00), UBADevices(0x07), data: 0B 03 00 00 00 00 00 00 00 00 00 00 03 03 00
2023-01-02 10:39:58.325 DEBUG 128: [emsesp] New EMS device detected with ID 0x68. Requesting version information.
2023-01-02 10:39:58.325 DEBUG 129: [telegram] Tx read request to device 0x68 for type ID 0x02
2023-01-02 10:39:58.325 DEBUG 130: [emsesp] New EMS device detected with ID 0x69. Requesting version information.
2023-01-02 10:39:58.325 DEBUG 131: [telegram] Tx read request to device 0x69 for type ID 0x02
2023-01-02 10:39:58.529 DEBUG 132: [telegram] Sending read Tx [#115], telegram: 0B E8 02 00 1B
2023-01-02 10:39:58.529 TRACE 133: [emsesp] Me(0x0B) <- 68(0x68), Version(0x02), length: 0x1B
2023-01-02 10:39:58.822 TRACE 134: [emsesp] Unknown(0x08) -> All(0x00), ?(0x08), data: 30 48 00 CB 00 2D 48 00 C8 09 35 48 01 36 40 35 48 01 36 40
2023-01-02 10:39:58.822 DEBUG 135: [emsesp] No telegram type handler found for ID 0x08 (src 0x08)
2023-01-02 10:39:59.664 DEBUG 136: [telegram] Sending read Tx [#117], telegram: 0B E8 02 00 1B
2023-01-02 10:39:59.664 TRACE 137: [emsesp] Me(0x0B) <- 68(0x68), Version(0x02), length: 0x1B
2023-01-02 10:40:00.209 DEBUG 138: [telegram] Sending read Tx [#118], telegram: 0B E8 02 00 1B
2023-01-02 10:40:00.223 TRACE 139: [emsesp] Me(0x0B) <- 68(0x68), Version(0x02), length: 0x1B
2023-01-02 10:40:00.818 DEBUG 140: [telegram] Sending read Tx [#119], telegram: 0B E8 02 00 1B
2023-01-02 10:40:00.818 TRACE 141: [emsesp] Me(0x0B) <- 68(0x68), Version(0x02), length: 0x1B
2023-01-02 10:40:01.052 ERROR 142: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E8 02 00 1B
2023-01-02 10:40:01.052 TRACE 143: [emsesp] 68(0x68) -> Me(0x0B), Version(0x02), data:
2023-01-02 10:40:01.052 WARNING 144: [emsesp] Unrecognized EMS device (device ID 0x68, no product ID). Please report on GitHub.
2023-01-02 10:40:01.748 DEBUG 145: [telegram] Sending read Tx [#116], telegram: 0B E9 02 00 1B
2023-01-02 10:40:01.748 TRACE 146: [emsesp] Me(0x0B) <- 69(0x69), Version(0x02), length: 0x1B
2023-01-02 10:40:02.661 DEBUG 147: [telegram] Sending read Tx [#120], telegram: 0B E9 02 00 1B
2023-01-02 10:40:02.661 TRACE 148: [emsesp] Me(0x0B) <- 69(0x69), Version(0x02), length: 0x1B
2023-01-02 10:40:03.253 DEBUG 149: [telegram] Sending read Tx [#121], telegram: 0B E9 02 00 1B
2023-01-02 10:40:03.273 TRACE 150: [emsesp] Me(0x0B) <- 69(0x69), Version(0x02), length: 0x1B
2023-01-02 10:40:03.713 WARNING 151: [telegram] Incomplete Rx: 10 08 35 00 11 11 30 00
2023-01-02 10:40:03.901 WARNING 152: [telegram] Incomplete Rx: 08 1E 00 01 9C
2023-01-02 10:40:04.260 DEBUG 153: [telegram] Sending read Tx [#122], telegram: 0B E9 02 00 1B
2023-01-02 10:40:04.260 TRACE 154: [emsesp] Me(0x0B) <- 69(0x69), Version(0x02), length: 0x1B
2023-01-02 10:40:04.508 ERROR 155: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 0B E9 02 00 1B
2023-01-02 10:40:04.508 TRACE 156: [emsesp] 69(0x69) -> Me(0x0B), Version(0x02), data:
2023-01-02 10:40:04.508 WARNING 157: [emsesp] Unrecognized EMS device (device ID 0x69, no product ID). Please report on GitHub.
2023-01-02 10:40:05.063 DEBUG 158: [emsesp] Fetching values for deviceID 0x70
2023-01-02 10:40:05.067 DEBUG 159: [emsesp] Fetching values for deviceID 0x71
2023-01-02 10:40:05.067 WARNING 160: [telegram] Incomplete Rx: 10 00 91 00
2023-01-02 10:40:05.125 DEBUG 161: [mqtt] Publishing topic ems-esp/thermostat_data (#232, retain=0, retry=1, size=1191, pid=1)
2023-01-02 10:40:05.125 DEBUG 162: [emsesp] Fetching values for deviceID 0x10
2023-01-02 10:40:05.125 DEBUG 163: [telegram] Tx read request to device 0x10 for type ID 0x3E
2023-01-02 10:40:05.125 DEBUG 164: [telegram] Tx read request to device 0x10 for type ID 0x3D
2023-01-02 10:40:05.125 DEBUG 165: [telegram] Tx read request to device 0x10 for type ID 0x3F
2023-01-02 10:40:05.125 DEBUG 166: [telegram] Tx read request to device 0x10 for type ID 0xA5
2023-01-02 10:40:05.125 DEBUG 167: [telegram] Tx read request to device 0x10 for type ID 0x37
2023-01-02 10:40:05.611 DEBUG 168: [mqtt] Publishing topic ems-esp/switch_data (#233, retain=0, retry=1, size=32, pid=1)
2023-01-02 10:40:05.690 DEBUG 169: [telegram] Sending read Tx [#123], telegram: 0B 90 3E 00 1B
2023-01-02 10:40:05.731 TRACE 170: [emsesp] Me(0x0B) <- Thermostat(0x10), RC35Monitor(0x3E), length: 0x1B
2023-01-02 10:40:05.758 DEBUG 171: [emsesp] Last Tx read successful
2023-01-02 10:40:05.758 TRACE 172: [emsesp] Thermostat(0x10) -> Me(0x0B), RC35Monitor(0x3E), data: 04 02 28 00 C4 00 00 00 00 00 00 00 64 11 30 00
2023-01-02 10:40:05.883 WARNING 173: [telegram] Incomplete Rx: 90 00 10 00 91 00
2023-01-02 10:40:06.141 TRACE 174: [telegram] Incomplete Rx: 8B 00 90 00
2023-01-02 10:40:06.526 DEBUG 175: [telegram] Sending read Tx [#124], telegram: 0B 90 3D 00 1B
2023-01-02 10:40:06.559 TRACE 176: [emsesp] Me(0x0B) <- Thermostat(0x10), RC35Set(0x3D), length: 0x1B
2023-01-02 10:40:06.711 DEBUG 177: [emsesp] Last Tx read successful
2023-01-02 10:40:06.769 TRACE 178: [emsesp] Thermostat(0x10) -> Me(0x0B), RC35Set(0x3D), data: 01 22 28 22 07 28 00 02 00 05 05 2D 01 01 04 4B 05 55 01 00 3C FF 14 05 05 02 02
2023-01-02 10:40:07.369 DEBUG 179: [telegram] Sending read Tx [#128], telegram: 0B 90 3D 1B 20
2023-01-02 10:40:07.369 TRACE 180: [emsesp] Me(0x0B) <- Thermostat(0x10), RC35Set(0x3D), length: 0x20 (offset 27)
2023-01-02 10:40:07.447 DEBUG 181: [emsesp] Last Tx read successful
2023-01-02 10:40:07.447 TRACE 182: [emsesp] Thermostat(0x10) -> Me(0x0B), RC35Set(0x3D), data: 00 00 28 19 0A 01 00 FF 32 2D 00 E1 05 05 02 (offset 27)
2023-01-02 10:40:07.660 DEBUG 183: [telegram] Sending read Tx [#125], telegram: 0B 90 3F 00 1B
2023-01-02 10:40:07.660 DEBUG 184: [mqtt] Publishing topic ems-esp/heartbeat (#234, retain=0, retry=1, size=289, pid=1)
2023-01-02 10:40:07.885 TRACE 185: [emsesp] Me(0x0B) <- Thermostat(0x10), RC35Timer(0x3F), length: 0x1B
2023-01-02 10:40:07.975 DEBUG 186: [emsesp] Last Tx read successful
2023-01-02 10:40:07.975 TRACE 187: [emsesp] Thermostat(0x10) -> Me(0x0B), RC35Timer(0x3F), data: 01 22 00 87 21 22 20 86 41 22 40 83 61 22 60 83 81 24 80 87 A1 27 A0 87 C1 27 C0
2023-01-02 10:40:08.227 TRACE 188: [emsesp] Unknown(0x08) -> All(0x00), ?(0x18), data: 30 80 00 64 0F 09 01 A5 40 80 00 02 32 80 00 FF FF FF 2D 48 00 C8 00 02 00
2023-01-02 10:40:08.227 DEBUG 189: [emsesp] No telegram type handler found for ID 0x18 (src 0x08)
2023-01-02 10:40:08.451 TRACE 190: [emsesp] Unknown(0x08) -> All(0x00), ?(0x08), data: 30 48 00 CB 00 2D 48 00 C8 09 35 48 01 36 40 35 48 01 36 40
2023-01-02 10:40:08.451 DEBUG 191: [emsesp] No telegram type handler found for ID 0x08 (src 0x08)
2023-01-02 10:40:08.772 DEBUG 192: [telegram] Sending read Tx [#129], telegram: 0B 90 3F 1B 20
2023-01-02 10:40:08.782 TRACE 193: [emsesp] Me(0x0B) <- Thermostat(0x10), RC35Timer(0x3F), length: 0x20 (offset 27)
2023-01-02 10:40:08.988 DEBUG 194: [emsesp] Last Tx read successful
2023-01-02 10:40:08.988 TRACE 195: [emsesp] Thermostat(0x10) -> Me(0x0B), RC35Timer(0x3F), data: 84 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 (offset 27)
2023-01-02 10:40:09.575 DEBUG 196: [telegram] Sending read Tx [#130], telegram: 0B 90 3F 36 20
2023-01-02 10:40:09.575 TRACE 197: [emsesp] Me(0x0B) <- Thermostat(0x10), RC35Timer(0x3F), length: 0x20 (offset 54)
2023-01-02 10:40:09.737 DEBUG 198: [emsesp] Last Tx read successful
2023-01-02 10:40:09.737 TRACE 199: [emsesp] Thermostat(0x10) -> Me(0x0B), RC35Timer(0x3F), data: E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 90 E7 (offset 54)
2023-01-02 10:40:10.361 DEBUG 200: [telegram] Sending read Tx [#131], telegram: 0B 90 3F 51 20
2023-01-02 10:40:10.361 TRACE 201: [emsesp] Me(0x0B) <- Thermostat(0x10), RC35Timer(0x3F), length: 0x20 (offset 81)
2023-01-02 10:40:10.426 DEBUG 202: [emsesp] Last Tx read successful
2023-01-02 10:40:10.471 TRACE 203: [emsesp] Thermostat(0x10) -> Me(0x0B), RC35Timer(0x3F), data: 90 E7 90 00 00 00 01 01 00 01 01 00 01 01 00 01 01 00 (offset 81)
2023-01-02 10:40:10.757 DEBUG 204: [telegram] Sending read Tx [#126], telegram: 0B 90 A5 00 1B
2023-01-02 10:40:10.757 TRACE 205: [emsesp] Me(0x0B) <- Thermostat(0x10), IBASettings(0xA5), length: 0x1B
2023-01-02 10:40:10.967 DEBUG 206: [emsesp] Last Tx read successful
2023-01-02 10:40:11.031 TRACE 207: [emsesp] Thermostat(0x10) -> Me(0x0B), IBASettings(0xA5), data: 00 00 00 00 FF F6 01 06 00 01 00 01 00 FF FF 00 00 05 21 05 28 FF 03 01 00 00 00
2023-01-02 10:40:11.615 DEBUG 208: [telegram] Sending read Tx [#132], telegram: 0B 90 A5 1B 20
2023-01-02 10:40:11.637 TRACE 209: [emsesp] Me(0x0B) <- Thermostat(0x10), IBASettings(0xA5), length: 0x20 (offset 27)
2023-01-02 10:40:11.637 DEBUG 210: [emsesp] Last Tx read successful
2023-01-02 10:40:11.679 TRACE 211: [emsesp] Thermostat(0x10) -> Me(0x0B), IBASettings(0xA5), data: 00 (offset 27)
2023-01-02 10:40:11.988 DEBUG 212: [telegram] Sending read Tx [#127], telegram: 0B 90 37 00 1B
2023-01-02 10:40:11.988 TRACE 213: [emsesp] Me(0x0B) <- Thermostat(0x10), WWSettings(0x37), length: 0x1B
2023-01-02 10:40:11.988 DEBUG 214: [emsesp] Fetching values for deviceID 0x11
2023-01-02 10:40:12.051 DEBUG 215: [emsesp] Last Tx read successful
2023-01-02 10:40:12.051 DEBUG 216: [emsesp] Fetching values for deviceID 0x08
2023-01-02 10:40:12.078 TRACE 217: [emsesp] Thermostat(0x10) -> Me(0x0B), WWSettings(0x37), data: FF FF 02 02 00 01 01 00 50 FF
2023-01-02 10:40:12.078 DEBUG 218: [emsesp] Fetching values for deviceID 0x09
2023-01-02 10:40:12.106 WARNING 219: [telegram] Incomplete Rx: 10 00 91 00
2023-01-02 10:40:12.507 WARNING 220: [telegram] Incomplete Rx: 91 00 11 00
2023-01-02 10:40:12.585 TRACE 221: [emsesp] Unknown(0x08) -> All(0x00), ?(0x16), data: FF 5A 64 00 06 FA 0A 01 05 64 00 02
2023-01-02 10:40:12.585 DEBUG 222: [emsesp] No telegram type handler found for ID 0x16 (src 0x08)
2023-01-02 10:40:13.186 TRACE 223: [emsesp] Unknown(0x08) -> All(0x00), ?(0x33), data: 0B FF 3C FB FF 28 FF 01 46 00 FF 00
2023-01-02 10:40:13.186 DEBUG 224: [emsesp] No telegram type handler found for ID 0x33 (src 0x08)
2023-01-02 10:40:13.680 TRACE 225: [emsesp] Unknown(0x08) -> All(0x00), ?(0x15), data: 00 3C 01 01 09 00 00 00
2023-01-02 10:40:13.680 DEBUG 226: [emsesp] No telegram type handler found for ID 0x15 (src 0x08)
2023-01-02 10:40:14.134 TRACE 227: [emsesp] Switch(0x11) -> Unknown(0x08), WM10TempMessage(0x1E), data: 01 9B
2023-01-02 10:40:17.593 TRACE 228: [emsesp] Unknown(0x08) -> All(0x00), ?(0x16), data: FF 5A 64 00 06 FA 0A 01 05 64 00 02
2023-01-02 10:40:17.593 DEBUG 229: [emsesp] No telegram type handler found for ID 0x16 (src 0x08)
2023-01-02 10:40:17.883 TRACE 230: [emsesp] Unknown(0x08) -> All(0x00), ?(0x18), data: 30 80 00 64 0F 09 01 A5 40 80 00 02 32 80 00 FF FF FF 2D 48 00 C8 00 02 00
2023-01-02 10:40:17.883 DEBUG 231: [emsesp] No telegram type handler found for ID 0x18 (src 0x08)
2023-01-02 10:40:18.170 TRACE 232: [emsesp] Unknown(0x08) -> All(0x00), ?(0x33), data: 0B FF 3C FB FF 28 FF 01 46 00 FF 00
2023-01-02 10:40:18.170 DEBUG 233: [emsesp] No telegram type handler found for ID 0x33 (src 0x08)
2023-01-02 10:40:18.480 TRACE 234: [emsesp] Unknown(0x08) -> All(0x00), ?(0x08), data: 30 48 00 CB 00 2D 48 00 C8 09 35 48 01 36 40 35 48 01 36 40
2023-01-02 10:40:18.480 DEBUG 235: [emsesp] No telegram type handler found for ID 0x08 (src 0x08)
2023-01-02 10:40:18.943 TRACE 236: [emsesp] Unknown(0x08) -> All(0x00), ?(0x15), data: 00 3C 01 01 09 00 00 00
2023-01-02 10:40:18.943 DEBUG 237: [emsesp] No telegram type handler found for ID 0x15 (src 0x08)
@cgeboers cgeboers added the question Question about something label Jan 2, 2023
@cgeboers
Copy link
Author

cgeboers commented Jan 2, 2023 •
edited
Loading

After restarting my browser, I can see this on the dashboard, both boilers have 0 entities , the RC35 does have 58

ems-bus-01

@cgeboers cgeboers closed this as completed Jan 2, 2023
@cgeboers cgeboers reopened this Jan 2, 2023
@proddy
Copy link
Contributor

proddy commented Jan 2, 2023 •
edited
Loading

Michael added a change for missing product IDs in v3.5. See if you can upgrade to that dev version.

And read https://emsesp.github.io/docs/FAQ/ on what to attach to this GH issue which will help us support you better

@MichaelDvP
Copy link
Contributor

Yes, please update, but 0x68 0x69 are unknown also in v3.5.
Please describe your system, how are the 2 boilers connected to the bus? Where is emsesp connected?
It looks like something like the cascade module, but with boilers mapped to 0x68/69 and the module as unknown boiler at device-id 0x08.
With v3.5 make a log (level all) of > 2 minutes and attach it here as file. Also load from help page the supportinfo and also attach it.

@cgeboers
Copy link
Author

cgeboers commented Jan 2, 2023

I don't really know how the boilers are connected to the EMS bus. What I discovered in the past is that when I connect my EMS-ESP32 to the service bus connector (3.5mm) of one of the boilers, I can only see the data of that boiler end not my RC35 for example. Currently my EMS-ESP32 is connected to the bus of the "controller" and in that case I can see bothe boilers, as well as the RC35 thermostat.

I also upgraded to v3.5 and have attached the requested info.
emsesp_log.txt
emsesp_info.txt

@MichaelDvP
Copy link
Contributor

Thanks, in first step i have added the cascade module as boiler/controller. his should give you the most values.
The boilers go to heatsources. The 0x68/0x69 devices are strange, we have to determine in a second step.
Please update this version to test: https://github.com/MichaelDvP/EMS-ESP32/releases

@cgeboers
Copy link
Author

cgeboers commented Jan 2, 2023

Thanks for the fast return! Looks better, I still see some unrecognized devices in the system log, but the device status shows no more unknown devices.
ems-bus-02

The heatsources however still only show 0 entities, is this intended behavior?

emsesp_log.txt

@MichaelDvP
Copy link
Contributor

The heatsources however still only show 0 entities, is this intended behavior?

Actually yes. For EMS+ cascade the boilers behind the cascade reports current flowtemp, burnerpower and workingtime, that's all. For this module we have to wait if there is something reported, Check the help/support_info after a few hours if there are ignored handlers for these devices.

@proddy What to do with the 0x68/0x69 devices, they are only registered in boiler devices-0x07 telegram, but no reply to version request and no other communication in this small log. Maybe register as controller to stop version requests and do not show them to dashboard? In support info they will show up with possible sent telegrams. I've added a test to my build.
I've fond on @norberts1 list that 0x68/0x69 is also heatingsource 1/2. But we have the two boilers with version info on 0x71/0x72 and i think there are no other boilers.
@cgeboers do you have more than these two boilers? Please update to new version from metioned repo, let it run some hours or a day and post the suport info here. A better description of yur system could be usefull. Make some photos. Also select in RC35 service menu the version info and tell us. (menu/ok+info+return keys simultanious, then select diagnostic, versions)

@proddy
Copy link
Contributor

proddy commented Jan 2, 2023

@proddy What to do with the 0x68/0x69 devices, they are only registered in boiler devices-0x07 telegram, but no reply to version request and no other communication in this small log.

@MichaelDvP how about having an ignore/block list of device-id's we simply ignore, if they don't service any purpose

@cgeboers
Copy link
Author

cgeboers commented Jan 3, 2023

I ran v3.5.0-dev15 all night and here are the results attached.
emsesp-system-status
emsesp_info.txt

My system has only two boilers:

boilers

The MCM10 is in the middle of the two.

MCM10

The RC35 versions info:

rc35

Everything seems to work fine now, the dashboard shows this:

emsesp-dashboard

The dasboard status shows some failed reads:

image

@emsesp emsesp locked and limited conversation to collaborators Feb 13, 2023
@proddy proddy converted this issue into a discussion Feb 13, 2023
@proddy proddy reopened this Feb 13, 2023
@proddy proddy converted this issue into a discussion Feb 13, 2023
@proddy proddy reopened this Feb 19, 2023
@proddy proddy closed this as completed Feb 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
question Question about something
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@proddy @MichaelDvP @cgeboers