You do not need bookworm on your pi to run a domoticz docker with bookworm.

Bookworm is not necessarily old. Installing trixy which is still being heavily developed is not the OS I would advise if being used on a production domotica system. I learned the hard way.

Remember to do full upgrades on trixy because dependencies change and expect problems if you don't.

I use a ...

Do you use docker? Because if you do, the latest dockers run bookworm.

Use docker and a lite version if you are not going to use the desktop. I would go for bookworm and not trixy.

Install the new pi, test it and finally swap them.

Also test the usb devices.

Just for your information, it is mentioned in the announcement of 2025.2 on the forum.

That is a known issue. But I always scroll through the release notes on the forum. And never updated through the gui.

The .ssh is to be able to execute a shell command from within the container in the host. I use it to have domoticz send a wake on lan packet to my mini pc. Configurated innsuchba way it is the only thing the container can do via dsh. This to make sure any security issue with domoticz can not easily ...

This is my docker-compose.yml

services:
domoticz:
#image: domoticz/domoticz:161125
image: domoticz/domoticz:051225
container_name: domoticz
init: true
restart: unless-stopped
# Pass devices to container
devices:
- /dev/ttyUSB-RFXcom:/dev/ttyUSB-RFXcom
ports:
- "8080:8080"
# - "443:443 ...

async is the problem in this case, in combination with docker.

I will never go to dzvents because of different reasons. I started lua before dzvents and solved the multiple lua scripts issue just before dzvents started. Dzvents is propably easier to start with without programming experience.

But ...

Please learn, it is needed in some cases. For instance when you use os.execute in lua to start processes. Due to docker functionality you may get defunct processes that cause a container to crash eventually. Defunct processes can be checked by logging into a container and issue a ´'ps -ef´. So in my ...

Because of a lot of defunct processes in my Domoticz docker, I added
init: true
to my docker-compose.yml. The line takes care of cleaning defunct proces and starts an initd (as I read) and takes care of a lot of things to let software inside a container.

Besides that I have not seen any errors ...

Shouldn't the error in that case not occur always instead of occasionally?

The plugin gives an occasional error since I use it.

The thing is the Solaredge Modbus TCP seems not to be real actively maintained.

I plan to look into that, but that will take some time before I have ehm time.

What I sometimes see is that shortly after modbus has an issue also the Solaredge API ...

Read the wiki about building Domoticz yourself, following the steps did it for me. I use it for testing changes before creating a pull request.

On a Pi 4 it should work quick enough. First time on a PI 3 took some time. Almost an hour I think.

Most likely you did and apt update/upgrade which disabled the plaintext ssh login.

Login via the console and google how to fix the ssh_config

Search for:
# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes


So PasswordAuthentication should be yes for clear ...

40% seems high on a pi 5. On average on my pi 3b O se around 20% docker for Domoticz, Mosquitto and Zwave

thanks Walter, while checking I came to the mqtt part which I overlooked
Soo fixed, the mqtt-part settings still hold localhost setting iso 192.168.2.100


Localhost inside a docker container is the docker container itself.

Hosturl in the zwave container for the MQTT server should most likely be ...

Looks like a problem with the USB stick. What does de webinterface on port 8091 say?

You know the os relase has to be bookworm?

Did you read the release notes?

I used this:

For the readme.
https://github.com/addiejanssen/domoticz-solaredge-modbustcp-plugin
I use the 2.04 which can be found here (mainy because I have a battery):
https://github.com/addiejanssen/domoticz-solaredge-modbustcp-plugin/tags

Login to the container with:
docker exec -it ...