John

just follow the [instructions from here](https://github.com/john30/ebusd-configuration#installation-on-up-to-date-ebusd-20-or-higher): downloading is as simple as cloning this repo

for bkm i might have something, the others are duplicates of already existing devices as far as i remember

the converted bkm file simply consists of a single line including the hcmode.inc, so the use is very limited. Here is the content of the "08.bkm.csv" file: `# type (r[1-9];w;u),circuit,name,comment,QQ,ZZ,PBSB,ID,field,part...

hm, can you simply check with "ebusctl find -a -d" after it ran for one day or so? for the unknown messages, please start with posting your scan result ("ebusctl...

> [main error] unable to load scan config 15: no file from /etc/ebusd/vaillant with prefix 15. matches ID "b7v00", SW0422, HW5503 I'm afraid I habe no information at all for...

afaik 84 is exactly the same as one of the other VR630 devices, so no new information to gather. 18, 38, and 78 are all bus couplers, right? what devices...

yes afaik. again the same question: what devices are attached behind the vr32?

the thing is, such a special configuration would have to be supported by ebusd in the first place. so this does not work until [issue 109](https://github.com/john30/ebusd/issues/109) is solved. After that...

you should start with checking and dumping the configuration by using e.g. "ebusd -f --checkconfig --dumpconfig -c /path/to/your/csvs"

since the device does not answer spec-compliant to the ID request, you'll have to switch of "--scanconfig" mode @OllisGit . Otherwise the CSV will never be loaded. @tomashora your grab...