RPi 4 ReSpeaker satellite : work once then no more Wake Word detection :(

Hello.

I have build a satellite with a RPi 4 and a ReSpeaker card.

I use this tutorial to set up my satellite :

This morning, after restarting all services on the RPi :

satellite@rpisatellite:~ $ sudo systemctl restart wyoming-satellite.service wyoming-wakeword.service 2mic_leds.service
satellite@rpisatellite:~ $ sudo systemctl status wyoming-satellite.service wyoming-wakeword.service 2mic_leds.service
● wyoming-satellite.service - Wyoming Satellite
     Loaded: loaded (/etc/systemd/system/wyoming-satellite.service; enabled; preset: enabled)
     Active: active (running) since Sat 2024-11-23 18:28:53 CET; 16h ago
   Main PID: 2672 (python3)
      Tasks: 4 (limit: 1575)
        CPU: 27min 54.479s
     CGroup: /system.slice/wyoming-satellite.service
             ├─2672 python3 /home/satellite/wyoming-satellite/script/run --name SatSejour2 --uri tcp://0.0.0.0:10700 --mic-command "arecord -D plughw:CARD=seeed2micvoicec,DEV=0 -q -r 16000 -c 1 -f S16_LE -t raw" --snd-command "aplay -D plughw:CARD=seeed2micvoicec,DEV=0 -q -r 22050 -c >
             ├─2675 /home/satellite/wyoming-satellite/.venv/bin/python3 -m wyoming_satellite --name SatSejour2 --uri tcp://0.0.0.0:10700 --mic-command "arecord -D plughw:CARD=seeed2micvoicec,DEV=0 -q -r 16000 -c 1 -f S16_LE -t raw" --snd-command "aplay -D plughw:CARD=seeed2micvoicec,D>
             └─2677 arecord -D plughw:CARD=seeed2micvoicec,DEV=0 -q -r 16000 -c 1 -f S16_LE -t raw

Nov 23 18:37:23 rpisatellite run[2675]: WARNING:root:Did not receive ping response within timeout
Nov 23 18:37:23 rpisatellite run[2675]: INFO:root:Disconnected from server
Nov 23 18:37:30 rpisatellite run[2675]: INFO:root:Connected to server
Nov 23 18:37:30 rpisatellite run[2675]: INFO:root:Waiting for wake word
Nov 23 18:39:43 rpisatellite run[2675]: WARNING:root:Did not receive ping response within timeout
Nov 23 18:39:43 rpisatellite run[2675]: INFO:root:Disconnected from server
Nov 23 18:39:46 rpisatellite run[2675]: INFO:root:Connected to server
Nov 23 18:39:46 rpisatellite run[2675]: INFO:root:Waiting for wake word
Nov 23 18:42:26 rpisatellite run[2675]: INFO:root:Waiting for wake word
Nov 23 18:45:09 rpisatellite run[2675]: INFO:root:Waiting for wake word

● wyoming-wakeword.service - porcupine1
     Loaded: loaded (/etc/systemd/system/wyoming-wakeword.service; enabled; preset: enabled)
     Active: active (running) since Sat 2024-11-23 18:26:49 CET; 16h ago
   Main PID: 2618 (python3)
      Tasks: 2 (limit: 1575)
        CPU: 1h 15min 39.990s
     CGroup: /system.slice/wyoming-wakeword.service
             ├─2618 python3 /home/satellite/wyoming-satellite/local/wyoming-porcupine1/script/run --uri tcp://127.0.0.1:10400 --sensitivity 0.5
             └─2622 /home/satellite/wyoming-satellite/local/wyoming-porcupine1/.venv/bin/python3 -m wyoming_porcupine1 --uri tcp://127.0.0.1:10400 --sensitivity 0.5

Nov 23 18:26:49 rpisatellite systemd[1]: Started wyoming-wakeword.service - porcupine1.
Nov 23 18:26:50 rpisatellite run[2622]: INFO:root:Ready

● 2mic_leds.service - 2Mic LEDs
     Loaded: loaded (/etc/systemd/system/2mic_leds.service; disabled; preset: enabled)
     Active: active (running) since Sat 2024-11-23 18:26:49 CET; 16h ago
   Main PID: 2619 (python3)
      Tasks: 4 (limit: 1575)
        CPU: 59.327s
     CGroup: /system.slice/2mic_leds.service
             └─2619 /home/satellite/wyoming-satellite/examples/.venv/bin/python3 2mic_service.py --uri tcp://127.0.0.1:10500

Nov 23 18:26:49 rpisatellite systemd[1]: Started 2mic_leds.service - 2Mic LEDs.
Nov 23 18:26:50 rpisatellite python3[2619]: INFO:root:Ready

I was able to turn on a light using voice command :

But after that, my Wake Word is not detected any more. No blue LED on the ReSpeaker to indicate that the wake word was detected.

Any clue or tips ? Is it normal for the Assist to stay in the Responding state ? When doing nothing, the stat shouldn’t be Idle ?