SONOFF S60ZBTPF - Power reading frozen when off

[iksela]

What happened?

As long as the plug is on, the power reporting works well.
When set to off, the power reading stays to the last value.
When set back to on, the power reading starts again.

What did you expect to happen?

Power reading should go back to 0 (or whatever the plug is consuming)

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.6.0

Adapter firmware version

6.10.3.0 build 297

Adapter

EZSP v8

Setup

Linux, docker image
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
Debian GNU/Linux 11

Device database.db entry

{"id":5,"type":"Router","ieeeAddr":"0xa4c13803065dffff","nwkAddr":1203,"manufId":4742,"manufName":"SONOFF","powerSource":"Mains (single phase)","modelId":"S60ZBTPF","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,3,4,5,6,1794,2820,2821,64599,64529],"outClusterList":[10,25],"clusters":{"genBasic":{"attributes":{"modelId":"S60ZBTPF","manufacturerName":"SONOFF","powerSource":1,"zclVersion":3,"appVersion":16,"stackVersion":2,"hwVersion":16,"dateCode":"20250411","swBuildId":"1.0.2"}},"customClusterEwelink":{"attributes":{"28675":"\u0004\u000b\u0001\u0000\u0001�6\u0000\u0000P�1\u0000","acCurrentCurrentValue":0,"acCurrentVoltageValue":238451,"acCurrentPowerValue":8082,"outlet_control_protect":0,"energyYesterday":0,"energyToday":0,"energyMonth":0,"faultCode":50462720}},"genOnOff":{"attributes":{"onOff":0,"startUpOnOff":0}}},"binds":[{"cluster":6,"type":"endpoint","deviceIeeeAddress":"0x6c5cb1fffe993d41","endpointID":1},{"cluster":64529,"type":"endpoint","deviceIeeeAddress":"0x6c5cb1fffe993d41","endpointID":1}],"configuredReportings":[{"cluster":64529,"attrId":28682,"minRepIntval":60,"maxRepIntval":3600,"repChange":50},{"cluster":64529,"attrId":28683,"minRepIntval":60,"maxRepIntval":3600,"repChange":50},{"cluster":64529,"attrId":28681,"minRepIntval":60,"maxRepIntval":3600,"repChange":50},{"cluster":6,"attrId":0,"minRepIntval":0,"maxRepIntval":65000,"repChange":1},{"cluster":64529,"attrId":28678,"minRepIntval":10,"maxRepIntval":30,"repChange":1}],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":16,"stackVersion":2,"hwVersion":16,"dateCode":"20250411","swBuildId":"1.0.2","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{"configured":332242049},"lastSeen":1756895332749}

Debug log

No response

[iksela]

Tested against 2.6.1 - issue is still there.

[chrisnav]

Same problem here, and the fix in this issue did not work for me

[Koenkk]

Fixed!

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.

[mfb-bbg]

Fixed!

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.

Thanks Koenkk. Just checked the newest dev branch. So its working partially. The "Current" drops to 0 when switching off. However the "Power" stays still at the old value. So whatever you did to get the "Current" to 0 you have to do it to the "Power" as well.

Regards
Michél

[Koenkk]

It should do it for both power and current, seems something is wrong, can you provide the debug log?

[mfb-bbg]

Attached the log. I had a quick look in the log as well and you can see that power and current went both to zero right after switch off. So you are right. However, for some reason, on the next message the power comes back.

log.log

[Koenkk]

This contains only the info logging, could you provide the debug one?

See this on how to enable debug logging.

[mfb-bbg]

Sorry i had debug on but i copied from the frontend, not from the logfile. Attached the debug log. Same behavior as already mentioned, when switched off then power is set to 0. But on the next message is back to the old value.

log.log

second log, already grouped with 3 on/off cycle
zigbee_reiskocher_blocks.log

[Koenkk]

Pushed another fix, can you check if it works?

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.