I got http://192.168.12.159:8123/onboarding.html to load! But when I restored from snapshot, I don’t know if it finished and now nothing is working. I think this is because I was using a static IP before too.
My device ip isn’t matching my HA ip?
Yes, because whatever network instructions you put in cmdline.txt on the SD card gets copied into /etc/dhcpcd.conf. When you configured to boot from USB disk, you copied /etc/dhcpcd.conf from the SD card.
Can you SSH into the Raspberry Pi?
1 Like
I read the manual on your router and the various forum posts. (Recommended)
This isn’t currently possible on your T-Mobile router. There is no access to DHCP server config or IP allocations. It may come in a firmware update later.
I don’t think there is a port forwarding option either which will cause you other issues.
1 Like
Got it. I could when the micro SD was inserted. What should I do once I ssh in?
This sounds really bad. What do you suggest I do then?
I was able to create a static ip for my pi that worked from what I did in the website posted above.
Use a different Internet provider or await a firmware update for the router and hope they add these features. Apparently T-Mobile have indicated they will be adding a bridge (pass through) mode to the capabilities which would allow you to use your own additional router internally.
In the meantime, yes you can create a static IP in the 192.168.12.x space that will work for you for internal LAN access.
External WAN access will likely be a problem. I believe there is an add on for HA discussed on this forum that offers a VPN like feature via an external provider that might work for you with a dynamic HA IP address and a dynamic WAN address. It doesn’t need port forwarding presumably because the connection is instantiated from within your LAN.
Maybe this one ? Not recommending as I don’t use it but it maybe works for you.
Hass.io Add-on: SocketXP - Home Assistant Remote Access (No DDNS + No Port Forwarding Required)?
1 Like
Ok I plan to use Ethernet access only. Thank you
Any idea how to access my HA with my static ip? I got 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
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.
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