You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Think this would be a useful added info when testing configurations; apologies if it already exists somewhere and I just haven't found it!
Background:-
Am trying to run ebusd via a docker container, and testing different configs. So far it seems difficult to be sure whether ebusd is continuing to use the default config files, or actually loading the manually pointed to volume + config directories. It's also a bit unclear whether you need to point the base of ebusd-configuration/ or very specifically to ebus-configuration/2.1.x/ or even ebus-configuration/2.1.x/en
OK, one workaround would be I could manually play with an example config and introduce some obvious falsely named parameter, and see if it loads, but that seems a little risky.
Proposal:-
Simple solution would be if ebusctl info would output the full path/web address of the current config dir, e.g. on a line after update: and before the addresses of masters and slaves.
For example:-
version: ebusd 23.2.23.2
device: /dev/ttyAMA0, enhanced high speed, firmware 1.1[3806].1[3806]
signal: acquired
symbol rate: 80
max symbol rate: 160
...
update: 10
configdir: /custom_ebusd/ # or perhaps https://cfg.ebusd.eu/ if loading from website
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0901;HW=5103", loaded "vaillant/08.hmu.csv"
...
@Tomasonx yes, something like could work well. Or to save on repetition, just show the base folder in the output: config loaded from "/etc/ebusd/config/ebusd-configuration/latest/en/"
@john30 It's very useful to be sure the location of the file that is actually being pulled is the one you intended.
For example:- a specific if you are running ebusd in docker and have made a typo in passing the name of the config variable (EBUSD_CONFIG). In this case, ebusd will silently adopt the default config, and you'd be none the wiser why certain custom configs were not being properly loaded.
(Speaking here from experience of being unable to track down the source of my problem for days...! :-) )
Description
Think this would be a useful added info when testing configurations; apologies if it already exists somewhere and I just haven't found it!
Background:-
Am trying to run ebusd via a docker container, and testing different configs. So far it seems difficult to be sure whether ebusd is continuing to use the default config files, or actually loading the manually pointed to volume + config directories. It's also a bit unclear whether you need to point the base of ebusd-configuration/ or very specifically to ebus-configuration/2.1.x/ or even ebus-configuration/2.1.x/en
OK, one workaround would be I could manually play with an example config and introduce some obvious falsely named parameter, and see if it loads, but that seems a little risky.
Proposal:-
Simple solution would be if
ebusctl info
would output the full path/web address of the current config dir, e.g. on a line after update: and before the addresses of masters and slaves.For example:-
OR provide full path in the address line
The text was updated successfully, but these errors were encountered: