Elecrow eBUS Stick C6 (ESP32-C6, build 20250216) Loses Settings After Home Assistant Reboot
Hello Community,
I am experiencing a persistent connectivity issue with my Elecrow C6 eBUS Adapter (based on an ESP32-C6, rev 2 chip). The stick works perfectly after manual configuration, but after a Home Assistant OS reboot, the stick loses its working configuration (presumably Plain Mode).
I currently do not have physical access to my C6 eBUS stick, as the system is running in my holiday/summer house, and am therefore seeking a remote solution to resolve this issue, which unfortunately makes troubleshooting somewhat difficult.
Crucially, functionality is only restored by accessing the stick's Web GUI via Wi-Fi and saving the settings again, which forces the necessary configuration to be written to the stick's memory.
My Setup:
Adapter: Elecrow C6 eBUS Adapter
Chip ID: ccba97f8e568 (ESP32-C6, rev 2)
Firmware Build: 20250216 (Crucial detail for support)
Platform: Home Assistant OS with eBUSd Add-on (v25.1.p20250414).
Connection: USB serial (/dev/serial/by-id/usb-Espressif_...).
Symptom: eBUSd loses communication and never shows signal acquired after an HA reboot.
I have confirmed that the issue cannot be resolved by standard commands, confirming that the high-level "SAVE" function of the GUI is the missing piece:
eBUSd CLI (Port 8888) & Direct Serial Commands: All known remote commands designed to set the mode (plainmode, set mode plain, mode 0) failed to restore functionality, proving that simple serial commands do not replicate the necessary configuration and save action.
Forced Enhanced Protocol: Changing the eBUSd configuration to use the Enhanced Mode protocol (--device=ens:/dev/serial/...) made the stick recognized as enhanced in the log, but communication was still lost (no signal acquired).
Is a firmware update a known and confirmed fix for the C6/ESP32 adapter to resolve the issue of settings persistence (i.e., failure to save operating mode to NVRAM) after a power cycle/reboot?
Is there a newer firmware build available than 20250216 that specifically addresses this persistence issue?
Is there an undocumented high-level CLI command (or sequence) that replicates the "Save Settings" function via serial access (which I have via SSH) that bypasses the need for the Web GUI?
Thank you for any technical guidance!