Problems uploading to Sondehub

[Rundfunkster]

Using Auto_rx for radiosondes, version 1.5.9 (and problem first occurred with version 1.5.6 after working perfectly for 5 months), I am receiving this error seen in the VNC output from the PI:

2022-02-17 19:05:03,855 ERROR:Sondehub Uploader - Upload failed after 0 retries

The error message detail is as follows:

{"error_message": "DFM radiosonde above 1000 and not enough data to perform z-check. Not adding DB to protect against double frequency usage.", "payload": {"software_name": "radiosonde_auto_rx", "software_version": "1.5.9", "uploader_callsign": "W4KZK-14", "uploader_position": [37.1713, -80.08171, 1000.0], "uploader_antenna": "Omni 6 dB", "time_received": "2022-02-18T00:05:00.906274Z", "datetime": "2022-02-18T00:04:59.000000Z", "manufacturer": "Graw", "type": "DFM", "subtype": "DFM17", "serial": "20051724", "frame": 1329177899, "lat": 37.43665, "lon": -78.6566, "alt": 20533.8, "temp": -58.9, "vel_v": 4.97, "vel_h": 28.41, "heading": 96.0, "sats": 17, "batt": 4.37, "frequency": 404.01, "snr": 25.5, "dfm_failure": true}}, {"error_message": "DFM radiosonde above 1000 and not enough data to perform z-check. Not adding DB to protect against double frequency usage.", "payload": {"software_name": "radiosonde_auto_rx", "software_version": "1.5.9", "uploader_callsign": "W4KZK-14", "uploader_position": [37.1713, -80.08171, 1000.0], "uploader_antenna": "Omni 6 dB", "time_received": "2022-02-18T00:05:01.714235Z", "datetime": "2022-02-18T00:05:00.000000Z", "manufacturer": "Graw", "type": "DFM", "subtype": "DFM17", "serial": "20051724", "frame": 1329177900, "lat": 37.43662, "lon": -78.65629, "alt": 20538.6, "temp": -58.8, "vel_v": 5.06, "vel_h": 26.53, "heading": 99.16, "sats": 17, "batt": 4.37, "frequency": 404.01, "snr": 25.5, "dfm_failure": true}}]}.

This seems unique to my configuration though it is a virtual mirror image of the software being used by other stations operating in my immediate area. SQ6KXY site continues to post data from my uploads. Also APRS.

Thoughts anyone?

[LukePrior]

This is the expected behavior see: https://github.com/projecthorus/sondehub-infra/wiki/DFM-radiosonde-above-1000-and-not-enough-data-to-perform-z-check

[Rundfunkster]

Thank you - I had read this statement but it never seemed to occur in the past 5 months (hundreds of sondes) until about a month ago when it began to occur consistently. Also, it never resolves for my station during the entire 2 hr monitoring period - Stated another way, my station is never seen to contribute to Sondehub as it used to regardless of altitude of sonde, consistency of ID frames etc.

It always took about 5-10 frames for an ID to be reliably assigned but for whatever reason, I am seeing no contributions in the left hand window by my station to sondehub despite 30 dB signal strength and excellent decodes. This is quite different behavior than I have carefully observed in the past.

On Thu, Feb 17, 2022 at 7:14 PM Luke Prior @.***> wrote:

This is the expected behavior see: https://github.com/projecthorus/sondehub-infra/wiki/DFM-radiosonde-above-1000-and-not-enough-data-to-perform-z-check

— Reply to this email directly, view it on GitHub https://github.com/projecthorus/sondehub-tracker/issues/241#issuecomment-1043666180, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX2MMG3WROXGN6BGEGDI4M3U3WFPHANCNFSM5OWILPXA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[LukePrior]

I will defer to @darksidelemm & @TheSkorm

[mwheeler-ep]

can you share your autorx config ? We only implemented this check in the last month. I can see from the error message that only 2 payloads are uploaded which is not enough for us to be certain that there isn't any decoding issues relating to DFMs

[Rundfunkster]

Happily! Several other folks had seen this sporadically in our group but I think I am the only member who seems to consistently get the error. I have a single dongle, a PI-3 and the problem started suddenly and mysteriously for me with (so far as I know) no changes to my config or physical layout of my receiver. The file is fairly generic I think.

Follows is my CONFIG file: #

Radiosonde Auto RX v2 Station Configuration File

#

Copy this file to station.cfg and modify as required.

#

If you only change a few settings, the important ones to change are:

- [habitat] -> uploader_callsign - Your station callsign!

- [location] -> station_lat, station_lon, station_alt - Your station

location!

- [search_params] -> min_freq, max_freq - Set these suitable for your

location! #

###################

RTLSDR SETTINGS

################### [sdr]

Number of RTLSDRs to use.

If more than one RTLSDR is in use, multiple [sdr_X] sections must be

populated below sdr_quantity = 1

Individual SDR Settings.

[sdr_1]

Device Index / Serial

If using a single RTLSDR, set this value to 0

If using multiple SDRs, you MUST allocate each SDR a unique serial number

using rtl_eeprom

i.e. to set the serial number of a (single) connected RTLSDR: rtl_eeprom

-s 00000002

Then set the device_idx below to 00000002, and repeat for the other

[sdr_n] sections below #

For the special case when auto_rx is used entirely with a JSON-via-UDP

input, set the below to TCP001

This will bypass all RTLSDR checks and allow auto_rx to continue

running. device_idx = 0

Frequency Correction (ppm offset)

Refer here for a method of determining this correction using LTE signals:

https://gist.github.com/darksidelemm/b517e6a9b821c50c170f1b9b7d65b824 ppm = 0

SDR Gain Setting

Gain settings can generally range between 0dB and 40dB depending on the

tuner in use.

Run rtl_test to confirm what gain settings are available, or use a

value of -1 to use hardware automatic gain control (AGC).

Note that this is an overall gain value, not an individual mixer/tuner

gain. This is a limitation of the rtl_power/rtl_fm utils. gain = -1

Bias Tee - Enable the bias tee in the RTLSDR v3 Dongles.

bias = False

[sdr_2]

As above, for the next SDR, if used. Note the warning about serial

numbers. device_idx = 00000002 ppm = 0 gain = -1 bias = False

Add more SDR definitions here if needed. ([sdr_3], [sdr_4])

##############################

RADIOSONDE SEARCH SETTINGS

############################## [search_params]

Minimum and maximum search frequencies, in MHz.

Australia: Use 400.05 - 403 MHz

New Zealand: Use 400.05 - 404 MHz

Europe: Use 400.05 - 406 MHz

US:

Some areas have transitioned to the 400.05 - 406 MHz band, so try

400.05 - 406

Some areas are still using ~1680 MHz sondes, which use channels of

1676, 1678, 1680 and 1682 MHz (Thanks Tory!)

Example only_scan for these sondes: [1676.0, 1678.0, 1680.0, 1682.0]

In these areas I suggest using the only_scan feature below instead of

using the peak-detect search.

You may also need to apply a small offset to the frequency for decoding

reliability (i.e. 1676.025 MHz) as

the sondes are often off-frequency. For now, check in something like GQRX

to get an idea of what offset is required.

min_freq = 403.20 max_freq = 405.10

After rx_timeout seconds of no valid data from a decoder, stop the

decoder and go back to scanning (if a SDR is available) rx_timeout = 180

Frequency Lists - These must be provided as JSON-compatible lists of

floats (in MHz), i.e. [400.50, 401.520, 403.200]

only_scan - Add values to this list to only scan on these frequencies.

This is for when you only want to monitor a small set of launch

frequencies. only_scan = []

never_scan - Any values added to this list will be removed from the list

of detected peaks.

This is used to remove known spurs or other interferers from the scan

list, potentially speeding up detection of a sonde. never_scan = [403.2,403.87,403.95, 404.02]

always_scan - Any values in this list will be added to the start every

scan run.

This is useful when you know the regular frequency of a local sonde, but

still want to allow detections on other frequencies. always_scan = [404.01,405.03,403.4]

####################

STATION LOCATION

####################

Used by the Sondehub Uploader, APRS Uploader, and by Rotator Control

Lat/Lon in decimal degrees, altitude in metres.

Note: You do not need to specify your home station accurately if you

don't want to!

Feel free to use a position somewhere near your general area, that

doesn't identify your home location. [location] station_lat = 37.1713 station_lon = -80.08171 station_alt = 1000

Station Position from GPSD

If your station is likely to move, then you may wish to have your station

position updated from GPSD.

NOTE: This feature is intended to make life slightly easier when using an

auto_rx station in a portable

capacity, in particular when using a rotator. For the web interface to

start up correctly, a lat/lon still

needs to be entered above.

If you are operating a stationary auto_rx station, please just set a

fixed position above rather than using GPSD. #

If you are doing mobile balloon chasing, please use chasemapper (

https://github.com/projecthorus/chasemapper )

which is far beter suited than auto_rx by itself...

gpsd_enabled = False gpsd_host = localhost gpsd_port = 2947

###################################################

SONDEHUB / HABITAT (deprecated) UPLOAD SETTINGS

################################################### #

Settings relating to uploads to the SondeHub v2 Database and tracker,

available at https://tracker.sondehub.org/

#

Note that uploads to the Habitat (amateur HAB) database are now disabled,

and any references to Habitat in this config are for legacy reasons only.

[habitat]

Uploader callsign. PLEASE CHANGE THIS TO SOMETHING UNIQUE.

uploader_callsign = W4KZK-14

Upload listener position to Sondehub? (So you show up on the map)

Note that if GPSD is used, this is overriden and enabled.

upload_listener_position = True

Uploader Antenna Description.

If upload_listener_position is enabled, this information will show up in

your station description on the habhub map. uploader_antenna = Omni 6 dB

[sondehub]

Enable uploading to Sondehub v2 - please leave this enabled!

sondehub_enabled = True

How often to push data to the SondeHub Database. (seconds)

All received positions are cached and uploaded every X seconds.

Uploads are gzip compressed, so don't require much data transfer.

sondehub_upload_rate = 10

An optional contact e-mail address.

This e-mail address will only be available to the Sondehub admins, and

will only

be used to contact you if there is an obvious issue with your station.

We recommend that you join the radiosonde_auto_rx mailing list to receive

updates:

https://groups.google.com/forum/#!forum/radiosonde_auto_rx

sondehub_contact_email = @.***

########################

APRS UPLOAD SETTINGS

########################

Settings for uploading to APRS-IS

[aprs]

Enable APRS upload (you will also need to change some options below!)

aprs_enabled = True

APRS-IS Login Information

The aprs_user field can have an SSID on the end if desired, i.e. N0CALL-4

If you are a licensed amateur radio operator, you may want to change the

aprs_port number below

to 14580, so that your uploaded telemetry makes its way out to the wider

APRS network. aprs_user = W4KZK-14

APRS-IS Passcode. You can generate one for your callsign here:

https://apps.magicbug.co.uk/passcode/ aprs_pass = 9356

APRS Upload Rate - Upload a packet every X seconds.

This has a lower limit of 30 seconds, to avoid flooding the APRS-IS

network.

Please be respectful of other uses of the APRS-IS network, and do not

attempt

to upload faster than this.

upload_rate = 31

APRS-IS server to upload to.

Default to radiosondy.info for now, to allow stats to show up on

http://radiosondy.info

Packets are forwarded onto the rest of the APRS-IS network from

radiosondy.info.

If you wish to inject packets directly into the APRS-IS network, use

rotate.aprs2.net aprs_server = radiosondy.info

APRS-IS Port Number to upload to.

When using radiosondy.info:

Port 14590 - Packets stay within radiosondy.info. Non-licensed

operators can use this.

Port 14580 - Packets are forwarded out to the wider APRS-IS network.

Only licensed amateur radio operators should use this!!

For all other APRS-IS servers (licensed amateur radio operators only!),

use port 14580. aprs_port = 14580

APRS Station Location Beaconing

If enabled, you will show up on APRS using the aprs_user callsign set

above.

This also requires your station location to be set in the above

[location] section. station_beacon_enabled = True

Station beaconing rate, in minutes.

station_beacon_rate = 30

Station beacon comment.

will be replaced with the current auto_rx version number

station_beacon_comment = radiosonde_auto_rx SondeGate v

Station Beacon Icon

The APRS icon to use, as defined in http://www.aprs.org/symbols.html

Note that the two characters that define the icon need to be

concatenated. Examples:

Antenna Tower = /r

House with Yagi = /y

Satellite Dish = /` (This is required if you want to show up on

radiosondy.info's station list.) station_beacon_icon = /`

Custom Object name / Callsign to be used when uploading telemetry to

APRS-IS (Max 9 chars)

WARNING: THIS SHOULD BE LEFT AT THE DEFAULT OF UNLESS YOU HAVE A

VERY GOOD REASON

TO CHANGE IT!

#

Using means the uploads from multiple stations remain consistent,

and we don't end up with

lots of duplicate sondes on APRS-IS. If you enable the station location

beaconing (below), maps

like aprs.fi and radiosondy.info will show your station as the receiver.

#

If used, this field should be either a callsign with a -11 or -12 suffix

(i.e. N0CALL-12),

or , which will be replaced with the radiosondes serial number.

#

WARNING - If running multiple RTLSDRs, setting this to a fixed callsign

will result in odd behaviour on the online tracker.

DO NOT SET THIS TO ANYTHING OTHER THAN IF YOU ARE USING MORE THAN

ONE SDR! aprs_object_id =

Confirmation of the above setting.

Set to True to confirm use of the custom object ID set above.

Please read the notes above before setting this to True.

aprs_use_custom_object_id = False

The APRS-IS beacon comment. The following fields can be included:

- Sonde Frequency, e.g. 401.520 MHz

- Sonde Type (e.g. RS41-SG, DFM09, etc....)

- Sonde Serial Number (i.e. M1234567)

- Sonde Vertical Velocity (i.e. -5.1m/s)

- Sonde reported temperature. If no temp data available, this will

report -273 degC.

- Sonde reported humidity.

- Sonde reported pressure

- Battery Voltage (e.g. 3.1V)

The default comment (below) is compatible with radiosondy.info's parsers,

and should only be modified

if absolutely necessary.

aprs_custom_comment = Clb= t= h= p= Type= ser= Radiosonde

###########################

CHASEMAPPER DATA OUTPUT

###########################

Settings for pushing data into Chasemapper and/or OziPlotter

Oziplotter receives data via a basic CSV format, via UDP.

Chasemapper can receive data in either the basic CSV format, or in the

more descriptive 'payload summary' JSON format. [oziplotter]

How often to output data (seconds)

ozi_update_rate = 5

Enable the 'OziMux' basic CSV output

Note - this cannot be enabled in a multi-SDR configuration.

ozi_enabled = False

OziMux UDP Broadcast output port.

Set to 8942 to send packets directly into OziPlotter, or set to 55681 to

send via OziMux ozi_port = 8942

Payload summary UDP output, which is the preferred input if using

ChaseMapper.

Using this output allows multiple sondes to be plotted in Chasemapper.

As of 2019-05, this is enabled by default.

payload_summary_enabled = True payload_summary_port = 55673

#######################

EMAIL NOTIFICATIONS

#######################

Sends an email notification to the specified address when a new Sonde is

detected [email] email_enabled = False

Send an e-mail for each new radiosonde observed.

launch_notifications = True

Send e-mails when a radiosonde is detected descending near your station

location landing_notifications = True

Range threshold for Landing notifications (km from your station location)

landing_range_threshold = 50

Altitude threshold for Landing Notifications (metres)

Notifications will only occur for sondes which have been observed

descending (>2m/s descent rate) below this altitude

for at least 10 observations

landing_altitude_threshold = 1000

Enable sending critical error notifications (one that cause auto_rx to

completely crash out) via email.

WARNING: If an error is persistent and you are running as a systemd

service, this could result

in many e-mails being sent!

error_notifications = False

Server details. Note that usually Port 465 is used for SSL auth, and 587

is used for TLS. smtp_server = localhost smtp_port = 25

Authentication type, Valid options are: None, TLS, and SSL

smtp_authentication = None

If using authentication, the following fields need to be populated:

smtp_login = None smtp_password = None

'Source' e-mail

from = @.***

Destination emails. You can send to multiple addresses by separating each

address with a semicolon,

i.e. @.**@.

to = @.***

Custom subject field. The following fields can be included:

- Sonde Frequency, i.e. 401.520 MHz

- Sonde Type (RS94/RS41)

- Sonde Serial Number (i.e. M1234567)

subject = Sonde launch detected on :

###################

ROTATOR CONTROL

###################

auto_rx can communicate with an instance of rotctld, on either the

local machine or elsewhere on the network.

This is, admittedly, a bit of a waste of an az/el rotator setup when a

vertical antenna usually works fine,

but it's still fun :-)

[rotator]

WARNING - This should not be enabled in a multi-SDR configuration.

Your station location (defined in the [location] section above) must also

be defined. rotator_enabled = False

How often to update the rotator position. (Seconds)

update_rate = 30

Only move the rotator if the new position is more than X degrees in

azimuth or elevation from the current position. rotation_threshold = 5.0

Hostname / Port of the rotctld instance.

rotator_hostname = 127.0.0.1 rotator_port = 4533

Rotator Homing.

If enabled, turn to a 'home' location when scanning for sondes.

This could be used to point an antenna at a known radiosonde launch

location. rotator_homing_enabled = False

Wait until x minutes after no sonde data received before moving to the

home location. rotator_homing_delay = 10

Rotator home azimuth/elevation, in degrees true.

rotator_home_azimuth = 0.0 rotator_home_elevation = 0.0

###########

LOGGING

########### [logging]

If enabled, a log file will be written to ./log/ for each detected

radiosonde. per_sonde_log = True

###########################

WEB INTERFACE SETTINNGS

########################### [web]

Server Host - Can be set to :: to listen on IPv6

web_host = 0.0.0.0

Server Port - Ports below 1024 can only be used if you run auto_rx as

root (not recommended) web_port = 5000

Archive Age - How long to keep a sonde telemetry in memory for the web

client to access, in minutes

Note: The higher this number, the more data the client will need to load

in on startup archive_age = 120

Enable control over the scanner, and starting/stopping decoders from the

web interface.

A password must also be set (below).

USERS ENABLE THIS AT THEIR OWN RISK!!

web_control = False

Password for controls on the web interface. The main interface will still

be publicly available.

Note that as the web interface is HTTP-only, this password will be sent

over the internet in the clear,

so don't re-use passwords!

web_password = none

KML refresh rate

kml_refresh_rate = 9

##################

DEBUG SETTINGS

################## [debugging]

WARNING - Enabling these settings can result in lots of SD-card IO,

potentially

reducing the life of the card. These should only be enabled to collect

data for

debugging purposes.

Save the audio that a detection pass is run over to: detect_.wav

This file is over-written with every new detection.

save_detection_audio = False

Save the audio from the output from a sonde decode chain to

decode_.wav

This file is over-written with each new sonde decoded for a particular

SDR.

This only works for the 'legacy' FM-based demodulators.

save_decode_audio = False

Save the decimated IQ data from an experimental sonde decode chain to

decodeIQ.bin

This will be in complex signed 16-bit int format, and may be either 48

kHz or 96 kHz.

Note: This will use a LOT of disk space.

save_decode_iq = False

Save raw hexadecimal radiosonde frame data. This is useful to provide

data for telemetry analysis.

Raw hex data is saved to the logging directory with a filename of format

YYYYMMDD-HHMMSS.raw

Saving raw data is currently only supported for: RS41, LMS6-1680,

LMS6-400, M10, M20, IMET-4 save_raw_hex = False

#####################

ADVANCED SETTINGS

#####################

These control low-level settings within various modules.

Playing with them may result in odd behaviour.

[advanced]

Scanner - Receive bin width (Hz)

search_step = 800

Scanner - Minimum SNR for a peak to be detected. The lower the number,

the more peaks detected. snr_threshold = 10

Scanner - Maximum number of peaks to search through during a scan pass.

Increase this if you have lots of spurious signals, though this will

increase scan times. max_peaks = 10

Scanner - Minimum distance between detected peaks (Hz)

min_distance = 1000

Scanner - Scan Dwell Time - How long to observe the specified spectrum

for. scan_dwell_time = 20

Scanner - Detection Dwell time - How long to wait for a sonde detection

on each peak. detect_dwell_time = 5

Scanner - Delay between scans. We should delay a short amount between

scans to allow for decoders and other actions to jump in. scan_delay = 10

Quantize search results to x Hz steps. Useful as most sondes are on 10

kHz frequency steps. quantization = 10000

Decoder Spacing Limit - Only start a new decoder if it is separated from

an existing decoder by at least

this value (Hz). This helps avoid issues where a drifting radiosonde is

detected on two adjacent channels.

If you regularly encounter radiosondes on adjacent (10kHz) channels, then

set this value to 5000. decoder_spacing_limit = 15000

Temporary Block Time (minutes) - How long to block encrypted or otherwise

non-decodable sondes for. temporary_block_time = 120

Upload when (seconds_since_utc_epoch%upload_rate) == 0. Otherwise just

delay upload_rate seconds between uploads.

Setting this to True with multple uploaders should give a higher chance

of all uploaders uploading the same frame,

however the upload_rate should not be set too low, else there may be a

chance of missing upload slots. synchronous_upload = True

Only accept a payload ID as valid until it has been seen N times.

This helps avoid corrupted callsigns getting onto the map.

payload_id_valid = 3

Paths to the rtl_fm and rtl_power utilities. If these are on your system

path, then you don't need to change these. sdr_fm_path = rtl_fm sdr_power_path = rtl_power

################################

DEMODULATOR / DECODER TWEAKS

################################

#

Alternate Decode Chains

#

NOTE: This section will be deprecated soon, with the fsk_demod chains

used permanently. #

These (not so) experimental demod chains use David Rowe's fsk_demod modem.

They have much better drift handling performance, and so may be better

suited for

1680 MHz sondes, but use considerably more CPU. Recommend use of a Pi 3

or better.

The experimental decoders can be enabled/disabled independently for each

radiosonde type.

It is recommended that these are always left enabled.

rs41_experimental = True rs92_experimental = True dfm_experimental = True m10_experimental = True lms6-400_experimental = True imet54_experimental = True

LMS6-1680 Decoder options:

False = Less CPU, possibly worse weak-signal performance.

True = Higher CPU (Pushing a RPi 3 to its limits), possibly better

weak-signal performance. lms6-1680_experimental = False

MRZ sondes have not yet been tested with the fsk_demod flowgraph in the

wild.

If someone can confirm that this works, I'll set it to True by default!

mrz_experimental = False

Note: As iMet-4 sondes use AFSK, using fsk_demod does not give any

advantage, so there is no experimental decoder for them.

Optimize 1680 MHz Scanning for RS92-NGP Sondes

This flag sets the use of IQ detection when scanning for 1680 MHz sondes,

which allows RS92-NGP sondes

to be detected reliably.

Set this to True if you are sure that only RS92-NGPs are flying in your

area. ngp_tweak = False

######################

POSITION FILTERING

######################

These are used to discard positions which are clearly bad, such as

where the payload has jumped halfway around the world,

or has suddenly ended up in orbit.

#

Users can also decide to temporary block sondes which are outside of a

radius range. # [filtering]

Discard positions with an altitude greater than 50000 metres.

max_altitude = 50000

Discard positions from sondes which are outside the following min/max

radius limits.

This requires the ground-station location to be set.

max_radius_km = 1200 min_radius_km = 0

Temporarily block the frequency of sondes which report a position outside

of the above limits.

WARNING: This may cause sondes which sometimes report glitchy positions

(RS92, DFM) to be blocked.

(True or False)

radius_temporary_block = False

Reported Time Threshold

Discard positions if the sonde's reported time is more than X hours from

the system time.

This helps catch glitches around 00Z UTC from iMet & LMS6 sondes, and bad

CRC checks from

DFM sondes.

sonde_time_threshold = 3

**** End Config**

Thanks to all!

Rundfunkster

On Thu, Feb 17, 2022 at 7:35 PM Michaela Wheeler @.***> wrote:

can you share your autorx config ? We only implemented this check in the last month. I can see from the error message that only 2 payloads are uploaded which is not enough for us to be certain that there isn't any decoding issues relating to DFMs

— Reply to this email directly, view it on GitHub https://github.com/projecthorus/sondehub-tracker/issues/241#issuecomment-1043676601, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX2MMG7XH2BQSQJBUD7UFITU3WH3FANCNFSM5OWILPXA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[TheSkorm]

Looks all good, and checking in our database I can definitely see updates over the last 7 days from your station for DFM sondes being saved so I don't think you need to do anything.