Yes this worked before with deconz. Even without the .silent() option. There the script of course was executed several times because the first device that was set triggered the script again. It only stops if all 3 setpoints were the same. For the use with frontend and homebridge etc. the left one is ...

Hello all, I recently migrated from deconz to zigbee2mqtt and I'm right now struggeling with synchronizing my 3 danfoss-popp ally thermostats in the dining room. From time to time my dzvents script creates a endless loop.The setpoint then jumbs from the old to the new value and never settle to one ...

Thanks @waltervl. That did the trick! I have now a nice script that just sends out the external measured temperature to the right topic. Works like a charm. @FlyingDomotic: Yes I know your nice plugin. For now it seems the easier solution to me, to just write a dzvents script that send out the data ...

I'm also trying to publish data a bit more customized, so not under domoticz/out. I'm running domoticz with docker, so I have not easy access to mosquitto_pub, if I'm not wrong!? Is there another solution with dzvents? In my case I try to move my danfoss ally thermostats from deconz to zigbee2mqtt ...

I have a small additional question regarding this topic.
Is there a possibility to change the values inside this setup section with dzvents or something?

Hello, I‘m using the „normal“ mqtt hardware to publish data from a general kWh meter. Is there a possibility to have also the counter today value published? That would be very helpful to not need to calculate this value in a different application again. It seems that only the actual watts and the tot ...

I am using the danfoss ally / popp zigbee thermostats. They are doing a great job.

But the advanced features (eg. external temperature sensors) are not support with deconz right now.

I‘m running into issues with the MQTT AD hardware, zwavejsUI with mosquito. In addition I try to integrate some other devices from iobroker to domoticz via MQTT and the MQTT Mapper plugin. So I have another subscriber that sends with the topic „smartmeter/…/„. Unfortunately when I activate the MQTT i ...

We are doing same for "state/loadestimateonthisradiator" and "config/loadbalancingenable" but I m realy lighter than you for "config/loadradiatorroommean" ^^ What do you mean with that? How your DDF looks like? It was just a quick `n` dirty try and error to build this DDF so I never really ...

Here is my DDF currently in use. Please not that this is for the POPP - Ally Clone.
I needed to rename as .txt to upload here.

I checked your PR without testing it. Sorry no time atm. :roll: But I think with the config/loadradiatorroommean you did a copy paste mistake. It is not Boolean, it should be a int16 and the description doesn’t fit properly. But all addresses seems to be good. In addition it seems that this value h ...

I will see if I can test the code as soon as possible, but I need some time I think. If I‘m not wrong I haven’t set a refresh interval. It is then the default if there is a default. I can share my DDF when I tested the code. Why always asking what to do with such value? :lol: I‘m a little bit nerdy a ...

But making a small PR with only 1 field have more chance to be valided, if I have understand you need "state/LoadEstimateOnThisRadiator" ? Yes, this would be the one which I now catch with the PM2.5. But currently I also use - config/duration , which could be config/LoadRadiatorRoomMean and ...

This one: https://www.domoticz.com/forum/viewtopic.php?t=40131 I faced some issues when I played around with the MqttMapper plugin. Domoticz version 2023.1 stable - Python Version: 3.7.3 Issue: The typ of my other python plugins changed to MqttMapper and the settings aren't available. (DeCONZ - idx ...

Thanks! It is working now. Very nice.

Just the problem with the changing hardware type to fix.

Yeah, software is moving, it’s totally okay. :lol: I just want to understand why the update broke the temperature readings with my DDF. I understood that the issue appear because the pm2.5 is now supported. Why the temperature value is replaced by the pm2.5? How is the API state linked to the d ...

But why the plugin takes now the pm2.5 and not the temperature anymore and the value seems not to be divided at all? Is the plugin just locking for the 5th state attribute? Can you may give me a hint in which line in the python script I can find this, so I can have a look by myself? I‘m using this p ...

In fact I don‘t really know if it appears just with the domoticz update or I‘ve updated also the plug-in. :roll: But for testing I set up a second Testsystem with the newest versions and only deconz plugin as hardware with same results. Very good hint to check the API. I have the issue only on the TR ...

You're right. As of now, multiplier is only applied when value to set is numeric (loaded in nValue). Here, we're loading a string with 2 numerical value. This clearly is a bug on my side ;-) It has been fixed in 1.0.10. Thanks for your feedback! Thanks for the fast modification, but sorry the ...

With update to domoticz 2023.1 the temperature readings of danfoss ally thermostats are incorrect.
Python Version: 3.7.3 (default, Oct 31 2022, 14:04:00) [GCC 8.3.0]

The are the room tempature reading from the thermostat and not the setpoint value. In phoscon the value are correct.