The server’s time is not a comfort detail. It governs the correct behaviour of your installation:
A shifted clock produces confusing symptoms: rules triggering at the wrong moment, or devices refusing to connect for no apparent reason.
These settings are not available from the touchscreen: connect over SSH (see SSH access).
timedatectl
This command shows the local time, the configured time zone, and whether automatic synchronisation is active.
Check three things: that the displayed time is correct, that the zone matches your country, and that automatic synchronisation is enabled.
To see the list of available zones:
timedatectl list-timezones
The list is long; to keep only European ones:
timedatectl list-timezones | grep Europe
Then apply yours:
timedatectl set-timezone Europe/Paris
Your server adjusts its clock by querying time servers on the Internet. This is what keeps it on time over the long run, including across daylight saving changes.
To check or enable it:
timedatectl set-ntp true
If the time is systematically wrong after every power cut, the motherboard battery is often dead. It is a cheap coin cell, easy to replace. Automatic synchronisation fixes the problem as soon as the network is available, but a few minutes may pass before that.
Time alone is not enough to know when the sun rises: you also need to know where you are. Without that information, rules such as “close the shutters at sunset” cannot work correctly.
The default coordinates are those of Paris. If you do not live nearby, your shutters will close at the Parisian sunset, with an offset that can reach a good half hour at the far ends of the country — and much more abroad.
This is a setting to make once and for all, and one that is easily forgotten since nothing flags the mistake.
So set the coordinates of your home:
calaos_config set latitude 47.636507
calaos_config set longitude 7.494156
Replace these values with your own. You can get them easily by looking your address up on any online map: both numbers are displayed, latitude first.
A precision of a few decimal places is more than enough — there is no need to be accurate to the metre. Do watch the decimal point though: write 47.636507, not 47,636507.
To check what has been saved:
calaos_config get latitude
calaos_config get longitude
Using sunrise and sunset in your rules is described in Time management.
Restart the Calaos server so the new setting is taken into account everywhere, or simply restart the machine:
reboot
Time handling in your rules — time ranges, calendars, sunrise and sunset — is described in Time management, in the Calaos Installer chapter.
For wall screens and their requirement of a correct clock, see Remote UI.