Page 6 of 8
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 18 June 2025 14:22
by jvdz
Did some GITHUB Branches cleanup and updated this in the first post at the bottom:
There are currently 3 Branches:
Original Master (v1.2.3) updated with the active_power_limit Dimmer&Sync option:
https://github.com/jvanderzande/domotic ... tcp-plugin
Original METERS (v2.0.4) updated with the active_power_limit Dimmer&Sync option:
https://github.com/jvanderzande/domotic ... ree/meters
Development based on my meters branch using the latest solaredge_modbus and Selector Switches for Battery modes:
https://github.com/jvanderzande/domotic ... /MetersDev
Documentation still needs work, but that will happen too someday when development is done.
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 18 June 2025 19:14
by jannl
Anyone did any checks on the net solarpower? The modbua valua is the AC value, as soon as the battery is being charges the value does not add up. Compare it to the value in the app (but remember it is a lot slower).
For now I use a lua script based on the battery being charged or not, the meter values ans the ev charger power for which I now have a very small plugin that only reads 1 modbua value from the charger.
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 18 June 2025 20:38
by imautohuttraeger
jannl wrote: Wednesday 18 June 2025 19:14
Anyone did any checks on the net solarpower? The modbua valua is the AC value, as soon as the battery is being charges the value does not add up. Compare it to the value in the app (but remember it is a lot slower).
For now I use a lua script based on the battery being charged or not, the meter values ans the ev charger power for which I now have a very small plugin that only reads 1 modbua value from the charger.
That's why getting these two devices would be excellent to have:
Pure solar production (not the net value)
Pure battery charge / discharge
Unfortunately I can't test it currently (traveling).
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 18 June 2025 20:52
by jannl
I can and the pure solar productuon is not a modbus value. So as ling as youbdon't charge a battery it is not problem.
Re: SolarEdge production throttling from Domoticz
Posted: Saturday 21 June 2025 22:55
by imautohuttraeger
Will soon be back from traveling on the job. So I hope to find some time next week to install and test. Is MetersDev the correct branch to take? Can I install it in parallel or will it overwrite the existing Hardware in Domoticz? Do I have to observe anything on top of the original instructions on Github?
Sorry, I am not really savy with it ...
Re: SolarEdge production throttling from Domoticz
Posted: Sunday 22 June 2025 10:28
by jvdz
Just have a look at my first post in this thread which is updated with the latest Status.
I don't know if you can run multiple instances of the plugin on your setup, but i couldn't and had to add any extra docker container that performs the role of modbus proxy after which i can run multiple.
For each change you will have to Perform the pip command to update the docker with the requirement.txt content.
I have added the required command to customstart.sh :
Code: Select all
pip3 install -r /opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/requirements.txt
so it is done with each creation of the domoticz container.
I am hoping that somebody with an battery installation can give me some feedback on the MetersDev branch whether or not those Selector switched work and are usefull.
Re: SolarEdge production throttling from Domoticz
Posted: Tuesday 01 July 2025 21:19
by imautohuttraeger
Sorry, that i took so long. Finally now I have de-installed the current master and installed the MetersDev Branch. There are more devices now including the dimmer switch - see Screenshot. But there is no batterie.
Do I use the correct versions?
Name: solaredge-modbus
Version: 0.8.0
Name: pymodbus
Version: 3.6.9
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 02 July 2025 9:15
by jvdz
You will have to change the logging to debug and then save the hardware which will restart the plugin. A lot of messages will capture in the domoticz log. Please send that log to my email address and then change the logging back to normal.
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 02 July 2025 16:20
by imautohuttraeger
jvdz wrote: Wednesday 02 July 2025 9:15
You will have to change the logging to debug and then save the hardware which will restart the plugin. A lot of messages will capture in the domoticz log. Please send that log to my email address and then change the logging back to normal.
Just have sent you a PM with the log data (don't know your email).
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 10:33
by 1kke
In docker Domoticz :latest and :beta
(Version: 2025.1 (build 16758) Build Hash: 79e16c172) the plugin doesn't run anymore:
Code: Select all
2025-08-13 10:27:06.803 Error: Inverter: (SolarEdge_ModbusTCP) failed to load 'plugin.py', Python Path used was '/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/:/usr/lib/python311.zip:/usr/lib/python3.11:/usr/lib/python3.11/lib-dynload:/opt/venv/lib/python3.11/site-packages:/opt/venv/local/lib/python3.11/dist-packages:/opt/venv/lib/python3/dist-packages:/opt/venv/lib/python3.11/dist-packages'.
2025-08-13 10:27:07.012 Error: Inverter: Traceback (most recent call last):
2025-08-13 10:27:07.012 Error: Inverter: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/plugin.py", line 60, in <module>
2025-08-13 10:27:07.012 Error: Inverter: import solaredge_modbus
2025-08-13 10:27:07.012 Error: Inverter: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/solaredge_modbus/__init__.py", line 6, in <module>
2025-08-13 10:27:07.012 Error: Inverter: from pymodbus.constants import Endian
2025-08-13 10:27:07.012 Error: Inverter: ModuleNotFoundError: No module named 'pymodbus'
With :2025-beta.16756 the plugin runs again normally.
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 10:41
by eddieb
Yeah, same here on my docker based system
Code: Select all
2025-08-07 11:25:05.067 Error: Solaredge: Call to function 'onHeartbeat' failed, exception details:
2025-08-07 11:25:05.076 Error: Solaredge: Traceback (most recent call last):
2025-08-07 11:25:05.076 Error: Solaredge: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/plugin.py", line 928, in onHeartbeat
2025-08-07 11:25:05.076 Error: Solaredge: _plugin.onHeartbeat()
2025-08-07 11:25:05.076 Error: Solaredge: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/plugin.py", line 279, in onHeartbeat
2025-08-07 11:25:05.076 Error: Solaredge: self.processValues(device_details, values)
2025-08-07 11:25:05.076 Error: Solaredge: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/plugin.py", line 316, in processValues
2025-08-07 11:25:05.076 Error: Solaredge: value = self.getUnitValue(unit, inverter_data)
2025-08-07 11:25:05.076 Error: Solaredge: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-08-07 11:25:05.076 Error: Solaredge: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/plugin.py", line 406, in getUnitValue
2025-08-07 11:25:05.076 Error: Solaredge: value = inverter_data[row[Column.MODBUSNAME]]
2025-08-07 11:25:05.076 Error: Solaredge: ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
2025-08-07 11:25:05.076 Error: Solaredge: KeyError: 'status'
2025-08-12 22:16:57.210 Error: Solaredge: (SolarEdge_ModbusTCP) failed to load 'plugin.py', Python Path used was '/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/:/usr/lib/python311.zip:/usr/lib/python3.11:/usr/lib/python3.11/lib-dynload:/opt/venv/lib/python3.11/site-packages:/opt/venv/local/lib/python3.11/dist-packages:/opt/venv/lib/python3/dist-packages:/opt/venv/lib/python3.11/dist-packages'.
2025-08-12 22:16:57.408 Error: Solaredge: Traceback (most recent call last):
2025-08-12 22:16:57.408 Error: Solaredge: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/plugin.py", line 60, in <module>
2025-08-12 22:16:57.408 Error: Solaredge: import solaredge_modbus
2025-08-12 22:16:57.408 Error: Solaredge: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/solaredge_modbus/__init__.py", line 6, in <module>
2025-08-12 22:16:57.408 Error: Solaredge: from pymodbus.constants import Endian
2025-08-12 22:16:57.408 Error: Solaredge: ModuleNotFoundError: No module named 'pymodbus'
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 10:43
by jvdz
What is returned when you run this command via customstart.sh?:
Code: Select all
pip3 install -r /opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/requirements.txt
This should install the required modules.
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 10:48
by 1kke
I think it has to do with:
gizmocuz wrote: Tuesday 12 August 2025 16:20
Could you update to the latest docker to see if that solved the issue?
The build system is now using a schroot bookwork build environment (it was updated to Trixy)
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 10:50
by 1kke
jvdz wrote: Wednesday 13 August 2025 10:43
What is returned when you run this command via customstart.sh?:
Code: Select all
pip3 install -r /opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/requirements.txt
This should install the required modules.
Code: Select all
Launch: Running customstart.sh
domoticz | /opt/venv/bin/python: error while loading shared libraries: libpython3.13.so.1.0: cannot open shared object file: No such file or directory
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 10:57
by 1kke
I think those images have a corrupt venv so only @gizmocuz could solve this I think.
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 11:20
by eddieb
These are the errors I get on stop/start domoticz docker
Code: Select all
2025-08-13 11:19:37.975 Error: Solaredge: (SolarEdge_ModbusTCP) failed to load 'plugin.py', Python Path used was '/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/:/usr/lib/python311.zip:/usr/lib/python3.11:/usr/lib/python3.11/lib-dynload:/opt/venv/lib/python3.11/site-packages:/opt/venv/local/lib/python3.11/dist-packages:/opt/venv/lib/python3/dist-packages:/opt/venv/lib/python3.11/dist-packages'.
2025-08-13 11:19:38.020 Error: Solaredge: Traceback (most recent call last):
2025-08-13 11:19:38.020 Error: Solaredge: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/plugin.py", line 60, in <module>
2025-08-13 11:19:38.020 Error: Solaredge: import solaredge_modbus
2025-08-13 11:19:38.020 Error: Solaredge: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/solaredge_modbus/__init__.py", line 6, in <module>
2025-08-13 11:19:38.020 Error: Solaredge: from pymodbus.constants import Endian
2025-08-13 11:19:38.020 Error: Solaredge: ModuleNotFoundError: No module named 'pymodbus'
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 11:28
by eddieb
and this is the error while inside the container trying to upgrade requirements
Code: Select all
python3 -m pip install -r requirements.txt --upgrade
python3: error while loading shared libraries: libpython3.13.so.1.0: cannot open shared object file: No such file or directory
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 12:06
by 1kke
I think libpython3.13 indicates a python3.13 venv while python3.11 is installed in the image.
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 12:39
by gizmocuz
This is quite odd as there is no reference to 3.11 in the Dockerfile... 3.13 should be installed
Re: SolarEdge production throttling from Domoticz
Posted: Wednesday 13 August 2025 12:44
by eddieb
I just did an apt upgrade on the rpi5 and my system still says
Code: Select all
root@domoticz2:/opt/stacks/domoticz/config# python3 -V
Python 3.11.2
Code: Select all
# apt info python3
Package: python3
Version: 3.11.2-1+b1
Priority: optional
Section: python
Source: python3-defaults (3.11.2-1)
Maintainer: Matthias Klose <[email protected]>
Installed-Size: 82.9 kB
Provides: python3-profiler, python3-supported-max (= 3.11), python3-supported-min (= 3.11)
Pre-Depends: python3-minimal (= 3.11.2-1+b1)
Depends: python3.11 (>= 3.11.2-1~), libpython3-stdlib (= 3.11.2-1+b1)
Suggests: python3-doc (>= 3.11.2-1+b1), python3-tk (>= 3.11.2-1~), python3-venv (>= 3.11.2-1+b1)
Replaces: python3-minimal (<< 3.1.2-2)
Homepage: https://www.python.org/
Tag: devel::interpreter, devel::lang:python, devel::library,
implemented-in::c, implemented-in::python, role::devel-lib,
role::program, role::shared-lib
Download-Size: 26.3 kB
APT-Manual-Installed: no
APT-Sources: http://deb.debian.org/debian bookworm/main arm64 Packages
Description: interactive high-level object-oriented language (default python3 version)
Python, the high-level, interactive object oriented language,
includes an extensive class library with lots of goodies for
network programming, system administration, sounds and graphics.
.
This package is a dependency package, which depends on Debian's default
Python 3 version (currently v3.11).