-
-
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
Missing WPPWMPower (0x7300
) since v24.1
#1445
Comments
please post the result of |
v24.1
v23.3
|
can't reproduce. please provide the logs again with additional "--lograwdata" |
v24.1v23.3 |
Yesterday, the system was rebooted. The problem no longer occurs since this reboot. This is really surprising to me: before the reboot, the value Anyway, not reproducible, no longer occurs => case closed. |
Description
After update from v23.3 to v24.1 (Docker), the value WPPWMPower (
0x7300
) is missing (Vaillant / BAI).First, I was thinking this might be related to the major configuration rework (typespec) or some other kind of configuraton issue (cf. john30/ebusd-configuration#450). But now I found out that even a request for the value by hex command has different behavior, so I guess this is no config issue.
Downgrading to v23.3 still provides the WPPWMPower value, so the hardware / heating side seems to be OK.
Actual behavior
Expected behavior
ebusd version
24.1
ebusd arguments
-f --device=/dev/ttyUSB_ebus --scanconfig --logareas=main,network,bus --loglevel=notice --mqtt...
Operating system
Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)
CPU architecture
armv7l
Dockerized
same as ebusd version
Hardware interface
other
Related integration
TCP (cmdline client like ebusctl or netcat)
Logs
v24.1
v23.3
The text was updated successfully, but these errors were encountered: