Logger: homeassistant.helpers.check_config
Source: config.py:472
First occurred: 10:29:57 (2 occurrences)
Last logged: 10:33:04
Unexpected error validating config
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/device_automation/action.py", line 61, in async_validate_action_config
return cast(ConfigType, platform.ACTION_SCHEMA(config))
File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 272, in __call__
return self._compiled([], data)
File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 595, in validate_dict
return base_validate(path, iteritems(data), out)
File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 433, in validate_mapping
raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: extra keys not allowed @ data['service']
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 113, in _try_async_validate_config_item
validated_config = await async_validate_config_item(hass, config, full_config)
File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 89, in async_validate_config_item
config[CONF_ACTION] = await script.async_validate_actions_config(
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 259, in async_validate_actions_config
return await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 274, in async_validate_action_config
config = await device_action.async_validate_action_config(hass, config)
File "/usr/src/homeassistant/homeassistant/components/device_automation/action.py", line 63, in async_validate_action_config
raise vol.Invalid("invalid action configuration: " + str(err)) from err
voluptuous.error.Invalid: invalid action configuration: extra keys not allowed @ data['service']
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/check_config.py", line 162, in async_check_ha_config_file
await config_validator.async_validate_config(hass, config)
File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 136, in async_validate_config
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 120, in _try_async_validate_config_item
async_log_exception(ex, DOMAIN, full_config or config, hass)
File "/usr/src/homeassistant/homeassistant/config.py", line 454, in async_log_exception
message, is_friendly = _format_config_error(ex, domain, config, link)
File "/usr/src/homeassistant/homeassistant/config.py", line 472, in _format_config_error
f"[{ex.path[-1]}] is an invalid option for [{domain}]. "
IndexError: list index out of range
After commenting this part out the automations loaded but all my zigbee devices were unavaliable. I think they seem to have disabled mqtt triggers, which the zigbee2mqtt integration needs. If this is the case and is with intent 2022.10 afterwards zigbee2mqtt is not supported anymore.
This is a fairly significant problem that I suspect is affecting quite a few installs. Does it need to be reported in a different place, such as the Core Issues tracker… Issues · home-assistant/core · GitHub
This weekend I tried to fix every automation trying to change the triggers according to the errors (eg. not using device trigger but state trigger, rewrite all the automations that use the netatmo camera, etc) and I managed to get 2022.10.1 to work. Today I updated to 2022.10.2 and it’s still working but it was very time consuming.
So I don’t know if 2022.10.2 fixed something or not
Yes 77 ZigBee devices recently migrated from deconz to ZigBee2mqtt but since I had to migrate all the sensors I already fixed the automations before migrating using the state trigger and not device trigger in that way I had to rewrite only the automations for ZigBee buttons.
ZigBee2mqtt never was an issue with 2022.10 core update for me
Is that really the intention of HA to only use state triggers instead of device triggers? Normally it should be possible to use all triggers which are available in the drop down. Otherwise the drop down makes no sense for me or should be limited only to triggers which work.
You are right but I was looking for a straight forward way to migrate from a controller (and ZigBee platform) to another and for a way to not have to fix a lot of automations every time I need to change my ZigBee network.
I found that using state trigger and models condition the 99% of my automation is still functional if during the network repair I maintain the same names between sensors.
I preferred to rewrite all my automations (where possible) with that on mind.
The automations that were giving me issues with the update were related to the “trigger device” used with the netatmo platform in the automations. I changed them with trigger state when I was on 2022.9.7 than updated to 2022.10.1 and no more automations errors for me…