Drayton Wiser Home Assistant Integration

msp1974 · January 29, 2022, 7:00pm

I am sometimes accused of having too much time on my hands and this maybe a perfect example.

Anyway, @Frazzyfin, looking at your script and your chat with @wombateer got me thinking if there was a way to do what you are trying to do without having to do it for each room separately and be able to boost/cancel to achieve the Goldilocks room temp - not too hot, not too cold! .

So, below, is a link to what I have got. This will go as a recipe on the integration repo when it has been tested in the wild. It needs to have the current dev branch of the integration which has the current_schedule_temp attribute.

github.com

asantaga/wiserHomeAssistantPlatform/blob/dev/manage_temps.md

# Using External Temp Sensor to Manage Room Temp Accuracy

The basic premise of these scripts is to monitor a series of external temperature sensors and fire an event when their reading changes.

Automation 1 is basically filtering all HA state change events to capture only those from your specific temp sensors.  When it detects one of your sensors has changed temp reading, it raises and event which is the in turn picked up by Automation 2 & 3.

In order for this to work, all you need to do is have your temp sensor and the wiser climate devices in the same HA Area, as it looks for a Wiser climate device in the same Area as the temp sensor.

Adding new climate devices or temp sensors (providing they are of the same type you already have) should require no changes to any of these scripts.

If you have rooms that have Wiser in them but no seperate sensor, then that is also fine as it is driven by the sensor.


# Automation 1

Depending on your sensors you are using, you may need to modify this script.  I am using Aqara sensors connected via ZHA integration.  The value template in the condition is where you will need to modifiy to filter this to your specific sensors.

```
alias: Fire Event when room monitoring temp sensors change reading
description: ''

This file has been truncated. show original

euinor · January 29, 2022, 10:23pm

Edit: Found the answer, it should be true not 'true'

I’m struggling to create a switch that boost/cancel the boost in the new version of this integration. The problem is that the switch immediately turns off, even though the attribute I’m testing against is remains true.
This is my switch. Any idea what is wrong with it?

  - platform: template
    switches:
      master_bedroom_boost:
        friendly_name: Master Bedroom
        value_template: "{{ is_state_attr('climate.wiser_master_bedroom', 'is_boosted', 'true') }}"
        icon_template: "{{ 'mdi:fire' }}"
        turn_on:
          service: climate.set_preset_mode
          target:
            entity_id: climate.wiser_master_bedroom
          data:
            preset_mode: Boost 1h
        turn_off:
          service: climate.set_preset_mode
          target:
            entity_id: climate.wiser_master_bedroom
          data:
            preset_mode: Cancel Overrides

Frazzyfin · January 30, 2022, 2:25pm

This looks really good. I’ll give it a go when I get some time this week.

Just one thing I saw while skimming through the code - in the Automation 1 condition, shouldn’t the logic be to subtract the sensor from the setpoint, not the other way round? Or perhaps I’ve misunderstood the code.

msp1974 · January 30, 2022, 2:57pm

Yes you are correct. I had changed it but seems the link i posted was link to previous version.

Frazzyfin · February 1, 2022, 5:53pm

@msp1974 is there a way to get the dev branch via HACS?

Angelo_Santagata · February 1, 2022, 10:14pm

I’ll answer this ,

no, HACS works by linking to the github releases, so everytime we release it then becomes available. What we have been doing is creating “pre-release”, aka beta, releases, these also become available.

I think you could clone the repo to a local directory on your computer and then copy the files across… Not tried this though, and HACS might get upset if you override the manifest file

msp1974 · February 2, 2022, 11:50pm

@Frazzyfin i have release v3.0.20 tonight which has the new current schedule temp attribute. You can now update it via HACS.

I have also been working on the automation and managed to consolidate it into a single file. See below.

github.com

asantaga/wiserHomeAssistantPlatform/blob/725e87e101d0badb06ea6d5074598d7686f94265/recipes/manage_temps.md

# Using External Temp Sensor to Manage Room Temp Accuracy

The basic premise of this automation is to monitor a series of external temperature sensors and boost wiser room heating to reach the correct temperature as set by the schedule.

On updates from the external temp sensor, it will compare this to the scheduled temp of the Wiser climate device (aka room).  If the room is not already heating or boosted, it will boost the room by 1.5x the difference.  I have found this to give pretty good results but this may need tweakign for your own situation.

It will also look if the current room temp is within 0.5C of the scheduled temp and cancel any boost if it is.  Again, this number can be changed but will involve a number of places to change it.

## There are 3 requirements for this automation to work:

1) You need at least version 3.0.20 of the Wiser integration for HA.  It uses the 'current scheduled temp' attribute that was new in this version.
2) That your temperature sensors are setup in HA Areas with the Wiser Climate device you wish to control in the same area, as it looks for a Wiser climate device in the same Area as the temp sensor that triggered a state update to get the scheduled temp and set a boost.
3) The first condition in the automation may/will need to be adjusted to filter your specific temp sensors.  I am using Aqara sensors via the ZHA integration.


Adding new climate devices or temp sensors (providing they are of the same type you already have) should require no changes to this automation.

If you have rooms that have Wiser in them but no seperate sensor, then that is also fine as it is driven by the sensor updating its reading.  If it's not there, no reading updates!

```yaml

This file has been truncated. show original

Chris_J · February 4, 2022, 12:23pm

Thanks for this.

I updated to 3.0.20 and copied your automation to my setup. I also use the Aqara sensors, so I hoped this would be a copy/paste job, but I get this error in the logs:

Error while executing automation automation.adjust_wiser_boost_for_ext_temp_sensor_heat_management: Error rendering data template: UndefinedError: 'dict object' has no attribute 'event'

Not sure I understand what the issue is. Any ideas?

msp1974 · February 4, 2022, 2:58pm

Did you run the automation manually? It relies on a temp sensor triggering a state update to provide the event details. Just tested running actions manually and get the same error - which is expected.

Let it run and see what happens. If you look a climate device, you will see in the history where is boosts and also in its log book it shows if it has boosted due to reading from temp sensor.

EDIT: To add, I am finding that the Aqara sensors seem to not update very regularly. I understand they will only send update if temp raises by x to save battery but not yet convinced this is right. However, after running for a few days with my boost settings, it does seem to do a pretty accurate job of managing to correct temp. You may need to play around with these if yours doesn’t.

Angelo_Santagata · February 4, 2022, 3:05pm

Nice, based on this Ive bought myself a Aqara sensor, and was tinkering with it… I wish the wiser TRVs had a “delta” setting, ie i record 18c but its really 20…

Chris_J · February 4, 2022, 3:07pm

Yes, I was running it manually to see whether my assumption was correct regarding entity naming. I’ll let it run normally and see what happens. Thanks again!

dunxd · February 4, 2022, 5:35pm

I’ve posted a suggestion for some form of calibration on the iTRV support page at https://schneider-electric.zendesk.com/hc/en-gb/articles/360014543338-Does-the-Wiser-Radiator-Thermostat-measure-temperature-the-same-way-as-a-Wiser-Room-Thermostat-

I don’t know if it has any influence on their development, but probably as good a place as any to make further suggestions and perhaps build some public support for ideas.

msp1974 · February 6, 2022, 11:56am

@Chris_J how is this working for you?

nofuse · February 6, 2022, 3:56pm

Hi all,

since upgrading to v3 my history stats sensors for calculating how long each room has been heating for don’t seem to work accurately. This is confirmed by checking the insights in the wiser app.

If there a LTS for calculating this info, I know there is for heating demand but that is a percentage not a time value.

Thanks

mark3267 · February 6, 2022, 7:46pm

Hi, I updated to v3.0.18 yesterday and I’m having a problem with cancelling a boost.

I’m trying to call the service CLIMATE.SET_PRESET_MODE as below

service: climate.set_preset_mode
data:
  preset_mode: 'Cancel Boost'
target:
  entity_id: climate.wiser_mark_s_office

Previously this worked, however following the upgrade yesterday it no longer cancels the active boost in wiser_mark_s_office

Has something changed?

Sandy · February 6, 2022, 10:20pm

Hi, I’ve just set this up and it seems great so far when it works. I do have an issue though that my HA has lost connection with the hub and now can’t reconnect despite multiple tries. It this a bug or simply a matter of the signal from the hub being too weak? The hub is in the loft but I have a mesh wifi network so it’s not that far to the nearest access point.

It was showing all the iTRV’s upstairs as having good signal before everything stopped working and there is an AP on this floor.

It is giving this log:

Connection error trying to update from Wiser Hub 192.168.68.101. Error is HTTPConnectionPool(host=‘192.168.68.101’, port=80): Max retries exceeded with url: /data/v2/domain/ (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7f0a75ef8190>: Failed to establish a new connection: [Errno 111] Connection refused’))

22:16:58 – (ERROR) Drayton Wiser Integration for Home Assistant (custom integration) - message first occurred at 21:58:11 and shows up 17 times

msp1974 · February 6, 2022, 11:03pm

Mark, Cancel Boost is now Cancel Overrides.

msp1974 · February 6, 2022, 11:06pm

Sandy, are you sure that is the IP of your hub? You’re unlikely to get a connection refused from a Wiser hub unless there is something wrong with it or something is blocking like a firewall or something. A connection refused means the IP is valid but it is not listening on port 80. Hence why i wonder if your IP is correct.

Sandy · February 7, 2022, 12:52am

On checking, you are correct, the IP given in the error does not match the IP of the hub. Why would that be? I had everything working yesterday, I can see in my history when it went down but I can’t think what I changed. I have been playing with various stuff all day though

msp1974 · February 7, 2022, 9:33am

This then would point me to a dhcp issue. It seems like the ip of your hub has changed. You will need to set an allocated IP to your hub in your WiFi Ap.