Automatically Light Up a Sign When Your Webcam Is in Use
fedoramagazine.org
fedoramagazine.org
2. Two Pi Zeros with LED hats light up during Zoom meetings. This uses the Zoom APIs to receive webhook events that are published to MQTT. The PIs listen to MQTT and adjust the light colors.
3. I have a color changing Pac-Man Ghost light behind me that turns off during video meetings. In this case, my home automation system listens to MQTT events and turns the plug off and on.
Extra. I used the Node/Office365 calendar querying to light up PI LEDs for wife’s meetings and kid’s meetings. I didn’t feel like trying to deal with another company’s Teams API or school’s Zoom settings. The kids meetings were also announced over Sonos in the area of home they were working. It worked well enough we didn’t have to look after them every time class started.
It's a closed system, like a restaurant kitchen. Determining whether the chef is wearing a hat by examining the plates coming out may be possible with enough plates and time, but the answer sufficiently becomes 'no' for practical purposes.
If it’s accessible via software, there’s the possibility that it can be controlled with software as well.
If there's a pin (or more likely, a USB control transfer controlling a pin) that controls the power state of the webcam (and thus the LED), you need to track the state of the pin anyway.
Pros: Not physically tied to PC. Cons: Another wifi device, unless you've already got a z-wave/zigbee stack setup you can piggyback on.
Q: Why does it take OverSight, a few seconds to display the webcam/mic usage notification?
A: There is not easy way to determine what process is using the webcam or mic, when either is activated. Worse, there is no direct indication that a new process is accessing an existing a webcam session. Thus OverSight has to perform various tests and has to poll the system (only when the camera/mic is active) in order to determine what process(es) is/are accessing the device. This takes a few seconds...mahalo for your patience!
EDIT: on my iMac M1 the built-in camera and mic are not detectable by MS. So, maybe not...
EDIT2: https://obdev.at/products/microsnitch/releasenotes.html
It's a bug in Big Sur, so hopefully it will be fixed and MS will work again.
It's able to detect camera and microphone activation/deactivation and logs it to stdout. Currently figuring out how to detect when a new peripheral is connected.
I’ve been using this for ~1 and it’s been more reliable than I expected - no maintenance required even with the update to Big Sur.
To save you a click:
log show --predicate 'subsystem == "com.apple.VDCAssistant" && \ eventMessage CONTAINS[c] "kCameraStream"' --last 1m --no-debug --no-pager \ --style compact | tail -n +2)
#or log stream ... # streaming is better to generate events
Which would not work for me as I generally keep the camera off to save bandwidth and the last remaining shreds of my sanity.