Has anybody encountered this error appear when starting up HASS.Agent on Win10? It was working fine up until recently, not aware of any other changes that may have caused it.
followed by
and then HASS.Agent crashes.
Have tried deleting the json file and reinstalling the app.
Hi guys - is there a way to install HAAS. Agent on a 32-bit system ? I tried to install it on tablet using win 8 which is 32 bit and i got the message that the installer stopped because the system which i want to install on is a 32 bit one? - Is there a way to install HAAS even in a limited version ?
So sad to see that this plugin isn’t maintained anymore. It really should be a part of the Home Assistant project to have a PC-sensor.
This app is super useful, but it seems that it would be better if it had more pc system readings. As it stands, I can see my GPU temperature, but not the CPU temp. I’m looking to ventilate my wiring closet based on CPU usage (temperature), but that does not seem possible currently. Where would one put in a suggestion for the developer? I’m guessing the discussion section on the Github page? Thanks
You can literally pull any value available in WMI: (including any temp available to the OS)
Very cool. Not sure how I missed that, but thanks for the link!
Great tool, I use it for various tasks. Do you know if it is possible to change the refresh intervals of the local sensors or even better trigger a local sensor refresh on my windows machine from Home Assistants side?
With that I could for example refresh a sensor in a Home Assistant automation right before I check its status.
Do anyone know what the Internal Device Sensor does? I have no options in the dropdown and the advanced section just allows me to enter device classes and what not.
Create a Command using PublishAllSensors and type Button and then press the button it creates in HA.
Hi all - I’m trying to set up an automation that prevents my motion sensors from turning off the lights if my PC is active (keyboard stroke or mouse movement). I thought the “lastactive” sensor would work but it’s just resetting every 10 seconds even if I don’t touch the keyboard or mouse. Anyone have any thoughts on how I should proceed?
Can’t you just use a powerplug? If your system goes into standby it consumes much less watt. Then set the standby timer to three minutes. That’s how I’ve done it
I did similar. Ended up running some tests, looking at sensor history, and making a template sensor that outputs states. Annoyingly complex, but it works quite well. Based on power consumption, and ping (that’s how we know it’s active vs booting or shutting down).
I’m not sure why yours is behaving like that.
My LastActiveSensor updates every 10 seconds in case there is mouse movement or keyboard stroke.
I used that to check if there was any activity in the computer in the last 10 minutes and if not, to turn off lights and monitors.
I used in the template below:
{{ (now()|as_timestamp - (10*60))|timestamp_custom("%Y-%m-%d %H:%M:%S", True) >
as_timestamp(states.sensor.computer_name_lastactive.last_changed)|timestamp_custom("%Y-%m-%d %H:%M:%S", True)}}
I’ve started using the HASS Agent to track when either my webcam or microphone is in use, to automate turning on my office DND (Do Not Disturb) light.
After finding the new fork (in the links above), I uninstalled it and then installed the new fork.
There are two things that I have noticed that are causing my automations to not work as intended.
It is always showing the MicrophoneActive as ON, and the MicrophoneProcess as “ptoneclk”. I’ve researched “ptoneclk”, and found that this is with Webex. I’ve followed the instructions to disable the Webex listening in on the microphone, and then even uninstalled Webex, but the HASS Agent is still showing as ON and the process is still “ptoneclk”. Are there any ideas on how to resolve this? I’m not sure that this is a HASS Agent issue, but merely a symptom that shows up in HASS Agent.
While trying to get this to work, I noticed that if I start using the microphone in another application (Zoom, Slack, etc.), the MicrophoneProcess will change to ‘2’, and when closed it then goes to ‘1’. Almost like it’s a counter of the number of processes using the microphone instead of the process name.
After restarting HA (for another reason), the observed behavior in #2 isn’t happening any longer. Note that I was using mictests.com for testing the microphone. The MicrophoneActive stayed at “ON”, and the MicrophoneProcess stayed at “ptoneclk”. Since it did happen, I wanted to report it so that this was known.
Does anyone know how HASS Agent determines whether the microphone is active, and what the process that is using it is? If so, I might be able to backtrack it all and figure out what registry remnants need to be removed (where I suspect the issue resides).
Thanks!