For some reason I don’t understand, Chirpstack appears to be pushing a GPS epoch time that’s about 134 seconds in the future. My system is NTP synced, and the time in the LORAWAN FRAMES matches actual epoch seconds exactly. I know about the 18 second leap second adjustment, but this is a bit more than that.
Here’s a screen capture that shows the correct “Oct 24 7:44:00 PM” (EDT), but the timeSinceGPSEpoch is 1350690392, which is 2022-10-24T23:46:14, or 2 minutes and 14 seconds ahead. The device profile is configured for Class C, although I don’t think that would make any difference.
What might cause this?
I use GWOSC to convert between GPS epoch seconds and current time.