No way…
The message does not change because of hardware and/or a restart.
Have a look here at the arguments:
Message structure from link above:
{
"event_type": "zha_event",
"data": {
"device_ieee": "ec:1b:bd:ff:fe:39:63:da",
"unique_id": "ec:1b:bd:ff:fe:39:63:da:1:0x0008",
"device_id": "a6e2928ee51d31c25e7afa6d1f55dbc9",
"endpoint_id": 1,
"cluster_id": 8,
"command": "move",
"args": [
0,
195,
0,
0
],
"params": {
"move_mode": 0,
"rate": 195,
"options_mask": 0,
"options_override": 0
}
},
"origin": "LOCAL",
"time_fired": "2022-04-12T21:03:00.224206+00:00",
"context": {
"id": "ad76032c18e711ee9757881b8ad66973",
"parent_id": null,
"user_id": null
}
}
the same event in 2022.3.3, same remote:
{
"event_type": "zha_event",
"data": {
"device_ieee": "5c:02:72:ff:fe:40:af:22",
"unique_id": "5c:02:72:ff:fe:40:af:22:1:0x0008",
"device_id": "f594d0a16628c130b023f476a35c0091",
"endpoint_id": 1,
"cluster_id": 8,
"command": "move",
"args": [
0,
195
]
},
"origin": "LOCAL",
"time_fired": "2022-04-14T11:42:59.725750+00:00",
"context": {
"id": "8797f70a0ae25787f8af15180bace373",
"parent_id": null,
"user_id": null
}
}
I do not believe this is due to hardware or restarts.
That data is from ZHA, there is no way the remote has any context of “time_fired” for instance.