Does it actually boost?
All this functionality is within HA code (core and integration), so the obvious question (after have you switched it off and on again! ) is what has changed? Any upgrades performed?
Does it actually boost?
All this functionality is within HA code (core and integration), so the obvious question (after have you switched it off and on again! ) is what has changed? Any upgrades performed?
Hi Mark, yes, it does boost - the trigger just wasnât fired.
And no, there were no changes I can think of that would have caused it to stop working. No updates or reboots.
However, I have now changed it to a Device trigger and it is now working fine!
triggers:
- device_id: 3b33c2b5b652d5c29b5107abe8f702d6
domain: wiser
entity_id: climate.wiser_living_room
type: boosted
trigger: device
I also found this sagely advice from a previous post of yours: Drayton Wiser Home Assistant Integration - #835 by msp1974
I.e. make sure the YAML is saved without quotes around the boolean values. I donât know if this is still an issue but I will certainly try it if I run into issues again.
Hi,
Just got this integration up and running with my wiser home hub and trvâs. Firstly to say great work.
Have a couple of questions though where itâs hard to find the answers. Sometimes the TRVâs will be on and displayed as on on the wiser app but will not say âheatingâ on the wiser card.
I have my lounge set to a schedule and all other rooms are in passive mode to my preferred heat settings.
Additionally is there a way to set thresholds between temperatures? Iâm not sure if wiser does this itself as I donât monitor it constantly but weâre having a cold week and with the lounge schedule set to 20C the heating is on/off constantly, it would seem once is decrements by 0.5C
I said I wouldnât contribute to this thread anymore butâŚno-one else is helping you out.
I donât think there is a way to set increments, Wiser thermostats and the hub, as far as I know work with 0.5C increments.
You are describing how I thought Wiser works.
It doesnât do anything until 0.5C under unless it thinks it will fall further below that before the end of the schedule when it will kick in again until it thinks the temp fall will be within its schedule.
With Passive this is amplified because there is a hard coded 0.5C increment. @msp1974 can confirm this (or deny).
The best person to clarify this is @robertwigley who designed the Passive mode algorithm.
Apologies to all tagged
I canât remember the exact algorithm for Passive Mode off the top of my head, but itâs discussed further up the thread. Search and you should find both the discussion and the original automation I wrote that @msp1974 incorporated into the integration.
There is an option to change the increments for Passive Mode from the default of 0.5. Open the Wiser Integration in Devices and Services, then select Configure / Automation Parameters / Passive Mode, but I wouldnât recommend changing this unless you have read the discussion about how the automation works.
Great, thank you for the time spent clarifying this for me, Iâll have a further search around this thread further.
Can I just clarify, the Wiser Hub needs a static IP for HA to be able to find it?
In that case, my router does not provide any options for me to reserve a IP. Is there a way to set a static IP somehow in/on the hub?
No, you cannot fix an ip on the hub, dhcp only. However, instead of using the IP address in the HA config, you could use the dns name.
Ie wiserheatxxxxx.local
Or what ever your dns domain is. Try getting the dns name to ping first before setting in config.
DNS name worked perfectly, thanks I may do the same with some of my other Tuya devices!