core: Cannot upgrade to 0.105.x from 0.104.3

The problem

Upgrade to 0.105.x from 0.104.3 consistently fails since the launch of 0.105.0.

Environment

  • Home Assistant release with the issue: 0.105
  • Last working Home Assistant release (if known):
  • Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
  • Integration causing this issue:
  • Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

supervisor’s log:

20-02-06 14:04:43 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.105.2
20-02-06 14:04:43 INFO (SyncWorker_19) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.104.3 to homeassistant/raspberrypi3-homeassistant:0.105.2
20-02-06 14:04:43 INFO (SyncWorker_19) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.105.2.
20-02-06 14:09:41 INFO (SyncWorker_19) [hassio.docker.interface] Stop homeassistant application
20-02-06 14:10:35 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
20-02-06 14:10:35 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/sabeechen/hassio-google-drive-backup repository
20-02-06 14:10:35 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
20-02-06 14:10:38 INFO (MainThread) [hassio.store] Load add-ons from store: 63 all - 0 new - 0 remove
20-02-06 14:10:43 INFO (SyncWorker_19) [hassio.docker.interface] Clean homeassistant application
20-02-06 14:10:44 INFO (SyncWorker_10) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.105.2
20-02-06 14:11:23 DEBUG (MainThread) [hassio.api.security] Passthrough /supervisor/ping
20-02-06 14:11:24 DEBUG (MainThread) [hassio.api.security] /homeassistant/options access from Home Assistant
20-02-06 14:11:24 DEBUG (MainThread) [hassio.api.security] /supervisor/options access from Home Assistant
20-02-06 14:11:24 DEBUG (MainThread) [hassio.api.security] /homeassistant/info access from Home Assistant
20-02-06 14:11:24 DEBUG (MainThread) [hassio.api.security] /ingress/panels access from Home Assistant
20-02-06 14:11:25 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
20-02-06 14:14:35 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-02-06 14:24:39 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
20-02-06 14:24:39 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
20-02-06 14:24:39 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.104.3
20-02-06 14:24:39 INFO (SyncWorker_13) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.105.2 to homeassistant/raspberrypi3-homeassistant:0.104.3
20-02-06 14:24:39 INFO (SyncWorker_13) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.104.3.
20-02-06 14:24:40 INFO (SyncWorker_13) [hassio.docker.interface] Stop homeassistant application
20-02-06 14:24:41 INFO (SyncWorker_13) [hassio.docker.interface] Clean homeassistant application
20-02-06 14:24:42 INFO (SyncWorker_2) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.104.3

Tried to check configuration using Hassio’s add on, it fails with the following log, which to me does not seem to come from the configuration itself (check succeeds for 0.104.3).

starting version 3.2.8
[08:35:33] INFO: Don't worry, this temporary installation is not overwriting your current one.
[08:35:33] INFO: Installing Home Assistant: latest...
[08:35:33] INFO: Please be patient, this might take a few minutes...
WARNING: You are using pip version 19.2.2, however version 20.0.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
[08:38:57] INFO: Installed Home Assistant 0.105.2
[08:38:57] INFO: Making a copy of your configuration for checking...
[08:39:06] INFO: Checking your configuration against this version...
[08:44:00] ERROR: The configuration check did not pass!
[08:44:00] ERROR: See the output below for more details.
INFO:homeassistant.util.package:Attempting install of colorlog==4.1.0
Testing configuration at /tmp/config
INFO:homeassistant.util.package:Attempting install of python-nmap==0.6.1
INFO:homeassistant.util.package:Attempting install of getmac==0.8.1
WARNING:homeassistant.components.device_tracker:The 'hide_if_away' option (with value 'False') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
INFO:homeassistant.util.package:Attempting install of pytile==3.0.1
WARNING:homeassistant.components.device_tracker:The 'hide_if_away' option (with value 'False') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
INFO:homeassistant.util.package:Attempting install of av==6.1.2
INFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20200130.2
INFO:homeassistant.util.package:Attempting install of defusedxml==0.6.0
INFO:homeassistant.util.package:Attempting install of netdisco==2.6.0
INFO:homeassistant.util.package:Attempting install of hbmqtt==0.9.5
INFO:homeassistant.util.package:Attempting install of paho-mqtt==1.5.0
INFO:homeassistant.util.package:Attempting install of pyatmo==3.2.2
ERROR:homeassistant.scripts.check_config:BURB
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/scripts/check_config.py", line 204, in check
    async_check_ha_config_file(hass)
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 579, in run_until_complete
    return future.result()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/check_config.py", line 129, in async_check_ha_config_file
    config = config_schema(config)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 386, in validate_mapping
    cval = cvalue(key_path, value)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 373, in validate_mapping
    new_key = ckey(key_path, key)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/config_validation.py", line 659, in validator
    value = config[key]
TypeError: string indices must be integers
Fatal error while loading config: string indices must be integers
Failed config
  General Errors: 
    - string indices must be integers

Successful config (partial)

Additional information

A forum thread is open with several people having the same issue: https://community.home-assistant.io/t/cant-update-hassio-to-0-105-x/169466

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 4
  • Comments: 29 (7 by maintainers)

Most upvoted comments

for me commenting out netatmo did not work, but updating to the new configuration did !

netatmo:
  client_id: YOUR_CLIENT_ID
  client_secret: YOUR_CLIENT_SECRET
+2
vlebourl on Feb 10, 2020

No success with temporary removing Netatmo config. Still no way to upgrade to 0.105.2

There must be something in the system config that is causing this issue…

+2
HFeenstra on Feb 8, 2020

for me commenting out netatmo did not work, but updating to the new configuration did !

netatmo:
  client_id: YOUR_CLIENT_ID
  client_secret: YOUR_CLIENT_SECRET

This worked also for me even I haven’t anymore the Netatmo configuration.

+1
naamah75 on Feb 10, 2020

?? What is the solution?? Or, what causes the not upgrading? Why closed?

+1
HFeenstra on Feb 8, 2020

For me, not starting up the frontend was fixed by removing the netatmo configuration (before I am going to fix it as described in the release notes).

+1
marcschumacher on Feb 8, 2020

I have the same problem but my error is different

2020-02-07 11:36:30 INFO (SyncWorker_9) [homeassistant.loader] Loaded alarm_control_panel from homeassistant.components.alarm_control_panel
2020-02-07 11:36:30 ERROR (SyncWorker_9) [concurrent.futures] exception calling callback for <Future at 0x7fe4c473da50 state=finished returned Integration>
Traceback (most recent call last):
  File "/usr/lib/python3.7/concurrent/futures/_base.py", line 324, in _invoke_callbacks
    callback(self)
  File "/usr/lib/python3.7/asyncio/futures.py", line 362, in _call_set_state
    dest_loop.call_soon_threadsafe(_set_state, destination, source)
  File "/usr/lib/python3.7/asyncio/base_events.py", line 728, in call_soon_threadsafe
    self._check_closed()
  File "/usr/lib/python3.7/asyncio/base_events.py", line 475, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
+1
matthewcky2k on Feb 8, 2020
Read more comments on GitHub
← core: Cannot tweak consider_home time for private_ble_device
core: Can't add damping factor in Forecast.solar config UI →