Error ebus: invalid plain 31

[schwerg]

On my eBUS Adapter Shield C6 Stick I am experiencing continuous errors of the form:

invalid plain 31

Since these errors started, the device no longer publishes any MQTT messages.

Does anyone know what this error indicates or how to resolve it? Any help would be appreciated.

Below is a shortened excerpt from the log (showing two occurrences out of many):

2026-03-20T17:53:56.703Z W repl: recovered 35 log entries
2026-03-20T17:53:56.703Z I repl: reboot 17 (3), using retained memory for logging
2026-03-20T17:53:56.723Z I memvfs: blocks ^^^^^^^^^^^^^^, 0 valid, 14 free, 0 deleted, 14 total, used x0, damaged x0
2026-03-20T17:53:57.701Z I �[5n0 duty 254
2026-03-20T17:53:57.710Z I function 'ledb' installed
2026-03-20T17:53:57.711Z I function 'ledg' installed
2026-03-20T17:53:57.711Z I function 'ledboot' installed
2026-03-20T17:53:57.712Z I function 'leds' installed
2026-03-20T17:53:57.712Z I IO 9 direction set to 01
2026-03-20T17:53:57.712Z I IO 9 pull set to 00
2026-03-20T17:53:57.713Z I IO 9 = 1
2026-03-20T17:53:57.717Z I 0 duty 254
2026-03-20T17:53:58.721Z I IO 9 level 1 is unmet
2026-03-20T17:53:58.722Z I 0 duty 254
2026-03-20T17:53:59.726Z I IO 9 level 1 is unmet
2026-03-20T17:53:59.727Z I 0 duty 254
2026-03-20T17:54:00.731Z I IO 9 level 1 is unmet
2026-03-20T17:54:00.732Z W exec: cmd failed: var -q hasrpi = 1
2026-03-20T17:54:00.733Z I var isnew = 0
2026-03-20T17:54:00.735Z I io trigger installed
2026-03-20T17:54:00.736Z I io trigger installed
2026-03-20T17:54:00.736Z I function 'start' installed
2026-03-20T17:54:00.737Z I network trigger installed
2026-03-20T17:54:00.738Z I network trigger installed
2026-03-20T17:54:00.738Z I network trigger installed
2026-03-20T17:54:00.738Z I network trigger installed
2026-03-20T17:54:00.739Z I network trigger installed
2026-03-20T17:54:00.739Z I server trigger installed
2026-03-20T17:54:00.740Z I function 'chkota' installed
2026-03-20T17:54:00.740Z I network trigger installed
2026-03-20T17:54:00.928Z I sta connecting to 'FloraNET'
2026-03-20T17:54:04.875Z I function 'wpsbtnnew' installed
2026-03-20T17:54:04.877Z I function 'chkethw' installed
2026-03-20T17:54:04.878Z I function 'chketh' installed
2026-03-20T17:54:04.881Z I 0 duty 0
2026-03-20T17:54:04.882Z I function 'chkethcfg' installed
2026-03-20T17:54:04.883Z W exec: cmd failed: eth -c = 1
2026-03-20T17:54:04.884Z I function 'enet' installed
2026-03-20T17:54:04.893Z I server started
2026-03-20T17:54:04.897Z I MQTT client started
2026-03-20T17:54:04.917Z W cmd_wifi: sta rssi low -67
2026-03-20T17:54:04.918Z I 0 duty 200
2026-03-20T17:54:05.019Z I time trigger installed
2026-03-20T17:54:05.020Z I time trigger installed
2026-03-20T17:54:14.561Z E ebus: invalid plain 31
2026-03-20T17:54:18.628Z E ebus: invalid plain 31
.
.
.

If relevant, I can provide additional configuration details (ebusd command line, adapter type, connection mode, etc.).

[sponnet]

Similar behaviour here since 2 days : ( running version [20260317] )

Hardware:

ESP32-C6, rev 1
--
Hostname: | ebus-957bc8
PCB: | 2.36.0
Build: | 20260317

No MQTT readings come out after this message. Falls right back in to this state after reboot.

logs:

...
10:12:49 | Info | ebus: switching to enhanced mode on TCP port (with bitrate deviation 0 and enhanced arbitration delay 200 us)
10:12:49 | Info | setup_ebus_host_tcp: listening on port 9999
10:12:49 | Info | setup_uart: eBUS UART 1 on TX=15(inv) RX=14(inv) with 2400 Bd
10:12:49 | Info | mdns: service added
10:12:49 | Info | exec: exit
10:12:49 | Info | exec: successfully ran 43/43 cmds from '/data/main.eas'
10:12:50 | Info | sntp: got NTP time: 2026-03-21 09:12:50
10:12:52 | Info | wait_host_tcp: accepted: 192.168.2.3
10:12:52 | Info | ebus: host reset
10:12:59 | Error | ebus: invalid plain 31
10:12:59 | Error | ebus: invalid plain 31
10:13:08 | Error | ebus: invalid plain 31
... etc ...

[sponnet]

@schwerg - see #1709 (comment) - this might be related. I will have a look if the suggestions there can result in a fix for me, which might also help you out.

[schwerg]

Perfect, that's it. Thank you.

The issue is caused by the changes in ebusd V26: Read here