Not possible to have whitespaces in aliases?

[livid coral]

Hey there,

I'm using Assist in fully local mode, see my config attached, using Wyoming satellites.

I was trying to use a voice command to close a specific cover, but Assist does not find the cover. Please see the aliases in the attacted screen.
I see Whisper correctly understands the command, but Assist still responds that there is no "Rollo links" in that room: INFO:wyoming_faster_whisper.handler: Schließe Rollo links im Esszimmer
I also tried it with a cover named "Rollo 1", same thing: Assist tells me it doesn't exist, but Whisper understands me: INFO:wyoming_faster_whisper.handler: Schließe Rollo 1 im Wohnzimmer
Assist in general can control the coversin those rooms: If I tell it to close all covers in that room, it does so.

Is having whitespaces in aliases not supported right now?

Thanks and greetings,

Andy!

[last stone]

check "Schließe Rollo 1 im Wohnzimmer" in DevTools - Assist (or any other intent using alias). Usually, spaces do not cause problems if the word combinations do not conflict with built-in commands.

[livid coral]

Oh yeah, I totally forgot that exist! Thanks!
Parsing it though, it seems there is a bug actually, as it parses a whitespace into the names: (ignore, read below)

[livid coral]

Ok, I guess I found the issue: The matched intent is wrong. It matches the sentences/de/lock_HassTurnOff.yaml.
If I remove the room from it, it works xD

I'm guessing the instructions are (at least in german) are too equal...
(<sperren>|<machen>) <name>[ <area>][ (zu|ab)]: https://github.com/OHF-Voice/intents/blob/69b193ed423d1fdc286da5603a2b3845f9b04399/sentences/de/lock_HassTurnOn.yaml#L6
is too equal to
<schliessen> (<abdeckung>|<tor>|<garage>) <area_floor>: https://github.com/OHF-Voice/intents/blob/69b193ed423d1fdc286da5603a2b3845f9b04399/sentences/de/cover_HassTurnOff.yaml#L18C13-L18C67

And (guessing) because it matches in a given order through the intents, the lock intent matches and therefore it doesn't continue further :/

So the issue is not related to whitespaces, but sentences being too equal. I tried renaming it to something without a whitespace and it works in EN, but not in DE. So I guess the closing of a specific cover is broken in DE right now

[last stone]

I guess the closing of a specific cover is broken in DE right now
The script is the same for all languages, most likely there is some character mismatch. Try experimenting with aliases instead of entity names.

[livid coral]

Sure the script is the same for all languages... but the translations in DE for lock and cover are too similar. That's the issue here

[last stone]

I looked at your language sentences. They are not similar. In German, there are no combinations of names and areas in commands (which is why your example with the closing command worked, but the others did not).