Did you run updatebeta twice, and did that solve the issue?

The angular changes take quite some time, and because the rendering is completely different, some small details could be overlooked.
The idea is that nobody will notice the difference, or at least not missing anything.
For this reason I might do a new stable release first...

There have been quite ...

Should be solved now by upgrading to the latest beta.

The build servers had to be adjusted because of a big (&$!@) change by mosquitto's CMake project.

Domoticz is now also using a new external library (libmosquitto1) that is installed by the updatebeta/updaterelease scripts (assuming you are on ...

Thank you for this plugin!

This device connects to a standard P1 meter?

Why not use a USB to P1 cable? or use the Network to P1 meter devices?

With this you can use the default native implementation

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

Another option, use the web gui. Click on your P1 meter, at the top click 'Report', then click on the right month to see a report by day
You ask for yearly data, so you get a year.. you can also query for the last month, has less values

With 'Set Right' you mean, it is not checked (= disabled) ?

I am quite sure that all your other devices work correctly, so what device is not working?

I have given a link above to our wiki, you need to create a github issue and provide all details otherwise we are not able to help

(config topic ...

Sorry about this.

I moved two variables (I thought) in the right scope

void CEventSystem::EventQueueThread()

Seems the vector is used differently perhaps.

Version 17056 should solve the issue, could you check this?

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

Yes, you need to be on the last beta to have the web update working again.
So it could you need to use the manual method one more time

No issues here, and the code has been stale for quite some time.
Best to report this issue in GitHub.
Also see our wiki for how to report MQTT-AD issues (topics payloads)

Also make sure you have the latest version of Zigbee2MQTT and don't get other devices for your switches/dimmers
There has been ...

Thank you for the script.

Maybe you can explain a bit more what it does? Screenshots, and why we need it?

If it has a blinking LED... maybe you can use a YouLess

https://www.youless.nl/hoewerkt.html

But a simple ESP with LED detection might also work

Settings is fixed in latest beta. Thanks for spotting!

Looking great!

Did you compile Domoticz yourself before?

This because by default support for Telldus is not available (See CMakeList.txt)

If you own a RFXTrx433, I would suggest to have a look at a 433Mhz Temp+Hum+Baro meter, or buy a Zigbee THB sensor.
Both are not expensive.

If it is still visible under the supported hardware dropdown list, it should still be supported.

The TE923 (as well as a certain Voltcraft CO2 sensor) uses a ...

In beta 17003 I now always force Domoticz to stop.
This should hopefully solve the problem, but this can only be testen when there is a new update...

And again, it is deprecated and you need to move to ZWaveJS-UI, it's 2026, OZW is dead for some years, maybe migrate this year?

That is crazy! That might be half of the price you pay for all your water in a year.
So forget this, and use a proximity sensor with an ESP32, that is how I track my water until there is one installed that works with the P1 meter

You can have a look at my attempt here

https://github.com/gizmocuz ...