Bad wording from me.
It did upgrade to 101.2, but HASSIO stopped (the log stopped populating) and the fronted never showed.
After trying and trying I was able to revert to 100.3
That’s the last part of the log (full log does not fit in this thread, too long)
e 475, in _check_closed
raise RuntimeError(‘Event loop is closed’)
RuntimeError: Event loop is closed
The warning isn’t the issue, but it’s followed by an error on the same component. I have no idea if it’s related but I would try to disable it as one error might cause others.
I disabled all custom component and have the same errors, hassio won’t load the front end, and I think it halts
So the problem lies in my configuration file. Is the below part of configuration correct for 0.101.2 (it works for 0.100)???
homeassistant:
name: Home # Name of the location where Home Assistant is running
latitude: !secret latitude
longitude: !secret longitude
elevation: 83
unit_system: metric
customize: !include customize.yaml
packages: !include_dir_named packages
whitelist_external_dirs:
- /config/www
- /config/python_scripts
- /share
frontend:
api:
http:
# api_password: !secret api_password
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
base_url: !secret base_url
some other folks had problem updating by having api_password in various files, I checked and I have none.
Really no other clue
This is getting wierd
The below configuration WORKS with 0.101.2
homeassistant:
name: Home
latitude: !secret latitude
longitude: !secret longitude
elevation: !secret elevation
unit_system: metric
time_zone: Europe/Rome
customize: !include customize.yaml
packages: !include_dir_named packages
whitelist_external_dirs:
- /config/www
- /config/python_scripts
- /share
frontend:
api:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
base_url: !secret base_url
If I add this single line to configuration.yaml
groups: !include groups.yaml
and the file groups.yaml contains
dining_room_lights:
name: Dining room lights
view: false
entities:
- light.chandelier_lights
- light.ceiling_lights
entrance_lights:
name: Entrance lights
view: false
entities:
- light.foyer
- light.foyer_ball_lamp
jim_ceiling_lights:
name: Jim ceiling lights
view: false
entities:
- switch.light_jim_ceiling_one
- switch.light_ijim_ceiling_two
jim_online:
name: Jim devices online_offline
entities:
- device_tracker.7802f8f27xxx
- device_tracker.3059b7143xxx
james_online:
name: James devices online_offline
entities:
- device_tracker.30f7c57a0xxx
- device_tracker.24a07455xxx
john_online:
name: John devices online_offline
entities:
- device_tracker.ljohn
- device_tracker.484baab80xxxx
I receive tons of errors in 0.101.2 (it was perfectly working in 0.100.3) … where is the problem???
something about indentaton changed with 0.101 ??
I don’t know if anything changed and I don’t know what the actual ‘rules’ are but I see you have some inconsistent (but clearly not wrong) indenting.
FWIW I always indent like this:
jim_online:
name: Jim devices online_offline
entities:
- device_tracker.7802f8f27xxx
- device_tracker.3059b7143xxx
Not like this:
jim_ceiling_lights:
name: Jim ceiling lights
view: false
entities:
- switch.light_jim_ceiling_one
- switch.light_ijim_ceiling_two
I wouldn’t begin to know if that is the issue and I would be surprised if it were, but it’s worth a try maybe?
I spot similar error to what I get. Can you run hass --script check_config and check if it executes without errors?
I opened a bug report here: https://github.com/home-assistant/home-assistant/issues/28504
How to run that script, under core-ssh?
And before or after the upgrade
I run HA in a virtual environment and run it like hass --script check_config in the venv. You can have a look here https://www.home-assistant.io/docs/configuration/troubleshooting/ about how to run that script in your environment. And yeah, run it after the upgrade.
Ok for whoever has HASSIO, thats the command in core-ssh
hassio homeassistant check
I will do it next weekend, I have a working environment and to check that would need to put HASSIO down for an hour, which will cause me problem with family 
I tried several times to upgrade from 0.100.1 to 0.101.2, without any luck. First time I have issues doing upgrades with hass.io.
It looks like everything is OK (downloading packages), then after some time hass;io restarts and I’m basically back on 0.100.1.
I ran ‘hassio homeassistant check’ and the command completed without any errors being reported.
I had the same problem of not being able to upgrade. Mine was due to API password still in the config file commented out http: and the API password and upgrade went fine.
Yes ! Just tried that (found in another post) and it indeed solved the issue.
I basically did add the auth_providers key under ‘homeassistant:’ in the configuration.yaml, having one entry for homeassistant auth provider and one for the legacy API password and voilà, upgrade problem solved.
So you commented out
http:
??
Sorry can you show that part of configuration, that is working for you
“hassio ha check” against 0.100.3 showed my config was fine - but running the “heck Home Assistant configuration” hassio image against 0.101.2 did find some issues. Trying to solve them now and see if this fixes my issues.
Same issue here - cannot update from 0.100.3 to 0.101.2
Maybe this in the release notes explains why it is not working:
The support of configuring the auth providers for API Password and Trusted Networks via the HTTP configuration is also removed. It now needs to be configured in the auth provider section (docs).
In configuration.yaml file under http: section try commenting api_password. In my case it is:
# api_password: !secret HA_Password
Trying right now, hope that will help.
Update: after commenting api_password update worked fine
I think this maybe the issue I am struggling with… When i run the config check, I get errors for frontend_hass and found this issue on github https://github.com/home-assistant/home-assistant/issues/28361
EDIT: I posted without seeing Serg’s post 1 up. It’s the same issue.