Failed to load no matter what I remove from config… it was streaming, then scripts, then darksky. After rollback to 0.100.3 it is the same… fails. What to do now… I noticed some cryptography, libav things un and installing…
Ok, after about 20 mins the prev version loaded again.
1 Like
My configuration checks out ok with no errors, and I’m not seeing anything unusual in the logs, but my 2 attempts to upgrade have failed as others have already noted.
I get a Failed config
General Error: light.led_strip
Not sure if it crashes at the entity setup or on a scene definition but 101.0 will not start-up with it.
in config light.led_strip looks like this.
light:
- platform: limitlessled
bridges:
- host: !secret ll_host
version: 5
port: 8899
groups:
- number: 1
name: 'Entry Light'
fade: on
- number: 2
name: 'led strip'
fade: on
- number: 3
name: 'Hallway Light'
fade: on
WITH
scene:
- name: romantic
entities:
light.tabletop_lamps:
state: on
brightness_pct: 15
rgb_color: [220, 20, 60]
light.led_strip:
state: on
brightness_pct: 15
rgb_color: [220, 20, 60]
- name: movie
entities:
light.led_strip:
state: on
brightness_pct: 10
rgb_color: [65, 105, 225]
light.tabletop_lamps:
state: off
- name: bright
entities:
light.tabletop_lamps:
state: on
brightness_pct: 100
rgb_color: [255, 255, 255]
light.led_strip:
state: on
brightness_pct: 100
rgb_color: [255, 255, 255]
- name: nite
entities:
light.tabletop_lamps:
state: on
brightness_pct: 10
rgb_color: [245, 245, 245]
light.led_strip:
state: on
brightness_pct: 10
rgb_color: [245, 245, 245]
- name: casual
entities:
light.tabletop_lamps:
state: on
brightness_pct: 50
rgb_color: [255, 255, 255]
light.led_strip:
state: on
brightness_pct: 50
rgb_color: [255, 255, 255]
…
Same error as others have reported
"No module named ‘hass_frontend’
Okay,
with 0.101.x it needs to be changed to:
- name: My Scene
entities:
cover.neq1368021:
state: closed
current_position: 0
cover.neq1368092:
state: open
current_position: 30
1 Like
No module named ‘hass_frontend`
I was able to resolve this issue by moving the frontend directive
frontend was moved immediately after the homeassistant block
eg
OLD
homeassistant:
logger:
frontend:
config:
history:
the following passes config checks
NEW
homeassistant:
frontend:
config:
logger:
history:
Upgrade Successful
These solved the problem:
in configuration.yaml:
host: 127.0.0.1
When registering the discovered integration:
host: 127.0.0.1
username: glances
password:
port: 61209 (I had problem to setup 61208 port).
The same host address used in Glances config.
Now it works as before the upgrade.
1 Like
Got following error 
[22:39:19] INFO: Installed Home Assistant 0.101.0
[22:39:19] INFO: Making a copy of your configuration for checking...
[22:40:24] INFO: Checking your configuration against this version...
[22:54:55] ERROR: The configuration check did not pass!
[22:54:55] ERROR: See the output below for more details.
INFO:homeassistant.util.package:Attempting install of colorlog==4.0.2
Testing configuration at /tmp/config
INFO:homeassistant.util.package:Attempting install of aioesphomeapi==2.4.2
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20191025.1
INFO:homeassistant.util.package:Attempting install of aiofiles==0.4.0
INFO:homeassistant.util.package:Attempting install of backoff==1.8.0
INFO:homeassistant.util.package:Attempting install of aiogithubapi==0.2.0
INFO:homeassistant.util.package:Attempting install of integrationhelper==0.2.2
INFO:homeassistant.util.package:Attempting install of HAP-python==2.6.0
INFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of aiohue==1.9.2
INFO:homeassistant.util.package:Attempting install of sqlalchemy==1.3.10
INFO:homeassistant.util.package:Attempting install of av==6.1.2
INFO:homeassistant.util.package:Attempting install of python-telegram-bot==11.1.0
INFO:homeassistant.util.package:Attempting install of mutagen==1.42.0
INFO:homeassistant.util.package:Attempting install of distro==1.4.0
INFO:homeassistant.util.package:Attempting install of homeassistant-pyozw==0.1.4
INFO:homeassistant.util.package:Attempting install of gTTS-token==1.1.3
INFO:homeassistant.util.package:Attempting install of bomradarloop==0.1.3
INFO:homeassistant.util.package:Attempting install of python-forecastio==1.4.0
INFO:homeassistant.util.package:Attempting install of construct==2.9.45
INFO:homeassistant.util.package:Attempting install of python-miio==0.4.6
INFO:homeassistant.util.package:Attempting install of PyTransportNSW==0.1.1
INFO:homeassistant.util.package:Attempting install of psutil==5.6.3
Failed config
homeassistant.packages.history.history:
- Package history setup failed. Component history No module named 'sqlalchemy'
- history: None
homeassistant.packages.logbook.logbook:
- Package logbook setup failed. Component logbook No module named 'sqlalchemy'
- logbook: None
Successful config (partial)
homeassistant.packages.history.history:
homeassistant.packages.logbook.logbook:
Small problem following maj. On Lovelace my calendar does not just give the state.
[%key_id:state::default::on%]
same issue here on check config
what can be the cause?
Failed config
General Errors:
- Platform error notify.html5 - No module named 'hass_frontend'
- Component error: history - No module named 'sqlalchemy'
from what I have been following with the MyQ component. there is a fix. hopefully it will be in the next minor release.
What have you been following?
Ok - once again, my mistake. I failed to remove the api_password which has been deprecated.
Once I removed that line, the upgrade worked.
1 Like
I found I had to update to v0.101.0 before I was able to to ‘check config’.
Once updated config check now works again.
A lot of people have issues with sqlalchemy in this HA update.
List of changes mentions sqlalchemy upgrade twice:
I wonder if that’s got something to do with it 
Same issue as reported by others:
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20191025.1
Failed config
General Errors:
- Component error: logbook - No module named ‘sqlalchemy’
- Platform error notify.html5 - No module named ‘hass_frontend’
Successful config (partial)
Exact the same errors, don’t think it’s an issue though… Did you already upgrade?
I get this in the config checker:
WARNING: You are using pip version 19.2.2, however version 19.3.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
I’m running Ubuntu 18.04 on a NUC. Do I execute the above command in the homeassistant container or at the OS level?
Failed config
General Errors:
- Component error: logbook - No module named 'sqlalchemy'
- Component error: mobile_app - No module named 'hass_nabucasa'