Rhasspy 2.5 with Hassio built in intents

Hi, I’m trying to get Rhasspy 2.5 working with Hassio’s built in intents but running into some trouble.

I think it’s setup right but there’s no change in the lights from Hassio (109.2) with an intent named HassTurnOn. If I name the intent something Hassio doesn’t recognize or I assign a value that Hassio doesn’t like I get an error in Hassio’s log for intent.py stating that so I know the intent is making it to Hassio. I’ve also tried this with HassSetState and changing the brightness, again no error unless I specify a value that doesn’t make sense like brightness of 150.

I’m testing just typing in text on the Rhasspy server to eliminate as much as I can. I am not using a shared MQTT broker and Rhasspy is set to send intents to Hassio (/api/intent/handle).

Any tips or things I can check?

Here’s the log from Rhasspy in case it’s helpful

[DEBUG:2020-05-02 16:46:03,536] rhasspyserver_hermes: Publishing 21 bytes(s) to rhasspy/handle/toggleOn
[DEBUG:2020-05-02 16:46:03,535] rhasspyserver_hermes: -> HandleToggleOn(site_id=‘default’)
[DEBUG:2020-05-02 16:46:03,532] rhasspyserver_hermes: Sent 657 char(s) to websocket
[DEBUG:2020-05-02 16:46:03,530] rhasspyserver_hermes: Sent 657 char(s) to websocket
[DEBUG:2020-05-02 16:46:03,528] rhasspyserver_hermes: Sent 657 char(s) to websocket
[DEBUG:2020-05-02 16:46:03,527] rhasspyserver_hermes: Sent 657 char(s) to websocket
[DEBUG:2020-05-02 16:46:03,516] rhasspyserver_hermes: Handling NluIntent (topic=hermes/intent/HassTurnOn, id=f04201d4-b6b4-4ad2-804f-4c2eefa6767f)
[DEBUG:2020-05-02 16:46:03,514] rhasspyserver_hermes: <- NluIntent(input=‘turn on the light.kitchen_lights’, intent=Intent(intent_name=‘HassTurnOn’, confidence_score=1.0), site_id=‘default’, id=‘215e884f-ca31-4ba0-ab14-7b9b06581416’, slots=[Slot(entity=‘Lights’, value={‘kind’: ‘Unknown’, ‘value’: ‘light.kitchen_lights’}, slot_name=‘name’, raw_value=‘kitchen lights’, confidence=1.0, range=SlotRange(start=12, end=32, raw_start=12, raw_end=26))], session_id=‘215e884f-ca31-4ba0-ab14-7b9b06581416’, custom_data=None, asr_tokens=[[AsrToken(value=‘turn’, confidence=1.0, range_start=0, range_end=4, time=None), AsrToken(value=‘on’, confidence=1.0, range_start=5, range_end=7, time=None), AsrToken(value=‘the’, confidence=1.0, range_start=8, range_end=11, time=None), AsrToken(value=‘light.kitchen_lights’, confidence=1.0, range_start=12, range_end=32, time=None)]], asr_confidence=None, raw_input=‘turn on the kitchen lights’, wakeword_id=None)
[DEBUG:2020-05-02 16:46:03,414] rhasspyserver_hermes: Publishing 201 bytes(s) to hermes/nlu/query
[DEBUG:2020-05-02 16:46:03,413] rhasspyserver_hermes: -> NluQuery(input=‘turn on the kitchen lights’, site_id=‘default’, id=‘215e884f-ca31-4ba0-ab14-7b9b06581416’, intent_filter=None, session_id=‘215e884f-ca31-4ba0-ab14-7b9b06581416’, wakeword_id=None)
[DEBUG:2020-05-02 16:46:03,409] rhasspyserver_hermes: Publishing 21 bytes(s) to rhasspy/handle/toggleOff
[DEBUG:2020-05-02 16:46:03,408] rhasspyserver_hermes: -> HandleToggleOff(site_id=‘default’)

I just started playing with Rhasspy today and seem to be having the same problem. Did you ever find a solution?

I think you need intents to be in your configuration.yaml or intent_script.yaml to define the intent