Retain transcript messages and add MQTT publish diagnostics

bridge/.env.example

@@ -38,6 +38,8 @@ VAD_MIN_SPEECH_MS=300
 MQTT_VAD_TOPIC=evs/+/vad_segment
 MQTT_TRANSCRIPT_TOPIC_TEMPLATE=evs/{device_id}/transcript
 MQTT_STT_ERROR_TOPIC_TEMPLATE=evs/{device_id}/stt_error
+STT_TRANSCRIPT_RETAIN=true
+STT_ERROR_RETAIN=false
 STT_MODEL=small
 STT_DEVICE=cpu
 STT_COMPUTE_TYPE=int8

bridge/README.md

@@ -108,6 +108,7 @@ You can build automations on these events (for STT/TTS pipelines or Node-RED han
   - reads `wav_path` from event JSON
   - transcribes with `faster-whisper`
   - publishes transcript to `evs/<device_id>/transcript`
+  - `STT_TRANSCRIPT_RETAIN=true` keeps latest transcript visible in MQTT UIs
 
 ## 6.1) STT Worker Config
 

bridge/docker-compose.yml

@@ -24,6 +24,8 @@ services:
       MQTT_VAD_TOPIC: "${MQTT_VAD_TOPIC:-evs/+/vad_segment}"
       MQTT_TRANSCRIPT_TOPIC_TEMPLATE: "${MQTT_TRANSCRIPT_TOPIC_TEMPLATE:-evs/{device_id}/transcript}"
       MQTT_STT_ERROR_TOPIC_TEMPLATE: "${MQTT_STT_ERROR_TOPIC_TEMPLATE:-evs/{device_id}/stt_error}"
+      STT_TRANSCRIPT_RETAIN: "${STT_TRANSCRIPT_RETAIN:-true}"
+      STT_ERROR_RETAIN: "${STT_ERROR_RETAIN:-false}"
       STT_MODEL: "${STT_MODEL:-small}"
       STT_DEVICE: "${STT_DEVICE:-cpu}"
       STT_COMPUTE_TYPE: "${STT_COMPUTE_TYPE:-int8}"