-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Stable connection only with --loglevel=debug #1001
Comments
I can only imagine that the timing is special for this recov device. you could check that now with the current firmware as stated here: |
Here is the output of the
I don't know how to judge. Does this look ok? Update:
with 2434 Hz, which is that 1.4% off of 2400? If I understood your explanation correctly this could be the problem? Is there a way to fix it? |
This is strange, I have also been having problems and just tried adding I am also using an adapter 5 via USB with a Vaillant boiler I adjusted the baud rate using the new feature (+24) and it didn't seem to make a difference.
|
I've found an issue hidden in the ESP32-C3 UART that reports a falsy non-TX-readiness. this seems to be an issue especially if ebusd handles the traffic too quickly as it seems to be the case on your host without the debug logging. could you check with the new firmware 20230917 just released? |
I confirm that with the new firmware the issue is resolved. Quick test showed identically good behaviour with and without debug log. |
Description
I have a weird situation where ebusd works stable only when I add
--loglevel=debug
to the arguments. Without the debug flag it takes very long to discover the device and most of the communications end up withERR: read timeout
. Must be some hidden configuration differences between debug and production modes?Actual behavior
with
EBUSD_OPTS="--scanconfig -d ens:/dev/ttyACM0 --scanconfig=08 -c /etc/ebusd/"
the device discovery may take very long and most (but not all) of reads/writes fail, i.e.
$ ebusctl read -f -c recov TempOutsideAir
end up with
ERR: read timeout
see Log-no-debug below.
When I add
--loglevel=debug
to the EBUSD_OPTS, the communication is stable.i.e. with
-d ens:/dev/ttyACM0 --loglevel=debug --scanconfig=08 -c /etc/ebusd/
most of reads are successfully.
see Log-debug below.
I tried playing with
latency
andreceivetimeout
parameters for production runs but saw no improvements. i.e. to be concrete--latency=10 --receivetimeout=50
does not help.Expected behavior
The communication quality is not expected to depend on log level. Also a stable communication with with the adapter is expected.
ebusd version
23.2
ebusd arguments
EBUSD_OPTS="--scanconfig -d ens:/dev/ttyACM0 --scanconfig=08 -c /etc/ebusd/"
Operating system
Debian 11 (Bullseye) / Ubuntu 20-21 / Raspbian 11 / Raspberry Pi OS 11 (including lite)
CPU architecture
x64
Dockerized
None
Hardware interface
adapter 5 via USB
Related integration
No response
Logs
Log-no-debug:
Log-debug:
The text was updated successfully, but these errors were encountered: