No, the values are directly uploaded in the device. You can make a dummy temperature device for every real temperature sensor and with a dzvents script that can do the filtering or calculations and fill the dummy sensor with the filtered data from your real sensor. For data like temp/hum that does ...

Hi Waltervi, I'm running latest stable. IMO that's not a plugin issue, but a plugin infrastructure issue: Changes to what will be used in hardware setup page, so even before starting the plugin after an update, just can't be managed on plugin side. IMO parsing plugin.py configuration options section ...

Hello, I'm testing some Z4D changes done by Pipiche concerning coordinator setup options. Plugin was updated correctly from test branch, new options in plugin.py are there... But even after a plugin restart from Domoticz hardware tab/cache clear from browser: Impossible to see updated options & even ...

Same for me: Updated from webUI 2 days ago & no issue. Just reloading the already opened webUI page a couple of minutes after restart was triggered (logs showing Z4D restart done) also lead to a blank page but closing the whole domoticz tab & re-opening the Z4D webUI custom page did the trick ...

Same here, I have a text device logging METAR (aviation related meteo information) every half hour that did not show any glitch, updated from Lua. Seems unrelated, but take care "textlog" HTTP/JSON API was deprecated and no more usable: https://wiki.domoticz.com/Domoticz_API/JSON_URL%27s#Warning ...

Hello, no issue as well: All went smoothly for a setup mostly OZW and Z4D based, with my own scripts that were already on par with previous APIs changes.

Thanks a lot for this release!

There are still some fixes in the Domoticz install script to come over the libssl1.1 issue for newer RPi OS's. Thanks for the info! On the update topic, one request you may consider: It's now locked (I presume to keep them clear to read)... But as a result, users feedback for a specific version are ...

Hello, Thanks a lot for this release but as the base topic is locked, not allowing to ask info/give feedback, I create this one with a question: Did not see info about libssl change that was earlier said to be planned for next stable? => Would like to know if this release must be managed in sync ...

Hello,

Did you use the version from domoticz repo?
https://github.com/domoticz/open-zwave

Looks last commit from Kiddigital was exactly about fixing the error you have!

I see your point on Zwave vs Zigbee about the lifecycle (although it will be there long enough so i am not in a hurry yet), but not the complixity. if i'm correct (i am not a zigbee user, so not 100% sure) then Zigbee is also not natively integrated in domoticz, but requires additional plugins ...

Considering the ROI, I tell everyone for now it justs cost money. However, around october (after one year of Tibber and a battery) I hope to prove myself wrong (at least a bit). PV+Battery historically only made sense to provide electricity for buildings in secluded places that could not be linked ...

openzwave is no longer maintained.... It's great that within domoticz you can still use it, but that's just for users to give them more time to migrate to the new version. Looking at the market/what you can shop for, IMO ZWave is dying & Zigbee took the wind, despite better interoperability for ...

I would advise you to buy a new Zigbee Dongle and use the Zigbee4Domoticz plugin. (if you do not want to use Zigbee2MQTT). Saves you a lot of work and frustration.... When I started with Zigbee & Z4D plugin, I wanted to do some replace to keep some existing devices (Zwave using integrated OZW) data ...

Some networks may block non standard ports use... So on my side I always kept default 443 open to the outside: HTTPS is much less attacked than SSH for instance, simply because that's much more valuable asset to get in! As is a VPN, because if someone managed to exploit it that's all your LAN that ...

Maybe the stable should be called LTS 8-) This would mean having to support them for long, so backport fixes from newest betas => More work maintaining 2 branches & you already do a lot... Still believe current approach to label a stable when this makes sense in terms of features addition since ...

As I said hereupper, there is some periods with heavier development/changes. In the past when I used beta because I needed mostly to support new HW or features recently added I always checked if this was smooth period that should be OK to pick a beta. More betas could probably be promoted as stable ...

Not sure droping stables at all is the way to go. Sometimes there is big changes ongoing and for someone not checking github to see if there is no important changes this may be risky. Can accept this when some additions to your system needs those and users testing. Otherwise stability is a strenght ...

homeJLB wrote: ↑Saturday 22 March 2025 9:40 When Netatmo permanently block a App without communication, we can try so much but always fail.

As always, only solution to avoid this kind of issue that almost always occurs (only unknown there is when?) on devices whose manufacturers do not allow 100% local control: Never buy!!!

NvBgm wrote: ↑Friday 14 March 2025 14:00 Aha ofcourse that could be the issue
I wil reconfig my firewall settings and see what it does

You may also see wiki, as there is some fail2ban configurations to handle such domoticz traces to dynamically ban (for some time) the IP addresses responsible for too many connect attempts.

Take care examples are just averaging values not taking into account the time they last. As well i'm not into dzVent as i stayed lua but i presume historical data used comes from DB If so you just get 5mn period samples that do not reflect true consumptions for devices with figures that may vary a ...