Home Assistant release with the issue:
Version 0.100.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Debian Linux (buster)
Docker 19.03
Official docker image from docker hub
Integration:
Description of problem:
After starting the docker container, docker logs report hass starting up fine. When browsing to srvip:8123
, I am asked to create an owner user. This works fine and some user details are stored in /config/.storage/auth
.
I am then forwarded to an onboarding page despite having configured these details in my config. After entering data (or leaving the defaults), pushing next leads to a browser popup with error message "FAIL". I cannot get any furter, even after various retries and attempts to delete .storage in config dir. Home assistant log says
2019-10-12 23:12:56 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140281321695632] Received invalid command: config/core/update
The home-assistant_v2.db
file gets created.
Problem-relevant configuration.yaml
entries and (fill out even if it seems unimportant):
homeassistant:
name: Home
latitude: !secret lat_home
longitude: !secret lon_home
elevation: 189
unit_system: metric
time_zone: Europe/Berlin
# Enables the frontend
frontend:
http:
# Checks for available updates
updater:
# Discover some devices automatically
discovery:
# Allows you to issue voice commands from the frontend in enabled browsers
conversation:
# Enables support for tracking state changes over time.
history:
# View all events in a logbook
logbook:
# Track the sun
sun:
Traceback (if applicable):
Additional information:
The same problem on similar system
Have you tried to start without a configuration.yaml
? This made it work for me.
If you could confirm, we could close the issue here.
No. It`s not working for me. I have used docker+ha on ubuntu 16.04 and 18.04. Then i installed python3.7 and install HA with pip3. And all the time i get the same issue.
And i even tryied to run HA 0.100.1 then 0.99.3 and nothing changed. What am i doing wrong? P.S. Ubuntu was clean installation every time(i used VM checkpoints)
Problen solved. Don`t know how. (:
Ok, let's close it for now since there is not much to work from in this issue + both of you have it resolved.
For anyone coming across this, for me the solution was to enable config:
in my configuration. Apparently having the UI but not allowing the UI to make configuration changes causes this.
Similar errors when starting up and trying to onboard on a new instance within docker:
Received invalid command: config/core/detect
Received invalid command: config/core/update
Needed these 2 in config/configuration.yml
to get started.
# Enables configuration UI
config:
# Enables the frontend
frontend:
Most helpful comment
For anyone coming across this, for me the solution was to enable
config:
in my configuration. Apparently having the UI but not allowing the UI to make configuration changes causes this.