Would anyone still experiencing this problem try the following and see if it helps.
Something similar was done on another website and it claimed it worked.
I did the following and it seems to have resolved at least part of the problem if not all of it.
On my iPhone Honeywell App I entered settings / location information / Locations details
Under "Time Zone" I was correctly indicated as UTC(Dublin, Edinburgh, ....
I changed it to UTC (Coordinated Universal Time)
I accepted the change and it confirmed "save".
I waited a few minutes and then changed it back to UTC (Dublin, Edinburgh, ...
Its now been 45 minutes and working okay on the controller. That might not be long enough.
BUT at least that weird problem (when I set an override, the end time reported by the controller and iPhone app were an hour out from each other) is gone, both the controller and app now reporting the same time.
BST
Re: BST
I have just tried setting the location to "UTC", then back to the normal setting. I will see what happens.
I raised this issue with Honeywell Technical Support on Sunday and they have acknowledged that there is a problem with the time synchronising, which they are working on.
Regards,
Alan.
I raised this issue with Honeywell Technical Support on Sunday and they have acknowledged that there is a problem with the time synchronising, which they are working on.
Regards,
Alan.
Re: BST
Setting the time zone to "UTC" then back to the normal setting for the UK does not work. My unit has returned to UTC. For now, choosing "West Central Africa" as the time zone seems to solve the problem with both the local display and the app.
Regards,
Alan.
Regards,
Alan.
Re: BST
Okay I am now two hours and all is well following my using iPhone app to change time zones and then switching back again. To add that I had the controller in "manual" time setting mode when I made those changes. Maybe I am just lucky and the problem was being resolved anyway, one user at a time.
Re: BST
Honeywell have posted as follows on that other website the following explanation and action:
"Some users that registered after Nov 2016 had an incorrectly set Summer time flag when the account was created for the first time. This is why many users were ok, and some newer users were affected.
The affected users are having their records updated correctly. There is no action required on the user side.
We apologize for any inconvenience caused. "
"Some users that registered after Nov 2016 had an incorrectly set Summer time flag when the account was created for the first time. This is why many users were ok, and some newer users were affected.
The affected users are having their records updated correctly. There is no action required on the user side.
We apologize for any inconvenience caused. "
-
- Posts: 1
- Joined: Wed Mar 29, 2017 9:07 pm
Re: BST - another workaround
Hi All,
I have the same problem so i opened a support ticket with Honeywell and got a confirmation that they know the problem.
My workaround is to disconnect the RFG100 so it doesn't poll the Honeywell servers. I can live without that for a while rather than have my DHW water timings out (with a wife and two small kids!)
I'm guessing if you have the wifi version then just disabling the wifi on it or renaming the SSID (to disconnect wifi) will do the same.
I only use the RFG100 with Fibaro so I've lost fine tuning for now.
UPDATE 03/04/17 - Honeywell contacted me to say its all been fixed, its now been working ok for 12 hours so it looks like it is!
I have the same problem so i opened a support ticket with Honeywell and got a confirmation that they know the problem.
My workaround is to disconnect the RFG100 so it doesn't poll the Honeywell servers. I can live without that for a while rather than have my DHW water timings out (with a wife and two small kids!)
I'm guessing if you have the wifi version then just disabling the wifi on it or renaming the SSID (to disconnect wifi) will do the same.
I only use the RFG100 with Fibaro so I've lost fine tuning for now.
UPDATE 03/04/17 - Honeywell contacted me to say its all been fixed, its now been working ok for 12 hours so it looks like it is!