Domoticz

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, the Python is 3.15.
That seems the issue.
Also some libs are not working anymore as wel, like the midea aircon plugin.

Please fix this.

For no we reverted back to 2025-beta.17005, that seems to be the last working version.

Thanks

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

waltervl wrote: Friday 23 January 2026 15:47 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.11 version has removed the telnet lib.
I tried 3.15 and 3.13 but none of them worked.
3.11 is not possible to install in the latest version.
also, one of the plugins with a lot of errors is the plugin of our solaredge (pvpanels) that is giving a lot of errors with the last (python) versions.

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.

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 standard library. It was removed in Python 3.13 after being deprecated in Python 3.11. The removal was decided in PEP 594.

Possible replacements are third-party libraries from PyPI: telnetlib3 or Exscript. These are not supported or maintained by the Python core team.

waltervl wrote: Friday 23 January 2026 16:49 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 standard library. It was removed in Python 3.13 after being deprecated in Python 3.11. The removal was decided in PEP 594.

Possible replacements are third-party libraries from PyPI: telnetlib3 or Exscript. These are not supported or maintained by the Python core team.

thanks for answering, but we are not very satisfied with this last beta version of domoticz..
for us it is not safe to go live with it for now, ofcourse we know its beta
its not only the telnetlib btw, its way more than that.
also a lot of devices from zigbee2mqtt has its issues as well since this update. (dont know the reason)
also struggling with a lot of other not working things, like midea i spoke before. (after the update).
some scripts inside domoticz has issues as well.
we did a revert back to 17005 and everything works again.
atm we stay at version 2025-beta.17005 and will not update since everything again working for sure.
if you need errors/logs, let me know.
Our HomeAssistant (beside domoticz) is working perfect anyway, but that has nothing to do with this domoticz instance (they just share the same devices/mqtt).

I am told next docker beta has python 3.13

And when you update to every beta it would be nice you report the issues you face in more detail. Beta is to test so things can be less functional as expected.

This user also complaints that zigbee2mqtt docker is not responding well after updating to a recent beta in docker. Restarting Domoticz should fix it.
viewtopic.php?p=330995#p330995

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 with Zigbee2MQTT.

If you have issues with Zigbee2MQTT and Domoticz MQTT-AD, this might have been caused by some patches that where done at the end of last year (more then a month ago)

To report MQTT-AD issues, please follow our wiki how to report them on Gibhub:

https://wiki.domoticz.com/MQTT_AD_Report_Problems

gizmocuz wrote: Saturday 24 January 2026 7:59 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 with Zigbee2MQTT.

If you have issues with Zigbee2MQTT and Domoticz MQTT-AD, this might have been caused by some patches that where done at the end of last year (more then a month ago)

To report MQTT-AD issues, please follow our wiki how to report them on Gibhub:

https://wiki.domoticz.com/MQTT_AD_Report_Problems

Sorry for a late reply, i was busy today.
you are right, i had it wrong. excuse me, it was v3.13.5 (and not 3.15 , my bad.. )
I'm struggling with some other scripts as well that depends on this python (3.11) related i guess.
If you need more debugging, pls let me know then i take some more time to find out and will send logs with more detail.
Some things that didnt work:
- Midea plugin had a disfunction
- Heospy wich didnt work (but that could be fixed by installing telnetlib again)
- Solaredge had a lot of errors
- Some zigbee2mqtt that didnt work, but i should test this tomorrow when i have some more time.
If i find more things, will let it know here.

i have made a test-container now wich i'm testing, i come back later.

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 error outputs (something with the api) - Modbus controller (heatpump) did not work at all anymore
For now i did not test further otherwise we have no heating

Back to v17005 did resolve everything.

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 same build number)

docker system prune -af

and after upgrading, check the python version with

docker exec -it domoticz bash

and issue

python --version

It should say 3.11

If this works, I keep it on 3.11 for now... but strange this is giving so much issues.. My only python script (Eastron SDM) is still working wonderful with 3.13

Can you see any errors? is it a library that is not compatible?

gizmocuz wrote: Sunday 25 January 2026 16:43 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 same build number)

docker system prune -af

and after upgrading, check the python version with

docker exec -it domoticz bash

and issue

python --version

It should say 3.11

If this works, I keep it on 3.11 for now... but strange this is giving so much issues.. My only python script (Eastron SDM) is still working wonderful with 3.13

Can you see any errors? is it a library that is not compatible?

Thanks for answering..
Its correctly that z2m is another container, but i think its not z2m itself but the way Domoticz connects with mqtt?
I can see all devices are connected in mqtt, but some (motion devices) didnt came into Domoticz.
I see there is motion detected, but i did not seen it in Domoticz.
Maybe i should give it more time to found out whats happening, but for today its enough.
I'm not using Domoticz from Docker itself, but i use it from portainer (stack), so Docker compose if that will make sense.
I come back with some updates later when i have more time.

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 with the (pip install telnetlib-313-and-up) telnetlib, so thats fine also.
I'm going to invest more time soon to check other logs/errors about missing libraries or dependencies of plugins that not work at this moment.
If i know more, i come back soon!