-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs: Network and WindowsUpdates sensors, UI exception #68
Comments
Can you please post both HASS.Agent and the service's logs? You can find the paths by going to Configuration and click the 'open logs folder' button in both the logging and satellite service tabs. |
I'm not seeing how I can attach a file to this comment. How do you want them? |
Looks like a few interesting bugs, I can work with this. Thanks for the extensive info! If the wupdates sensor doesn't work from HASS.Agent either, it's possible there's something wrong/off with your wupdate service. |
Fixed in the latest beta: https://github.com/LAB02-Research/HASS.Agent/releases/tag/2022.13.0-beta1 |
Not sure which is the buggy sensor, but I added the following to Satellite:
CpuLoad, LastBoot, LastSystemStateChange, MemoryUsage, Network, WindowUpdates
The first time it replaced the WindowsUpdate with a second instance of Network. Then it left the above list in, but added a second instance of Network at the end. Removing all three (Network, WU, Network), then sending and activating, closing window, and re-opening left all three in there. At some point (trying to remove all three) it did remove the WindowsUpdate sensor, but left the duplicate Network sensors. At this point (trying to add/remove and fix it), I now have four Network sensors.
So there's some issues going on there that are beyond my comprehension
It also gives me a JIT debug occasionally when adding/removing:
The text was updated successfully, but these errors were encountered: