Irregular electricity consumption readings

What happened?

A few days ago, I noticed that the energy consumption readings for at least 2 of the 8 outlets (Girier JR-ZPM01) have been updating less frequently than before, at longer intervals, and this has been happening since August 1 at 11:00 a.m. So my first suspicion is that this is due to the Z2M update to version 2.13.0-1. Have you also noticed similar behavior on your end? :

What did you expect to happen?

I expect a more "smooth" readings, like before August 1.

How to reproduce it (minimal and precise)

I'm not sure what triggered this behaviour since I have not set any specific parameters (like "report interval", "calibration", "precision")

Zigbee2MQTT version

2.13.0-1

Adapter firmware version

20260310

Adapter

SLZB-MRW10 (ZStack)

Setup

Add-on HA OS, running in a 64-bit VM on a SA6400 NAS

Device database.db entry

{"id":20,"type":"Router","ieeeAddr":"0xa4c138518e89f965","nwkAddr":16792,"manufId":4107,"manufName":"_TZ3000_ww6drja5","powerSource":"Mains (single phase)","modelId":"TS011F","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,3,4,5,6,10,57344,1794,2820,4096,6280],"outClusterList":[25],"clusters":{"genBasic":{"attributes":{"hwVersion":0,"manufacturerName":"_TZ3000_ww6drja5","zclVersion":3,"appVersion":112,"modelId":"TS011F","powerSource":1}},"haElectricalMeasurement":{"attributes":{"acCurrentDivisor":1000,"acCurrentMultiplier":1,"rmsVoltage":237,"rmsCurrent":620,"activePower":133,"acVoltageMultiplier":1,"acVoltageDivisor":1,"acPowerMultiplier":1,"acPowerDivisor":1}},"seMetering":{"attributes":{"divisor":100,"multiplier":1,"currentSummDelivered":107916}},"genOnOff":{"attributes":{"32768":1,"onOff":1,"tuyaBacklightMode":1,"moesStartUpOnOff":2,"onTime":0,"offWaitTime":0}},"manuSpecificTuya3":{"attributes":{}}},"binds":[{"cluster":6,"type":"endpoint","deviceIeeeAddress":"0x00124b00339dbb6b","endpointID":1},{"cluster":2820,"type":"endpoint","deviceIeeeAddress":"0x00124b00339dbb6b","endpointID":1},{"cluster":1794,"type":"endpoint","deviceIeeeAddress":"0x00124b00339dbb6b","endpointID":1}],"configuredReportings":[{"cluster":2820,"attrId":1285,"minRepIntval":5,"maxRepIntval":3600,"repChange":5},{"cluster":1794,"attrId":0,"minRepIntval":5,"maxRepIntval":3600,"repChange":257},{"cluster":2820,"attrId":1288,"minRepIntval":5,"maxRepIntval":3600,"repChange":50}],"meta":{}}},"appVersion":112,"stackVersion":2,"hwVersion":0,"swBuildId":"1.0.5\u0000","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{"configured":"0.0.1"},"lastSeen":1787673797400}

Debug log

No response

Notes

No response

No source file, test, or code entry point is named. Start by reproducing the slower reporting with the supplied TS011F device database entry and Zigbee2MQTT 2.13.0-1 setup, then collect a debug log; done means identifying whether the reporting interval changed and restoring smooth readings comparable to those before August 1.