HERO13: *SYNC=1 GPS sync won’t correct wrong date after long offline — any Labs option to sync date?

[Strom6adam]

Hi,

I’m using HERO13 with GoPro Labs and trying to keep the camera’s date/time correct for unattended use.

From the Labs docs:

*SYNC=1 (H9-11,13 / MAX1-2): GPS time/timecode sync. With a good GPS signal, the camera’s internal clock will be precisely updated to the millisecond. It will not update the hour or date, preserving your current timezone offset. Permanent required.

My issue:

If the camera sits offline / unused for ~2 weeks, it can come up with the wrong date.

When I start recording, GPS is enabled and gets a good lock, but the date stays wrong (and since *SYNC=1 doesn’t update date/hour by design, it seems there’s no recovery).

Is there any Labs command/setting that will sync the date (or full clock) from GPS after lock?
Is there a way to force a one-time clock/date set from GPS at boot or at record start (e.g., “wait for GPS → then set time/date”)?
If this is intentionally blocked, what’s the recommended best practice for unattended deployments to avoid wrong dates after long storage (script pattern, required manual sync step, etc.)?

Thanks!

[dnewman-gpsw]

I just tried it and my date was updated. HERO13

[Strom6adam]

Damn, so it’s probably something else that’s causing the problem. I have a lot of functions enabled via Labs code, so there could be some kind of conflict. But thanks for your reply.

[dnewman-gpsw]

I looked at the code and can see that it might not always set the date. This feature was designed for timecode, I will see if it can be extended to reliably include the date.

[Strom6adam]

Thanks