-
Notifications
You must be signed in to change notification settings - Fork 45
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
Allow functionality which boosts the entire house #180
Comments
fixed in 3.0 |
Is there an option to set the temperature boost for this all rooms update? Just testing all my setup/automations for V3 so thought id have a look at new bits and for all rooms its set 1 hour & 0.5c boost, time is ok (although my be nice to also have a default boost time) but 0.5c seems pretty low (especially when default for 30/60/120mins per climate is 2c) |
Yes, this is a bug in the api. Will be fixed in next release. |
thanks!! just an fyi, there appears to be an issues with set_heating_schedule on multiple climate zones at once (via node_red) too but still trying to debug it as doesn't always happen; code I have is https://pastebin.com/FLBbkbFF (was fine on v2) its changing the schedule temps of each climate fine but often its changing the first climate it finds (in my house living room) to +5c for 300mins (although not always) edit: screens re second points (will create a new post when I find the link) set to summer living room (18.3 - set to 8): set to winter living room (18.3 - set to 23.5 for 300mins): living room [after clicking auto/schedule] (18.3 - set to 13): |
so found the issue, wiser.boost_heating is now only a boost only settings rather than allowing for a target temp to be set even if its lower than current temp; a few of my current automations are along the lines of "if door is open then 'boost' room temp to 5c." (to kill the radiator) which is now being read a 'current temp + 5c'. guess best way forward is requesting a wiser.set_target_temp service? (as I assume the wiser.boost_heating changes have been reduplicated/replicated/called into all the other actions? i.e. 'boost for X mins') |
Maybe not very clear in documentation but you can use a number of the climate services, the wiser ones are only for additional functions not built into standard climate device. There is a climate.set_temperature service which will do exactly what you are asking. Only difference is that it does not do it for a specified time, just until next schedule change. You could also call the climate.set_hvac_mode and set to off if you just want to kill the radiator. As a side note, there is a window/door open function on the trvs (which can now be enabled in v3). Never really tested it so not sure if works well or not but think it is designed to stop heating if it detects a sudden drop in temp. Mark |
climate.set_temperature seems to work thanks 👍 window/door open within wiser is shite lol |
Issue with boost all rooms not honouring the temp setting is fixed in 3.0.15, which I have just released. |
This should now be fixed, so closing issue. |
yeah working fine now mate! (apologies thought i'd already replied confirmed working with the update) |
From https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965/285
This can be done today via scripts, hard coding the rooms (or dynamically querying them?).
FR to either
a) Add script to release
b) Add functionality to integration so that it loops around and boosts all radiators
User can then bind a button to boost all
The text was updated successfully, but these errors were encountered: