I am able to connect to the device using PuTTY and configure it, but when I attempt to login by using hassbian.local:8123 in my web browser, it fails to connect. Any idea what might be causing this issue?
hasbian.local will only work on the machine itself - the fact that you are using putty leads me to believe you might be trying to access hass from a remote browser in which case you will need to use the IP address of the pi, instead of hasbian.local.
Thanks for the quick response! The pi and the machine I am using are connected to the same switch, which I thought would allow hassbian.local to work. I tried using the pi’s ip address in place of hassbian.local, no no avail.
Did you include the :8123 along with the IP address?
Yes. I used ‘ip addr’ in putty to get the address, is that the correct way?
Yes that works but you need to be sure you are using the correct address - it should be the one for eth0 if you are connected via a switch and not wireless. If you paste the output I’ll let you know which URL you should be using.
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:5a:30:f1 brd ff:ff:ff:ff:ff:ff
inet 170.140.230.64/21 brd 170.140.231.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::f99a:856d:41a0:1d5d/64 scope link
valid_lft forever preferred_lft forever
This site can’t be reached
170.140.230.64 refused to connect.
What address are you using to connect to the pi with putty?
That looks more like an internet addr or gateway addr.
Most routers use 192.168.x.x for local ip addrs
Yes, I thought it was strange too.
I used hassbian.local in putty to connect to the pi.
Also 170.140.xxx.xx is the ip for all local machines on the network. For reference, the local ip of the machine with putty is 170.140.230.63
What does your router say is the local ip of the pi, i’m assuming x.x.x.64? Then assuming you are not using ssl then Aimc is right about the IP:8123.
Have you cleared the browser cache and can you ping the pi ip?
Also is HA running on the pi (ps -aux and look for HA in the output).
Ping to the pi worked, but I don’t think HA is actually running on the pi.
try reading the log file to see if anything came up that caused it for error and stop
I can’t seem to find the log file. I think the issue is in hass starting up (or failing to) on the pi.
Try starting HA manually in the ssh window, not knowing what type of install you are using I can’t help with that, but if AIO then something like …
sudo systemctl restart home-assistant.service
or
sudo systemctl restart [email protected]
depending on which AIO you may be using.
Have you tried it on multiple devices, I had a lot of trouble in the early days where specific devices wouldn’t work. Turned out it was something weird the router was doing where if you accessed it through wi-fi it wouldn’t work if you then tried to use the same device over a hard wire until the next day. Changed routers and all good now.
My work VPN does still stop it even though it’s only meant to tunnel specific traffic.
The second syntax of restart command seemed to work (or didn’t give an error message), but hass still does not show up in the list of processes with ps -aux.
Also, I have Samba installed and hassbian appears as a device on my network, but I am unable to access the device.
I will check if I have another pi to try out different hardware. Is it possible that being on a university network might be affecting it too? (170.140.xxx.xx)