-
Notifications
You must be signed in to change notification settings - Fork 8
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
Warmwasser push does not work #50
Comments
Please try 1.0.4pre. At least on my production system Ww Push works |
Hi, homeassistant has its own language selection. I think this is the one that counts. (but not 100% sure) Fallback (if no file for the selected language exists) is strings.json.(german). Your screenshots are ok. I'll explain: The entity Heat pump Operation (friendly name "Heat Pump operation" has the value hp_betrieb_19 hp_betrieb_19 (translation key) has the english translation of "Heating Mode) |
so this means that inside automations and scripts, I need to use hp_betrieb_19. This makes it a bit hard to read the automation or troubleshoot. Is there a possibility to, for example, add an attribute to the entity that houses the English translation of hp_betrieb_19? That way I can use this attribute in the automations and scripts. |
We could rewrite thentranslation keys to meaningfull names. hp_betrieb_heating_mode. I used the numbers cause it was quicker. This has to be done in: hpconst.py, strings.json, de.json, en.json and your files. |
I like your idea! That would indeed make it more user friendly. |
Pull requests welcome ;) |
I will close this here. Further discussion of translation feater should be in #30 |
Describe the bug
I've been playing around with the translations, when I observed an error when selecting the warmwasser push options. As that version is unstable, I installed version 1.0.3 again and I have the same error
To Reproduce
Select any option in the select.warmwasser_push entity
Expected behavior
The selection amount of minutes to be 'pushed' to the heat pump
The text was updated successfully, but these errors were encountered: