John

scan result: 08;Vaillant;EHP00;0327;7201 15;Vaillant;UIH00;0216;6901 1c;Vaillant;RC C ;0501;6201 23;Vaillant;EHP00;0327;7201 25;Vaillant;EHP00;0327;7201 50;Vaillant;EHP00;0327;7201 52;Vaillant;MC2 ;0500;6301 53;Vaillant;MC2 ;0500;6301 75;Vaillant;RC C ;0501;6201 grab result: 1008b50303010100 / 08020d1101030e1902 1008b50303010101 / 08020d1101030e1902 1008b50303010102 / 08020d1101030e1902 1008b50303010103 /...

Error and service history are now supported (b503030101XX and b503030102XX), see commit https://github.com/john30/ebusd-configuration/commit/0d4cd358b2b2ae63bddec4b27c2d935004bc73b1

@romor: the "error" in Status01 is related to a pump state, so maybe the pump is not present? Or the field ist just not of "pumpstate" type but instead a...

regarding the pump state I'll check the MDB if it contains more details of this particular data type.

@romor: there was no hint for the pump state in the database, but I changed the value translations to your findings with commit 0369535d84b54f3f530391f0c0f713a51641dc49

@MikiDi: there is already a script doing some calculations on the grab result: [makegrabcsv.sh](https://github.com/john30/ebusd/raw/master/contrib/scripts/makegrabcsv.sh) Yes I know, having it all in one issue is a little bit nasty, but otherwise...

[ebusd-2.1.x](https://github.com/john30/ebusd-configuration/tree/master/ebusd-2.1.x/de/vaillant) is going to be the next generation of config files also supporting a greater variety of BAI devices than ebusd-2.x.x. In order to use it, the next ebusd version...

@andig not "grep" but "grab"! the output of `ebusctl grab result` is desired

I'm pretty sure this is a clone of the 0010015600. can you simply insert ";'0010021887'" right after "'0010021888'" in the 08.bai.csv file and check if d.14 and d.15 work then?

for the bai there should be more values. just check with `ebusctl find` which messages are available