Bug Report: Meteoblue API data rendering with 12-hour time shift / inverted time series
-
Subject: Bug Report: Meteoblue API data rendering with 12-hour time shift / inverted time series
Hi Support Team,
I am reporting a severe data rendering issue when using the Meteoblue data feed in the app for my location (Alcochete, Portugal / WEST timezone).
The temperatures and hourly forecasts appear to be offset by approximately 12 hours. As a result, peak daytime temperatures (e.g., 35°C–38°C) are being displayed during midnight and early morning hours (01:00–06:00), while cool night temperatures (18°C–22°C) are showing up in the middle of the afternoon (14:00–17:00).
I have cross-checked this directly with Meteoblue’s web model and other raw API parsers (like Open-Meteo and Sonuby), and the underlying forecast data is correct. The issue appears to be a local timezone shift or an array index parsing error when your app reads the UTC timestamps from the Meteoblue API feed.
Could you please look into how the Meteoblue JSON array is being mapped to local time for the WEST/UTC+1 timezone?
Best regards -
Hello,
We looked into this and found that there were some discrepancies in some of our weather data last night.
This likely explains the reversed display of day and night temperatures that you described. We’re currently investigating internally to determine the exact cause so that this doesn’t happen again in the future.In the meantime, however, the data should have returned to normal, so the displayed values should be correct again.
