MQTT status re-query keeps push-only state fresh
With account login configured, the integration now asks every device that has an AWS IoT topic for its current status on a schedule — every 5 minutes by default, configurable from 60 to 3600 seconds under MQTT status re-query interval, or 0 to turn it off — and once more each time the MQTT session (re)connects.
Reverse-engineering of the Govee app by @alexlenk (#192) showed that devices mostly answer status queries rather than push spontaneously: the app's device list sends this exact query while it is on screen, and govee2mqtt and homebridge-govee send the same one. Without it, everything that exists only in the push — the H7152's pump state, hose mode, temperature and humidity from v2026.9.4, the H1310/H1370 ceiling-fan state, H5127 occupancy — froze at its last value once the Govee app was closed, with nothing in the logs to say so. Queries are fire-and-forget (QoS 0), so a lost one costs a single interval.
Every device also gains a Last MQTT Received diagnostic timestamp. Last Update Received is the newest timestamp across every transport, so a healthy cloud poll kept it reading "just now" even when MQTT specifically had gone silent for hours; the new sensor isolates the MQTT signal.
Landed as @alexlenk's PR plus a follow-up that adds the off switch and the QoS 0 publish.
Also
- README: the H5160/H5161 outlet switches have followed the strip's own outlet reports since v2026.9.3; the table said otherwise.