We have a ebus adapter v2.2 since monthes, working fine working under USB on a Raspberry Pi3B.
Since 2/3 days, we lost the update of our variables that we used to retrieve by eBus.
We made several tests, including the reinstall of a fresh Rasbian buster with only the ebusd.
So we installed a buster raspbian on another R.Pi3B + the package from https://github.com/john30/ebusd-debian and connected only the ebus adapter on it.
We can connect to the ebus and retrieve data, but only sometime. The major part of the time, there is "ERR: element not found" issue that bocks the rest of the process.
This seems to be linked to the reading/accessing of the config files. We resent the "scan full" request, but that doesn't seem to reload the config files.
The only way to make it run it to stop/start the ebus daemon several time until the retrieve of the config files is OK. (we have a stable Internet connection).
Here is a "classic" return that we have :
2021-04-10 22:41:38.664 [main notice] ebusd 21.2.v21.2 started with auto scan on device /dev/serial/by-id/usb-Silico$
2021-04-10 22:41:43.681 [main error] error reading config files from http://ebusd.eu/config/: ERR: element not found$
2021-04-10 22:41:43.698 [bus notice] bus started with own address 31/36
2021-04-10 22:41:43.733 [bus notice] signal acquired
2021-04-10 22:43:58.130 [main error] update check connect error
2021-04-10 22:44:47.888 [bus notice] new master 03, master count 2
2021-04-10 22:44:48.509 [bus notice] scan 08: ;Vaillant;BAI00;0609;5502
2021-04-10 22:44:48.509 [update notice] store 08 ident: done
2021-04-10 22:44:48.510 [update notice] sent scan-read scan.08 QQ=31: Vaillant;BAI00;0609;5502
2021-04-10 22:44:48.510 [bus notice] scan 08: ;Vaillant;BAI00;0609;5502
2021-04-10 22:44:48.635 [main error] error reading templates in vaillant: ERR: element not found, last error: vailla$
2021-04-10 22:44:48.692 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0609, HW5502
2021-04-10 22:44:48.692 [main error] error resolving conditions: ERR: element not found, last error: condition scan $
2021-04-10 22:44:48.818 [main error] error executing instructions: ERR: element not found, last error: error resolvi$
2021-04-10 22:44:48.818 [main notice] found messages: 1 (0 conditional on 25 conditions, 0 poll, 0 update)
2021-04-10 22:46:50.877 [main notice] update check: OK
On the other side, the scan result is OK:
sudo ebusctl scan result
08;Vaillant;BAI00;0609;5502
But we can't retrive data (because the element is not well listed:
ebusctl read -f -c bai FlowTemp
ERR: element not found
We also tested without using it as a service and this seems to be less complicated for the deamon to get the config files :
Is there any way to get the config files locally (internet access is not always a need to run a system)?
Do you have some suggestions of tests or actions to solve this?
Hello,
We have a ebus adapter v2.2 since monthes, working fine working under USB on a Raspberry Pi3B. Since 2/3 days, we lost the update of our variables that we used to retrieve by eBus.
We made several tests, including the reinstall of a fresh Rasbian buster with only the ebusd. So we installed a buster raspbian on another R.Pi3B + the package from https://github.com/john30/ebusd-debian and connected only the ebus adapter on it.
We can connect to the ebus and retrieve data, but only sometime. The major part of the time, there is "ERR: element not found" issue that bocks the rest of the process. This seems to be linked to the reading/accessing of the config files. We resent the "scan full" request, but that doesn't seem to reload the config files. The only way to make it run it to stop/start the ebus daemon several time until the retrieve of the config files is OK. (we have a stable Internet connection).
Here is a "classic" return that we have :
On the other side, the scan result is OK:
But we can't retrive data (because the element is not well listed:
We also tested without using it as a service and this seems to be less complicated for the deamon to get the config files :
Is there any way to get the config files locally (internet access is not always a need to run a system)? Do you have some suggestions of tests or actions to solve this?