Wiser rooms do not stay set to off #95
Comments
|
Yep that happens It is not a new problemI think it may be more to do with wiser cloud implementationI set mine to heat and set a 10c trigger level. Check back a hour later and reset any that have not taken it can take up to 5 tries to doI believe it happens at schedule switching times. Wiser hub over rides off to next schedule time ie off more like a anti boost function On 15 Apr 2020 12:04, Mark Parker <notifications@github.com> wrote:
Don't think this is an integration issue but wondering if anyone else has seen this issue.
As the warmer weather has come, I have set some of my rooms to off (as I haven't got around to creating a summer schedule yet). However, (and I thought I was going mad at first) I keep noticing that the next day, some of the rooms are set to manual heat with a temp higher than the away set temp but not all.
It looks (from yesterday) that this happened at 11:26. Has anyone else seen this behaviour with their hub?
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
im not seeing this.. I have a front room which is set to off and its still off.. I did notice something similar to this when the battery was low.. but more like the rad was heating and reporting back the temp.. edit : That said Ive set my to off from the official wiser app not the integration.. I think thats the difference.. I think when we're setting it to off its turning out to be a override "off" vs setting the mode to off.. Will look at the rest api and see if we can make this change.. |
|
I'm seeing both somehow. I have some that just show off and some that show off- override. Was going to have a look at this too to see if we should cancel any override first. Have got 5 showing off and 3 showing off - override. Will see what happens to these later. |
|
|
|
Finding if you set of off, it is now more often than not going to off - override. However, if you go to manual mode, change temp and then set to off, it is always off (if you don't change temp then goes to override too). Wonder if we should do a 2 step process to turn off. 1: to set to manual mode 2: set temp to -200. Having said this, still haven't worked out if it is just these ones that say off - override that are going back to manual mode or a random selection. Will report back over next 24 hours if I can work it out. |
|
I just had one room to heat at 12C and checked ok after 2 hours 4 days later it went to heat 21c 6
Sent from Mail for Windows 10
From: Mark Parker
Sent: 15 April 2020 16:37
To: asantaga/wiserHomeAssistantPlatform
Cc: scooper1; Comment
Subject: Re: [asantaga/wiserHomeAssistantPlatform] Wiser rooms do not stay setto off (#95)
Finding if you set of off, it is now more often than not going to off - override. However, if you go to manual mode, change temp and then set to off, it is always off (if you don't change temp then goes to override too). Wonder if we should do a 2 step process to turn off. 1: to set to manual mode 2: set temp to -200.
Having said this, still haven't worked out if it is just these ones that say off - override that are going back to manual mode or a random selection. Will report back over next 24 hours if I can work it out.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
actually yeah, both of the rads I set to off using HA are now back on , so yeah the turning off isnt working :-) and :-( We'll work it out... we always do! |
|
I've noticed that one of my TRV's for the past couple of days comes on when the heating does and it's schedule is pretty much off i.e. set to 14 degrees but my other TRVs are fine for some reason. Scrap that: My fault. Think it came loose. Re-calibrated and it's fine. Sorry! |
|
I've noticed this issue as well, but generally it only happens once, i.e. the turning off works the 2nd time. |
|
PR for the api posted that I think fixes this |
|
Needs testing.. will add to readme |
|
@asantaga just to make sure you haven't missed the PR for the wiser-heating-api that needs to be merged to fix this issue. Best to do with 2.3 release I think. |
|
Hey mark, I think this PR is in 2.3.1 right? |
|
No. The fix for this is actually an update to the api not the HA integration. The PR is still open for the api. |
|
PR Merged into a new wisehubapi, 1.0.8 .. I need to think how to document how to force an API upgrade as I dont think HA automatically does it on boot |
|
don't you just update the version in manifest.json and issue a new release? |
|
yup, but i hate to create new releases just to force a library update.. although thats what Im going to do later tonight.. you can also upgrade the library by issueing the pip3 --upgrade command.. from the virtual env or within the docker container. but it would be nice if HA detected the later version and just upgraded it, especially as we've said min version not exact version |
|
True but ive seen lots of integrations do a version update just to upgrade the library its using so wouldnt worry. |
|
Will release this with 0.110 compatible release |
|
fixed, and tested |
Don't think this is an integration issue but wondering if anyone else has seen this issue.
As the warmer weather has come, I have set some of my rooms to off (as I haven't got around to creating a summer schedule yet). However, (and I thought I was going mad at first) I keep noticing that the next day, some of the rooms are set to manual heat with a temp higher than the away set temp but not all.
It looks (from yesterday) that this happened at 11:26. Has anyone else seen this behaviour with their hub?
The text was updated successfully, but these errors were encountered: