Minor feature request for a "last activity" or "last message" item for each device.
Would have the last time/timestamp/whatever I'll figure it out that a device communicated with hcpy. Would be updated on any inbound data; i.e. answers to queries, pings, keepalives requests/answers, etc. Would NOT be updated if a ping or keepalive is sent and never answered.
Right now if no actual state or data changes nothing changes in mqtt, which makes it almost impossible to tell if things have hung if/when hcpy goes on a long walk off of a short pier. I know about the device LWT (and hcpy's LWT), but that only gets updated on clean data or clean python exit. If python or hcpy hangs but doesn't die (see #244), LWT doesn't update and downstream has no way to detect there's a problem.
(First step is detecting a problem, second step is stepping in and doing something about it!)
Minor feature request for a "last activity" or "last message" item for each device.
Would have the last time/timestamp/whatever I'll figure it out that a device communicated with hcpy. Would be updated on any inbound data; i.e. answers to queries, pings, keepalives requests/answers, etc. Would NOT be updated if a ping or keepalive is sent and never answered.
Right now if no actual state or data changes nothing changes in mqtt, which makes it almost impossible to tell if things have hung if/when hcpy goes on a long walk off of a short pier. I know about the device LWT (and hcpy's LWT), but that only gets updated on clean data or clean python exit. If python or hcpy hangs but doesn't die (see #244), LWT doesn't update and downstream has no way to detect there's a problem.
(First step is detecting a problem, second step is stepping in and doing something about it!)