The geolocation? Im surprised you dont get more complaints about this… If I didnt have home assistant to control the away mode I would have moved away from Wiser when life360 dropped their integration.
Surprisingly, the average user (not us power users), are not complaining about the lack of geolocation in the app. We do have a handful of users requesting it, and it is a very useful feature, so we will be adding it eventually.
I am also very surprised geolocation is not at the top of the development backlog. Personally, I don’t need it as I have this integration, and presence detection in Home Assistant is always going to be far more accurate than any companies commerical offering. However, if I was a ‘regular’ consumer, this would be a massive missing piece if functionality.
Thank you @jamiebennett for being active in this thread. I’m sure we all appreciate someone from Wiser being here.
1 Like
Im now curious to what is the most requested, top of the pile feature for the average user 
1 Like
Thanks - I saw that in the update notes just now.
The issue with the LTS sensor now causes a different, interesting problem. When I turn the stat off, I now get a second graph appear:
As as for the preset mode error…I’m still seeing it. 
You will still see the preset mode error. It is likely to be fixed in the next HA frontend release which normally comes with a HA update. Next one is due in October, ie 2022.10.
In terms of your extra graph, i dont see this. It maybe you need some of the old data to drop off.
Really interesting that Geolocation isn’t a frequently requested feature. Any chance you could reveal anything that IS coming down the pipeline? 
Genuinely, it’s very refreshing to have someone from the corporate side so engaged with the HA/open source community. Creates so much goodwill.
Mark, I’ve just started fully using this integration and it is top notch. Automated heating is the cornerstone of a good smarthome and you are crushing it.
3 Likes
Sometimes the communication between HA and the Wiser hub stop.
sometimes the led of the wiser hub stay in green sometimes in red or red blinking.
I read all the conversations on the forum; I imagine another scenario.
My scenario
For my point of view the WiserHub can manage a certain number of connections as server (often for Schneider: 32) or per client.
I have already seen such issue when the client opens a new connection after an error, without closing the previous. When the maximum number of connections is reached it’s impossible to open a new one…
In this case there are two ways to recover:
Wait until the Wiserhub close the connection on time out
A power cycle clears all the connections and then the communications capability is available again.
To test this scenario: I ‘ve made some tests
In HA I restart the system and I check the communication on Wireshark. In the following example, I made it 6 times. For the 5 firsts the communication restart but the 6th I’ve got an issue
The Issue starts at 14:54:21.649 and ends at 13:31:16:.270, so time-out is about 36:54.
The led of the WiserHub is still green and the wiser entities are not refreshed in HA, they had been initialized.
Today ( 222.09.01) an issue began at 17:01:23 and stopped at 20:06:35
I couldn’t ping the wiser hub
the led was Red
after a power cycle on the Wiser Hub the communication restart normally
1 Like
Roger that! Thanks for the answer!
This does sound like an internal issue with the firmware, as I suspected, in that case.
Typically, after setting up more monitoring the other day, I am yet to see another disconnect.
Hi everyone, I’ve installed Wiser Hub with Room Thermostat and 6 Radiator Thermostats on 25th of September.
@jamiebennett as software engineer I’m surprised there is no way to say - check for updates and upgrade firmware. The only way is waiting for magic to happen and get updates automatically - this resulted in multitude of issues for me.
- Hub was connected to wi-fi fine during installation, it received firmware update and it seems stopped supporting 2.4ghz N mode - took me 5 hours of trial and error as app was just says “password incorrect” until I’ve enabled 2.4ghz legacy mode in router.
- During above process at some point without any notice Room Thermostat decided to update - it is currently stuck and only showing clock icon and empty bar. I’m trying to reach engineer on schneider zendesk to find out how to hard reset thermostat. So far only been getting answers coming from manuals, which all been tried already.
- 4 Radiator thermostats are on newest version “0000dac0” and 2 are on “000008ed” which I assume is some old version as it doesn’t even come up on internet. Apart from weirdly reporting version in HEX rather than human readable format, I’m at the mercy of zendesk to resolve it again.
Having button to check firmware versions and trigger upgrade would solve all of these problems. Even getting notification on app during firmware upgrade would help prevent bricked devices.
edit ---------------------
Just got a response “In this instance, the product needs to be returned under warranty for an exchange. You would need to contact your installer to facilitate this.” No tradesman would bother to go through RMA to exchange item on client’s behalf when issue is not related to the work they carried out!
2 Likes
I hot the flashing red LED this morning, I cannot say was the first time or not, but I went to check it, when I saw errors in the log.
Pressed the Setup button on the Hub, AP started, then just a bit later pressed the Setup button again. First solid red, then a second later back to solid green and all works again.
I know it is a battery preservation technique, but if the room stat would stay awake permanently by a setting that would be great.
I find it cumbersome to press it and then it shows the values, but usually I change the setting on it when I press it. I am not really a fan of that way of working. 
2 Likes
The Room Thermostat is designed to have 2 years+ of battery life. I suspect, if we kept the display on for, say 12 hours a day, that would reduce the battery life to 6 months or probably less. It’s a trade-off.
Thanks. Personally, I have over 25 years of Open Source experience and my team and I try to be as open as possible so happy to help.
I can’t reveal too much but what I can say is that Schneider Electric (the company behind Drayton and Wiser) is dedicated to optimising energy use, reducing CO₂, and really making a positive difference when it comes to climate change. It’s not just a fancy slogan or hollow mandate, it’s in every product we create (Company Purpose & Mission | Schneider Electric UK). So, with Wiser there are very big plans outside of just heating control (although heating energy use is a major contributor to emissions globally - https://wiser.draytoncontrols.co.uk/save-energy-and-money-better-control). Our platform is used on the continent too so expect to see a lot of overlap between was has already been released or announced elsewhere and what the platform is capable of. For a sneak peak of where Schneider feels Wiser works extremely well, see https://wiser.draytoncontrols.co.uk/insights (also works very well with HA).
2 Likes
The idea behind this was to take the complexity away from the general user. In essence, if we get everything right, the version of software in your Wiser system doesn’t matter one little bit. We ensure that you get the latest security updates, fixes, and features without any work from you to check and apply updates. Now if that process goes wrong for any reason, which it seems to have in your case, then we need to fix that - reaching out to the support team is the right approach.
As for 2.4ghz N we didn’t remove anything in an update so I suspect that was a red herring. The Room Thermostat issue isn’t something I’ve come across before but to reset it there is a handy video here: https://schneider-electric.zendesk.com/hc/en-gb/articles/360005309278-How-to-factory-reset-a-Wiser-room-thermostat.
Totally understand the battery preservation trade off with the room stat display. Being new to the Wiser setup, I hoped there would be a user selectable toggle for ‘always-on’ display for the room stat within the app, with a clear warning about impact on battery life.
If the brightness of the display could be altered even to extend battery life up to say 12 months, id be happy with that for the convenience of glancing at the room stat to see current temp/status.
I had to figure out why our heating ‘suddenly’ came on a couple of days ago, when the set point was down at 12 degrees, as we are keen to only start using the heating when things get a lot colder than present. It wasn’t until the other half confessed to moving the room stat while cleaning, and curious to see what the current temp in the room was, she pressed the middle button, which should have only woke the screen up, but ended up boosting the already more than warm enough house!
Just some (hopefully useful ) customer feedback
3 Likes
Thanks for the feedback, all is very welcome.
1 Like
I agree, the way the room stat works is not ideal. It’s all too easy to touch the screen to wake it up and find you’ve changed something. To be honest once it was set up and HA is working we don’t use the display at all.
The option of non display additional stats would be interesting for other rooms.
That’s what I am talking about. It is really annoying me all the time when I want to see the temperature.
I wouldn’t mind either running the room stat from rechargeable batteries. I guess the voltage should be sufficient, as it is not running a motor.