-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
[bug] dangling eBus signal while WiFi enabled #63
Comments
please check with the new version 20240505 just published if this is still the case |
Hi @john30 , also with the new version the ebus Signal is very soon lost and the "overrun" error messages appear, see screenshot below:
|
what is the signal strength according to the status page? |
Note the fact that the wifi commands are causing the "overrun" errors. |
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? |
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.
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.
The text was updated successfully, but these errors were encountered: