RTC keeps resetting to 2016-11-03

[Bouke]

I've just installed my brand new RaspBee II on a Raspberry Pi 3. After setting updating the RTC to the current and performing a reboot, the RTC is reset to 2016-11-03 ~17:18:00.

pi@pi3:~ $ timedatectl
      Local time: Mon 2020-11-30 18:39:15 UTC
  Universal time: Mon 2020-11-30 18:39:15 UTC
        RTC time: Thu 2016-11-03 17:22:24
       Time zone: Etc/UTC (UTC, +0000)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

pi@pi3:~ $ sudo hwclock --systohc

pi@pi3:~ $ timedatectl
      Local time: Mon 2020-11-30 18:39:35 UTC
  Universal time: Mon 2020-11-30 18:39:35 UTC
        RTC time: Mon 2020-11-30 18:39:35
       Time zone: Etc/UTC (UTC, +0000)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

 pi@pi3:~ $ sudo hwclock -c
hw-time      system-time         freq-offset-ppm   tick
1606761601   1606761601.000880
1606761613   1606761613.000211               -56     -1
1606761624   1606761623.999039               -80     -1
^C

pi@pi3:~ $ sudo hwclock -D
hwclock from util-linux 2.29.2
Using the /dev interface to the clock.
Last drift adjustment done at 1606761573 seconds after 1969
Last calibration done at 1606761573 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2020/11/30 18:40:33
Hw clock time : 2020/11/30 18:40:33 = 1606761633 seconds since 1969
Time since last adjustment is 60 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2020-11-30 18:40:32.481980+0000

pi@pi3:~ $ sudo reboot

pi@pi3:~ $ sudo hwclock -D
hwclock from util-linux 2.29.2
Using the /dev interface to the clock.
Last drift adjustment done at 1606761573 seconds after 1969
Last calibration done at 1606761573 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2016/11/03 17:17:43
Hw clock time : 2016/11/03 17:17:43 = 1478193463 seconds since 1969
Time since last adjustment is -128568110 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2016-11-03 17:17:42.616381+0000

pi@pi3:~ $ timedatectl
      Local time: Thu 2016-11-03 17:18:11 UTC
  Universal time: Thu 2016-11-03 17:18:11 UTC
        RTC time: Thu 2016-11-03 17:18:12
       Time zone: Etc/UTC (UTC, +0000)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

[ChrisHae]

Could it be that the battery is empty or wrong inserted?

[Bouke]

I just received the item through Amazon. The battery was already inserted. I'll take a look on the orientation.

[Bouke]

I've just checked: the battery is inserted correctly and providing 1.7V.