Summary
Add support for synchronizing the camera clock from an NTP server over WiFi, similar to the existing GPS-based SYNC feature.
This would greatly improve the usability of GoPro Labs for stationary, indoor, remote, and permanently installed cameras where GPS reception is unavailable or unreliable.
Current Situation
Today, GoPro Labs provides excellent support for:
WiFi credential storage via JOIN
Network connection via !W
GPS-based clock synchronization via *SYNC=1
Timezone configuration via oTZ
Boot scripts via *BOOT
However, there is currently no method to synchronize the camera clock from a network time source.
For many installations, GPS is either:
unavailable indoors,
unreliable in urban environments,
blocked by enclosures,
slower than a simple network time lookup.
Proposed Solution
Option 1: New NTP Extension
Introduce a permanent metadata field:
*NTP="pool.ntp.org"
Examples:
*NTP="pool.ntp.org"
*NTP="time.google.com"
*NTP="time.cloudflare.com"
Then add a synchronization action:
!T
Example:
!W!T
Meaning:
Connect to configured WiFi network.
Query NTP server.
Update camera clock.
Continue script execution.
Option 2: Extend Existing SYNC Functionality
Allow the current SYNC implementation to support both GPS and NTP.
Example behavior:
*SYNC=1
Could:
Use GPS if available.
Fall back to NTP if WiFi is configured and connected.
Preserve timezone handling exactly as current GPS sync does.
This would maintain backward compatibility while improving reliability.
Option 3: Boot-Time Automatic Synchronization
Allow automatic synchronization whenever the camera boots and WiFi is available.
Example:
*BOOT="!Lbt"
!SAVEbt=!W!T
or
*NTPAUTO=1
Use Cases
Remote Monitoring
Cameras powered by USB in remote locations need accurate timestamps without GPS reception.
Indoor Timelapse
Construction, laboratory, manufacturing, and security timelapses often operate entirely indoors.
Multi-Camera Synchronization
NTP would provide a common time source across multiple cameras on the same network.
Permanent Installations
Many GoPro Labs users run cameras continuously on external power with WiFi available but no GPS access.
Benefits
Faster synchronization than GPS acquisition.
Works indoors.
No GPS signal dependency.
Lower power consumption compared to waiting for GPS lock.
Better support for fixed-location deployments.
Complements existing Labs automation workflows.
Existing Infrastructure
Most of the required building blocks already appear to exist:
WiFi credential storage (JOIN)
Network connection (!W)
Time synchronization logic (SYNC)
Existing internet-based features such as livestreaming and uploads
This suggests NTP support may be achievable with relatively modest firmware changes.
Suggested Example
*BOOT="!Lbt"
!SAVEbt=oTZ60!W!T
At boot:
Connect to WiFi.
Synchronize time from NTP.
Apply timezone.
Continue normal operation.
Thank you for considering this feature. It would significantly improve the usability of GoPro Labs for remote and stationary deployments.
Summary
Add support for synchronizing the camera clock from an NTP server over WiFi, similar to the existing GPS-based SYNC feature.
This would greatly improve the usability of GoPro Labs for stationary, indoor, remote, and permanently installed cameras where GPS reception is unavailable or unreliable.
Current Situation
Today, GoPro Labs provides excellent support for:
WiFi credential storage via JOIN
Network connection via !W
GPS-based clock synchronization via *SYNC=1
Timezone configuration via oTZ
Boot scripts via *BOOT
However, there is currently no method to synchronize the camera clock from a network time source.
For many installations, GPS is either:
unavailable indoors,
unreliable in urban environments,
blocked by enclosures,
slower than a simple network time lookup.
Proposed Solution
Option 1: New NTP Extension
Introduce a permanent metadata field:
*NTP="pool.ntp.org"
Examples:
*NTP="pool.ntp.org"
*NTP="time.google.com"
*NTP="time.cloudflare.com"
Then add a synchronization action:
!T
Example:
!W!T
Meaning:
Connect to configured WiFi network.
Query NTP server.
Update camera clock.
Continue script execution.
Option 2: Extend Existing SYNC Functionality
Allow the current SYNC implementation to support both GPS and NTP.
Example behavior:
*SYNC=1
Could:
Use GPS if available.
Fall back to NTP if WiFi is configured and connected.
Preserve timezone handling exactly as current GPS sync does.
This would maintain backward compatibility while improving reliability.
Option 3: Boot-Time Automatic Synchronization
Allow automatic synchronization whenever the camera boots and WiFi is available.
Example:
*BOOT="!Lbt"
!SAVEbt=!W!T
or
*NTPAUTO=1
Use Cases
Remote Monitoring
Cameras powered by USB in remote locations need accurate timestamps without GPS reception.
Indoor Timelapse
Construction, laboratory, manufacturing, and security timelapses often operate entirely indoors.
Multi-Camera Synchronization
NTP would provide a common time source across multiple cameras on the same network.
Permanent Installations
Many GoPro Labs users run cameras continuously on external power with WiFi available but no GPS access.
Benefits
Faster synchronization than GPS acquisition.
Works indoors.
No GPS signal dependency.
Lower power consumption compared to waiting for GPS lock.
Better support for fixed-location deployments.
Complements existing Labs automation workflows.
Existing Infrastructure
Most of the required building blocks already appear to exist:
WiFi credential storage (JOIN)
Network connection (!W)
Time synchronization logic (SYNC)
Existing internet-based features such as livestreaming and uploads
This suggests NTP support may be achievable with relatively modest firmware changes.
Suggested Example
*BOOT="!Lbt"
!SAVEbt=oTZ60!W!T
At boot:
Connect to WiFi.
Synchronize time from NTP.
Apply timezone.
Continue normal operation.
Thank you for considering this feature. It would significantly improve the usability of GoPro Labs for remote and stationary deployments.