Originally posted by jzwack-honeywell
View Post
On a slightly different note, an issue that has been affecting me ever since installed the Evohome system at the beginning of December, is the infamous failed zone change:
"Dear user,
We would like to notify you that your attempt to remotely implement a change to the following zone failed at 01/26/2016 11:15:58 UTC:
Zone: Main Bedroom"
I get this depressingly often, and usually (always ?) when I'm making multiple changes in a row. For example I might try to perform the following steps via the phone app:
* Disable Heating off Mode
* Enable Day off mode
* Manually override zone 1
* Manually override zone 2.
Of those actions, one at random will fail, for example manually overriding zone 1. The iPhone app will give absolutely no indication that anything went wrong, in fact the user interface will "lie" by showing the expected change. Then a few minutes later (because I am in the house) I will notice that one of the adjustments I made mysteriously isn't taking effect - I will go back into the App, pull down to do a forced refresh and see that one of the settings I changed did not in fact change. I will then check my email and sure enough there will be an "Alert: Failed Zone Change" email waiting for me that was sent almost exactly at the same time that I originally attempted to make the change.
There is no problem with the controllers internet connection at the time of the issue, and the commands actioned just a few seconds either side of the failed command were successful. It seems almost as if sending a second command before the first one has been actioned and reported back by the controller causes the following command to immediately fail, whereas if you wait long enough for the controller to report the change as being successful back to the server it doesn't seem to happen. If so this is rather unfortunate when so many changes that I want to make are often a string of changes - for example disabling heating off mode then enabling day off mode.
I was hoping that this issue might go away with the server improvements but it still seems to be there. Any thoughts on what might cause individual actions to "fail" despite actions on either side of it succeeding ?
It happens often enough to me (typically at least once a day) that when I'm away from the house and doing something important such as turning the heating on I don't trust the iPhone app to report the truth - I will wait for about 10 seconds after the last change, then do a forced refresh in the app (swiping down) then check that all the changes I made actually were actioned, and for good measure I will check my emails as well to make sure no failed zone change messages are awaiting me.
This really shouldn't be necessary, and shakes my confidence of the reliability of remote controlling the system.... I know to be paranoid and wait then do a forced refresh in the app to make sure that changes really occurred, but try explaining to your significant other why when she turned the heating on in the app it didn't really go on and the house is cold when she got home...
Comment