Old install quit working, fresh install has issues as well

Sorry for the wall of text about to appear. I have had HA installed for several years on a Windows laptop running in VA. Several times in the past my instance would quit working. After much troubleshooting and help from the community, it always seemed the only solution was to do a fresh install. The biggest problem with that is adding 150+ zones on the map and resinstalling all the software for my smart home. Not the most efficient thing to do and requires so much time to get everything back right. I was using duckdns to access it away from the house and that mostly worked fine. There were some issues at some point and I decided to do a fresh install and pay for HA cloud to insure stability and get rid of those problems. It ran perfect with 0 glitches for about 3 months and then sure enough, I can not connect from outside of my network again on either Android phone. I did my best to troubleshoot again to no avail. I figured here we go again. I did a fresh install again, but I can still not get it to work outside of my home. I can login to a local browser and see HA and monitor everything. The more troubleshooting I do the more confused I get. When I log in to nabu casa page it gives me this error:

Your instance is not connected to Home Assistant Cloud

Remote address: Not available

I have not changed router or internet service. I submitted a ticket to nabu casa but they said they only support their own green or yellow hardware. At a loss where to begin and so frustrated. I will be glad to share logs or router settings or any information that you would need to help get it going again. Willing to do another fresh install if necessary, but I would love to get my last working one running again as it has so much work put into it.

TY, Brian

Have you tried restarting/rebooting your router? Routers, especially ones using manufacturer firmware, are rather fickle devices that often use outdated firmware. Neighbor routing tables freezing and cache breaks are common issues. Always, always, try a restart, or better yet, a hard reboot of the router during debugging of anything external access related to HA.

I have had some power outages recently, but have not done a restart myself, so I will do that now.

Brian

Update: Rebooted router and laptop HA is on, no change.

I currently only have the new instance of HA running and the IP is 192.168.1.107. Pictures might be valuable.


My laptop IP is 192.168.1.226

I am suspecting that my issues lie within my router settings. I went to a port forwarding site and verified that my port 8123 was NOT open. I am now looking into changing the settings of my ATT BGW210-700 router. It had worked fine previously.

Here is what I have in the router.


Not sure if I need the IP passthrough or not, but I believe I had in on old version when it was working.

Is your laptop IP reserved (is it a static IP)? That’s what you’ll want to do if not. HA is a host, so it needs a static IP on the local network.

Yes I did have it on static IP, but will have to check if it still is. What is easiest way to check?

Brian

Typically, in your DHCP/DNS settings. Albeit, so there’s no confusion and we’re on the same page - there’s two ways to give it a static IP. One way is on the laptop itself. The other is the router. I prefer using the router to assign/lease a static IP, instead of changing the interface card settings on the laptop. Do what you prefer.

I found it in the IP settings of router, went to allocate, clicked the one it was using and then saved. Now it says fixed allocation. In the above screenshot i sent earlier it says DHCP allocation. I am powering down HA and restarting. I may have to restart router too perhaps. I restarted HA and it still shows 8123 to be closed using the port checker. Forgot to mention earlier that I run Adguard, but I have it disabled. Never had a problem in the past, but figured I would eliminate it.

Brian

Now tbh… I don’t have personal experience setting up a Nabu subscription. I’m a very DIY type of person in this regard. I use Nginx Proxy Manager and a domain service for external access. So I don’t know anything about Nabu’s onboarding process other than what I can read in a quick dive. I’d assume there’s some type of permissions you gave them. Is there anything you can log into to check on Nabu’s side? You shouldn’t need to open ports according to their documentation. They are a proxying your connection. Did you enable remote access?

EDIT This sums it up. https://support.nabucasa.com/hc/en-us/articles/26474279202973-Enabling-remote-access-to-Home-Assistant#to-enable-remote-access-to-home-assistant

I had remote access enabled prior to it not working but now it says:

Your instance is not connected to Home Assistant Cloud

Remote address: Not available

Tried logging out and back in but nothing. Due to the fact that port 8123 is not open any more, I believe that is the culprit, but willing to try other stuff.

Is there anyone else using HA Cloud and an ATT BGW210 router on fiber that could possibly weigh in?

Brian

Take a good look at that link. You can login to Nabu’s Account page and activate remote access that way.

Here is what I am seeing.

Brian

is that from the Home Assistant Cloud page from your VM? Or is that from https://account.nabucasa.com/?

From https://account.nabucasa.com/

Not sure how to access Cloud page from VM

Alright, so you can access HA locally at http://192.168.1.226:8123? If yes, go to Settings > Home Assistant Cloud. Remote access should be enabled there.

That is my laptop’s address. My HA instance is the (http://192.168.1.107:8123/) address.

Ahh, yea… I see that now on the screenshot. Well good. So it’s accessible? Login and go to Settings > Home Assistant Cloud and check there.

No, under settings, HA Cloud is not visible.

That’s very strange… So the option is missing? Mine looks like this -