search

PiInTheSky / lora-gateway

LoRa gateway to Habitat
96 stars 69 forks source link

Sondehub HTTP 202 error #75

Closed OZimmermann closed 12 months ago

OZimmermann commented 12 months ago

Hi, after starting the gateway, the following error appears after some time "Unexpected HTTP response 202 for URL 'https://api.v2.sondehub.org/amateur/telemetry'"

But error.txt file contains error 400 Example: 21:20:22: 400 response to: [{"software_name": "LoRa Gateway","software_version": "V1.10.0","uploader_callsign": "TrEsLora868","time_received": "2023-08-18T19:20:22Z","payload_callsign": "TrEs2Lora868","datetime":"2023-08-18T21:19:22Z","lat": 51.24919,"lon": 6.18008,"alt": 48,"frequency": 868.6625,"modulation": "LoRa Mode 1","snr": 7,"rssi": -55,"raw": "$$TrEs2Lora868,173,21:19:22,51.24919,6.18008,00048,12,40.6,0.0,0.000,0123456A9P*70F8","sats":12,"temp":40.6,"batt":0.0,"uploader_position": [ 51.366, 6.413, 0],"uploader_antenna": "868_Self_Construction"}]

The gateway has normal internet, because the photos are transferred correctly to my ftp-server and ping api.v2.sondehub.org also works correctly.

I attach errors.txt telemetry.txt packets.txt and gateway.txt. Also attach screenshot showing gateway with error 202 and ping to api.

errors.txt packets.txt telemetry.txt gateway.txt

gateway-1 gateway-2 ping

Want to start a new flight in two weeks on 2023/09/01 :-) Oliver

daveake commented 12 months ago

Thanks for the detailed report.

202 is caused if the uploaded time is too far in the future, and from the logs I can see that the upload time is far ahead of the actual UTC time from the tracker.

All times should be UTC. The gateway gets the UTC time from the operating system.

So, please check your system clock settings on your Pi receiver. You might have the current time and/or timezone set wrongly, so when UTC is calculated from those the result is incorrect.

PiInTheSky commented 12 months ago

Please see https://linuxize.com/post/how-to-set-or-change-timezone-in-linux/

Dave

On Tue, 22 Aug 2023 at 13:22, David Akerman @.***> wrote:

Thanks for the detailed report.

202 is caused if the uploaded time is too far in the future, and from the logs I can see that the upload time is far ahead of the actual UTC time from the tracker.

All times should be UTC. The gateway gets the UTC time from the operating system.

So, please check your system clock settings on your Pi receiver. You might have the current time and/or timezone set wrongly, so when UTC is calculated from those the result is incorrect.

— Reply to this email directly, view it on GitHub https://github.com/PiInTheSky/lora-gateway/issues/75#issuecomment-1688081382, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4ERK6GKKRL45CCR53U73LXWSQBPANCNFSM6AAAAAA3XNFEPM . You are receiving this because you are subscribed to this thread.Message ID: @.***>

PiInTheSky commented 12 months ago

Closed as believed to be an error in Pi system time / timezone. Tests with correct settings show that the upload works as expected.