Displays incorrect next set

[hTiger1 50]

and shows the wrong change at.

 

<1min will be standing.

 

Shows incorrectly, but does it right

 

Please login or register to see this spoiler.

 

[hTiger1 50]

On 11/19/2018 at 10:35 PM, hTiger1 said:

and shows the wrong change at.

 

<1min will be standing.

 

Shows incorrectly, but does it right

 

Please login or register to see this spoiler.

Hi
If I choose manual mode via desktop, it will display correctly, but will display incorrectly when it returns to schema.
I also tried to choose manual mode from the mobile, and when it went back to schedule, the error was corrected. The error was also correct on the disktop.
The error is enough again ........

[petergebruers 1,268]

Indeed. Some users have reported this "wrong next setpoint" in the GUI and I've seen it myself... sometimes.  But I do not look often at that status message. AFAIK the "next set" message is wrong in some cases, on all firmwares up to and including 4.512, which is the latest version when I write this. AFAIK it does not affect the schedule on the FGT, it should match the schedule of the heating panel (although I have seen reports of a real mismatch, problem not well understood at this time). A "synchronize" does not fix that display. The FGT stores its "set point" time and other temperatures in the blackbox logs, so if you suspect a mismatch, you can ask Fibaro support to have a look at the logs and see if the FGT really switches at the right time to the right temperature...

[hTiger1 50]

The error has not occurred in the last 7 days. 

[marcwau 30]

I have this problem now on two FGT's. They follow the heating schedule as they should, so they operate properly, and the indication on the FGT LED ring is correct.

But the temperature and the next setting, displayed in the app and the web client, are wrong. 

If I click the button "Read configuration" in the Advanced Settings of the FGT in the web client, the HC2 retrieves the values from the FGT, and displays the correct temperature and next setting... at least for a while. When the next setpoint of the heating schedule is reached, the FGT reacts properly, but the values in the app and web client do not change, and are wrong again.

If have tried to soft reconfigure, remove the FGT from the heating schedule and put it back in, go through standby-wakeup, nothing helps.