-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Some “heating” activations aren’t displayed when using heatmiser profiles #241
Comments
Hi @mnbf9rca, you are correct, when the thermostats are in optimum start, this integration correctly sets the In the meantime, you can use the There are also new controls available (hidden by default) to control various parameters including the optimum start period. |
@mnbf9rca do you need any more help with this issue or can it be closed? |
i assume it's this which needs to be changed? |
@mnbf9rca yes I thinks that's the right place. I haven't played around with a dev HA ui, but the docs make it sound simple enough. If I get some time I'll see what I can do, but it's probably still best to raise an issue there. |
I've raised home-assistant/frontend#23876 |
Awesome thanks. It's something that's bugged me in the past, but not enough to do something about it! |
The change in Home Assistant has been released in 2025.2.0. Preheating is now filled in the charts in the same way as heating. |
I’ve been using the heatmiser profiles for about 12 hours - you can see the break in the schedule where I switched over to v3 and reprogrammed them circled. What I notice is that some “heating” events aren’t being reported - eg where the temperature starts rising around 5am today. Presumably that’s the “optimum start” feature on the thermostats themselves. This is consistent across all of my thermostats.
The text was updated successfully, but these errors were encountered: