I started from scratch as suggested by @HorizonKane now for both master and satellite using the mqtt approach and the udp settings for audio streaming as documented in the tutorial. On the Pi there was definitely something messed up.
For the master I exposed the mqtt port 12138 so that my satellites can directly connect via mqtt to the master.
That way I can separate my existing broker from the Rhasspy setup. The siteId is correct in this setup.
@moqart
I tried the websocket method earlier and I think (80% sure) that the site id was the master one.
I listen on hermes/intent/
I’m using a Pi Zero W and a ReSpeaker 2-Mics Pi HAT for under 10USD.
I did some tests and I think for the price the results are really good. Wake word was detected about 4m away without issues. Will do some more tests later.
I am using the same setup for satellites and it is performing good. Recording a good wakeword and modify the audio gain setting was crucial but now it is near perfect.
I am happier with rhasspy than I was with Snips already. Almost no false positives and still responding 98% of the time.
With Snips I also had the problem that often the satellite in the other reacted together with the correct one, this has gone away, too with rhasspy.