Faults don't appear in ebusd readings (Vaillant AtmoTec 280, vrc700)

[voroshkov]

Hi John! First of all thanks for the great job with all the ebus stuff made available to enthusiasts!

Issue description: I've just tried testing if a heating hardware fault could be detected via ebusd, but it failed: no errors are reported although my heater clearly displays the F.28 (ignition fault) error.

Details: Hardware setup:

• ebus adapter v.3, connected to home network via Ethernet cable
• Vailant AtmoTec 280, VR 70, VRC 700

I closed the gas valve to initiate the error and issued several readings from ebusd:

bash-5.1# ebusctl read -f error
ERR: element not found

bash-5.1# ebusctl read -f currenterror
-;-;-;-;-

bash-5.1# ebusctl read -f errorhistory
ERR: end of input reached

Can you kindly help finding how to track such faults via ebusd?

Additional details: This doesn't look like an issue of my setup because everything else (reading ebus messages, writing desired temperature settings) works just fine.

[stadid]

Andrey, your problem is that you are reading errors incorrectly, VRC700 has it's own "variable" for errors and Heating unit has it's own. If you don't say which circuit you want to read from, then ebusd will pick the first in order of read definitions. So, the correct way of reading current error is the following: ebusctl read -f -c bai currenterror ebusctl read -f -c 700 currenterror

Remember that VRC errors differs from the heater - it's the erros of the regulator itself, they are not linked with the heater.

error history in BAI is read in the following way (it's the "array" of the last 10 heating unit errors): ebusctl read -f -i 0 -c bai errorhistory ebusctl read -f -i 1 -c bai errorhistory .... ebusctl read -f -i 9 -c bai errorhistory

BTW if you are not doing integration with the HA or any other type of "smart house" and looking for Multimatic app replacement you can check this thread https://www.forumhouse.ru/threads/417757/page-23 and upwards