-
Notifications
You must be signed in to change notification settings - Fork 157
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 Request: Privacy mode - blur & dim picture based on a boolean entity #624
Comments
It's not very smart to protect your camera on the client side. This protection bypasses. |
It is not a protection against unauthorized use or anything of the sort. I use the "privacy mode" when I take screenshots of the dashboards that include cameras, when I share my desktop (view only) to show something to those I help, or when I show Home Assistant on my phone to others. Streamers would also benefit from this. If I need to be 100% sure that someone with dashboard access cannot see the feed, I can power down the camera (PoE) or disable HA's access to the NVR. |
|
Are you suggesting that I can write a template that resolves to the correct camera feed if privacy mode is off, and to nothing if privacy is on? If so, it gets me close but would be nicer if the privacy on mode had a predefined look rather than an error message for inaccessible camera. Will have to research this as I don't have a clue on how to do this off the top of my head. |
You can create some dummy stream with streaming static file. But template will work only with |
If I can't turn privacy on or off based on an entity then it seems this solution doesn't work for my case and I have to go back to the old card :( The picture-glance card is worse in nearly every way possible but I like 2 things about it: 1) |
When showing my Home Assistant Dashboard to others, or sharing it online, I prefer to blur out the camera feeds.
Using the picture-glance card, this is how I was achieving it:
Example of the privacy mode:
Now that I am using the webrtc-camera card I can't find a way to do it.
Would you kindly consider adding this feature?
The text was updated successfully, but these errors were encountered: