-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
No endities available #85
Comments
Hello I forgot that the Github default language is English. I think I have a similar problem as the colleagues from the other thread. The question for me is whether the heatpump.yaml has to be created manually or whether it should come through the installation? |
The configuration is entirely in yaml, so yes, you have to create the heatpump.yaml manually. sensor: !include_dir_merge_list sensors
binary_sensor: !include_dir_merge_list binary_sensors These will merge any yaml file in the subfolders into the configuration. |
So the designation
is only an example and should then be named
And where must the heatpump.yaml be stored? Directly via the file editor in the /homeassistant directory. |
Sorry for the huge delay. In your configuration.yaml you have this line: - platform: luxtronik
scan_interval: 60
sensors:
- group: calculations
id: ID_WEB_Temperatur_TVL
friendly_name: Temperatur Vorlauf
state_class: measurement Home Assistant will merge all the yaml files in that folder as if you write a giant structure within your configuration.yaml. The idea is that you can split your config and make it more readable. |
Hallo
Ich glaube ich habe ein ähnliches Problem wie der Kollege aus dem anderen Tread.
#11
Allerdings habe ich wie du auch da schon beschrieben hast noch mal das AddOn gelöscht und neu installiert. Installation läuft über HACS fehlerfrei durch.
sensor: !include_dir_merge_list sensors
binary_sensor: !include_dir_merge_list binary_sensors
The text was updated successfully, but these errors were encountered: