No communication via EMS BUS connection after K30RF upgrade - error 1010

[212850a]

DESCRIPTION

After upgrading firmware of K30RF from v12 to 14.00.01 my HomeCom app has stopped working whenever I connect the EMS-ESP32S3 gateway to my heating system.
As soon as the gateway is connected to the EMS bus, the HomeCom app can no longer communicate with the system. Bosch 7800i system also reports about Locking error 1010 - No communication via EMC BUS connection.
CR20RF remote module also shows error 1010.
If I disconnect the EMS-ESP32S3 and restart the controller, the HomeCom app works again without any issues.

I use ESP32S3-16MB+, initially it was version 3.7.0, then upgraded to version 3.8.2.
Also tried to switch EMC Tx Mode to EMS+, EMS BUS ID to Gateway 7 (0x4D) - still the same problem.
In system log a lot of messages like:

2026-05-24T15:58:33.151 W 61: [telegram] Incomplete Rx: 90 48 F7 00 FF 0A F0 29
2026-05-24T15:58:36.542 W 62: [telegram] Incomplete Rx: 90 48 F7 00 FF 0C EC FF FF 88 00 07 00 09 00 00 00 00 00 00 00 01 00 00 00 00 82
2026-05-24T15:58:39.075 W 63: [telegram] Incomplete Rx: 90 48 F7 00 FF 0C F9 00 00 2A
2026-05-24T15:58:43.075 W 64: [telegram] Incomplete Rx: 90 48 FF 32 FA 48
2026-05-24T15:59:28.714 W 65: [telegram] Incomplete Rx: 90 48 F7 00 FF 05 7A 00 0B
2026-05-24T15:59:46.389 W 66: [telegram] Incomplete Rx: 90 48 FF 00 02 09 FF 14 00 5C FF FF FF FF 4C
2026-05-24T15:59:53.664 W 67: [telegram] Incomplete Rx: 90 48 FF 00 04 93 02 C0 48
2026-05-24T15:59:57.120 W 68: [telegram] Incomplete Rx: B8 48 FF 00 09 57 01 DD FF 88 00 07 00 09 00 00 00 00 00 01 00 01 01 00 00 00 CA
2026-05-24T16:00:00.001 W 69: [telegram] Incomplete Rx: 90 48 01 1B 48 4D 49 38 30 30 2E 32 00 00 00 00 00 00 00 00 50
2026-05-24T16:00:02.439 W 70: [telegram] Incomplete Rx: 90 48 FF 00 05 15 01 18 00 5C FD 41
2026-05-24T16:00:28.140 W 71: [telegram] Incomplete Rx: C8 90 F7 00 02 FF 13
2026-05-24T16:00:53.571 W 72: [telegram] Incomplete Rx: 90 48 F7 00 FF 0A 0B FF FF FF FF FF FF FF 88 00 07 00 09 01 00 00 00 00 01 00 01 00 00 00 00 0A
2026-05-24T16:00:59.666 W 73: [telegram] Incomplete Rx: 90 48 01 2B 37 31 35 32 39 39 F0 26
2026-05-24T16:01:14.037 W 74: [telegram] Incomplete Rx: F0 88 90 FF 0C 01 01 40 D3
2026-05-24T16:01:29.729 W 75: [telegram] Incomplete Rx: 90 48 FF 19 09 F8 00 00 00 00 00 F0 15
2026-05-24T16:01:39.030 W 76: [telegram] Incomplete Rx: C8 90 FF 32 19 14
2026-05-24T16:01:42.242 W 77: [telegram] Incomplete Rx: C8 90 FF 00 19 CA 61
...
2026-05-24T18:20:33.805 W 757: [telegram] Incomplete Rx: 90 48 FF 19 03 4A 18 01 FC 0B
2026-05-24T18:20:36.580 W 758: [telegram] Incomplete Rx: C8 90 FF 4B 09 17
2026-05-24T18:20:58.444 W 759: [telegram] Incomplete Rx: 90 48 F7 00 FF 03 4C 00 00 00 00 00 00 00 00 00 00 00 EE 0F
2026-05-24T18:21:26.231 W 760: [telegram] Incomplete Rx: C8 90 F7 00 0D 0D
2026-05-24T18:21:32.719 W 761: [telegram] Incomplete Rx: 90 48 F7 00 FF 0A 10 FF FF FF 48
2026-05-24T18:21:53.382 W 762: [telegram] Incomplete Rx: 90 48 F7 00 FF 0A 35 00 67 C0 48
2026-05-24T18:22:12.345 W 763: [telegram] Incomplete Rx: C8 90 F7 00 FF 38
2026-05-24T18:22:46.846 W 764: [telegram] Incomplete Rx: C8 90 F7 00 01 FF FE FF 48
2026-05-24T18:23:09.384 W 765: [telegram] Incomplete Rx: C8 90 F7 00 0D FF 09 FA 48
2026-05-24T18:23:12.084 W 766: [telegram] Incomplete Rx: C8 90 F7 00 0D FF 0A 1F 19
2026-05-24T18:23:14.692 W 767: [telegram] Incomplete Rx: C8 F8 88 90 FF 0C 01 01 40 D3
2026-05-24T18:23:15.004 E 768: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 90 FF 00 15 01 F5
2026-05-24T18:23:17.143 W 769: [telegram] Incomplete Rx: 90 48 F7 00 FF 00 66 88 00 E3 00 01 00 01 00 00 00 00 00 00 00 00 00 F1 00 00 50 CC
2026-05-24T18:23:29.965 W 770: [telegram] Incomplete Rx: C8 90 F7 00 88 00 07 00 09 00 00 00 00 00 01 00 01 00 00 00 00 C2
2026-05-24T18:23:30.497 E 771: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 90 FF 00 17 01 40
2026-05-24T18:23:32.497 W 772: [telegram] Incomplete Rx: 90 48 FF 4B 04 93 58 03 FF 03 FF 03 FF 03 FF 0E
2026-05-24T18:23:35.984 E 773: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 90 BB 00 14
2026-05-24T18:23:38.322 W 774: [telegram] Incomplete Rx: 90 48 FF 19 09 F8 00 00 F0 3D
2026-05-24T18:23:44.347 W 775: [telegram] Incomplete Rx: C8 90 FF FE 12
2026-05-24T18:23:46.810 W 776: [telegram] Incomplete Rx: C8 90 FF 4B 19 0A 21
2026-05-24T18:24:17.561 W 777: [telegram] Incomplete Rx: 90 48 F7 00 FF 0A 35 00 67 88 00 FF 18 03 8F 01 B1 00 97 00 9B 0F
2026-05-24T18:24:21.580 W 778: [telegram] Incomplete Rx: C8 90 F7 80 88 00 07 00 09 01 00 00 00 00 01 00 01 00 00 00 00 0A
2026-05-24T18:24:26.723 W 779: [telegram] Incomplete Rx: 90 48 F7 00 FF 01 BA 00 43
2026-05-24T18:24:36.661 W 780: [telegram] Incomplete Rx: C8 90 FF 00 19 FE 0C
2026-05-24T18:25:31.036 W 781: [telegram] Incomplete Rx: C8 90 F7 00 0D FF 0A 48
2026-05-24T18:25:51.550 W 782: [telegram] Incomplete Rx: C8 90 F7 00 12 FF 0C EE F0 38
2026-05-24T18:26:09.826 W 783: [telegram] Incomplete Rx: 90 48 F7 00 FF 00 68 FF 0B
2026-05-24T18:26:26.501 W 784: [telegram] Incomplete Rx: C8 90 F7 00 02 FF 01 B1 FF 48
2026-05-24T18:26:44.002 W 785: [telegram] Incomplete Rx: 90 48 F7 00 FF 0A 11 FF FF 48
2026-05-24T18:26:46.465 W 786: [telegram] Incomplete Rx: 90 48 FF 00 01 9C 01 03 00 00 00 02 05 28 41 88 0E
2026-05-24T18:27:12.790 W 787: [telegram] Incomplete Rx: C8 90 F7 00 FA 0A
2026-05-24T18:27:16.503 W 788: [telegram] Incomplete Rx: C8 90 FF F0 88 00 FF 00 01 D6 00 00 00 00 00 19 F7
2026-05-24T18:27:19.897 W 789: [telegram] Incomplete Rx: 90 88 00 FF 30 03 95 00 00 00 96 00 00 00 00 00 00 15 7F 00 00 00 00 00 00 16 5B 00 00 11 E5 C1
2026-05-24T18:27:25.865 E 790: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 90 BB 00 14
2026-05-24T18:27:27.353 W 791: [telegram] Incomplete Rx: 90 48 FF 2B 01 C3 FF 03 FF 01 FF 03 18 B7 0D
2026-05-24T18:27:29.953 W 792: [telegram] Incomplete Rx: 90 48 01 1B 48 4D 49 F8 53
2026-05-24T18:27:32.528 W 793: [telegram] Incomplete Rx: C8 90 FF 2C 01 C1 14
2026-05-24T18:27:35.740 W 794: [telegram] Incomplete Rx: 90 48 FF 0B FF 0E
2026-05-24T18:27:54.903 W 795: [telegram] Incomplete Rx: C8 90 F7 00 01 FF FE 06 48

TO REPRODUCE

Upgrade K30RF to v14.00.01.

SCREENSHOTS

ADDITIONAL CONTEXT

Based on data from HA before K30RF upgrade to v14 I definitely didn't have RX/TX failures and now they constantly grow.

[MichaelDvP]

Please set tx mode to off(zero), i've made dev.4 https://github.com/MichaelDvP/EMS-ESP32/releases with this option.
Then connect to the bus and check if there is still a communication error 1010. Log all for ~10 minutes and attach the log here. Are there still rx-errors, than the crc calculation may be changed.

[212850a]

@MichaelDvP I've just updated to 3.8.4 and set tx mode to off.

After 10 mins no errors in the log and no 1010 errors anymore

2026-05-25T13:23:48.000 I 2: [emsesp] Last system reset reason Core0: Power on reset, Core1: Power on reset
2026-05-25T13:23:48.000 I 3: [emsesp] Loaded board profile S32S3 (PSRAM: 8189 KB)
2026-05-25T13:23:48.000 I 4: [emsesp] Library loaded: 129 EMS devices, 569 device entities, 11 languages (en,de,nl,sv,pl,no,fr,tr,it,sk,cz)
2026-05-25T13:23:48.000 I 5: [emsesp] Starting Scheduler service
2026-05-25T13:23:48.000 I 6: [emsesp] Starting Custom Entity service
2026-05-25T13:23:48.000 I 7: [temperaturesensor] Starting Temperature Sensor service
2026-05-25T13:23:48.000 I 8: [analogsensor] Starting Analog Sensor service
2026-05-25T13:23:48.000 I 9: [emsesp] Starting Modules service
2026-05-25T13:23:48.000 I 10: [emsesp] Starting Web Server
2026-05-25T13:23:50.568 I 11: [emsesp] WiFi connected (Local IP=192.168.7.129, hostname=ems-esp32, TxPower=17 dBm)
2026-05-25T13:23:50.593 I 12: [emsesp] Starting mDNS Responder service
2026-05-25T13:23:50.593 I 13: [emsesp] Starting NTP service
2026-05-25T13:23:50.653 I 14: [mqtt] MQTT connected
2026-05-25T13:23:51.620 I 15: [emsesp] IPv6 (WiFi) local: fe80:0000:0000:0000:764d:bdff:fe9e:bcf0
2026-05-25T13:23:53.852 I 16: [system] NTP connected
2026-05-25T13:24:01.374 I 17: [emsesp] Detected EMS device: boiler (0x08)
2026-05-25T13:24:58.584 I 18: [emsesp] Detected EMS device: thermostat (0x10)
2026-05-25T13:25:00.103 I 19: [emsesp] Detected EMS device: gateway (0x48)
2026-05-25T13:25:01.229 I 20: [emsesp] Detected EMS device: connect (0x50)
2026-05-25T13:25:55.465 I 21: [emsesp] Detected EMS device: thermostat (0x38)

However for some reason I don't see any EMS Reads/Writes in status

In HA I've lost ability to set mode of hot water (Thermostat dhw Operating mode) and can't set desired temperature of HC1.
Is it due to tx mode is set to 0?

[MichaelDvP]

Ok, so just connecting and only rx does not give errors. But we need tx reads and for detecting the right devices and writes for setting values. I've pushed a dev4a version to my repo, If you set bus-ID to 0x0D, ems-esp will not send ack to each master poll. Only read/writes are send out. Try start a full log first and then set bus-ID 0x0D and tx-mode auto.

[212850a]

Try start a full log first
Is it called "Log EMC telegrams in hexadecimal" in Settings -> Application?

Before you suggested to set bus-ID 0x0D and tx-mode auto I've just set tx-mode back to EMS and restarted heat system with EMS-EMC32.
It returned only few errors in the log in the beginning, but now after 30 mins, no new errors, no 1010 errors either.

2026-05-25T17:51:31.000 I 1: [emsesp] EMS-ESP version 3.8.3-dev.4
2026-05-25T17:51:31.000 I 2: [emsesp] Last system reset reason Core0: Power on reset, Core1: Power on reset
2026-05-25T17:51:31.000 I 3: [emsesp] Loaded board profile S32S3 (PSRAM: 8189 KB)
2026-05-25T17:51:31.000 I 4: [emsesp] Library loaded: 129 EMS devices, 569 device entities, 11 languages (en,de,nl,sv,pl,no,fr,tr,it,sk,cz)
2026-05-25T17:51:31.000 I 5: [emsesp] Starting Scheduler service
2026-05-25T17:51:31.000 I 6: [emsesp] Starting Custom Entity service
2026-05-25T17:51:31.000 I 7: [temperaturesensor] Starting Temperature Sensor service
2026-05-25T17:51:31.000 I 8: [analogsensor] Starting Analog Sensor service
2026-05-25T17:51:31.000 I 9: [emsesp] Starting Modules service
2026-05-25T17:51:31.000 I 10: [emsesp] Starting Web Server
2026-05-25T17:51:33.415 I 11: [emsesp] WiFi connected (Local IP=192.168.7.129, hostname=ems-esp32, TxPower=15 dBm)
2026-05-25T17:51:33.440 I 12: [emsesp] Starting mDNS Responder service
2026-05-25T17:51:33.440 I 13: [emsesp] Starting NTP service
2026-05-25T17:51:33.500 I 14: [mqtt] MQTT connected
2026-05-25T17:51:34.616 I 15: [emsesp] IPv6 (WiFi) local: fe80:0000:0000:0000:764d:bdff:fe9e:bcf0
2026-05-25T17:51:34.982 I 16: [system] NTP connected
2026-05-25T17:51:44.373 I 17: [emsesp] Detected EMS device: boiler (0x08)
2026-05-25T17:52:43.482 I 18: [emsesp] Detected EMS device: thermostat (0x10)
2026-05-25T17:52:44.941 I 19: [emsesp] Detected EMS device: gateway (0x48)
2026-05-25T17:52:46.070 I 20: [emsesp] Detected EMS device: connect (0x50)
2026-05-25T17:53:29.374 I 21: [emsesp] Detected EMS device: thermostat (0x38)
2026-05-25T17:54:56.381 W 22: [telegram] Incomplete Rx: C8 90 FF 88 00 07 00 09 01 00 00 00 00 01 00 01 00 00 00 00 0A (crc: 45)
2026-05-25T17:55:01.950 E 23: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B D0 FF 00 FF DA 65
2026-05-25T17:55:05.161 W 24: [telegram] Incomplete Rx: 90 48 FF 19 05 88 00 FF 00 03 A0 00 00 00 94 4C (crc: B8)
2026-05-25T17:55:07.814 W 25: [telegram] Incomplete Rx: 90 48 FF 4B 09 F8 00 00 00 00 00 00 00 00 F8 14 (crc: 7B)
2026-05-25T17:55:10.415 W 26: [telegram] Incomplete Rx: 90 48 FF 19 0A 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 19 (crc: 69)
2026-05-25T17:55:18.502 W 27: [telegram] Incomplete Rx: D0 48 FF 00 0A B8 01 FF 00 24 57 (crc: F3)
2026-05-25T17:55:21.001 W 28: [telegram] Incomplete Rx: D0 48 FF 00 0A C3 01 FF 28 (crc: 0A)
2026-05-25T17:55:26.527 W 29: [telegram] Incomplete Rx: 90 48 FF 4B 0A 12 00 00 00 00 00 00 00 00 00 00 00 00 FE 2A (crc: 04)
2026-05-25T17:56:03.365 W 30: [telegram] Incomplete Rx: D0 48 FF 00 0A 0B (crc: 1A)
2026-05-25T17:56:46.841 W 31: [telegram] Incomplete Rx: D0 48 FF 00 0A BC 01 FF 00 09 (crc: C7)
2026-05-25T18:00:34.752 W 32: [telegram] Incomplete Rx: 90 48 F7 05 FF 04 11 00 88 00 07 00 09 01 00 00 00 00 01 00 01 01 00 00 00 02 (crc: 9E)

Mystics...

[MichaelDvP]

I mean log level all and bus ID modem 0x0D, you have still set service key 0x0B.

[212850a]

OK, I've set log to ALL, set tx-mode to auto, bus id to modem 0x0D and restarted EMS gateway.

Now almost all EMS Reads (tx) failed

It can't also correctly determine heat pump model

Full log is attached.

log.txt

I'm switching back to tx-mode EMC and service key 0x0B now.

[MichaelDvP]

Seems the 1010 error is solved with id 0x0D (without poll-ack)? For tx issued check with the different modes.

[212850a]

Seems the 1010 error is solved with your dev.4 release.
After I switched yesterday back to tx-mode EMS and service key 0x0B I got no 1010 errors and there was only one incomplete Rx

Log from yesterday:

2026-05-25T19:13:36.000 I 1: [emsesp] EMS-ESP version 3.8.3-dev.4
2026-05-25T19:13:36.000 I 2: [emsesp] Last system reset reason Core0: Software reset CPU, Core1: Software reset CPU
2026-05-25T19:13:36.000 I 3: [emsesp] Loaded board profile S32S3 (PSRAM: 8189 KB)
2026-05-25T19:13:36.000 I 4: [emsesp] Library loaded: 129 EMS devices, 569 device entities, 11 languages (en,de,nl,sv,pl,no,fr,tr,it,sk,cz)
2026-05-25T19:13:36.000 I 5: [emsesp] Starting Scheduler service
2026-05-25T19:13:36.000 I 6: [emsesp] Starting Custom Entity service
2026-05-25T19:13:36.000 I 7: [temperaturesensor] Starting Temperature Sensor service
2026-05-25T19:13:36.000 I 8: [analogsensor] Starting Analog Sensor service
2026-05-25T19:13:36.000 I 9: [emsesp] Starting Modules service
2026-05-25T19:13:36.000 I 10: [emsesp] Starting Web Server
2026-05-25T19:13:38.441 I 11: [emsesp] WiFi connected (Local IP=192.168.7.129, hostname=ems-esp32, TxPower=15 dBm)
2026-05-25T19:13:38.467 I 12: [emsesp] Starting mDNS Responder service
2026-05-25T19:13:38.467 I 13: [emsesp] Starting NTP service
2026-05-25T19:13:38.521 I 14: [mqtt] MQTT connected
2026-05-25T19:13:38.866 I 15: [system] NTP connected
2026-05-25T19:13:39.622 I 16: [emsesp] IPv6 (WiFi) local: fe80:0000:0000:0000:764d:bdff:fe9e:bcf0
2026-05-25T19:13:49.647 E 17: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 90 02 00 FF
2026-05-25T19:13:49.650 W 18: [emsesp] Unrecognized EMS device (deviceID 0x10, no productID). Please report on GitHub.
2026-05-25T19:13:50.042 I 19: [emsesp] Detected EMS device: boiler (0x08)
2026-05-25T19:13:50.489 I 20: [emsesp] Detected EMS device: thermostat (0x10)
2026-05-25T19:13:50.797 I 21: [emsesp] Detected EMS device: thermostat (0x38)
2026-05-25T19:13:51.174 I 22: [emsesp] Detected EMS device: gateway (0x48)
2026-05-25T19:13:51.470 I 23: [emsesp] Detected EMS device: connect (0x50)
2026-05-25T19:14:56.638 W 24: [telegram] Incomplete Rx: D0 48 FF 00 0A E2 D6 F0 0B (crc: 36)
2026-05-26T08:41:28.608 I 25: [command] Called command thermostat/seltemp (selected room temperature) with value 22.5 and id 1 on device 0x10

Not sure what was the cause of problem.

May be your version 3.8.3-dev.4 contains something what works well with K30RF v14.00.01 (in comparison to 3.8.2)?

[MichaelDvP]

I switched yesterday back to tx-mode EMS and service key 0x0B I got no 1010 errors

Then the error was not caused by ems-esp, for this mode/ID combination the dev is unchanged.

[212850a]

Today I reverted EMS-ESP32S3 back to 3.8.2 and it worked fine before I restarted K30RF, then again the same issues came.

I disconnected EMS-ESP32S3 from heat pump system and restarted it fully (together with K30RF), then connected EMS-ESP32S3 back and no issues are seen since then.

2026-05-29T16:19:24.000 I 1: [emsesp] EMS-ESP version 3.8.2
2026-05-29T16:19:24.000 I 2: [emsesp] Last system reset reason Core0: Power on reset, Core1: Power on reset
2026-05-29T16:19:24.000 I 3: [emsesp] Loaded board profile S32S3 (PSRAM: 8189 KB)
2026-05-29T16:19:24.000 I 4: [emsesp] Library loaded: 128 EMS devices, 569 device entities, 11 languages (en,de,nl,sv,pl,no,fr,tr,it,sk,cz)
2026-05-29T16:19:24.000 I 5: [emsesp] Starting Scheduler service
2026-05-29T16:19:24.000 I 6: [emsesp] Starting Custom Entity service
2026-05-29T16:19:24.000 I 7: [temperaturesensor] Starting Temperature Sensor service
2026-05-29T16:19:24.000 I 8: [analogsensor] Starting Analog Sensor service
2026-05-29T16:19:24.000 I 9: [emsesp] Starting Modules service
2026-05-29T16:19:24.000 I 10: [emsesp] Starting Web Server
2026-05-29T16:19:26.543 I 11: [emsesp] WiFi connected (Local IP=192.168.7.129, hostname=ems-esp32, TxPower=11 dBm)
2026-05-29T16:19:26.576 I 12: [emsesp] Starting mDNS Responder service
2026-05-29T16:19:26.576 I 13: [emsesp] Starting NTP service
2026-05-29T16:19:26.632 I 14: [mqtt] MQTT connected
2026-05-29T16:19:27.618 I 15: [emsesp] IPv6 (WiFi) local: fe80:0000:0000:0000:764d:bdff:fe9e:bcf0
2026-05-29T16:19:28.107 I 16: [system] NTP connected
2026-05-29T16:19:45.777 I 17: [emsesp] Detected EMS device: boiler (0x08)
2026-05-29T16:19:57.602 I 18: [emsesp] Detected EMS device: thermostat (0x10)
2026-05-29T16:19:59.420 I 19: [emsesp] Detected EMS device: thermostat (0x38)
2026-05-29T16:20:00.397 I 20: [emsesp] Detected EMS device: gateway (0x48)
2026-05-29T16:20:01.322 I 21: [emsesp] Detected EMS device: connect (0x50)

So it looks like EMS-ESP32S3 prevents K30RF (with version 14.00.01) to do some initial actions when it starts.

[JoBenk17B]

I am still experiencing the same issues as you. Without the EMS-ESP32S3 connected, the app and the K30RF work as expected. As soon as I connect the EMS-ESP32S3, the app can no longer establish a connection to the heat pump. If I leave the EMS-ESP32S3 connected, error A91-1010 appears at irregular intervals.

Just like in your case, the problem started after updating the K30RF to firmware version 14.0.0.1 Before the update, everything was working correctly.

[proddy]

Perhaps one test is to use TxMode 0, so EMS-ESP is just listening to the bus and not transmitting, and then see if the K30RF reports an warning. EMS-ESP will be unable to detect any devices when TxMode is 0 as Tx is needed to pull the ems device information, so it's just a quick test and will help us find the root cause.

[JoBenk17B]

I have set the TX mode to read-only, and since then the A91-1010 error has not occurred during the last 12 hours.

[proddy]

I have set the TX mode to read-only, and since then the A91-1010 error has not occurred during the last 12 hours.

does the error go when EMS-ESP is using a different EMS Bus ID?