Drayton Wiser Home Assistant Integration

Third party integrations
130

thank you
Its a community effort though and there are other contributors, like Mark - but thanks!

131

This integration is really useful - and looking pretty nice now.

One issue - I assume it is something to do with my network rather than the Wiser hub, but I’m struggling to get the hub to use a consistent IP address. I do see some duplicated IP addresses (for other devices), so probably it’s my network setup but thought it was worth making a post just to see if anyone else sees this.

132

Hi Angelo,

I keep getting these errors in the log every time I restart HA.
I think I first saw these on 0.110.x but they are definitely there on 0.111.x
I haven’t tried 0112.x yet.

2020-07-03 14:11:01 WARNING (MainThread) [homeassistant.components.switch] SwitchDevice is deprecated, modify WiserSwitch to extend SwitchEntity
2020-07-03 14:11:01 WARNING (MainThread) [homeassistant.components.switch] SwitchDevice is deprecated, modify WiserSmartPlug to extend SwitchEntity
2020-07-03 14:11:03 WARNING (MainThread) [homeassistant.components.climate] ClimateDevice is deprecated, modify WiserRoom to extend ClimateEntity

Is there something I should be doing to resolve these?

I also notice that your integration can now be added through the configurator UI.
Should I remove the old one configured in the configation.yaml and re-install it through the configurator UI? If so will all the device names and entity names change?
I wouldn’t want to have to go through amending all my automations, scripts and the lovelace yaml.

Thanks for a great integration

133

Hey im sure we resolved these in the latest Wiser integration. (2.3.1) have you upgraded?

I’ll check later (its my sons birthday today) but im sure these are solved.

Oh, no need to use the configurator UI (configFlow) , you can continue to use yaml

134

Hi,

Happy birthday to your son.

According to HACS i’m running 2.3.1
I haven’t seen any updates from you for a while though hence my thoughts that maybe I need to install through the configurator rather than HACS.

Thanks, I’ll wait for you to come back.

135

Hey,

Right , we fixed this bug in dev but didnt push it to master yet. Why?

Well , we’ve been working to try and get the Wiser integration included with HA as a native component… Alas we’ve done all the code changes, tests etc and now the HA team want us to publish the component , one platform at a time. Given we have sensors, switches, services and climate we think this is kinda daft… anyway we’re asking that given this component has been around for a while on HACS , if we can work around this…

Alas I havent received a response from the HA team so I dont know… For now its on HACS…

Ive released a new version of the code to HACS (2.4Beta), can you give it a swirl?

thanks
Angelo

136

Hi Angelo,

Yes 2.4Beta solves the errors and all looks to be working.

Why bother with the the native component. It appears to me you will lose the control and flexibility you have now through HACS.

Thanks again

137

I know,… Im thinking of keeping it a HACS component

138

ok , based on https://github.com/home-assistant/architecture/issues/408 I have to split up the PR into multiple pieces and thats it…

q: How important is having this integration with HA Core? Or is leaving it in HACS just fine.?

139

After a few weeks of my system working fine with this Integration (apart from a rebuild due to ye olde SD card burnout), I came to do a reboot (upgrade to Hassio and to the Wiser integration) and HASSIO seems to have lost any connection to Wiser, with all my devices/entities showing as Unavailable. My wiser app works fine (as does the heating, thankfully) and I’ve tried rolling back on the Wiser integration itself, with a few reboots, but no dice. Any ideas what’s up?

140

Has your IP address of the HeatHub changed?
Any error messages in the log files?

141

I’ve a few ‘unable to find’ messages in the logs, so I expect you could be right with the IP changing. How do I view what the integration expects the IP to be? I used the interface to set up the IP and secret initially, rather than the config.yaml, but I don’t know where it stores it. I’ve had a route around in the File Editor and the Integration itself but can’t seem to find any record of what it expects it to be set to. Presumably I can make my DCHP server set it back again once I determine if it’s changed…

142

Hi there.

Right firstly I recommend you use your router to set a fixed IP to the wiser heat hub. I have a virgin hub and in the DHCP section you can select the wiser heat hub and say “reserve this IP”…

In the same section you can see what IP address has been allocated…

Secondly, the “current” setting can be found in ./storage/core.config_entries look for the domain wiser

Mine looks like this

        "connection_class": "local_poll",
                "data": {
                    "boost_temp": 2,
                    "boost_time": 30,
                    "host": "192.168.0.15",
                    "name": "WT724R1S0902",
                    "password": "xxxxx"
                },
                "domain": "wiser",
                "entry_id": "xxxxx",
                "options": {},
                "source": "import",
                "system_options": {
                    "disable_new_entities": false
                },
                "title": "WT724R1S0902",
                "unique_id": "WT724R1S0902",
                "version": 1
            }

Just edit this file and perhaps restart HA if it doesnt take immediate effect

Let me know how this goes

143

Awesome. Thank you very much for your help!

I usually fix IP addresses (albeit I have an extra router attached to my Virgin Hub to do that) but I’d obviously forgotten to create one for the HeatHub and it HAD changed. Looked up the file you’ve pointed me at, forced the router to change the IP back, and it’s all up and running again.

Thanks again!!

1 Like
144

Awesome… I need to get a new router to front end my crappy VM3 hub… its crappy… :slight_smile:

145

Hi

What sensor do you monitor to get “ the heating on today” time value.

I’m not using Node-Red just a direct integration in HA

146

Use history_stats and reference the area state value. I have written all my interface in node red, so your text via the wiser add-on may differ from mine.

  - platform: history_stats
    name: Guest Bedroom Heating On Today
    entity_id: sensor.guest_bedroom_state
    state: 'On'
    type: time
    start: '{{ now().replace(hour=0).replace(minute=0).replace(second=0) }}'
    end: '{{ now() }}'
2 Likes
147

Hi all,

Does anyone know if the boost remaining time can be shown in the intergration?

Also is there anyway to view the time the heating has been on for each room like what Lev has achieved using node red? When I look at the entities none of them seem to include this data unless it is the “control_output_state”

Thanks

148

For #1 : Boost Time remaining : No, I don’t think I saw that in the data from the hub, but I’ll check later. If boosted from HA you could set a variable to when the boost was initiated and then do a count down…

For #2 : Alas I dont use nodered :frowning:

149

  1. The boost remaining time is definitely there as it was available in the OpenHab binding for Wiser.

  2. nodered isn’t required to obtain the individual room “control_output_state” This value is available to view if you query the “climate.wiser_xxxxx” state from the developers menu in HA. I just want to be able to use this state change from Off to On so I can try and log heating on duration for each room visually and/or export the data in to Grafana so any help doing this would be appreciated