SolarEdge production throttling from Domoticz

[1kke]

This is quite odd as there is no reference to 3.11 in the Dockerfile... 3.13 should be installed

This is what I find in the container (:beta):

sh-5.2# cd /usr/lib
sh-5.2# ls
apt dpkg git-core init locale lsb mime os-release python3.11 sasl2 ssl systemd terminfo tmpfiles.d udev x86_64-linux-gnu+

[gizmocuz]

Could you try the new docker version? Went back to Python 3.11-slim image

[eddieb]

It works again with the new image

[1kke]

yes, pulled the :beta again (Version: 2025.1 (build 16758)
Build Hash: 79e16c172) and it's working for me also.

[gizmocuz]

Thanks for the feedback! Aldo I am happy about this... It is strange that when using the Docker image python:slim (which uses python 3.13) it does not work...

[eddieb]

tnx for fixing this @gizmocuz

[1kke]

Weird thing is, I've build the image locally:

Code: Select all

git clone https://github.com/domoticz/domoticz-docker.git
cd domoticz-docker 
changed the Dockerfile:
FROM python:slim
and libpython3.9-dev to libpython3.13-dev
docker build -t domoticz:local . 

and everything is running fine:

Code: Select all

# ls /usr/local/bin
docker-entrypoint.sh  idle3	normalizer  pip3     pydoc   pydoc3.13	       pymodbus.server	   pyserial-miniterm  python	     python3	     python3.13
idle		      idle3.13	pip	    pip3.13  pydoc3  pymodbus.console  pymodbus.simulator  pyserial-ports     python-config  python3-config  python3.13-config
# 

[eddieb]

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.

I just today bumped on the 2 pollers to 1 modbus...
Can you share the docker compose yml for docker proxy ? The stuff I found does not work

[jvdz]

Think it was pretty strait forward to get it to work for me.
This is what I use currently:
IPaddresses:

Code: Select all

SolarEdge                 : 192.168.0.10
Host Docker Domoticz&proxy: 192.168.0.20

------------------------------------------
Docker modbusproxyYAML
------------------------------------------

Code: Select all

services:
  modbusproxy:
    image: modbus-proxy:latest
    container_name: modbusproxy
    restart: unless-stopped
    ports:
      - 5020:502
    volumes:
      - /data/docker/modbusproxy/modbus-proxy.yml:/config/modbus-proxy.yml

------------------------------------------
File: /data/docker/modbusproxy/modbus-proxy.yml
------------------------------------------

Code: Select all

devices:
- modbus:
    url: 192.168.0.10:502
  listen:
    bind: 0:502

------------------------------------------
Domoticz SOLAREDGEMODBUS PLUGIN setting:
------------------------------------------

Code: Select all

Inverter IP Address:192.168.0.20
Inverter Port Number: 5020

[eddieb]

needed to modify the compose.yaml a bit to run in dockge on my rpi5

Code: Select all

services:
  modbusproxy:
    build: https://github.com/tiagocoutinho/modbus-proxy.git
    container_name: modbusproxy
    restart: unless-stopped
    ports:
      - 1502:1502
    volumes:
      - /opt/stacks/modbusproxy/:/config/
networks: {}

seems to run, going to test now

[michealabroy]

You can monitor SolarEdge production in Domoticz, but throttling (limiting output) usually isn't supported directly. It depends on your inverter and API access.

[eddieb]

the above compose.yaml for dockge works on rpi5

I am using the modbus-proxy.yml below to test

Code: Select all

devices:
- modbus:
    url: 192.168.0.10:1502
  listen:
    bind: 0:1502
logging:
  version: 1
  formatters:
    standard:
      format: "%(asctime)s %(levelname)8s %(name)s: %(message)s"
  handlers:
    console:
      class: logging.StreamHandler
      formatter: standard
  root:
    handlers: ['console']
    level: DEBUG
~

[jvdz]

You can monitor SolarEdge production in Domoticz, but throttling (limiting output) usually isn't supported directly. It depends on your inverter and API access.

It should work with this version of the plugin or are you having issues? It is not using the local web/api but the modbus interface of the solaredge inverter.

[hjzwiers]

I replaced the old version 'domoticz-solaredge-modbustcp-plugin.2.0.4' with the new version 'domoticz-solaredge-modbustcp-plugin-MetersDev' ran the requirements file but now I think I have new versions of the devices in the overview, how do I recognize the old version so I can delete them?

I have an 3 phase inverter with 23 kw batteries and was seeing some errors concerning the metering, so I though why run the newer version.

Anyone have this problem?

[waltervl]

The ones not being updated anymore are the old ones. Should be noticable on the last seen date being old.

[hjzwiers]

I deleted them all and add to the devices through a restart and the hardware switch.

[hjzwiers]

I still get errors with the meters, its once a day. I have no idea where it is coming from:

2025-10-12 20:51:25.902 Error: SolarEdge ModbusTCP: Call to function 'onHeartbeat' failed, exception details:
2025-10-12 20:51:25.903 Error: SolarEdge ModbusTCP: Traceback (most recent call last):
2025-10-12 20:51:25.903 Error: SolarEdge ModbusTCP: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin-MetersDev/plugin.py", line 928, in onHeartbeat
2025-10-12 20:51:25.903 Error: SolarEdge ModbusTCP: _plugin.onHeartbeat()
2025-10-12 20:51:25.903 Error: SolarEdge ModbusTCP: File "/opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin-MetersDev/plugin.py", line 258, in onHeartbeat
2025-10-12 20:51:25.903 Error: SolarEdge ModbusTCP: meter = self.inverter.meters()[device_name]
2025-10-12 20:51:25.903 Error: SolarEdge ModbusTCP: ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
2025-10-12 20:51:25.903 Error: SolarEdge ModbusTCP: KeyError: 'Meter1'
2025-10-12 21:52:50.270 Error: Getting error 'Transport endpoint is not connected' while getting remote_endpoint in connection::start

After the error the system just goes on as usual

[jvdz]

I will have a look tomorrow to see what it could be. Assume you have a battery as it is trying to work with the meters info?

[hjzwiers]

Yes i have a SE10K inverter with 5 battery units and a SolarEdge meter in the electrical cabinet, I appreciate the help. i am running: domoticz-solaredge-modbustcp-plugin-MetersDev, and requirements.txt is run from within docker (and in the customstart.sh).

I just ran this version due to the newer files for the meters, which functionality does it have which is newer?

[jannl]

I think I have a similar issue with the 'original' plugin. I realized it can have something to do with the timing settings in the hardware tab.

Not tested yet