So great and refreshing to see engagement from Schneider on this forum. It really is a great product priced at a reasonable price point (unlike some of the other systems). The ability to control it using home assistant via this integration is invaluable and I really do hope Schneider will continue to allow local access to their products far into the future.
Re: the disconnections I experience them infrequently but they do occasionally happen. Interestingly, it happened this morning - usually I would power cycle the heat hub but after reading on this forum about changing from setup mode and back again, I tried that. However, on this occasion it actually caused the hub to power cycle and once powered on it connected back on to my WiFi network. My network is just a Linksys router running Openwrt as the firewall/router and a number of Unifi APs.
Had another 6h 00m 5s outage. Had 2 in the last 24 hours. Not sure whatâs changed to increase the durations on these.
On a side note does anyone know if the Wiser System is about to be made EOL, or specifically the TRVs?
Iâve bought a bigger house and I need 5 more TRVs and have been looking around to get them sorted before we move. Last week I had to replace a TRV under warranty and had to go down the refund and rebuy route as the retailer couldnât do a straight exchange due to it being over 12 months.
I purchased it at ÂŁ40 14 months ago, but I had to buy it again at ÂŁ43 last week. This week they are ÂŁ53 at the same retailerâŚbut lots of places have them listed at around ÂŁ35-40 but are on clearance or special offers but nearly everywhere is out of stock. Is this just a stock shortage or is something going on?
I am thinking of changing from Lightwave to Wiser as my LW Boiler switch is knackered and LW is rubbish in HA.
With wiser in HA would be able to do an automation where a trigger from Google Calender will let me alter the temperatures of the Trvs and therefore my heating would come on / go off?
I work shifts so cannot use a schedule.
Many thanks
This is the direct result of a global component shortage. We are making them as fast as we can but demand is very high at the moment.
Thatâs great to hear (that they are not disappearing)
Managed to secure the 5 needed from a store, it was a 2 1/2 hour round trip but with the âclearanceâ discount was worth it.
Iâve been having disconnection problems for months but wasnât aware this was a known problem until I came across https://github.com/asantaga/wiserHomeAssistantPlatform/issues/307 a few days ago.
In case it is useful here is some information about my issue:
I started using the integration in mid-November 2021. I have a Unifi USG router and two Unifi UAP-AC-LR access points. I experienced disconnects but they were not frequent or lengthy (just annoying). I attributed this to the large distance between the APâs and the Wiser Hub (though other devices were OK).
Something changed around July 2022. I started getting frequent disconnects, the worst lasting for 2, 4 or 6 hours exactly (the â2nâ disconnects).
Hereâs what I tried:
1 Using a Netgear Wifi Repeater EX3700.
2 Using a Raspberry Pi set up as an access point
3 Using a TP-Link TL-WA850RE set up in repeater mode
4 Using the TP-Link TL-WA850RE set up as an access point
All of these were within 12 feet of the hub. None of them made any difference to the problem. I ended up leaving setup 4 in place, <8 feet from the hub and with only the hub configured to connect to it.
I also tried using piHole as the DHCP server, instead of my router. No difference. Increasing the polling time to 60 secs hasnât fixed the problem (though it is possible it might have eased it).
Eventually I tried logging the disconnects using a program which retrieves data from the Home Assistant database to indicate (a) when the disconnects occurred and how long they lasted, and (b) when the Wiser integration was enabled.
See graph (which covers almost 2 months so is a bit congested). Although disconnects occur with the integration disabled, they are much more frequent when it is enabled. Also I have never had a â2nâ disconnect with the integration disabled, though it has been enabled for quite a lot longer than it has been disabled.
I have been trying to figure out what might have changed around July. All I can think of is:
(a) possible hub firmware upgrade
(b) integration upgrade
(c) TRV batteries got very low (I didnât care much because the heating was off). I donât see why this would make a difference, but since I put new batteries in the integration has been running for over 3 days without a â2nâ disconnect. I plan to run it a few more days before upgrading to 3.1.7.
When the hub disconnects the left hub light is solid red (though maybe sometimes it flashes and I havenât noticed).
Could it be that there are two problems, one resulting in disconnects of around 35 mins, and the other involving the integration and resulting in â2nâ disconnects? I tried disabling the integration shortly after the beginning of a disconnect to see if this would trigger a re-connect, but the disconnect still lasted 4 hours. I am convinced the hub firmware must have a two hour timer somewhere - this could perhaps be a clue to the problem.
Probably an answered question, but whatâs the best way to âswapâ between different schedules based on a home assistant event (for example, a âguest modeâ being activated)?
I see you can create two schedules in the Wiser app and have them apply to the same room, which is a bit weird. How is that feature meant to work?
EDIT: Just realised that selecting one schedule deselects the previous one, which makes sense 
Just need to automate it I guess.
This is great info. Thanks Steve.
There is a wiser service to assign schedule so just use that to select which schedule you want active.
The other way is to load schedule from file to over write the assigned schedule with new settings. Again, wiser service for this.
(for the record)
I managed to get all the buttons working fine following your advice @msp1974 and the documentation from v3.1.6.
Hot water (cancel + 30min boost buttons):
- show_name: true
show_icon: true
type: button
icon: mdi:water-boiler-off
tap_action:
action: toggle
hold_action:
action: none
entity: button.wiser_cancel_hot_water_overrides
name: Cancel boost
- type: button
name: Boost 30m
icon: mdi:water-boiler
tap_action:
action: call-service
service: wiser.boost_hotwater
service_data:
time_period: 30
Heating (specific iTRV, 30min boost + cancel buttons):
- show_name: true
show_icon: true
type: button
tap_action:
action: call-service
service: wiser.boost_heating
service_data:
time_period: 30
temperature_delta: 2
target:
entity_id: climate.wiser_bedroom
entity: climate.wiser_bedroom
name: Boost 30m
- type: button
tap_action:
action: call-service
service: climate.set_preset_mode
target:
entity_id: climate.wiser_bedroom
data:
preset_mode: Cancel Overrides
entity: climate.wiser_bedroom
icon: mdi:fire-off
name: Cancel boost
I also created sensors to pick up the target temperature attribute from the iTRVs so I could plot the iTRV target vs the room temp taken from another sensor.
- sensor:
- name: "Bedroom iTRV target temperature"
state: >
{{ state_attr('climate.wiser_bedroom','temperature') }}
icon: mdi:thermometer
device_class: temperature
and finally
- type: custom:mini-graph-card
hours_to_show: 24
points_per_hour: 2
entities:
- entity: sensor.snz_t4_temperature
show_points: false
- entity: sensor.bedroom_itrv_target_temperature
show_fill: false
show_points: false
show_state: true
smoothing: false
Thank you!!
Pedro,
Firstly glad that the updated documentation helped you.
Just a minor point and not a big deal in your setup.
This is actually not the iTRV temp but the room temp. If you have either 2 TRVs in a room or a TRV and a roomstat then this will be different from the TRV temp. If you only have 1 TRV, then this is the same. The true TRV temp is on the ITRV signal sensor as the temperature attribute. On the signal sensor doesnât make a lot of sense but didnât think it needed its own sensor.
For your situation, there is also already a sensor that provides this information (you need to turn on LTS sensors in the integration config). The LTS sensors provide, room temp (same as TRV if only 1 in room), room target temp and room heating demand. Saves you creating this sensor yourself.
Anyway, glad you got this working and thanks for sharing your setup for others.
My entrance hall spans two floors with a radiator on each.
Iâm currently treating it as one room and noticed that both radiators arenât always heating at the same time. The graph shows that the lower radiator often measures a lower temperature than the higher one, and this is often lower than the room temperature calculated by Wiser and the target temperature for the room. Iâve noticed that the downstairs radiator is often not heating when the upstairs one is, even though it is colder, and the lower part of the hallway is noticably colder (because warm air rises).
I placed my Sonoff Temperature and Humidity Sensor in the hall to get a more trusted view on the true temperature.
I am going to start treating my hallway as two separate rooms in Wiser to see if this improves things. Has anyone else done any experimentation around this? Any input from the Wiser folk?
What are people using to monitor the wifi dropouts?
I setup ping to scan every 5 minutes but how does this differ from the cloud connection attribute?
The cloud connection attribute is coming from the hub and is its connection status to the cloud. If the hub drops off wifi, you cannot get that info from the hub and therefore it does show as connected as this was the last update it got.
As ping sensor is obviously your HA machine pinging the hub to see if it is on the network
Much appreciated, I didnât know about the LTS sensors (why are these disabled by default, to save HA the calculations/load or to lighten the load on the wiser hub?).
In my case, I only have 1 rad per room at most, but I find it silly to take a temp reading fro the trv valve, so all I want is to get the target temp so I can adjust against a separate zigbee sensor. I just enabled the LTS sensors so will change the config to read off those.
I would definitely recommend treating it as two rooms. At best you would get an average temperature across the two hallways, if one is warmer than the other (which is the case with the upstairs hallway) then it will always drag up the average temp for the downstairs one too. Do you have any room thermostats in the hallways? If you do, that temp will be used instead of the iTRV averages and if you have it only in one hallway it wonât be reflective of the other.
Thanks for the info and advice. At the moment there is no room thermostat in the hallway - just in the living room which has two radiators and where the family spends more time.
Already the hallway feels warmer than yesterday. Will keep an eye on it over the next few days.
The system time on my Wiser Home app seems to be permanently set to GMT (as shown in System Settings), even though we are currently in BST. As a result, my heating schedules come on an hour too late. As far as I can tell, the system doesnât seem to be aware of daylight savings time and so doesnât switch appropriately.This seems like a significant oversight.
I thought about trying to hack around this problem using HA in two ways:
-
Use HA to set the Wiser system clock to the correct time twice a year â this would be ideal but I donât see a way to achieve it
-
Use HA to fetch all the schedules twice a year, modify all the times by 1 hour, and upload them to the hub
Before I embark on (2), I wondered if anyone else has either succeeded in doing (1) or has a simpler solution to this problem.
Mine handles BST, so I would presume you have something set wrong. I would check what timezone you have set via the app in system settings
My Wiser also shows the correct time in System Settings > System Time and Date. Note that the Time Zone set in System Settings doesnât display any DST indicator - I have UTC Dublin, Edinburgh, London.
Also check the location of your home in Settings > Account > My Home.
If all this is set correctly you should log a support ticket through Settings > Support > Help. DST should be honoured by the Wiser system.