WMI Query sensors do not work if the WindowsMediaInstrument service restarts
I know this is a bit of a rare off-case, so I understand if y'all dont wanna do anything about it. What happens is, if I restart the WMI service (sometimes that service acts up when I restart my computer), my WMIQuery sensors wont work, until I go to "modify" on one of them and press "Test WMI Query".
Again maybe this is too much of an off case but I wanted to at least note the issue. Maybe there's a way to work around this somehow.
Solution:Jump to solution
ok, I think I've fixed it, I'll create a test release tmrw and ping you with link
13 Replies
hmm
that is interesting, I know that WMI in general needs some time to "spin up" (a windows quirk rather than HASS.Agent one) but that sounds a bit different, what update period do you have for the sensors? do they start working again only and solely when you test them via UI?
Theyre at 10 second inverals and yeah I've observed them not working for multiple hours, not working again till manual intervention via testing in the UI
oh yes, HASS.Agent doesn't like the service being restarted
Solution
ok, I think I've fixed it, I'll create a test release tmrw and ping you with link
Ok sounds good
GitHub
Release 2.1.1-beta2-wmirestart · amadeo-alex/HASS.Agent
Please do not download files from this "release"
It's only purpose is to provide unstable testing for insiders/issue reporters.
Unless explicitly instructed by the developers, please ...
lemme know how it behaves 😄
yep i restarted the service and so far so good, sensors are still working!
@Ellie do you have a GH account?
yes
wanna give me the name? I'd like to credit you for the issue report
no pressure tho, if you don't want to that's fine 😄
yeah its jack5mikemotown