tachioma
(John Dixon)
July 10, 2019, 7:30pm
1
So, I followed the below to install on my fresh ubuntu 18.04 box. Worked a treat. I spent all day getting it setup with mqtt, my cameras, all my devices etc…
sudo -i
apt-get install software-properties-common
add-apt-repository universe
apt-get update
apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
curl -fsSL get.docker.com | sh
And to install Hass.io the one below. That one is used also for other distributions.
curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
Rebooted it so I could whitelist a directory for camera snapshot and now i get this :
No front end, no nothing. Anyone seen this before. I’m pretty sure i didn’t do anything, happy to provide any logs.
TIA
tmjpugh
(Tmjpugh)
July 11, 2019, 12:36am
2
qemux86-64-Homeassistant container need port 8123 for frontend
I dont see any of your container showing 8123
This is incorrect. Network mode = host doesn’t map any ports. This isn’t the issue.
@tachioma , please look at the home assistant log file. Guarantee you have a configuration issue.
tachioma
(John Dixon)
July 11, 2019, 11:18am
4
ok so, update this morning. I stepped through the config line-by-line and it WAS this that broke it :
homeassistant:
whitelist_external_dirs:
- '/www/camera/images'
Rebooted multiple times, no more issue since i hashed it out. Funny thing being there are no error messages anywhere as to why. The syntax is correct right? Even if it wasn’t… why would it stop the entire system from coming up correctly?
In your log file there would have been a statement that the path doesn’t exist.
syntax is correct, path is not, unless you SPECIFICALLY created a DIRECTORY INSIDE the container called /www
If you are trying to whitelist your www directory inside the config directory you need to call it correctly.
/config/www
tachioma
(John Dixon)
July 11, 2019, 12:58pm
6
Hey, thanks guys.
Yes there was that - although i suspected that may have been before i rebooted. Couldn’t tell at the time. Still odd that it broke the whole system :
So to clarify then :
Physical location : /usr/share/hassio/homeassistant/**www**/**sounds**
Virtual location : /config/**www**/**sounds**
not really. it’s trying to use a path that doesn’t exist.
Yes
tachioma
(John Dixon)
July 11, 2019, 3:51pm
8
That did it!
Thanks a bunch @flamingm0e .
finity
July 11, 2019, 7:06pm
9
For future reference all HA logs are reset the second you hit the restart button. If it’s in the log then it is from the current HA session.