Would like user limitations

When I log into it from a user’s phone; it would be nice to have them restricted to local use if needed. That way when they aren’t at home the device won’t turn on when they try to use it. Or the app will only turn on if they are within the local network.

Go to Configuration / People and Zones then click on Users up top.

Click on the user and turn on local access only:

Untitled

I have already tried that but it does not work.
When I try to connect my phone to local network using the local IP like I do in my browser the app shows me this.

The certificate for this server is invalid. You
might be connecting to a server that is
pretending to be “192.168.1.10” which
could put your confidential information at
risk.
NSURLErrorDomain-1202

That has nothing to do with local access control. That is because you are using https for an IP address. The certificate is only valid for the domain name.

I want them to have access to HA with the domain name; but access to control to be limited to local only.

For example: they can see cameras or temp readings or whatever. But they will only be able to open the gate if they are at home so they can visually see the gate isn’t going to crash into something.

I also do not appreciate my posts from getting closed before I have a chance of replying or asking about something. Especially when the issue hasn’t been resolved.

I’d like to know why I am unable to access the supervisor store on my Raspbian Pi; yet in the VM with the same backup it allows it.

It was closed because your feature request was not supported and there is very clear documentation as to why it is not supported.

  1. Find http in your config. Remove everything about SSL.
  2. Install the NGinx SSL Proxy addon
  3. Specify your domain and the path to your SSL certificate and key file in the config of that addon
  4. In your router remove the mapping for port 8123. Instead map port 443 to port 443 on the HA machine
  5. Go to https://<your domain> from outside your network. Go to http://<IP address> from inside your network. Both work, there are no errors
  6. Set some users to local only. See how http://<IP Address> works fine and https://<your domain> does not

Just don’t use the SSL features in HA. HA’s job is home automation, let it be good at that. Use a reverse proxy and let NGinx be good at handling the features of HTTP and SSL encryption.

Ok, if it isn’t supported; then maybe someone would have commented to me as to how I can get the cloning tool into Debian. :man_shrugging:
But you closed it before I got a solution to my issue… :man_facepalming:

I would like my connection to HA to be encrypted which is why I use https.
Any video in youtube that explains all that you said and explains as to why it is a better feature?

I also need 443, to work for other things as well such as NextCloud.

Feature requests is not the place to post issues.

I know it is a feature request; but if no one is willing to add the feature based on whatever reason, then at the least they can help me with the cloning tool so I wouldn’t need the feature…

I’m not suggesting you enable unencrypted connections to HA, at least not from outside your LAN. External traffic to HA will still be encrypted if you use a reverse proxy. Traffic inside your LAN won’t be but since that’s only visible in you LAN that’s usually ok.

No idea if there’s a YouTube video, I rarely go on YouTube. Here’s nginx’s explanation on the benefits of a reverse proxy: What is a Reverse Proxy Server? | NGINX. And here’s cloudflares: https://www.cloudflare.com/learning/cdn/glossary/reverse-proxy/ (although cloudflare wants you to use their cloud service rather then hosting your own so you have to read between the lines a bit, most of what they’re saying still applies though).