You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of problem: I setup a snips intent (HassTurnOn and HassTurnOff) so I could use snips to turn things on or off. It was working fine, but now returns an error when an intent gets passed in.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
snips:
probability_threshold: .6
NOTE: I did add probability_threshold after upgrading as I was trying to reduce the number of bad intents that were being handled.
Traceback (if applicable):
2018-06-10 20:41:54 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <ServiceIntentHandler - HassTurnOff>
2018-06-10 20:41:54 WARNING (MainThread) [homeassistant.helpers.intent] Received invalid slot info for HassTurnOff: extra keys not allowed @ data['site_id']
2018-06-10 20:41:54 ERROR (MainThread) [homeassistant.components.snips] Error while handling intent: HassTurnOff.
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/intent.py", line 59, in async_handle
result = await handler.async_handle(intent)
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/intent.py", line 187, in async_handle
slots = self.async_validate_slots(intent_obj.slots)
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/intent.py", line 142, in async_validate_slots
return self._slot_schema(slots)
File "/usr/lib/python3.6/site-packages/voluptuous/schema_builder.py", line 267, in __call__
return self._compiled([], data)
File "/usr/lib/python3.6/site-packages/voluptuous/schema_builder.py", line 587, in validate_dict
return base_validate(path, iteritems(data), out)
File "/usr/lib/python3.6/site-packages/voluptuous/schema_builder.py", line 425, in validate_mapping
raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: extra keys not allowed @ data['site_id']
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/components/snips.py", line 139, in message_received
hass, DOMAIN, intent_type, slots, request['input'])
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/intent.py", line 65, in async_handle
'Received invalid slot info for {}'.format(intent_type)) from err
homeassistant.helpers.intent.InvalidSlotInfo: Received invalid slot info for HassTurnOff
Additional information:
I have snips running on a different device than home assistant. I bridge the MQTT from that device to home assistant and only share specific topics. I did not change this configuration between upgrades as it was working.
The text was updated successfully, but these errors were encountered:
Home Assistant release with the issue: 0.71.0
Last working Home Assistant release (if known): 0.68 - I upgraded from .68 to .71
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io running on Raspberry Pi
Component/platform: snips
Description of problem: I setup a snips intent (HassTurnOn and HassTurnOff) so I could use snips to turn things on or off. It was working fine, but now returns an error when an intent gets passed in.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):NOTE: I did add probability_threshold after upgrading as I was trying to reduce the number of bad intents that were being handled.
Traceback (if applicable):
Additional information:
I have snips running on a different device than home assistant. I bridge the MQTT from that device to home assistant and only share specific topics. I did not change this configuration between upgrades as it was working.
The text was updated successfully, but these errors were encountered: