German Translation

[oerkel47]

Hey @JarvyJ,

I will be working on a german translation.

[oerkel47]

As a proof that I am in fact German, I accidentally capitalized the T in translation.

[oerkel47]

Is there a way to overwrite numbers? Rhasspy maps them via num2words package, but it lacks some details.

For example it maps 128: einhundertachtundzwanzig, but in most cases you would just say hunderachtundzwanzig.

[JarvyJ]

We should be able to create a custom number slot dictionary:

@intents.dictionary_slots
def number(self):
    return {
        "one": "1",
        "two": "2",
        "three": "3",
    }

and then in the sentences do:

"set timer ($number) minutes"

I might play around and see what's possible. The above should work!

[JarvyJ]

Ah, right now, we can't do "repeatable" slots... so instead of one slot defining all the numbers and then reusing for hours/minutes/seconds. It has to be effectively the same slot repeated three times with different slot names. So instead of "number" in the example above, you'd have a slot for minutes, hours, and then seconds. Not super ideal...

I might try to work in "repeatable" slots, so you could have one slot definition for numbers, then reuse the slot in the sentence:

multiply ($number){first} times ($number){second}

and the actual number would come back in first and second

[JarvyJ]

I did create a new branch (#234) that has a repeatable_dictionary_slots in the intent, which should allow for the above to work. I'll write up some docs on it and merge it in. It's mostly so we can try it out and see if it works for the use case!

[oerkel47]

Nice. Unfortunately I couldn't figure out how to get it running.

Do I need to put

@intents.repeatable_dictionary_slots
def number(self):
    return {
        "one": "1",
        "two": "2",
        "three": "3",
    }

inside the de.py and/or the base class?

[JarvyJ]

Yes, it would be inside the de.py class. I think technically it would have to be timer_number for it to be named properly.

So you'd have something like this (but with all the numbers in german in de.py):

    @intents.repeatable_dictionary_slots
    def timer_number(self):
        return {
            "five": "5",
            "four": "4",
            "three": "3",
            "two": "2",
            "one": "1",
        }

and then one of the sentences would look something like this:

"set timer [($timer_number){hours} hours] [($timer_number){minutes} minutes] [($timer_number){seconds} seconds]"

I've also written some docs and will merge those in to hopefully clarify a bit more if needed: https://homeintent.io/reference/api/intents-class/#intentsrepeatable_dictionary_slots

Hope it helps!

[JarvyJ]

and I ended up merging the repeatable_dictionary_slots into main for now!

[oerkel47]

Yes, it would be inside the de.py class. I think technically it would have to be timer_number for it to be named properly.

So you'd have something like this (but with all the numbers in german in de.py):

    @intents.repeatable_dictionary_slots
    def timer_number(self):
        return {
            "five": "5",
            "four": "4",
            "three": "3",
            "two": "2",
            "one": "1",
        }

and then one of the sentences would look something like this:

"set timer [($timer_number){hours} hours] [($timer_number){minutes} minutes] [($timer_number){seconds} seconds]"

I've also written some docs and will merge those in to hopefully clarify a bit more if needed: https://homeintent.io/reference/api/intents-class/#intentsrepeatable_dictionary_slots

Hope it helps!

Yes, it helps. Thanks a lot. The incorrect naming was the problem I faced yesterday.

With
"time =($timer_number|0..99)"
and then using
"(<time>){hours}" as before, I managed to only specify the numbers >99 inside timer_numbers to avoid having to write out the ones that don't need changing. This does exactly what I needed, thanks again.

[oerkel47]

Since the states of entities (lights) that are returned by HA api are in english ("on"), I implemented a little translation function into the language file.

This principle works perfectly fine, but maybe there is a better way to implement a function like this. For example Integrating it into the base class and only define the translated states inside the translation. This would make it work the same for all translations.

[JarvyJ]

Yeah, this is kinda interesting. Since it affects just Home Assistant, I think I might add a language dictionary that gets auto-loaded based on language settings and provided back in the base constructor for use. English words that need to be translated from Home Assistant could all be defined there with their translations and the code could reference. I'll create a new issue and play around with it a bit to see how it would work.

[oerkel47]

Is there a way to get a working frontend running with the dev setup? It seems as though it would only communicate with rhasspy once on startup. Also, it seems as my custom rhasspy config in /config gets ignored which might be related to that.

[JarvyJ]

Yeah, the dev frontend situation is not super great... It should be able to read/write the config, and view logs. So the "Save" partially works, but the restart functionality doesn't work.

When I need to test it all end-to-end, I have a separate docker-compose file (docker-compose.build.yaml):

version: "3.9"

services:
  homeintent:
    build: .
    container_name: homeintent
    restart: unless-stopped
    volumes:
      - "./development-env/rhasspy:/profiles"
      - "./development-env/config:/config"
      - "/etc/localtime:/etc/localtime:ro"
    ports:
      - "12101:12101"
      - "11102:11102"
    devices:
      - "/dev/snd:/dev/snd"
    environment:
      - LANGUAGE=en

and then just do a docker-compose -f docker-compose.build.yaml up --build and restart as necessary... If I could get the API to control the other containers, that would help with that, but I haven't looked into it much.

Can you post your rhasspy config? I might've introduced a bug while setting the default TTS based on language...

[oerkel47]

Sure. That's the config. Ah I just remember to have read something about externally managed rhasspy flag. Do I have to activate that additionally?

 {
    "dialogue": {
        "system": "rhasspy"
    },
    "intent": {
        "system": "fsticuffs"
    },
    "microphone": {
        "pyaudio": {
            "device": "6",
            "udp_audio_host": "127.0.0.1",
            "udp_audio_port": "12202"
        },
        "system": "pyaudio"
    },
    "sounds": {
        "aplay": {
            "device": "sysdefault:CARD=Generic"
        },
        "system": "aplay"
    },
    "speech_to_text": {
        "system": "kaldi"
    },
    "text_to_speech": {
        "marytts": {
            "locale": "de",
            "url": "http://192.168.2.2:59125/process",
            "voice": "bits1-hsmm",
            "volume": "0.65"
        },
        "system": "marytts"
    },
    "wake": {
        "porcupine": {
            "keyword_path": "jarvis_linux.ppn",
            "udp_audio": "127.0.0.1:12202"
        },
        "system": "porcupine"
    }
}

And thanks for that docker-compose code.