The “Wiser Valve Protection” toggle in Home Assistant does change the status of “ValveProtectionEnabled” in the Wiser hub correctly between true and false. I always have mine switched on so I don’t know if switching it off achieves anything other than changing the status in the hub.
Hi - please excuse a potentially dumb newbie question … I’m planning a Drayton Wiser installation on my existing central heating/hot water system, and intend to use this HA integration as my main controller. I have a running HA setup, just doing a few very simple things at the moment, but its main use will be for this integration. There will be 12 radiator iTRVs and probably a couple of plugs for range extension (its a three storey house with thick walls and WiFi has been a real problem).
I’m now trying to work out how many room thermostats to get. We’ll have the HA app on our phones so should be able to make adjustments from there on a routine basis, but I am mostly thinking about guests. We have a couple of guest bedrooms and I don’t think its reasonable to ask guests to load an app! But these things aren’t cheap. So how easy is it, really, to repurpose a room thermostat from one room to another? I guess I’m particularly concerned about having to fiddle with both the native Drayton configuration AND HA settings very time I move a thermostat.
Or should I just bite the bullet and get a room thermostat for every room that might potentially be occupied by guests, including main living rooms?
I wouldnt go mad on the roomstats, they are expensive as you say. If the rooms are proper guest rooms then maybe yes go for a few room stats. I havent had much time recently but I think someone up in the thread here mentioned its possible to get some EU thermostats for 1/2 the price…
1 Like
I agree with Angelo - no need to get many roomstats. Guests can boost the heat up and down using the iTRV twist control. The roomstats are good if they want to know the actual temp in the room, but for just adjusting for comfort the iTRVs are good enough.
You might want to use the integration to increase the boost time beyond the default - 30 minutes is too short when guests are likely to assume the iTRVs work like old style TRVs and just turn the temp up till they are turned down.
1 Like
The Wiser system isn’t a “learning” one like Nest. When boosting the temp, it just goes back to the regular setpoint after the boost ends.
Has anyone figured out a method to observe boosts allowing insight that a particular room should have a higher setpoint? Would an automation that notices if a room is frequently boosted and increments the setpoint be a way to build the learning feature that Wiser lacks? Anyone tried this?
Something like:
If there is more than 1 boost in a room per day in the same direction, then increment the scheduled setpoints in that room by 1° in the same direction.
Sounds like someone wants us to build a AI Reactive Model 
this could be built in the integration but would need to think how it would work… how intrusive etc…
I can see how this could be useful. However, and I’m pretty sure it would be anyway, but if this does become a feature of the integration, please keep it optional. This was one of the numerous reasons I got rid of the Nest that was here when we moved in. I don’t want an AI fiddling with my settings. 
5 Likes
I found the Nest “learning” feature rather underwhelming. Deciding on setpoints isn’t something that needs doing very often, especially with a single thermostat and schedule such as with Nest. I don’t think it is worth a ton of effort.
I would be happy with a system that suggested adjusting the setpoints for a room based on data gathered from boosts. I was hoping that the Insights feature of Wiser might do this sort of thing, but it just tells me the total number of boosts per month across the whole system, which isn’t really an actionable insight. It’s collecting a whole bunch of data but not really doing much with it (at least not for me).
Better would be - “It looks like the master bedroom feels cold in the evening - it’s been boosted 5 nights out of 7 between 10 and 11. Would you like to increase the setpoint between 9 and midnight by 2°C? Or maybe it’s time to swap in the winter duvet.”
How hard would it be to build that functionality into the integration, or with a collection of HA automations, or for Wiser to do it in the cloud and expose it to the Wiser app?
Seeking some help with an automation: How to suppress the next upcoming hot water event without modifying schedules?
Ideally assigned to an HA button that, once clicked, will prevent or immediately turn off the next upcoming HW heating event.
I’m thinking the button’s action enables an automation that waits for the next HW on event, toggles the HW off, then exits/disables itself.
Is that a viable approach and is there a better way?
Many thanks.
sensor.wiser_hot_water has an attribute next_schedule_datetime which contains the date & time of the next schedule change.
You could have your button set a timer for 1 second after the next_schedule_datetime and when the timer expires toggle the state of the hot water back to the previous state using button.wiser_toggle_hot_water
Alternatively have an automation which fires when sensor.wiser_hot_water changes state, this automation would check the state of your button and change the state of the hot water back to the previous state if your button is on.
1 Like
Many thanks for the suggestions.
With the second option, presumably I should also toggle the button state. I’m thinking I should also check sensor.wiser_hot_water is in the expected state prior to toggling it. I’ll give it a go and post result of my efforts back here.
EDIT - If sensor.wiser_hot_water is updated only after the data is read back from the hub, it is possible the state does not change to ON for some time after the schedule. In my case up to 1 minute as that is the update interval I configure in HA. I think that makes option 2 favourite.
I created a boolean input and added it to a dashboard. With this automation, which seems to be working.
Thanks for the guidance.
alias: HW off if skip_hw on
description: Acts on the skip hotwater toggle
trigger:
- platform: state
entity_id:
- sensor.wiser_hot_water
from: "Off"
to: "On"
condition:
- condition: state
entity_id: input_boolean.skip_hw
state: "on"
action:
- device_id: <wiser_hub_id>
domain: button
entity_id: button.wiser_toggle_hot_water
type: press
- service: input_boolean.toggle
data: {}
target:
entity_id: input_boolean.skip_hw
mode: single
1 Like
Bitten the bullet and acquired a Pi4 to run HA and integrate with my Wiser heating, initially to use the network/connection analysis tool to help me get an adequate signal to every corner of the big stone pile I live in. Got HA running, Installed HACS. Installed the Drayton Wiser integration. Got the secret from the Wiser hub. Attempted to set up the hub but got an error message “Invalid flow specified”. All software was installed yesterday & today so should be at latest versions.
Help!
Can you provide info on how you are setting up. Does it discover your hub and you add this way or are you clicking add integration…drayton wiser etc?
EDIT: Just found this. Invalid flow happens if you restart HA while it’s in a flow. You need to restart the flow after any restart of HA. Did you reboot HA after starting setup of Wiser integration?
Installed the integration via HACS and it discovered the hub, was providing the info as required in the configuration. HA was not restarted between installing the integration and attempting the configuration.
You do need to restart HA after installing i tegration before you can configure it.
Thanks. Here goes…
Success! Thanks
Hi All, Hoping to reach any NodeRED gurus which might be about.
I’m trying to set my Wiser climate entities to Heat/18.0*C using a Call Service node.
I can’t work out how to use a flow.temperature value in the Data section, I keep getting invalid syntax errors.
Data:
{
"data": {
"hvac_mode": "heat",
"temperature": [... this is what I can't work out ...]
}
}
Thanks in advance!
Looking back through some old notes I see that I successfully connected a Wiser smart plug, roomstat and iTRV to Home Assistant through ZHA instead of via the Hub and this integration. This was out of curiosity. I don’t recall there was anything additional available in terms of sensors or control that this integration doesn’t make possible. The smart plugs were detected as Heiman SmartPlug - and a search for that turned up these which look pretty familiar.
1 Like
