Add statistics

[AlCalzone]

Things that should be considered (total and per node):

• Transmitted messages per node (feat: implement transmission statistics for the controller and nodes #2736)
• Transmitted messages (controller) (feat: implement transmission statistics for the controller and nodes #2736)
• Received messages per node (feat: implement transmission statistics for the controller and nodes #2736)
• Received messages (controller) (feat: implement transmission statistics for the controller and nodes #2736)
• Dropped messages from nodes
• Dropped messages from the controller (feat: implement transmission statistics for the controller and nodes #2736)
• Controller errors (CAN, NAK, timeout) (feat: implement transmission statistics for the controller and nodes #2736)
• Node errors (NoACK, timeout, ...) (done in feat: implement transmission statistics for the controller and nodes #2736, but currently no distinction between not sent and NoACK)
• Response time (feat: expose RSSI and routes as part of node statistics #4022)
• Background RSSI, current and average (done in feat: measure background RSSI frequently when the controller is idle #5545)
• Failures during interview
• When was a node last seen (alive/awake/unsolicited msg) (feat: add lastSeen property to node and node statistics #6008)
• Queue: size, what is in the queue? (Implement message queued/dequeued events #1270)

[LordMike]

Bonus to having events per message, rather than just counters, is also being able to see how long it actually took to deliver that "turn on" message. Would help immensely in tracking down where delays are occurring, when lights appear slow.

#1270 (comment)

[nicoh88]

+1 for last seen

[jaimevisser]

Especially on bigger z-wave networks this would be a big help in tuning sensor data output.

[Masterz69]

Missing last seen property on Home Assistant for ZWave devices.

Just today had an situation: FGBS-222 was powered off for ~25 minutes.
Device is configured to report every 5 minutes, couple of messages not received by controller.
ZWAVEJS2MQTT device node status still alive :(

• as no configuration on device level: when to declare device to not alive when no messages received from.

IMHO I can't relay on node status to determine actual device status.
last seen will help to react on devices sending no info long time.

[AlCalzone]

lastSeen will be added in #6008