You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Looking for Vaillant ebusd users for passive cross-installation testing
#1802
I'm looking for a few additional Vaillant + ebusd users who would be willing to provide passive cross-installation evidence.
The small tool is here:
"MarcelT87/ebus-evidence"
Current release: "v0.1.0rc2"
The goal is not to control or probe the heating system. "ebus-evidence" only reads an already existing ebusd message-mode raw log and creates a small, privacy-conscious Evidence ZIP for comparing telegrams between different Vaillant installations.
There are:
no eBUS writes;
no direct adapter access;
no active probing;
no MQTT publishing;
no automatic upload;
no need to publish the complete "ebusd.raw".
The tool has already been independently tested on:
The HW0403 test was particularly useful because it already showed which telegram families appear to be portable across hardware generations and which ones do not occur on that system.
What would be especially useful now are a few more different Vaillant installations, for example:
aroTHERM plus or split;
older/newer HMU generations;
VRC 700;
VRC 720 / sensoCOMFORT;
VWZ / VR70 / VR71 systems;
or simply any Vaillant installation already running ebusd.
No protocol knowledge is required.
For an existing static message-mode raw log, the basic workflow is:
./evidence doctor --raw /path/to/ebusd.raw
./evidence import --raw /path/to/ebusd.raw
./evidence status --raw /path/to/ebusd.raw
./evidence export
For a running installation, "collect" can be used instead.
The resulting "data/evidence.zip" is verified locally before sharing and does not contain the complete raw log.
Even a result where some of the current checks produce zero matches is useful — negative cross-hardware evidence is part of what we are trying to collect.
If anyone is interested but unsure whether their system is useful or how to run it, just let me know. Failed installations or unusual results are useful feedback as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I'm looking for a few additional Vaillant + ebusd users who would be willing to provide passive cross-installation evidence.
The small tool is here:
"MarcelT87/ebus-evidence"
Current release: "v0.1.0rc2"
The goal is not to control or probe the heating system. "ebus-evidence" only reads an already existing ebusd message-mode raw log and creates a small, privacy-conscious Evidence ZIP for comparing telegrams between different Vaillant installations.
There are:
The tool has already been independently tested on:
The HW0403 test was particularly useful because it already showed which telegram families appear to be portable across hardware generations and which ones do not occur on that system.
What would be especially useful now are a few more different Vaillant installations, for example:
No protocol knowledge is required.
For an existing static message-mode raw log, the basic workflow is:
git clone https://github.com/MarcelT87/ebus-evidence.git
cd ebus-evidence
bash install.sh
./evidence doctor --raw /path/to/ebusd.raw
./evidence import --raw /path/to/ebusd.raw
./evidence status --raw /path/to/ebusd.raw
./evidence export
For a running installation, "collect" can be used instead.
The resulting "data/evidence.zip" is verified locally before sharing and does not contain the complete raw log.
Even a result where some of the current checks produce zero matches is useful — negative cross-hardware evidence is part of what we are trying to collect.
If anyone is interested but unsure whether their system is useful or how to run it, just let me know. Failed installations or unusual results are useful feedback as well.
Thanks!
All reactions