Times and time zones
Choose your display time zone and send correctly dated readings.
On this page
What you need
A correctly set clock on every device that sends data.
How to do it
- Choose your time zone in Settings. History views use this setting.
- In integrations, send a timestamp including its time zone, preferably UTC. For example, 2026-10-02T12:00:00Z means noon UTC.
- For scheduled jobs, choose the actual local time zone, such as Europe/Berlin, alongside the cron schedule.
Good to know
Readings can arrive up to 24 hours late and no more than two minutes ahead of the current time. Daily usage resets at 00:00 UTC, regardless of your display zone.
For cron schedules, a local time skipped by daylight saving is skipped. If a time occurs twice, only its first occurrence is expected.
If something goes wrong
Never add Z to a local time without converting it to UTC. Check the device's clock and time zone if values appear in the wrong period.
Related guides
- Explore measurement history
Explore readings in charts and tables for a period you choose.
- Monitor jobs and cron schedules
Track scheduled commands and find failed, late or missing executions.