Issue with eBUSd Not Loading Configuration for Vaillant BAI00 #1498
-
Hello everyone,I'm having an issue with Previously, Even at that time, running Now, after restarting And What I Tried:Config files exist ( System Info:
Would really appreciate any help! Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 7 replies
-
|
Have you changed within the csv from "r" to e.g. "r1", that it will poll the values (like r1;w,,AdaptHeatCurve,adaptive heat curve,,,,1400,,,yesno,,,automatic correction of configured heat curve) ? See https://github.com/john30/ebusd/wiki/4.1.-Message-definition where it says What happens if you Afte that we will look, why the csv are not loaded (ebusctl info). Mine looks like: My AdaptHeatCurve is within 15.ctlv2.csv. Regards Sebastian |
Beta Was this translation helpful? Give feedback.
-
|
I have not explicitly modified Attempting to Read
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, but you want it to load and then load a config file with message definitions, worse-case bai.308523.inc. Your startup logs may be useful? |
Beta Was this translation helpful? Give feedback.
-
|
@Hotelk52339 - it's a bit confusing when you have two threads open for the same issue, here and on the issues forum! I'd be inclined to close one (the other one)? I'd also be inclined to review the logs on start-up, capturing the details around the scan process and post those back here? This will help you see if there was some issue on startup. It would be helpful If you could more fully describe your equipment maybe. And are you sure you're showing the whole And when you say you use to get some observed behaviour and now you don't, what could have changed - new adapter, some other hardware change, boiler service etc? Have you ever been able to read values successfully from ebusd and it had recently stopped or you haven't got that far yet? (and anyway 08.bai,csv only loads a few status message definitions, it's main role is as a 'manifest' to match and load either specific boiler config files or failing that, load the default definitions file bai308523.inc so you want to at least get to that point, but one step at a time!) |
Beta Was this translation helpful? Give feedback.
-
1. Threads on different forumsI understand the confusion. If needed, I can close one of the threads 2. Startup logs & scan detailsI've checked the logs, and while Startup LogsScan Results3. Issue with Configuration Files
4. Attempting to Read Values
5. Responses to your questions:
Could the empty |
Beta Was this translation helpful? Give feedback.
-
|
Did you point ebusd to the directory with the CSV config files using the --configpath parameter?
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, root@CT102:~/ebusd# ps -fp $(cat /run/ebusd.pid)
UID PID PPID C STIME TTY TIME CMD
root 461 1 0 Feb26 ? 00:00:11 /usr/bin/ebusd --configpath=/etc/ebusd/configs --device=ens:192.168.1.111:9999 --scanconfigI also stopped journalctl -u ebusd --no-pager | tail -n 50Here are the key log entries: Feb 26 08:22:43 CT102 systemd[1]: ebusd.service: Deactivated successfully.
Feb 26 08:22:43 CT102 systemd[1]: Stopped ebusd, the daemon for communication with eBUS heating systems..
Feb 26 08:22:43 CT102 systemd[1]: ebusd.service: Consumed 59.875s CPU time.
Feb 26 09:05:55 CT102 systemd[1]: Starting ebusd, the daemon for communication with eBUS heating systems....
Feb 26 09:05:55 CT102 systemd[1]: ebusd.service: Failed to parse PID from file /run/ebusd.pid: Invalid argument
Feb 26 09:05:55 CT102 systemd[1]: ebusd.service: Failed with result 'protocol'.
Feb 26 09:05:55 CT102 systemd[1]: Failed to start ebusd, the daemon for communication with eBUS heating systems..
Feb 26 09:06:25 CT102 systemd[1]: ebusd.service: Scheduled restart job, restart counter is at 1.
Feb 26 09:06:25 CT102 systemd[1]: Stopped ebusd, the daemon for communication with eBUS heating systems..
Feb 26 09:06:25 CT102 systemd[1]: Starting ebusd, the daemon for communication with eBUS heating systems....
Feb 26 09:06:25 CT102 systemd[1]: Started ebusd, the daemon for communication with eBUS heating systems..
Feb 26 17:01:44 CT102 systemd[1]: Stopping ebusd, the daemon for communication with eBUS heating systems....
Feb 26 17:01:44 CT102 systemd[1]: ebusd.service: Deactivated successfully.
Feb 26 17:01:44 CT102 systemd[1]: Stopped ebusd, the daemon for communication with eBUS heating systems..
Feb 26 17:01:44 CT102 systemd[1]: ebusd.service: Consumed 11.308s CPU time.
-- Boot d912d0d632ca412ab240913626b8a22e --
Feb 26 21:35:07 CT102 systemd[1]: Starting ebusd, the daemon for communication with eBUS heating systems....
Feb 26 21:35:07 CT102 systemd[1]: Started ebusd, the daemon for communication with eBUS heating systems..
Feb 26 21:41:26 CT102 systemd[1]: Stopping ebusd, the daemon for communication with eBUS heating systems....
Feb 26 21:41:26 CT102 systemd[1]: ebusd.service: Deactivated successfully.
Feb 26 21:41:26 CT102 systemd[1]: Stopped ebusd, the daemon for communication with eBUS heating systems..
-- Boot daf9cb80b9704fa1b38b7c44b164ae03 --
Feb 26 21:41:32 CT102 systemd[1]: Starting ebusd, the daemon for communication with eBUS heating systems....
Feb 26 21:41:32 CT102 systemd[1]: Started ebusd, the daemon for communication with eBUS heating systems..
Feb 26 21:45:45 CT102 systemd[1]: Stopping ebusd, the daemon for communication with eBUS heating systems....
Feb 26 21:45:46 CT102 systemd[1]: ebusd.service: Deactivated successfully.
Feb 26 21:45:46 CT102 systemd[1]: Stopped ebusd, the daemon for communication with eBUS heating systems..
Feb 26 23:16:01 CT102 systemd[1]: Starting ebusd, the daemon for communication with eBUS heating systems....
Feb 26 23:16:01 CT102 systemd[1]: ebusd.service: Failed to parse PID from file /run/ebusd.pid: Invalid argument
Feb 26 23:16:35 CT102 systemd[1]: ebusd.service: Deactivated successfully.
Feb 26 23:16:35 CT102 systemd[1]: Stopped ebusd, the daemon for communication with eBUS heating systems..
Feb 26 23:16:35 CT102 systemd[1]: Starting ebusd, the daemon for communication with eBUS heating systems....
Feb 26 23:16:35 CT102 systemd[1]: Started ebusd, the daemon for communication with eBUS heating systems..
Feb 26 23:35:27 CT102 systemd[1]: Stopping ebusd, the daemon for communication with eBUS heating systems....
Feb 26 23:35:27 CT102 systemd[1]: ebusd.service: Deactivated successfully.
Feb 26 23:35:27 CT102 systemd[1]: Stopped ebusd, the daemon for communication with eBUS heating systems..
Feb 26 23:35:27 CT102 systemd[1]: Starting ebusd, the daemon for communication with eBUS heating systems....
Feb 26 23:35:27 CT102 systemd[1]: Started ebusd, the daemon for communication with eBUS heating systems..
Feb 27 22:25:16 CT102 systemd[1]: Stopping ebusd, the daemon for communication with eBUS heating systems....
Feb 27 22:25:16 CT102 systemd[1]: ebusd.service: Deactivated successfully.
Feb 27 22:25:16 CT102 systemd[1]: Stopped ebusd, the daemon for communication with eBUS heating systems..
Feb 27 22:25:16 CT102 systemd[1]: ebusd.service: Consumed 12.818s CPU time.
-- Boot e015b6e653214a969deccf7c9858b6ce --
Feb 27 22:25:22 CT102 systemd[1]: Starting ebusd, the daemon for communication with eBUS heating systems....
Feb 27 22:25:22 CT102 systemd[1]: ebusd.service: Can't open PID file /run/ebusd.pid (yet?) after start: Operation not permitted
Feb 27 22:25:22 CT102 systemd[1]: Started ebusd, the daemon for communication with eBUS heating systems..From the logs, I see the following messages: There are no explicit errors regarding CSV file loading, but there is also no confirmation that they are loaded. Additional checks:I checked root@CT102:~/ebusd# ebusctl i | grep -i "loaded"(Empty output) Checked the root@CT102:~/ebusd# ls -l /etc/ebusd/configs/08.bai.csv
-rw-r--r-- 1 root root 0 Feb 26 23:44 /etc/ebusd/configs/08.bai.csvThe file is empty (0 bytes). Trying to read root@CT102:~/ebusd# ebusctl read -V AdaptHeatCurve
ERR: read timeoutTrying root@CT102:~/ebusd# ebusctl find
basv AdaptHeatCurve = no data stored
basv ContinuosHeating = no data stored
basv CylinderChargeHyst = no data stored
basv CylinderChargeOffset = no data stored
basv Date = no data stored
basv FrostOverRideTime = no data stored
basv GlobalSystemOff = no data stored
basv HwcLockTime = no data stored
basv HwcParallelLoading = no data stored
basv HydraulicScheme = no data stored
basv MaintenanceDate = no data stored
basv ManualCooling = no data stored
basv MaxCylinderChargeTime = no data stored
basv MaxRoomHumidity = no data stored
basv PumpAdditionalTime = no data stored
basv Time = no data stored
basv WaterPressure = no data stored
scan.08 = Vaillant;BAI00;0302;0903Conclusion:
Question: |
Beta Was this translation helpful? Give feedback.
-
|
Yes- it shouldn’t be empty! You can observe what it should have here : https://github.com/eBUS/ebus.github.io/blob/main/en/vaillant/08.bai.csv maybe a permissions issue when you copied? Not sure without seeing the Product Id which other file it would load, probably bai.308523.inc - but for now I would clone the entire config files folder, or at very least those bai……inc files as well. It should load 08.bai.csv based on address and circuit name and then iterate through it trying to match product id or hw level. If it matches (lines 15-40) it loads the specifically referenced file. If it matches none, it should load bai308523.inc (line 41) |
Beta Was this translation helpful? Give feedback.
-
1. Downloaded
|
Beta Was this translation helpful? Give feedback.
-
|
I suspect that I might have installed ebusd incorrectly on Ubuntu, which could be causing these issues. If that is the case, I am willing to completely remove and reinstall ebusd from scratch If anyone could provide a step-by-step guide on how to properly install and configure ebusd for my setup, I would really appreciate it |
Beta Was this translation helpful? Give feedback.
-
|
You could start from scratch, but first I'd be tempted to simply clone the whole config repository - there are other .csv files like broadcast, templates, hcmode etc. that you need as well and also bai.308523.inc may not be the right file for your boiler. Or alternatively, do not clone the files and do not set I'm not an expert at either ebusd or linux but I think you're using some of the commands incorrectly too. Do you get the product id if you run (I don't think that To install did you follow the instructions for Ubuntu here: https://github.com/john30/ebusd/wiki/1.-Build-and-install |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your response! I ended up reinstalling Ubuntu from scratch and following the installation guide from the wiki. This fixed my initial issue – now the configuration loads properly, and I can successfully read data from my boiler. Regarding your suggestions:
This confirms that my boiler is recognized correctly Now that I have a working |
Beta Was this translation helpful? Give feedback.
You could start from scratch, but first I'd be tempted to simply clone the whole config repository - there are other .csv files like broadcast, templates, hcmode etc. that you need as well and also bai.308523.inc may not be the right file for your boiler.
Or alternatively, do not clone the files and do not set
--configpathto your local and use the online service instead (I think if you omit --configpath the default will be https://ebus.github.io/ but you can explicitly use that instead to be sure I guess)I'm not an expert at either ebusd or linux but I think you're using some of the commands incorrectly too.
Do you get the product id if you run
ebusctl find id | grep -i "scan.08"? If yo…