Yet another weird bug just happened on me.
From some point I lost access to HASS Frontend from Android devices.
It just goes into “Error, Connection timeout” from any android phone. I tried to clear browser cache and use different browser.
I can still access HASS from my PCs and windows-based devices both from wifi and from a wired connection.
Raspberry pi itself is connected wirelessly. Wifi connection is solid, that I did check. And if there was a problem, I think I would not have access to it from Windows machines, right?
I can, however, access WebMin of this same Raspberry Pi from any device
So… Any ideas, what possible causes could be there?
Thanks a lot.
Maybe a confusion between http:// and https:// access?
Do you access hass with the local address (ip) ?
Do you use SSL encryption?
Yes, I use local address.
No, I don’t use SSL, but just to be sure, I did try it with http and https, no result.
I can, however, access WebMin of this same Raspberry Pi from any device.
And oooops, I forgot to mention that I’m running it from Raspberry Pi, of course, and use Hassbian.
Did you try to restart your router? It seems like a routing problem more than a problem with hass alone.
Did you maybe set a port forwarding on hass port?
Also check if you see any entry in log when you try to access it from your smartphone.
That was the first thing I did 
I did not port-forward HASS (not gonna do it until I setup SSL), and port forwarding should not interfere with direct LAN IP connections anyway, since I specifically type in the local ip of my pi.
I did have some power supply issues before, but I just reconnected and rebooted pi right now, and there’s no red flashing light at all! 
Which is even new to me. Guess there was an issue with how tightly the cable was plugged in. Yet the problem persists.
I see no relevant errors in home-assistant.log file, but I remember it’s possible to view the output of hass service itself, but I can’t find anywhere how to do it again =\
With pi account:
sudo journalctl -fu [email protected]
Depending on your install it might be different (I’m under Docker…).
But that’s a weird problem, it should work from any device on the network.
Did you maybe setup a conditional VPN on your router? (For example I have certain device connecting a French VPN to access localized content).
Or maybe a VPN/Proxy or AddBlocker setup on your smartphones?
Silly lazy me, found this command here right after you posted it: https://home-assistant.io/docs/hassbian/common-tasks/
Apparently the problem just resolved itself. After I connected to the output of the process to see the errors, I tried to reach it from my phone again, and saw the message “Serving websocket to…”… I was puzzled as to “how this is an error” then looked at my phone and was like “Whaaaa!?”, I saw the Frontend.
And even the SSH is working perfectly fine now, I had issues with slow-typing in there before. Copy-pasting was pasting text word-by-word, slowly.
Weird how this issue was actually there for about a week now, I just did not have time to solve it, but I did reboot router a few times, and did reboot Pi multiple times throughout the week, hoping for it to fix itself after reboots.
Huh, I guess Ill have to keep an eye on it. Still gotta find out what it was, I want my HASS stable
Thanks, touliloup, for you time and Assistance
Gotta say, that HASS community seems to be the most friendly community I ever saw yet.
Glad it work for you 
I used to have a problem also accessing it from a particular phone but I think it was due to access through duckdns external address and the router not being rebooted.
I guess we all suffer the same problem at some point, that could explain it
Well, it keeps happening. I can’t figure out why. Sometimes I can access it from my phone, sometime I can’t. And each time it stays accessible from Windows PCs.
Worth mentioning that I did a clean install of the latest Hassbian version now. And I still get the same issue.
Most of the time I can access it from phones for a while after I reboot pi. But then I can’t again.
This time I started losing access to Webmin as well. But again, it’s all accessible from PCs. Issue is only with two android devices, one running Cyanogenmod, latest android version, another one MIUI android 6. Galaxy note 3 and Redmi Pro 4, I don’t think they share anything but Android system core.
If it was routing issue, I guess I would lose access to it from any wifi device at least, not just android phones?
I can still access router from any phone, as well as my NAS server (which runs a few nginx pages, and lots of servers on different ports, none of which inteferes with 8123, even if it could be an issue…)
That’s frustrating.
Router is Asus RT-AC66U. Trying to disable QoS. Apart from the fact that I pulled the contents of my router out to cool it down with a fan, QoS is the only thing that comes to mind that can interfere with traffic…
UPDATE:
Well, no. Turning QoS off did not help
UPDATE 2:
Log shows nothing. Journalctl - when I try to refresh HASS page on the phone, or open it, it shows nothing. When I try to open it from PC it does the usual “Serving /api/websocket to…”… ugh
One more update. Which makes everything even more weird.
Lumia 950, Windows Phone 10 - HASS frontend works perfectly fine.
What’s wrong with these android devices, ugh. And yes, I tried turning mobile data completely off, leaving just wifi.
I have almost the same problem but in my case, i can open if i’m via wifi (internal or external network) but can’t open if i’m in mobile network.
The login page opens but then i can’t connect.
I’ve tried disabling the api paasword but it’s the same problem.
I’m not sure what helped in the end, but it works fine now. So all steps attempted:
-
I had a fan to cool the router, and I later found out that it’s magnetic field was actually interfering with wifi for devices with weaker wifi recievers like RPI or Perception Neuron suit. Proved by testing.
-
I did make sure to secure the cable connection to RPI, and to use a 2.3A power supply
-
Rebooted router a couple times, and reset it to factory defaults, then uploaded settings again (In Asus-WRT you can save all settings in a file)
-
Installed latest Hassbian from scratch. I was afraid that it would be a hassle to set things up again, but actually once you did it once, and know what you’re doing, it takes about an hour, especially if you have your config files at hand, and make use of Hassbian scripts to install samba and open zwave and whatever else you need from that package.
Everything works now so far.
Did/do you have a vpn anywhere in the mix, they can mess up local network device to device connections as can some anti-virus software.
No. No VPN anywhere in the mix. Never used it.