FW1.17.0 - time setting not correct nRF52

[rolandwhoffmannrh-alt]

After updating and clkreboot and clock sync time still wrong on repeater and compagnions with nRF52 boards.

[recrof]

can you show current and expected time and also your timezone?

[rolandwhoffmannrh-alt]

date ist correct time differs about 48 minutes to expected time. my timezone is UTC+1 (Berlin)

[rolandwhoffmannrh-alt]

After trying again date is now 1 day ahead.

[recrof]

what is the exact hardware you use?

[rolandwhoffmannrh-alt]

Seeed Studio Xiao nRF52 WIO. With roomserver on Heltec V3 it works fine.

[rolandwhoffmannrh-alt]

[rolandwhoffmannrh-alt]

expected time 9:00 UTC (sorry UTC+2. It is summer!)

[hmbusch]

I'm seeing the same issue on my Heltec T114 repeater (running Heltec_t114_repeater-v1.17.0-727fc05 firmware). After restart, time is May 15th, 2024 12:52pm, after performing clock sync (either from a Windows PC or the app using a BLE companion), time is now August 12th, 11:00 UTC, whereas my local time is August 11th, 15:17 GMT+2, thus the correct time on the repeater should be August 11th, 13:17 UTC.

When I try another clock sync, the repeater tells me: ERR: clock cannot go backwards.

If it helps: I updated to 1.17.0 because of the issue, it was already present with 1.16.

Addition: Setting the time manually using e.g. time 1786455132 works as expected.

[rolandwhoffmannrh-alt]

@hmbusch Thanks! I also tried it that way and after clkreboot it worked with time 1786455067. The issue seems to be spefic to some boards/roles. On Heltec V3 as roomserver it worked using clock sync.

[cwichura]

clock sync will set the repeater to your companion's time, which is not necessarily your mobile's time. The "clock sync" GUI option in remote management settings uses the time <unixseconds> command to set time on the repeater, ensuring the time is set based on the mobile's clock, which should be pretty accurate as the mobile syncs time with the cellular network.

[hmbusch]

Did a little more digging: the wrong time comes from my BLE companion. It had an uptime of 30+ days and the clock seems to be running a little fast, giving it a "current" time of

Current time : 2026-08-13 09:45:50 (1786607150)

whereas in reality, time is only Wed, 12 Aug 2026 10:03:03 GMT. My board (the Seeed Studio Wio Tracker L1 Pro) has some way of keeping the time despite not being connected to any power source. That, together with Meshcore's restriction preventing the clock being set to an earlier point in time, currently makes it very difficult for me to set a correct time in the companion.

So the problem isn't really the remote sync with the nRF52, it's dealing with a runaway companion clock. (and btw, the only way I could actually see that time my companion device was set to, was by installing the meshcore-cli and querying the time from there)