John
John
you should be able to check if the files are still there once it occurs again by issuing a "podman exec ls -la /ebusd-config" or so
maybe just a rights issue. start ebusd with additional "--log=debug" and check the output. it should give lines like ``` 2023-10-08 06:17:49.571 [main info] loading configuration files from /ebusd-config/ 2023-10-08...
closed due to inactivity
this is a matter of correcting the definition of the message, especially the unit, e.g. in [bai.0010007508_inc.tsp:463](https://github.com/john30/ebusd-configuration/blob/e257ec9c39b95550ca0415fa6f24e625a8c6ac71/src/vaillant/bai.0010007508_inc.tsp#L463) or [bai.0010007508.inc:96](https://github.com/john30/ebusd-configuration/blob/e257ec9c39b95550ca0415fa6f24e625a8c6ac71/ebusd-2.1.x/en/vaillant/bai.0010007508.inc#L96) and friends
ebusctl is no longer maintained from my side and it is only kept for people claiming about it missing instead of switching to anything else (like netcat). the listen command...
no idea. is this tado thing connected to ebus or how would it influence ebusd in the first place?
maybe it is just an address conflict, so check the result of "ebusctl info" for that and post the list of found addresses
closing due to inactivity
reworked+merged in cffa1cec
please check the [next](https://ebus.github.io/next/) generated csvs with ebusd 24.1 (or current source) as described there or by using a local clone of https://github.com/eBUS/ebus.github.io and using the "next" folder in there