Just to let you know that v3.2.2 has now been released with some bug fixes and some new features.
1. Schedule card list view
2. View schedule id on schedule list (default view)
3. Events and Triggers
We have added triggers and events for the following room based events:
boosted
started_heating
stopped_heating
target_temperature_increased
target_temperature_decreased
These can be used as individual device triggers in automations to monitor specific rooms or as event triggers in automations to listen for these events across any room. See Events & Triggers for how to use.
I hope these new functions help you derive your automations more easily to be able to more efficiently manage your heating as the weather gets colder.
If there are more events that you would like adding to this list, please feel free to raise a feature request on the github page.
Mark - thanks for the update. Just one question, how do we configure the new views on the schedule card? Iāve updated but donāt seem to be seeing anything different.
I have upgraded to 3.2.2 and switched an existing automation to the new built-in event. All working. (And disabled generating the old wiser_room_boosted event). Thanks again Mark.
Turning the boiler on and off frequently isnāt that much of an issue, in fact with OpenTherm, the boiler is constantly modulating to achieve the desired temperatures. If a single room calls for heat then yes, the boiler will come on but if all other rooms are not calling for heat (iTRV closed) then the boiler will not be using as much energy as when multiple rooms need heat (less water to heat up). If the room(s) you donāt want to heat overnight are triggering the boiler you can create a specific schedule for that room(s) and put the fallback temperature lower for them.
So multi-room is energy efficient (I believe BEAMA have some research on this and concluded high single digit percentage savings). As others have said, only heating the rooms you need, and most importantly, keeping doors closed, is key to energy saving.
Iāve noticed over the past couple of months that entity history graphs, such as the temperature graphs for a climate entity, seem to freeze randomly for various lengths of time. When the graph unfreezes, the historical data is then shown correctly. Has anyone else noticed this?
Thanks! Our boiler is strictly on/off at the moment and non-condensing, but the whole topic is really interesting.
What youāre saying makes sense, but itās completely opposed to some online like HeatGeek who are pretty anti-zoning (although they admit it depends on lots of factors) because they claim it reduces boiler efficiency. So you might use more gas even though youāre dumping less heat energy into the house. Honestly, trying to wrap my head around it the last few days Iām gonna look for the research you mentioned!
I think in your case (no condensing boiler or modulating boiler), even Heat Geek say that zoning and setting the boiler temperature as desired in different rooms is absolutely fine. I believe the reason that they advocate for more restricted zoning is mostly predicated on the use of modulating gas boilers (& heat pumps) as they will run most efficiently at lower flow rates and therefore they advocate for longer lower heat rather than short blasts of much hotter heat.
I have a condensing boiler but not a modulating boiler as none of the main brands in the UK manufacture oil boilers that modulate. Iāve made sure Iāve set my boiler so that it is always in condensing mode. I also try to avoid over managing zones but I think Iāve found a really nice balance now.
I have just noticed this with one climate entity history graph. It flatlines in the HA android app. However the same entityās graph displays as expected in firefox.
But you are right, with heating a home it can get complicated. Different boiler types, different fuel types (gas, oil, solid, electric), different technologies, different secondary heating (UFH, radiators, electrical convection, IR), but most importantly, different home dynamics that affect the thermal profile of your home. If you know what you are doing then itās fine, if not it is always advisable to consult a heating engineer.
Maybe I misunderstand the gauges in HA, but my system is set to away mode, away mode threshold is 13.5 degrees.
In the wiser phone app, Lounge & Bed 3 are shown as below threshold and on, but in home assistant, the gauges show the actuals are below the threshold but I see no indication that the heating is on in those 2 rooms ??
AFAIK, Wiser wonāt automatically fire the boiler once a zone goes 0.1c below the setpoint, probably because otherwise itād overshoot and youād end up wasting energy. Sometimes it allows the temp to drift lower (although not by much) before giving it a short burst try and keep it as close to the setpoint as possible. Avoiding that confusion is probably also why the app doesnāt report in 0.1c increments
Itās still a lot better than other systems, for example I had a relatively new thermostat that would only begin āmodulatingā the boiler output when a zone fell 0.5c below threshold, and it would keep firing on-and-off until it was 0.5c above.
seems that all rooms except for the kitchen follow the away target mode, no idea why or how to make the kitchen follow the same target as all of the other rooms !
Click the 3 vertical dots in the room thermostat, Operation > Select Heat, and Preset Select āCancel Overridesā and the room will then follow the same away settings as other rooms.
The āCancel all Heating Overridesā does not appear to do what it says
@msp1974 - I think this might be a bug, āCancel all Heating Overridesā does not appear to do what it says on the box ??
I dont think the hub clases away mode as a true mode setting. As such, it is not classed as something that gets overridden. If there is an override (as far as the hub is concerned) then it will display override on the climate card.
Therefore, what ever happened to take kitchen out of away mode, is not classed as an override to cancel.
Ill have a look at this but it is definitely the way the hub behaves as we call a single command to cancel all overrides on the hub. I presume, if you tried the same with the app it would do the same?
Iām gonna look for the research you mentioned!
