Message metadata unavailable in intent_script about hassio-addons

[MichaelBitard]

Indeed the keywords you see in the code are not variables passed on to home assistant, but are keywords the signal-cli I rely on to communicate with signal uses. It's only internal to this addon.

Home assistant receives what is passed to https://github.com/agileek/hassio-addons/blob/master/signal/root/app/ws.py#L6

I'll have to look into the intents again to see what is received by the intent, and what can be used. Could be a good opportunity to add this to the readme too

[bastiaanterhorst]

Ah, thank you for pointing me to that. If I read the code correctly, only the message is passed as a variable named text. I assume this is what HA internally expects to trigger intent handling. This bit:

await websocket.send(json.dumps({
                    "id": 1,
                    "type": "conversation/process",
                    "text": message,
                }))

Looking here it seems that text is the only thing to pass (assuming this websocket call triggers conversation.process internally. Looking at the source of that service, I don't think it is even possible to pass it other things unfortunately -- but I might be reading it wrong.

I will try to edit my local code and pass it some other things and see if they arrive in the intent_script, when I have a moment. I also see on that page that it should be possible to use slots to make commands variable (like 'set thermostat to 19', where 19 is a variable passed to the intent_script). I'll play with this also.

If I figure something out I'd be happy to contribute a PR to the docs to explain how to do this.