Thanks.
Maybe I misunderstood my reading up on the emonhub - that it would read from eg modbus over TCP and write to an input and hence a feed. That would be perfect for my local installation (non-pi).
For completeness, I just ran the emonhub.sh installer and the log output is below
-------------------------------------------------------------
BEGIN emonHub install
-------------------------------------------------------------
Cloning into 'emonhub'...
remote: Enumerating objects: 5888, done.
remote: Counting objects: 100% (632/632), done.
remote: Compressing objects: 100% (180/180), done.
remote: Total 5888 (delta 509), reused 490 (delta 443), pack-reused 5256 (from 1)
Receiving objects: 100% (5888/5888), 2.74 MiB | 4.71 MiB/s, done.
Resolving deltas: 100% (4033/4033), done.
EmonHub directory: /opt/openenergymonitor/emonhub
/opt/openenergymonitor/emonhub/install.sh: line 21: cd: 0/EmonScripts/update: No such file or directory
/opt/openenergymonitor/emonhub/install.sh: line 22: load_config.sh: No such file or directory
emonSD_pi_env provided in arg = 0
user provided as arg = pi
installing or updating emonhub dependencies
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package python3-pymodbus
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.12/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.12/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.12/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Creating /etc/emonhub directory
chown: cannot access '/var/log/emonhub': No such file or directory
No existing emonhub.conf configuration file found, installing default
emonhub.conf permissions adjusted to 666
Default emonhub.conf log level set to WARNING
Installing /usr/local/bin/emonhub symlink
Installing emonhub.service in /lib/systemd/system (creating symlink)
Created symlink /etc/systemd/system/emonhub.service → /opt/openenergymonitor/emonhub/service/emonhub.service.
Created symlink /etc/systemd/system/multi-user.target.wants/emonhub.service → /opt/openenergymonitor/emonhub/service/emonhub.service.
Failed to restart emonhub.service: Unit var-log.mount not found.
Failed to restart emonhub.service: Unit var-log.mount not found.
- Service ActiveState=inactive
/opt/openenergymonitor/EmonScripts/sudoers.d/emonhub-sudoers: parsed OK
-- emonhub service control sudoers entry installed
-------------------------------------------------------------
END emonHub install
-------------------------------------------------------------
(The BEGIN and END are mine)
For myself, I decided the shorter path to happiness was to write a couple of quick scripts and cron them so that I can read from my heatpump modbus and a Shelly energy clamp and push them into emoncms via the POST api. Seems to work a treat.
I have other questions, but I’ll find or start a different thread.
Thanks for the help in getting this far!
Miles
