-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Feature: WebcamProcessSensor #108
Comments
Hey @DennisGaida, good point! That'll really increase usability :) Created a ticket for this request: hassagent-120. |
Added in the latest beta: https://github.com/LAB02-Research/HASS.Agent/releases/tag/2022.13.0-beta2 |
Do you want comments on the feature here or somewhere else since this issue is closed? Currently isn't ideal in the beta. Microsoft Teams shows up as Checking a similar service I know that it is certainly possible to get more information from the registry (https://github.com/sleevezipper/hass-workstation-service/blob/master/hass-workstation-service/Domain/Sensors/WebcamProcessSensor.cs). Leveraging this service, Microsoft Teams shows up as: Windows Camera shows up as |
Here is fine :)
I'll tweak the parser, thanks for letting me know.
Yea that is by design. WindowsCamera is a lot more readable, so I parse the actual name from the reg entry. |
Just so you have some test data, here is a dump of the HKLM...\webcam hive. Please note that the
and here are a "couple" of entries for the HKCU...\webcam hive:
|
That's great stuff @DennisGaida, thank you! |
@LAB02-Admin, with 2022.13.0-beta3 [BETA], Microsoft Teams shows up as "non-packaged" for the WebcamProcess sensor as does Windows authentication/login prompt via Windows Hello. Is that expected behavior for this version? |
No, I think I forgot to add the actual fix :x I'll re-release this beta later and let you know |
Thanks :) Appreciate the fast turnaround! |
I've re-released beta3: https://github.com/LAB02-Research/HASS.Agent/releases/download/2022.13.0-beta3/HASS.Agent.Installer.exe You can just run the installer again, no need to uninstall. Let me know how it goes! |
Latest re-released beta works (also the microphoneprocess sensor). Any reason the WebcamProcess, WebcamActive (and Microphone equivalents) are hass.agent only? I believe the Windows service could easily just read the registry also while not being logged in. |
It could get the HKLM key, but not the user one when the user's logged in - the hive will be locked iirc. And no point getting it when the user's not logged in, since no app will be using anything. By logged in I mean a session, connected or not, by the way. I guess I could add it to the service if that would be useful, with the notion that it only reads elevated usage. |
Not that important to me personally. https://github.com/sleevezipper/hass-workstation-service was able to do this (and maybe only the HKLM key, not sure). It actually led to "problems" with Windows Hello because then it is not svchost.exe using the camera, but another service. Personally I don't need it prior to login, but it may be interesting to others (e.g. to do something especially when you authenticate with Windows Hello). |
Looking at the code, he gets both keys - it depends under what user the service runs whether that's useful. But I'll enable it for hass.agent's service, doesn't require extra coding anyway and users can decide for themselves. At any rate, glad it's working for you, let me know whenever it might need tweaks :) |
Works for me also. Thanks for the re-release and for your contributions in general! |
Is your feature request related to a problem? Please describe.
Windows Hello enabled cameras are also registered as webcams in Windows, meaning whenever you authenticate to your Windows machine using Windows Hello camera (infrared), all the automations based on webcam activity are triggered.
Describe the solution you'd like
When the webcam is active I want to know what process is using it. Many use cases for this:
Describe alternatives you've considered
Use HASS Workstation Service
The text was updated successfully, but these errors were encountered: