Hi,
There is a long-term bug in the ViCare app display of temperature sensor data. The graph always shows one day in the past on the x-axis.
For example, today is Monday, however the graph always shows Sunday - please see the attached images.
The boiler date and time is correct and it is clear from the images that the app is aware that it is October 6th, so it looks like the code might be using the wrong day of week reference internally.
Any way to resolve this?
Works for me with Android 12 and ViCare-app version 3.35.1, location DE.
I should have added the app details - 3.35.1 / iOS 26 / UK
Problem has existed for as long as I can remember in prior app and iOS versions.
O.k., that's what I assumed.
Sounds like a software-thing.
In this case you best send a message via ViCare-App / settings / feedback directly to the responsible Viessmann guys, as far as the item is availabe in your version. Maybe they pick it up on this channel quite fast(er).
Thanks Andy - actually I followed the support steps in the app, sent them an email. I received an automatic response telling me that there was no support over email (vicare-service@) and I should raise this in the community forum 🙂
I do not see any other direct feedback option - I think there was one in the past and I raised this same issue about a year ago, but no reply, no fix.
Well, what should I say ... @Flo_Schneider - can you forward this issue, please ?
Only for testing ... did you change your mobile timezone to e.g. "Berlin" once ?
Hi Andy,
My mobile changes TZ quite frequently due to travel - usually automatically, but also sometimes I fix the TZ because (thanks for your reminder) sometimes I noticed weirdness in ViCare.
What is odd is that the system knows it is October 6th - the boiler reports that date and it is included in the heading of the app page. I can imagine the reports being out of alignment by an hour or two, but the chart and the 'live' min/max/current are all dated yesterday.
So to your suggestion - I just fixed my TZ to Berlin and the graph and report are now correct (without restarting the app).
Changing to Lisbon or Dublin, same TZ as UK, reintroduces the issue. New York is the same .. so maybe 12:00 and 00:00 are swapped around somewhere..
Perhaps you can check your data in the morning local time to see if something is different for you?
Sydney (currently 00:50 on 7th) shows Tuesday on the graph (no data) but Monday on the day readings.
I think the solution is for the application time to be based on boiler local time - this would avoid conflicting outputs and strange rendering when travelling.
> So to your suggestion - I just fixed my TZ to Berlin and the graph and report are now correct (without restarting the app).
Lol ... excatly what my crystal ball told me ... 😉
I guess there might be a comparision between the local TZ and time of the mobile device and the TZ / timestamp of the data holding on the Viessmann servers. If there is a mismatch anything buggy is done with the effect you described.
Well, the developers are asked to fix this and find a better solution.