-
Notifications
You must be signed in to change notification settings - Fork 47
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
Parameters cannot be changed retrospectively (away_temp, sleep_temp; home_temp; eco_Themp) #205
Comments
That's not a bug, it's a feature. The values in YAML are only used at first start or after crashing or cleaning of the HA recorder database. This has been added a while ago so the users can easily adjust the preset temperatures and gains without requiring to reboot HA. |
I have already searched for setting options under Devices and Entities. And now again. But I can't find this anywhere. Can you help me to find it. Via a picture or directions? |
Oh man, I would never have guessed that. I went to devices and services. |
Thank you, that worked perfectly. Even if it is quite hidden. |
Describe the bug
The parameters (away_temp, sleep_temp; home_temp; eco_Themp) can no longer be subsequently adjusted. Unless you assign a new unique_id, which is not expedient.
To Reproduce
Steps to reproduce the behavior:
2 . Restart HA
3 After this has been created, change the values for *.temp e.g. eco_temp: 5
4. Restart HA
3. Change the mode in the visualization.
Result
The value is not changed as specified in the configuration.
Expected behavior
The setpoint should be adjusted to the value from the configuration.
Screenshots
The value from the config is not used.
Even if the parameter is commented out, the mode is still suggested.
The value is only accepted if the unique_id is manipulated.
Desktop (please complete the following information):
Additional context
Deleting and recreating the entity does not help either.
At first I thought it was a mistake on my part, but now I think it's a bug.
This discussion is therefore rather superfluous.
#204
The text was updated successfully, but these errors were encountered: