I recently installed a new smart switch which resulted in the power getting turned off to my router and raspberry pi 3 running hassio. Now I can’t log into home assistant. I have the duck dns add on. My windows pc can see hassio on the network and I can see my yaml files. I can also putty into hassio using hassio.local on port 22. I have port forwarding setup on my router for port 443. I suspect the ip address of hassio may have changed, but I can’t seem to find a way to figure out what the new ip address is. I thought I had it tracked down at one point and changed the port forwarding rule, but home assistant still won’t load from my phone or web browser. Can anyone tell me how to determine the ip address of hassio from windows or from putty? Any ideas on what the issue might be?
Your router will tell you what the external IP addrs is and you then need to put that into duckdns.
The router should also show the connected IP’s so you should be able to figure out which one is HA.
Also your internal IP may have changed if you haven’t set the router to static IPs or not set the lease of IPs to forever
On my routers status page I get…
External IP Addr
All internal connections…
My ip address under WAN setup --> DHCP matches what is in duck dns. I don’t know where to find other connected devices.
Try this…
Type ipconfig (or ifconfig on Linux) at command prompt. This will give you the IP address of your own machine. …
Ping your broadcast IP address ping 192.168.1.255 (may require -b on Linux)
Now type arp -a . You will get the list of all IP addresses on your segment.
The MAC will tell you what is connected.
I did that earlier. I then repeated the process with the raspberry pi running hassio unplugged. I saw how the list changed, and that seemed to indicate how the ip address changed. I then modified the port forwarding rule for my router, but things still don’t work.
Well each time you power off the pi you will get a new internal IP addrs so you need to either in the DCHP settings set the IP lease to forever and setup address resevation or set the DHCP to static, that way it won’t change.
I am not sure how to do those things. I have cycled the power on the raspberry pi over and over again when changing the config file and it has never been an issue until the breaker was turned off which also cut the power to the router.
Do I need to restart my router after changing the port forwarding or something like that? Actually, that seems like it was the cause of the issue in the 1st place…
You don’t normally have to restart the router, when you save the changes it should apply them, but you could try, however if you do remember to change the duckdns IP, you will have to do this everytime you power off the router.
duck dns seemed to have the correct ip. I am a bit confused here though. This is what I see:
My raspberry pi has a 192.XXX.X.XX ip address (from ip config)
duck dns has a 173.XX.XXX.XX ip address that matches the ip address found in the DHCP section of my router.
I don’t know what I would update in duck dns or what I would even change it to.
The 173.xx.xx.xx number should change everytime you reset or turn off the router as it’s give to the router by your ISP, it may stay the same but that’s quite rare. You change it in duckdns website if it changes after you reset/turn off the router. Where is says update IP.
FINALLY GOT IT!!!
The duck dns IP address is still good, I didn’t need to update it.
I also found that from a windows cmd window, you can type ping hassio and it will give you the IP address of hassio.
The hassio IP address did change which required me to delete and re-create my port forwarding rule. When it was recreated with the updated hassio IP address I accidentally changed the port forwarding from 443->8123 to 443->443. Fixed that and I am off to the races again.
Glad you got it sorted 
None of the unknown devices on my router point to Hassio. Any other pointers on determining what IP Hassio is using?
Monitor and keyboard on the hassio machine?
Edit: Nope, of course not. His setup is on Windows so that may or may not be the difference. I pulled up ipv4 and the information I put in was there, saved, but neither hassio.local nor the ip address worked to load HA. Now nothing works and I’ve been trying it to work for the last 4 hours since posting this. I did learn, however, all I had to do from the “hassio >” prompt was type “homeassistant info” to get the ip address. Its time for bed and I have to go get a ladder to pull the battery from a smart vent so we don’t have to watch it blink all night. AWESOME
For anyone that comes across this post by searching (as I did) I just watched a video on the youtube channel “The Hookup” trying to figure out another issue I have. This video, at about 7:45 lays out how to look at the ip address and set a fixed ip address. My machine is rebooting now, but I think this should take care of this issue. When I pulled up ipv4 information it didn’t show an address at all, now I have one chosen and hopefully my Fire tablet can look at it as it couldn’t pull up hassio.local. On to the next issue!
Edit: Nope, of course not. His setup is on Windows so that may or may not be the difference. I pulled up ipv4 and the information I put in was there, saved, but neither hassio.local nor the ip address worked to load HA. Now nothing works and I’ve been trying it to work for the last 4 hours since posting this.
This thread is the first result when googling “hassio find ip address”
- Access the hassio console as “root”
- Drop into the shell with
login - Use the “nmcli” configuration tool:
nmcli con show "HassOS default"and page-down until you find it
Awesome, this worked. Thank you!
sigh this didn’t work for me. Im stuck with an IP Addr Show that is wrong but when I go to NMCLI it is correct. Weird right? What am I doing wrong?