Domoticz

For years I got data from solaredge via API.
Now it does not work anymore.
After consulting my supplier I got a new API.
Also this one did not solve my problem.
Makes this sense to someone?

Bart

You're right! Since 2 days it does not work, hoping the solaredge hardware can be fixed soon.
In the meanwhile, I suggest to install the domoticz-solaredge-modbustcp-plugin that permits you to fetch data directly from the inverter every 10s or less. API permits to get data every 5 minutes.

Thanks for your message. I read about the plugin. I never used any plugin. Is it just installing a plugin or does this also require any setting in the solaredge converter?

BartSr wrote: Thursday 11 December 2025 15:14 Thanks for your message. I read about the plugin. I never used any plugin. Is it just instaaling a plugin or does this also require any setting in the solaredge converter?

You just need to install the plugin, no need to configure the inverter. It uses ModbusTCP protocol to fetch data from the inverter.

trying to install the plugin but get next error

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.

original container with domoticz is running also once the container has been started it seems something hangs
now I get stuck

FYI: https://wiki.domoticz.com/SolarEdge#Usi ... e_inverter

After following the plugin install I got stuck on the error showed before

If you run a plugin in Domoticz in Docker you should install the plugin required modules in the docker container.....
See wiki https://wiki.domoticz.com/Docker#Python_Plugins

So use the following command to get into the container Then use the plugin install commands to install the python modules.
Something like below from the location where your plugin folder is within the container (not the same locations as in your system!) And also add this command to the custom startup script (customstart.sh) to be sure the required python modules are reinstalled when you update the docker image.

That is a way. But also check customstart.sh to automate this when a new container is released.

Thanks Walter. For my understanding:
The folder plugins is now outside the container. Do I unserstand you right this must moved into the container? If so? The container launches just afaik domoticz and config folder. I once went jnto the container for another reason. So I understand how to. It's a bit weird to me what to do where and how. But that must be my shortcoming.

For zwave2mqtt there's a very clear instruction how to get thaf up and running. Might if be possible to get in the wiki something similar for plugins?
Bart

Welcome to the docker confusion....
In your docker-compose.yml you have something like After starting domoticz in docker for the first time Domoticz will create a plugins folder in the docker container in /opt/domoticz/userdata/plugins.

Depending on your docker-compose file location this will end up in your host system in So you can copy or use git to put the plugin py files in <docker-compose-file-location>/config/plugins/<yourpluginfolder>
Then go inside the docker and run the python module install files on /opt/domoticz/userdata/plugins/<yourpluginfolder>

I am sorry, I cannot make it easier.....

And also make sure you put the python module install commands in the customstart.sh file else you have to do the install again after you have updated your Domoticz container to a new stable (or beta) version. The normal plugin files will remain on your host system in <docker-compose-file-location>/config/plugin/<yourpluginfolder> so do not need to be reinstalled.

jannl wrote: Thursday 11 December 2025 22:00 That is a way. ....

Is there another way with current venv environments on bookworm and later? I would be happy to know. The Domoticz container is already configured as a venv so inside the docker there are no special things to do other than installing the modules...

I started to understand until this popped up

And also make sure you put the python module install commands in the customstart.sh file else you have to do the install again after you have updated your Domoticz container to a new stable (or beta) version.

Never ever had a need to do something with a file called customstart.sh

That customstart.sh file you need if you need to install something in the container. It could also be you use a linux command like wget that is not installed yet in the container. It is a very simple box so then you have to extra install that command in the container.

You can decide to not use customstart.sh but then you have to reinstall these things if you update your container.....

waltervl wrote: Thursday 11 December 2025 22:42

jannl wrote: Thursday 11 December 2025 22:00 That is a way. ....

Is there another way with current venv environments on bookworm and later? I would be happy to know. The Domoticz container is already configured as a venv so inside the docker there are no special things to do other than installing the modules...

Another way compared to doing it manually.

On my pi 3b it takes around 10 minutes to finish customstar.sh

@jannl no idea what to do in my setup

Read this: https://github.com/addiejanssen/domotic ... tcp-plugin
Check via tags the 2.04 version

And also read this: viewtopic.php?t=40917

That should be a good start. jvdz created a fork from Addie's branch, also the 2.04.

To install things not standard in the docker container, you can install it manually every time the container gets a fresh start, or use customstart.sh.
Explained here: https://wiki.domoticz.com/Docker

I copied the plugin in the system's plugin map (not inside the container) as I expects it will be copied into the container.
Then when I take a look inside the container in the plugins map I don's see the solaredge plugin.
pls don't blame me for this is my first plugin ever. And there should also be done somewhat with git.

This is what I see: What's AwoxSMP ?
Should I create a customstart.sh outside the container and if yes , where?

I have Domoticz 2024.7 running on a pi and was using the SolarEdge via Web API without any problem but since a while it is throwing errors in the log.
Example:
2025-12-17 09:55:12.943 Error: Home Solar: Error getting http data (Equipment details)!
2025-12-17 09:55:13.290 Error: Home Solar: Error getting http data (currentPowerFlow details)!
2025-12-17 10:00:13.671 Error: Home Solar: Error getting http data (Equipment details)!
2025-12-17 10:00:14.026 Error: Home Solar: Error getting http data (currentPowerFlow details)!
2025-12-17 10:05:14.383 Error: Home Solar: Error getting http data (Equipment details)!
2025-12-17 10:05:14.733 Error: Home Solar: Error getting http data (currentPowerFlow details)!
2025-12-17 10:10:15.106 Error: Home Solar: Error getting http data (Equipment details)!
2025-12-17 10:10:15.452 Error: Home Solar: Error getting http data (currentPowerFlow details)!
End Example:
They don't show up all the time but every day at different starting times and exist for about an hour. All normal data is showing up in Domoticz.
anybody any idea what is going on?

I see that sometimes it works, sometimes it doesn't work.
I've got no data on 10, 14 and 15 December. Today it works here.