I’ve just really started working with Snips. I have a Base running on Ubuntu 18.04 and a satellite on a Pi 0 W.
I’ve never gotten the base to properly respond to commands spoken to the satellite. The base recognizes the intent but doesn’t seem to send the audio. So after a few rebuilds, endless hours troubleshooting I had someone help me integrate Snips with Home Assistant and use HA to capture the intents and process them.
So last night I installed Node Red and started playing with it. I sub’d to # on my mqtt broker to figure out the topic and payload when Snips was being used and I discovered that Snips is spamming my MQTT broker.
So in Node Red I see that on the topic /hermes/audioServer/base/audioFrame there are thousands? of messages. I’ve attached a screenshot, it’s hard to describe but the time just keeps counting and the _msgid: " " numbers change so fast that they are honestly a blur.
Using mosquitto_sub on topic ‘#’ I see this constant lines of:
RIFF4WAVEfmt ▒>}tim▒▒ endata RIFF4WAVEfmt ▒>}tim▒▒ endata RIFF4WAVEfmt ▒>}tim▒▒ endata RIFF4WAVEfmt ▒>}tim▒▒ endata RIFF4WAVEfmt ▒>}timё endata
When I stop ‘snips-audio-server’ the “RIFF4WAVEfmt ▒>}timё” messages disappear.
This can’t be normal can it?