I am running HA on a pi4 via generic linux install on raspbian and as soon as I updated to the latest version HA is no longer loading for me.
When I tried a hassio homeassistant check via ssh I get this:
Error: Testing configuration at /config
INFO:homeassistant.util.package:Attempting install of alexapy==1.0.0
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 https://github.com/xernaj/python-ring-doorbell/archive/fix/oauth-fail-due-to-blocked-user-agent.zip#ring_doorbell==0.2.4
INFO:homeassistant.util.package:Attempting install of aiogithubapi==0.4.3
INFO:homeassistant.util.package:Attempting install of hacs_frontend==20200104192235
INFO:homeassistant.util.package:Attempting install of integrationhelper==0.2.2
INFO:homeassistant.util.package:Attempting install of semantic_version==2.8.4
WARNING:homeassistant.components.automation:The 'hide_entity' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107
INFO:homeassistant.util.package:Attempting install of https://github.com/xernaj/python-ring-doorbell/archive/fix/oauth-fail-due-to-blocked-user-agent.zip#ring_doorbell==0.2.4
ERROR:homeassistant.scripts.check_config:BURB
Traceback (most recent call last):
File "/usr/src/homeassistant/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 583, in run_until_complete
return future.result()
File "/usr/src/homeassistant/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/src/homeassistant/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)
I have two instances one on a pi3 via hassos
But the 2nd is home assistant (the old hassio) installed on raspbian via docker (standard install method) onto a hard disk
No problems with mine. (both upto 0.105.2)
The only addons I have are auto backup, motioneye, ssh, samba and configurator.
Restoring a backup of 104.3 brought it back to life.
I’ll try @bend’s suggestion with updating to 105.0 first and check if it resolves, thanks
Ok I did one version at a time and got it to run but 3 integrations are broken (openuv/netatmo/discovery) or maybe their config has changed just now:
2020-02-08 15:13:57 ERROR (MainThread) [homeassistant.config] Invalid config for [openuv]: [binary_sensors] is an invalid option for [openuv]. Check: openuv->openuv->binary_sensors. (See /config/configuration.yaml, line 286). Please check the docs at https://www.home-assistant.io/integrations/openuv
2020-02-08 15:13:57 ERROR (MainThread) [homeassistant.setup] Setup failed for openuv: Invalid config.
2020-02-08 15:13:57 ERROR (MainThread) [homeassistant.config] Invalid config for [discovery]: value is not allowed @ data['discovery']['ignore'][0]. Got 'samsung_tv'. (See /config/configuration.yaml, line 29). Please check the docs at https://www.home-assistant.io/integrations/discovery
2020-02-08 15:13:57 ERROR (MainThread) [homeassistant.setup] Setup failed for discovery: Invalid config.
2020-02-08 15:14:50 ERROR (MainThread) [homeassistant.config] Invalid config for [netatmo]: [api_key] is an invalid option for [netatmo]. Check: netatmo->netatmo->api_key. (See /config/configuration.yaml, line 107). Please check the docs at https://www.home-assistant.io/integrations/netatmo
2020-02-08 15:14:50 ERROR (MainThread) [homeassistant.setup] Setup failed for netatmo: Invalid config.
Not sure why openuv is complaining about binary_sensors, worked just fine in 0.104.2
Netamo I heard needs to be configured again as a breaking change
Tried to get netatmo to work via the integrations page but once I click accept on the allow HA to access netatmo nothing happens (on the netatmo page) Any ideas?