Hassio .99.2
Fire Tablet 8"
Not sure why, but when I load my hassio URL (https) in Fully Kiosk Browser, I just get a “Webpage Not Available” with the net::ERR_FAILED message and the little android robot upside down in the upper left.
TileBoard is working fine on Chrome, but I can’t get a Kiosk mode in Chrome on the tablet.
Ideas?
Hi Arretx,
I have the same issue. Since 0.99 update I cannot load hassio in Fully Kiosk Browser. The message I get from Hassio is that webview version is outdated .59. I have assumed that this is what is causing the issue. I haven’t managed to update webview and haven’t managed to find a solution either I’m afraid
Regards,
M
have you tried 99.3, there was a fix for fully kiosk, not sure if it will fix this but worth a try
I saw that there was work being done to fix the problem, but wasn’t sure if this was going to be a HA update fix or something else. Did the 99.3 release notes mention something about this?
Thanks Adrian. All works fine under 0.99.3.
I must be doing something wrong. I still see Webpage not available net::ERR_FAILED.
Okay, I got in but I had to use the local network IP address : 8123 with https:// in order for it to work.
And now, I’m finding that Compact Custom Header is ignoring the user’s restrictions.
I’ve recently discovered a similar issue with Fully Kiosk Browser (FSK). Approximately 3 days ago (10/5/2019), my Fire 7" 5th generation stopped displaying HA via FSK. I did a complete reset of the tablet, reloaded the most recent version of FSK, and I am still unable to have the Lovelace interface load. The screen shows HA icon and initializing…
I can not get HA loaded with hassio.local or https! address. The previous webpage was set to http://IP:8123. I loaded a new FSK app on a Fire 7, 7th generation with the exact same results. Interesting, I have another Fire 7 (7th gen) that still works running FSK 1.29. Again, this system was working flawlessly until recently and there have been no recent system updates. Current version HA 99.4Has anyone else experienced this issue lately or knows of a solution? Any guidance would be much appreciated.
sorry to bring this issue back up but it seems like this is the same error I’m running into, with the same hardware. I’m a complete beginner to this and i don’t even know what question to ask to get any help.
Papierus; I am having exactly the same issue on Fully Kiosk. Currently updating the Fire OS. I know this is an old topic but was it ever resolved?
