Feature request: keep track of device command retries somewhere

[hubitrep]

I was skeptical of this feature when it first came out but it has turned out to be both an effective band-aid AND a valuable troubleshooting tool... but only when I do catch it in action in the hub logs before they roll off, which is both rare and fortuitous.

Would it be possible to count the number of retries attempted per device (and possibly retry failures) and make that count available somewhere outside of hub logs? I was thinking the Zigbee/Z-Wave/Matter details might be a good place for that.

@mike.maxwell

[velvetfoot]

filtering by "retry" in past logs isn't enough?
It changes all the time, details would just have the last?

[chrisbvt]

@velvetfoot

details would just have the last

Yeah, if anything, the max number of retries required by a device would be a useful number. Though it would need a way to be reset, to see if a problem was fixed after.

[hubitrep]

@velvetfoot

filtering by "retry" in past logs isn't enough?

No, the logs roll off and can be missed.

@velvetfoot

It changes all the time, details would just have the last?

That is why I am suggesting a count. The idea being that devices with a high retry count might have a marginal connection. Sort of analogous to how Z-Wave devices that have a high route change count should be looked at.

@chrisbvt

Though it would need a way to be reset, to see if a problem was fixed after.

Could reset on reboot, like other stats.