OpenVoiceOS / ovos-personal-backend

personal backend - self-hosted backend to manage multiple OVOS devices
Apache License 2.0
78 stars 26 forks source link

stt configuration inconsistently shared #62

Open mikejgray opened 1 year ago

mikejgray commented 1 year ago

My backend STT configuration is:

{
  "stt": {
    "module": "ovos-stt-plugin-server",
    "ovos-stt-plugin-server": {
      "url": "http://192.168.86.58:9090/stt"
    },
    "fallback_module": "ovos-stt-plugin-selene",
    "ovos-stt-plugin-selene": {
      "url": "https://api.mycroft.ai",
      "version": "v1",
      "identity_file": "/root/.local/share/ovos_backend/identity2.json"
    }
  }
}

However, what got passed to my OVOS device was:

  "stt": {
    "module": "ovos-stt-plugin-selene",
    "ovos-stt-plugin-server": {
      "url": "http://192.168.86.58:9090/stt"
    }
  },
emphasize commented 1 year ago

Had some similar expirience while setting up my local whisper docker, but didn't dig deeper. There was no request to whisper but i got a transcription (from somewhere), so i think the second definition was chosen.

BTW i use selene plugin on ovos side pointed at the personal backend stt endpoint. That way the transcription gets saved in the database. (just fyi)

JarbasAl commented 1 year ago

STT configuration isnt passed from backend to device, the backend simply uses the same config format but this wont be sent to devices, its just for the stt endpoint

there is no fallback_stt in backend either