Open amaisano opened 2 years ago
I have the exact same issue, exactly as described.
Related to #168 too
FYI I am using this workaround.
value_template: "{{ is_number(states('sensor.bebop_gpu_temp')) }}"
unknown
when the PC is off (not a number).
I have two Windows 10 machines in my office. Both exhibit this behavior.
After choosing "Sleep" from the Windows start menu, upon waking back up via a Wake On Lan command (wake on magic packet via LAN) or keyboard, HASS W doesn't report a change from the
SessionStateSensor
to Home Assistant.Waking the machine puts me back into the lock screen, by the way, for security purposes.
The
LastActivity
sensor works (is picking up when I move my mouse), but theSessionStateSensor
(InUse, Off, etc) is stuck onUnknown
.If I unlock my screen, then lock my screen again,
SessionStateSensor
goes toLocked
. But I don't want to have to do that after waking up and unlocking the first time .Here's the timeline
Unknown
->InUse
InUse
->Locked
->Off
->Unknown
(happens over 1-2 minutes)Unknown
(no transition)Unknown
(no transition, butLastActivity
is working)Unknown
->Locked
Locked
->InUse
If it's stuck in
Unknown
and I edit theSessionStateSensor
in the UI, (without actually changing anything) and click save, it bumps it toInUse
in Home Assistant.Any tips? It seems somewhat related to https://github.com/sleevezipper/hass-workstation-service/issues/58 and/or https://github.com/sleevezipper/hass-workstation-service/issues/46