We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could we use a relative path here i.e conf/available.conf instead of hardcoding the path to handle emonhub being installed in a different location?
conf/available.conf
emonhub/src/emonhub_auto_conf.py
Line 49 in f672445
Also, even when autoconf is disabled emonhub still tries to load available.conf
available.conf
The text was updated successfully, but these errors were encountered:
please also see: https://community.openenergymonitor.org/t/mqtt-interfacer-gets-no-data/23097 related to this issue when trying to use emonhub as standalone. Thanks
Sorry, something went wrong.
Could create a symlink from /etc/emonhub/ at install time to point back to where autoconf is and use the /etc/emonhub/ location in the script.
/etc/emonhub/
autoconf
Another instance
https://community.openenergymonitor.org/t/power-outage-and-suddenly-stops-sending-data-to-emoncms/25611/22?u=borpin
No branches or pull requests
Could we use a relative path here i.e
conf/available.conf
instead of hardcoding the path to handle emonhub being installed in a different location?emonhub/src/emonhub_auto_conf.py
Line 49 in f672445
Also, even when autoconf is disabled emonhub still tries to load
available.conf
The text was updated successfully, but these errors were encountered: