Last update:
Last night we went back to our domoticz test container and let it work for a night.
It seems that z2m is working again, so no issues for that anymore.
( i recreated the z2m and domoticz container after the domoticz update, and that seems to work)
The heospy script is working correctly ...

I think Zigbee2MQTT has nothing to do with a python version, both run in a separate docker !?

Could you try the latest docker, I forced it to python 3.11 again, please log into you docker with

You might want to run this before updating your docker to be sure it is downloading it (as it has the ...

Okay... There is more:
We using a lot of scripts (i think that also depends on python 3.11?)
- Lightning script that isnt function 100% anymore, some lights stay off while others turn on by (motion), very weird
- Midea script not working anymore
- Heospy (like said before)
- Solaredge api gives ...

Just to be clear, the domoticz docker never had python 3.15, but was upgraded from 3.11 (bookwork) to 3.13 (trixie)

The reason for this was because of zigpy, which is used by https://github.com/zigbeefordomoticz/Domoticz-Zigbee.

Sure we can revert to 3.11, but this has absolutely nothing to do ...

Ok so it is an issue for the telnet lib...
Did you try ttelnetlib3? As that is the proposed successor according Python https://docs.python.org/3/library/telnetlib.html

telnetlib — Telnet client
Deprecated since version 3.11, removed in version 3.13.

This module is no longer part of the Python ...

Okay, i fixed the telnetlib by installing the in the startup of the container.
Still not everything work. Some scripts like midea / solaredge still have its troubles and are not function with python v3.13.5.

On your search, will Python 3.13 work for the plugins? As that is the standard for Trixie.

No it is also not working unfortunately.
I tried to downgrade and update the python, but it isnt working. It could not found the telnet libs. Last version with this lib was 3.11, all versions after the 3 ...

Hi,

since we yesterday updated our server with domoticz (and all other containers) a lot of our plugins are not working anymore.
After some lookaround it has to do with the new python version.
It always was 3.11 and that worked perfectly for years, but after updating to the last version of domoticz ...

waltervl wrote: Friday 21 November 2025 18:42 And the nocache option was added in the code in 2023 but not documented in the wiki, now it is....

Great! Thats why i couldnt find..
Thanks both, have a good weekend

I was hoping it was that easy, but:


It is, but is the "-no-cache" a valid parameter? This is what the wiki states: https://wiki.domoticz.com/Command_line_parameters.
Isn't the "-no-cache" a parameter for your browser on your the computer?

Ah, now its working with this environment:
- EXTRA ...

I was hoping it was that easy, but:


It is, but is the "-no-cache" a valid parameter? This is what the wiki states: https://wiki.domoticz.com/Command_line_parameters.
Isn't the "-no-cache" a parameter for your browser on your the computer?

No, Domoticz has an no-cache command line parameter ...

Docker/docker compose is the same thing, just a different way to configure the stack/Container, like you do with portainer. :D

I was hoping it was that easy, but:
environment:
- TZ=Europe/Amsterdam
- WWW_PORT=80
- SSL_PORT=0
- loglevel=error
- EXTRA_CMD_ARG=--no-cache
is not working ...

jvdz wrote: Thursday 20 November 2025 20:23 You mean the parameters you can define for env variable EXTRA_CMD_ARG? Just check the docker wiki page.

Nice answer, i'll Check. Thanks!

Its for Docker, not Docker compose?

Hi all,

i do not want to use the cache function of domoticz at all, but i can't find a way to disable this.
I'm using domoticz from docker compose (portainer).

thanks!

I created an issue on github, thanks Walter and Gizmo!

But you forgot to add the requested data in the issue: https://github.com/domoticz/domoticz/issues/6353


Could you please take a look into the last reply?
Is it what you looking for, otherwise can you tell me what exactly do you need to ...

I created an issue on github, thanks Walter and Gizmo!

Hi all,

i'm seeing this error messages in my log from the mqtt auto discovery since a couple of weeks.:

2025-06-14 16:47:34.812 Error: MQTT-AD: Climate device invalid/unknown preset_mode received! (ESPclimateairco3: none)
2025-06-14 16:47:35.629 Error: MQTT-AD: Climate device invalid/unknown ...

Already fixed. Used an external docker with sshpass in it and mount the local to remote port.
It worked.
Anyway, atm im using vpn with WireGuard since i could also connect trough my local dns and do network things from outside.

Hello everybody, does someone know how to do autossh with sshpass inside docker/customstart script?
I used an autossh with sshpass from local.rc before that made a connection to my remote VPS so i could connect domoticz behind NATs firewalls, but that is not working in my domoticz docker, and is the ...