Skip to content

[IT] Improve climate common names to avoid clashes with fan #3054

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
giobber opened this issue Mar 13, 2025 · 0 comments
Open

[IT] Improve climate common names to avoid clashes with fan #3054

giobber opened this issue Mar 13, 2025 · 0 comments

Comments

@giobber
Copy link

giobber commented Mar 13, 2025

Hi, thanks for all the great work for the italian language support

When i try to switch on or off a climate using the term "climatizzatore" or "condizionatore" HA keep trying to use a fan entity which never existed (I don't actually have any fan entity)

So for clarifying, when i ask:
Accendi il condizionatore in camera
Assist respond with:
Non conosco nessun dispositivo di tipo 'fan' (or something similar)

By looking in the default intents I understood that the terms "condizionatore" e "climatizzatore" are used either for fan entities and climate entities, which is not what I was expecting at all as I'm not sure I'll ever call a fan with these terms (but maybe it's a subjective thing, I don't know). In any case It seems odd to me that HA default to fail on first entity class assumption

For now I solved by removing the two terms from fan domain in my local _common.yaml file, a procedure which is hinted but basically not documented at all in the official documentation (https://www.home-assistant.io/voice_control/custom_sentences_yaml/)

Here are my configuration (in case I'm not the only one struggling with this)
The file should be saved in config/custom_sentences/it/_common.yaml, create sub-folders if needed

# config/custom_senteces/it/_common.yaml
language: it
expansion_rules:
  fan: "(ventol(a|e) | ventilator(e|i) | ventilazione)"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant