Sensor becoming unavailable after every update
Hi folks. I've got a PerformanceCounter sensor set up, and it's reporting 'Unavailable' after every update (see screenshot).
Does anyone know how I can make it remember the last value, rather than switching? Otherwise, I can't set up automations with triggers like
if under threshold for X minutes, do something as it's frequenting switching between a value and unavailable.
2 Replies
I had a brainwave pretty much as soon as I posted this.
I found the culprit! The legacy LAB02 HASS.Agent was conflicting with the new HASS.Agent. The new HASS.Agent published the correct value, the legacy HASS.Agent was publishing "Unknown" hence the switching.
Problem solved 🙂
Yeah we do recommend uninstalling or at least de-activating lab02 on startup