Usually this works pretty flawlessly, but from time to time I'll notice that my other sensors seem to be updating, however LastActive (and sometimes SessionState too, I believe) will just stop publishing their state attributes to MQTT.
Upon removing LastActive and re adding it, it shows in the list of published sensors, but the state is empty.
Just "Warning" on its own isn't enough to me to figure out what to do next. Also curious, I presumed that the HASS Workstation Service was backgrounding itself as a windows service, however I dont seem to be able to find it in any services list - In the frontend, the only thing "Disable" seems to do is disable autostart at boot - what's the suggested way to properly restart the app if necessary?
Hi,
Usually this works pretty flawlessly, but from time to time I'll notice that my other sensors seem to be updating, however LastActive (and sometimes SessionState too, I believe) will just stop publishing their state attributes to MQTT.
Upon removing LastActive and re adding it, it shows in the list of published sensors, but the state is empty.
Looking in the logs, I see:
{"@t":"2022-09-06T19:47:43.3323624Z","@m":"Sensor failed: LastActive","@i":"408e4d89","@l":"Warning"} {"@t":"2022-09-06T19:47:44.4504528Z","@m":"Sensor failed: LastActive","@i":"408e4d89","@l":"Warning"} {"@t":"2022-09-06T19:47:45.5611911Z","@m":"Sensor failed: LastActive","@i":"408e4d89","@l":"Warning"}
Just "Warning" on its own isn't enough to me to figure out what to do next. Also curious, I presumed that the HASS Workstation Service was backgrounding itself as a windows service, however I dont seem to be able to find it in any services list - In the frontend, the only thing "Disable" seems to do is disable autostart at boot - what's the suggested way to properly restart the app if necessary?