The satellite seems to work ok, maybe an issue with the settings on the sat. I could not find them listed yet,
Also, what is the connection of MQTT on base and sat?
MQTT is setup to connect to my external MQTT broker.
I can see the connections of the Base and the Satellite on my MQTT Broker.
Is there a way to push audio from the base out to the satellite?
What is the importance of Intent Recognition and Dialogue Management? I mean, do any additional work of just recognizing the exact words in sentences?
(I apologize for getting off topic. It just occurred to me to ask, I hope not to bother).
Yes, you can use the command line.
You can also use Node-Red for it, I have an audio test flow:
The Node-Red is the addon in Home Assistant. I just placed some wav’s in the share folder.
File id nodes are configured like this:
So, whenever I push one of the buttons, it sends the corresponding wav file to the topic of the MQTT node.
I was using this in my streamer to test various samplerates
I saw the base settings, but what about the satellite settings?
They are both connected to the same MQTT broker?
Also, it might be a very good idea to not use Rhasspy on a VM, but you the Home Assistant Addon on. In any case the base, the sat and HA should be on the same broker, which I think you have but just to be sure and double check.
The sat seems to correctly detect the hotword and intent detection.
Did you follow this guide?
I did use the tutorial but just to be safe I just double checked and all the settings are the same as what is outlined in the tutorial except for:
On the Base the Intent Handling is now set to Home Assistant with the HASS URL set to “http://192.168.1.105:8123”, the Access Token pasted in, and Send Intents to Home Assistant radio button selected.
On the Satellite I noticed that there is now a host field (along with the port field) for the UDP Audio (Output) were the docs just show a port field.
Do I need anything in the hosts field?
I don’t believe HA is picking up the intents being published by my Rhasspy base.
I can see in my Rhasspy logs “rhasspyserver_hermes: Sent 435 char(s) to websocket”
But I am not seeing anything on HA end.
I thought since that HA and Rhasspy are both containerized that the HA container IP should be used instead of the host IP.
Changing to the container IP doesn’t seem to have made a difference.
I did make sure that the HA container IP was reachable from the Rhasspy Base container.
I have found ha doesn’t support intents as of late just events. Try using events instead.
Can you give a link where you got that information?
No link, experience. Try using curl to access the intent api for HA. It should error out with 404 code. Here is an example:
curl -X GET -H "Authorization: Bearer " -H “Content-Type: application/json” :8123/api/intents
404: Not Found
FYI it did work in a previous version of ha compared to the version I’m currently using Home Assistant 0.118.5. I don’t know the previous version. As I said events work fine.
Intents are managed via intent_script in configuration.yaml.
There is no api endpoint for intents (anymore apparently), so that is why you get the 404.
Yes I saw that but thought docs were out of date. Well events are working but easy for me to try intents with the script. I redirect the received events to their intents(ones in the config files) and works fine.
1 Like