Drayton Wiser Home Assistant Integration

Thanks Jamie, I am also on the Schneider Wiser forum but unfortunately no one from Schnieder or Drayton ever seem to answer questions over there. Its a shame as people are asking for help and making feature requests and no one acknowledges them.

It’s just for the love of it! :grinning:

1 Like

WAF dropped from 100% to about 50%. Hub connectivity to my mesh quite unstable at times.

Can you catch me up on the current issue?
Thanks

I don’t know if the hub chooses the best ZigBee channel based on the whole 2.4 GHz spectrum that ZigBee channels inhabit. Does it assess which WiFi channels are in use and avoid them? Does it look for other sources of radio interference in this range? At its simplest it might just select a ZigBee channel that isn’t being used by any other ZigBee networks.

Without knowing the answers to those questions, personally I wouldn’t switch and risk the hub deciding on zigbee channel 16 or 17 which overlap both WiFi 1 and 6.

If you aren’t dealing with lots of neighbours’ WiFi, I suggest sticking with ZigBee 25 and adjust your WiFi networks instead as a lot more control is possible. Switching to 5Ghz for most things is likely better than tweaking channels.

All that said, I am not sure how much of an issue ZigBee and 2.4 GHz WiFi coexistence causes.

1 Like

Love… hahha

well actually 11 – 15 would be ideal. In my house I have neighbor interference , my wifi and another zigbee network to contend with.

12-15 potentially interfere/get interference from both 2.4 GHz Wi-Fi channels 1 and 6, so the most favourable ZigBee channels are 11, 25 and 26, with 25 and 26 best of all as they only overlap the side lobes of Wi-Fi channel 11.

If you have to share a Wi-Fi channel with one or more neighbours that is better than sharing with zigbee channels, as Wi-Fi is designed to negotiate sharing spectrum with other Wi-Fi network. You will lose maximum speed, because each network has to take it in turns to speak, but you shouldn’t get intermittent outages. Sharing spectrum with non-Wi-Fi traffic (ZigBee, microwave ovens, cordless phones, baby monitors etc.) is more likely to manifest as Wi-Fi disconnections and drop outs which are hard to troubleshoot. You probably won’t notice any issues on the ZigBee side, as it is far less user facing and resilient to brief outages.

You aren’t guaranteed to experience any of these problems, much of the time it just works out fine. You won’t know till you make a change and live with it for a few weeks in your specific environment.

a ticket had been logged n°152122 but no response unless see in France where a ticket had also been logged.
No response on this zigbee instability.
Today I have some devices that randomly do not follow the schedules…
Do you have an idea.

my living room uses 2 electrical radiators and one roomstat, this night the target temperature move from 19 ° to 16 at 11 PM by a schedule
One of my radiator follow the schedule but not the other.
right behavior;

faulty one

How can we explain that? what can I do ?

The roomstat and both radiators are all in the same Wiser room right?

Like this in the Wiser app Settings > Rooms > Living Room:

yes they are
this problem is not systematic, it can also happen on other devices or rooms…

@msp1974 Any chance of adding an option to the Schedule Card to hide the title/heading?

Set it to a single space and it will hide it.

1 Like

:joy: I hadn’t thought of trying that. Perfect. Thanks. :+1:

Does anyone here use Wiser with a heat pump?

I have a hybrid ASHP / gas boiler system, and have my Boiler Type set to ‘Heat Pump’, which should give a Cycles Per Hour (CPH) value of 3; however, I’m seeing the Wiser Heating sensor showing the boiler turned off for 2 minutes, then back on for 8 minutes, or 10 minutes or 12 minutes:

image

I would have thought CPH_3 would have meant 20 mins off, 20 mins on cycling. If the heat pump is only spinning for 8 minutes, it’s burning electricity for no apparent benefit as the water circulating will still be cold.

Hoping someone else with a heat pump can confirm how short their cycles are!

@liveware-problem as far as community is aware heating-type only changes how many times heating can be demanded per hour. For Heat pump or Oil boiler number is 3 but it doesn’t control the duration at all.
I have gas boiler and have setting set to Oil boiler and getting same behaviour as you. Basically single heating duration in same hours can last from 1min to 60min. Also I think this means if 3 heating demands have been used by 3 5min cycles and you change schedule you will be waiting for next hour to get heating. This doesn’t apply for the overrides though.

I think all it means there will be a maximum of 3 cycles per hour. I see a number of 4 minute on periods followed by 16 minutes off or other combinations with the “on” and “off” periods summing to 20. The start of two “on” periods will be 20 minutes apart. That’s with the oil option. Although I have a gas boiler I’ve set the oil option to minimise the number of hourly cycles to 3.

I’m trying to move my wiser installation from a hub first generation to a box 2nd generation (step by step of course).
I 've got the secret key to configure the Wiser integration, the new hub is detected by HA and when I give the secret code I get an error:
“Unable to authenticate with the Wiser Hub. Check the secret key and try again.”,
logs:
2023-02-06 14:08:24.230 ERROR (MainThread) [custom_components.wiser.config_flow] Unknown error connecting to Wiser Hub
Traceback (most recent call last):
File “/config/custom_components/wiser/config_flow.py”, line 158, in async_step_zeroconf_confirm
validated = await validate_input(self.hass, user_input)
File “/config/custom_components/wiser/config_flow.py”, line 60, in validate_input
await wiserhub.read_hub_data()
File “/usr/local/lib/python3.10/site-packages/aioWiserHeatAPI/wiserhub.py”, line 188, in read_hub_data
self._rooms = _WiserRoomCollection(
File “/usr/local/lib/python3.10/site-packages/aioWiserHeatAPI/room.py”, line 514, in init
self._build()
File “/usr/local/lib/python3.10/site-packages/aioWiserHeatAPI/room.py”, line 526, in _build
_WiserRoom(
File “/usr/local/lib/python3.10/site-packages/aioWiserHeatAPI/room.py”, line 44, in init
self._extra_config = self._wiser_rest_controller._extra_config.config(
AttributeError: ‘_WiserRestController’ object has no attribute ‘_extra_config’

Yes - its a bug in the v3.2.3beta versions that it errors on setup. Install the v3.2 version and then upgrade and it should work.

1 Like