T-Mobile Home Internet Gateway

There are three ways to set a Pi with static IP. Two of them are wrong. Since you mentioned “config file”, I’ll assume it was done correctly.

Edit ‘dhcpcd.conf’
sudo nano /etc/dhcpcd.conf

Use the arrow keys on the keyboard to go to the bottom of the file. Find the line that starts with
interface eth0
and comment out that line and all that follow it.

Reboot the Pi
Connect the Ethernet from the Pi to the router.
You should now be able to find the Raspberry on your LAN. The router will assign it an IP address.

This is all doing thing the hard way. Do you have a recent snapshot tar file? In that case I would just start over with a fresh install of Home Assistant image for Pi:

Then copy the snapshot file into your backup folder and restore the snapshot. Done.

Ok thank you. I’m not sure if you can make any sense of my jumble previous comments but I did get to that point where HA asked to restore my snapshot. So I was able to access http://192.168.12.159:8123/onboarding.html but soon as I tried to restore my snapshot it failed. I’m guessing HA went to my old ip while the pi is on the new static one. How can I access HA with my current IP when my snapshot has a different static address stored?

Describe each step that you took to get here.
Do you have a snapshot tar file?

I appreciate all your help! Yes I have a snapshot of my system a day before all of this luckily.
I started over with a fresh install of HA on my drive and booted my Pi from usb.
http://192.168.12.159:8123/onboarding.html
Allowed me to upload a snapshot from onboarding.
I’m not sure if it finished restoring but shortly after clicking, that url didn’t respond.

http://homeassistant.local:4357
The observer shows the supervisor is connected

I have no clue what /onboarding.html is- I’ve never seen it.
Can you SSH into 192.168.12.159?
You need to FTP the snapshot tar file into the backup directory on the Pi. I can’t help you with where the backup directory is because every installation method, and there are a dozen, puts it in a different place.

In some installations it is a folder off the config folder.
Mine is in /usr/share/hassio/backup
Others have found backups in usbshare1-8/supervisor/backup/
Or you can brute force it with the find command:
*find . |grep backup

This might help you find the backup directory.
Go into the Home Assistant front end and in Supervisor, create a snapshot.
Then SSH into the Pi and enter
sudo find / -iname *.tar
The newest tar file is the snapshot you just made, and you will then see the location.

After you copy the backup snapshot tar file to the backups folder, go into Home Assistant and in the Supervisor, Snapshots you will see the old snapshot, and you can restore from there.

/onboarding.html is like a sign up/log in screen to make a HA or restore from snapshot.

I cannot ssh into 192.168.12.159

I onboarded as a new HA and saw my old snapshot ready in the supervisor panel.
Just like before from the onboarding screen and now from a new HA in the supervisor panel when I restore the url goes bad.

http://homeassistant.local/ or http://192.168.12.159/ doesn’t load with or without 8123.
Strangely, http://homeassistant.local:4357/ (Observer) shows the supervisor is connected.

I’m guessing HA went to my old ip while the pi is on the new static one. How can I access HA with my current IP when my snapshot has a different static address stored?

I can ping 192.168.12.159 successfully

Do you think this is part of the problem? Since my Tmobile router doesn’t have port forwarding, when I restore the snapshot my server port is expecting 443 but receives 8123 so nothing works?

Since that is the same network as your router then it got its IP from the DHCP server.

Restoring a snapshot does not change the IP address. I recently moved my HA from a Pi to an Intel NUC which had a different IP and the snapshot restore had me working in minutes.

What happens when you enter:
http://192.168.12.159:8123
on your browser?

ok that’s good then

and

I have a keyboard and monitor hook up so I can access the ha command line. I don’t know how this can help though

I asked, what happens?
How did you install Home Assistant?

Connection refused

And

Etcher image

That doesn’t say how you installed Home Assistant. Which image file- there are more than one. Are you installing HA on Raspian, on Ubuntu, on Debian? In a Docker? Or did you download HassIO or HassOS?

Sorry yes I flashed an image running a docker image

HassOs I believe

What happens when you enter:
http://192.168.12.159

Connection is refused.
When I enter https://192.168.12.159 it works!

Another problem that I never mentioned that was a major contributor to the solution has to do with this:

When I plug this back in, I plugged it into the usb 3.0 port instead of the 2.0 port. So that’s why it never showed up on the router list. Once I started making progress it’s because I wasn’t using the powered usb.