Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Homekit - Error setting up trigger #78774

Closed
JampireX opened this issue Sep 19, 2022 · 4 comments · Fixed by #80703
Closed

Homekit - Error setting up trigger #78774

JampireX opened this issue Sep 19, 2022 · 4 comments · Fixed by #80703
Assignees

Comments

@JampireX
Copy link

The problem

I have error in a log that appear on startup. Everything works fine, but I would like to know what's wrong.

What version of Home Assistant Core has the issue?

core-2022.9.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

homekit

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homekit/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.homekit.type_triggers
Source: components/homeassistant/triggers/numeric_state.py:76
Integration: HomeKit (documentation, issues)
First occurred: 17:08:25 (2 occurrences)
Last logged: 17:08:26

Error setting up trigger
Traceback (most recent call last):
  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 818, in validate_callable
    return schema(data)
  File "/usr/src/homeassistant/homeassistant/helpers/config_validation.py", line 146, in validate
    raise vol.Invalid(f"must contain at least one of {expected}.")
voluptuous.error.Invalid: must contain at least one of below, above.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/device_automation/trigger.py", line 81, in async_attach_trigger
    return await platform.async_attach_trigger(hass, config, action, trigger_info)
  File "/usr/src/homeassistant/homeassistant/components/sensor/device_trigger.py", line 158, in async_attach_trigger
    numeric_state_config = await numeric_state_trigger.async_validate_trigger_config(
  File "/usr/src/homeassistant/homeassistant/components/homeassistant/triggers/numeric_state.py", line 76, in async_validate_trigger_config
    config = _TRIGGER_SCHEMA(config)
  File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 232, in __call__
    return self._exec((Schema(val) for val in self.validators), v)
  File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 355, in _exec
    raise e if self.msg is None else AllInvalid(self.msg, path=path)
  File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 351, in _exec
    v = func(v)
  File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 276, in __call__
    raise er.MultipleInvalid([e])
voluptuous.error.MultipleInvalid: must contain at least one of below, above.

Additional information

No response

@probot-home-assistant
Copy link

homekit documentation
homekit source
(message by IssueLinks)

@probot-home-assistant
Copy link

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)

@heroclix
Copy link

Same issue here all my device triggers not working anynmore

@bdraco
Copy link
Member

bdraco commented Oct 13, 2022

You have an invalid trigger from some integration which unfortunately isn’t in the trace.

HomeKit enumerates all of them so it’s hitting the invalid one. Short of doing some debugging the best you can likely do is disable devices in HomeKit and then integrations one by one until the issues goes away and then report it to that integration so it can be fixed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants