Local IP to home assistant app

[Tinkerer (aka DubhAd on GitHub)]

@Rikpal

I assume that also if I get a warning from the browser that the certificate is not recognized (since it has been issued for the example.duckdns.org), but the connection is still working with full encryption. Am I right?

Yes

Of course, this is a terrible practice and if the hostname works from inside the network use it. Your connection remains local, connecting to the router and back to HA.

@Rikpal

to deploy also a reverse proxy (caddy or nginx), I’ll completely loose https inside the LAN (since the only encryption will be only up to the reverse proxy). Am I right?

If you connect directly to HA, correct. If you connect using the DuckDNS/whatever hostname then no.

[MartinG (Martin)]

Of course, this is a terrible practice and if the hostname works from inside the network use it. Your connection remains local, connecting to the router and back to HA.

But in this scenario I can’t distinguish internal and external connection. Is there any way to do that?
I mean I don’t want my kids to access home assistant from outside, only when they are at home.
Before https it was easy with two address (internal and external) but I had to leave port open and unencrypted.

Now with https I can only use one address for both internal and external address and therefore unable to restrict control from internal and external IP.