Excellent video Chris! We explored all - from 1 to 5 - and since we're not just doing HA for ourselves but for others as well, we decided to go the easiest route with Nabu. Not only we eliminate headaches of configs, but we also support the 'project' as a whole, which is the least we can do for the HA community. 🔴
I'm surprised this doesn't get more attention. It feels like easily the best solution. Very easy to setup, works for folks with static IPs and dynamic IPs without fiddling with DDNS nonsense, and is actually more secure as the subdomains you're using for the tunnel never list an IP address but are transparently managed by Cloudflare. Finally, should you want greater ingress control or to use this tunnel for DNS over TLS ... you can do that too.
I REALLY need to do a video on this. I have had many people tell me about it. I made a video on a different CloudFlare option but not the tunnel (iirc).
Just set it up myself after using NGINX Proxy Manager for months. The "Cloudflared" community add-on makes the tunnels super simple. I think this is my perfect solution. If you want external access and allow stuff like Google Assistant, then you need something like this, and VPNs aren't an option.
My list Using my own domain with port forwarding and SSL. Using my own domain with a VPN hosted on my network. Cloudflare with my own domain. This is a nice solution to protect the network but a little overkill. Engenix This is probably where my network is heading due to the number of self hosted services I use.
I installed Home Assistant in a boat, as a proxmox VM, , with Starlink Internet access. Starlink does not permit port forwarding (CGNAT), which system would work?
When away all I want to know is if a door opens or a light goes on, all I want to do is turn on/off lights so I use a particle reading MQTT and pushing out to the mobile app, on the app I can turn on off key lights and respond to a few critical events, so no firewall holes, no vpn - simple and as secure as I need it to be..
Thank you for this video. Do you mind explaining how you configured the DNS rewrite in AGH? I’m trying to achieve local HTTPS access of my HA Blue using Wireguard + AGH.
Go to Filters -> DNS Rewrites and add your domain and the internal IP it should point to. For SSL sites internal, I'm using Nginx Reverse proxy and pointing rewrites there and letting the proxy handle SSL to the device. I do this for my production HA instance.
As a relative new HA user I tried setting up DuckDNS and failed miserably due to the SSL complications. I disagree with your 6 rating and give it a 9. Nabu Casa is certainly a 1, but the cost is 3x higher than my existing VPN service through Private Internet Access. I'm off to try Tailscale and Wireguard. Those look like good options!
Thanks for the feedback. I use Tailscale for a lot of stuff and still support HA via a Nabu Casa sub. That primarily drives my smart speaker connections in making those seamless.
Being a newbie, I installed all except Tailspin. What can I remove from HA or are there compelling reasons I should have more than Nabu Casa? Thanks for the great videos.
That's a great question. I don't know how you would put them all in one UI. However, you could run one HA and then point all your entities back to a single HA using MQTT and other methods. There is a way to run more than one HA and have it report back as well. Just haven't tried that.
@@mostlychris aren't those intergrations instead of add-ons? but HACS mentions " there are no Add-ons n HACS, but can you can click here to go the supervisor"
Any help! i was using home assistant remotely by duckdn, now i just subscribe to nabu casa but the remote control doesn't work, when i try to log in my home assistant remotely i receive the error message (login blocked: User is local only) ,but the cloud service is enable. any help please.
There is an option to make a user ONLY local. You need to edit the user and make sure that "Can only log in from the local network" is not enabled. You can always go to your homeassistant IP:8123 on the local network and fix this, even if you have the cloud enabled.
Excellent video Chris! We explored all - from 1 to 5 - and since we're not just doing HA for ourselves but for others as well, we decided to go the easiest route with Nabu. Not only we eliminate headaches of configs, but we also support the 'project' as a whole, which is the least we can do for the HA community. 🔴
Cloudflare Tunnel is another access option.
It's fairly simple to setup, doesn't open any router ports, and automatically handles SSL.
I'm surprised this doesn't get more attention. It feels like easily the best solution. Very easy to setup, works for folks with static IPs and dynamic IPs without fiddling with DDNS nonsense, and is actually more secure as the subdomains you're using for the tunnel never list an IP address but are transparently managed by Cloudflare. Finally, should you want greater ingress control or to use this tunnel for DNS over TLS ... you can do that too.
I REALLY need to do a video on this. I have had many people tell me about it. I made a video on a different CloudFlare option but not the tunnel (iirc).
Just set it up myself after using NGINX Proxy Manager for months. The "Cloudflared" community add-on makes the tunnels super simple. I think this is my perfect solution. If you want external access and allow stuff like Google Assistant, then you need something like this, and VPNs aren't an option.
I’ve messed with all of them… but once I used tailscale… that was it! Haven’t changed since!
Outstanding!
The method I prefer and use is Wireguard. But not the HA integrated version, I have a separate Ubuntu VM for it. Great video!
Thanks! Yes, Wireguard can be self hosted and is a good option.
nice vidro ... today only i setup my unifi VPN to connect to my HA .... now it is working very good :)
Excellent!
Great video Chris. I use Nabu Casa for one instance, and zero tier for the other.
Good point. Nabu only connects to one. I have two main HA servers so I have different access for each.
Thanks you chris for consolidating all option in to one video
Absolutely.
Thanks for explaining all these options. I use the NABU Casa option and in addition the AVM router build in Wireguard VPM to access the NAS.
You're welcome.
Hello from France !! Thanks a lot for this video 😊😊 I use DuckDNS but because of this video i think i'll change soon !
Excellent and Hello!
My list
Using my own domain with port forwarding and SSL.
Using my own domain with a VPN hosted on my network.
Cloudflare with my own domain. This is a nice solution to protect the network but a little overkill.
Engenix This is probably where my network is heading due to the number of self hosted services I use.
That's a good list.
I'm using cloudflare tunnel and i think it's the easiest way to do it :)
...and I didn't even include that one in my list. I have used CloudFlare as well. I have a video on one method using CloudFlare.
I installed Home Assistant in a boat, as a proxmox VM, , with Starlink Internet access. Starlink does not permit port forwarding (CGNAT), which system would work?
In a boat? That sounds so cool! What kind of boat do you have and did you do any automations?
@@JoeyTurVic a sailing catamaran, so far I have all the victron sensors up and running into Home Assistant,
Nice video, but I was wondering if all these methods work with CGNAT?
When away all I want to know is if a door opens or a light goes on, all I want to do is turn on/off lights so I use a particle reading MQTT and pushing out to the mobile app, on the app I can turn on off key lights and respond to a few critical events, so no firewall holes, no vpn - simple and as secure as I need it to be..
Nice.
Thank you for this video. Do you mind explaining how you configured the DNS rewrite in AGH? I’m trying to achieve local HTTPS access of my HA Blue using Wireguard + AGH.
Go to Filters -> DNS Rewrites and add your domain and the internal IP it should point to. For SSL sites internal, I'm using Nginx Reverse proxy and pointing rewrites there and letting the proxy handle SSL to the device. I do this for my production HA instance.
Any new sites for free domain
tge one you mentioned is not accepting any new registrations
My solution is FIxed IP + own DNS domain + Ngnix proxy manager outside HA
Outstanding. Lots of options.
As a relative new HA user I tried setting up DuckDNS and failed miserably due to the SSL complications. I disagree with your 6 rating and give it a 9. Nabu Casa is certainly a 1, but the cost is 3x higher than my existing VPN service through Private Internet Access. I'm off to try Tailscale and Wireguard. Those look like good options!
Thanks for the feedback. I use Tailscale for a lot of stuff and still support HA via a Nabu Casa sub. That primarily drives my smart speaker connections in making those seamless.
Thank you.
Welcome.
Being a newbie, I installed all except Tailspin. What can I remove from HA or are there compelling reasons I should have more than Nabu Casa? Thanks for the great videos.
You don't need anything other than Nabu Casa unless you are doing special stuff.
Thxs for the info!
¿Wich solution might be most appropiare to manage multiple houses (different IPs) under one homeassistant UI?
That's a great question. I don't know how you would put them all in one UI. However, you could run one HA and then point all your entities back to a single HA using MQTT and other methods. There is a way to run more than one HA and have it report back as well. Just haven't tried that.
@@mostlychris I just found “remote home-assistant” integration in hacs. Will try
Does HACS has add-ons?
Yes.
@@mostlychris aren't those intergrations instead of add-ons? but HACS mentions " there are no Add-ons n HACS, but can you can click here to go the supervisor"
Any help! i was using home assistant remotely by duckdn, now i just subscribe to nabu casa but the remote control doesn't work, when i try to log in my home assistant remotely i receive the error message (login blocked: User is local only) ,but the cloud service is enable. any help please.
There is an option to make a user ONLY local. You need to edit the user and make sure that "Can only log in from the local network" is not enabled. You can always go to your homeassistant IP:8123 on the local network and fix this, even if you have the cloud enabled.