Incorrect lastUpdate.minutesAgo value in DzVents – 2025.2 (build 17252)

[tomes]

Domoticz version: 2025.2 (build 17252)
Platform: (Raspbian 13.2)

After upgrading to the latest beta version 2025.2 (build 17252), I noticed an issue with the lastUpdate.minutesAgo parameter in DzVents.

I am using OWFS 1-Wire temperature sensors.
The sensors update correctly — at least once per minute (confirmed in the device log and hardware level).

In my DzVents scripts, I check:

device.lastUpdate.minutesAgo

Since the last update, even though the sensor was updated less than a minute ago, Domoticz shows an increasing minutesAgo value indefinitely for randomly selected sensors.

The value keeps increasing as if the device had not been updated at all, while in reality:

The device value is changing correctly.

The device “Last Update” timestamp in the UI appears correct.

Only lastUpdate.minutesAgo in DzVents is incorrect.

The issue does not affect all sensors at once — it appears randomly on different OWFS devices.


The same scripts worked correctly in previous versions.

[gizmocuz]

In the current beta, non-switch-alike sensors are now checked if the value has changed.
If it has not changed, then no even is fired.
I think in the OWFS code (but please check this!), the data is directly written into the database and bypasses the normal event routes.

I don't know the reason why you work with last_update, but you could maybe use the global data to store things.

If it is an issue, please open a github issue and mention this topic

The reason why I skip same values is that there are users (with ESPHome for instance) that receives many updates with the same value, sometimes multiple updates in a second. This caused the whole system to degrate.
I had a Zigbee wallplug that (for a still unknown reason) was spamming my zigbee network with 20 messages a second...

Most (if not all) scripts react on a 'state', if this state is not changed, there should be no reason to fire a script, last value should always be good as well.

[meal]

Hello,

To complement the information shared on the subject my understanding is the following:
- Domoticz does not update the LastUpdate information used by LUA or dzvent and does not fire event if the value has not changed. Thus saving CPU usage.
- However the LastUpdate information in domoticz.db is updated.

In my domoticz application I implemented the following use case:
I have installed ZWAVE plugs which are always activated to monitor the power consumed by water pumps.
Every 10 s the plug sends the current power to Domoticz.
- Power is null when the pump is not running .
- Power > 0 when the pump is activated in case of flood.
It allows also to know if the plug is alive by raising an alarm if no power information is submitted within a 30s delay. In that case it means either the power supply is down or the Zwave connection is down.

To achieve the last requirement I cannot use the "otherdevices_lastupdate" LUA function because it is updated only when power data changes but I read the LastUpdate data in the domoticz.db "DeviceStatus" table.

One improvement could be to have both information in LUA
- LastUpdate information showing the date of the last change (as currently)
- LastWriteDate information showing the latest writing date in the DB (improvement)

BR

[gizmocuz]

And what triggers your script? A timer?