[bug] dangling eBus signal while WiFi enabled

[JavanXD]

With my V5 Shield Adapter I had huge difficulties and I didn't know where they came from. I tried wifi, usb, and Ethernet but I still had lot's of overrun errors, on all recent release versions.

All the time I had the WiFi enabled, not for the data transfer but for being able to access the webinterface.

Today I found out, that disabling the WiFi on the esp32 fixes the disconnecing ebus signal.

I wrote a small rest sensor in Home Assistant which monitores the ebus signal status.

After I turned off the WiFi in the Adapter Configuration, the random ebus signal loses went away.

WiFi station/client: inactive
WiFi access point: inactive

And I am still able to access the webinterface via the IP address from the ethernet plug.

In the screenshot you can see the purpe little lines which showed that the ebus Signal was disconnected. After I disabled the WiFi at 1pm the signal kept constantly working.

[john30]

please check with the new version 20240505 just published if this is still the case

[JavanXD]

Hi @john30 , also with the new version the ebus Signal is very soon lost and the "overrun" error messages appear, see screenshot below: Once I disable the WiFi the Adapter works again.

Chip ID: 543204842644, ESP32-C3, rev 4
Hostname: vaillant-ebus
PCB: 1.24.1
Build: 20240505
Flash: 4194304
IDF: v5.3-dev-3675-ge486f3b944-dirty
Reset reason: 5
eBUS r/w: 3630/39
Host r/w: 98/4718
Up time: 423
Free heap: 109448 / 271268
ebusd connected: yes (inactive)
eBUS signal: no signal

[john30]

what is the signal strength according to the status page?

[JavanXD]

Before the firmware update I was able to connect in parallel to ethernet and to wifi. After the update - while being connected to ethernet, the ebus Adaper cannot connect to my Wifi network, the Wifi status stays "not connected", while it creates the following error messages: Looks like it was not able to connect to my WiFi - the router is only 30cm away from the ebus Adapter.

But what works is running the WiFi Access Point on the Adaper while being connected via Ethernet.

[JavanXD]

Note the fact that the wifi commands are causing the "overrun" errors. But I am not using Wifi, I am connecting the ebusd container via the ethernet-ip-address.

[john30]

if you're so close to the router, then maybe lowering the tx power might help (can be done with recent firmware in the web ui). is there any logging in the router?

[john30]

closed for inactivity