Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid json being submitted to sondehub - inf in the humidity field. #460

Open
TheSkorm opened this issue Sep 7, 2024 · 4 comments
Open

Comments

@TheSkorm
Copy link

TheSkorm commented Sep 7, 2024

Describe the bug
JSON sent to sondehub includes invalid json. Specifically in the humidity field we are receiving an inf value.

To Reproduce
Steps to reproduce the behavior:

  • W1310471 radiosonde had a sensor fault
  • TTGO stopped showing up on SondeHub

Expected behavior
Data ends up in SondeHub

Screenshots
If applicable, add screenshots to help explain your problem.
image

SondeHub logs show:

    {
        "software_name": "rdzTTGOsonde",
        "software_version": "master_v0.9.5",
        "uploader_callsign": "KF5LJD",
        "time_received": "2024-09-07T00:49:01.000Z",
        "manufacturer": "Vaisala",
        "serial": "W1310471",
        "datetime": "2024-09-07T00:49:18.000Z",
        "lat": 32.74656,
        "lon": -97.13464,
        "alt": 35540.33203,
        "frequency": 404.800,
        "vel_h": 4.67977,
        "vel_v": 8.47726,
        "heading": 257.74380,
        "rssi": -106.0,
        "frame": 8248,
        "type": "RS41",
        "sats": 9,
        "subtype": "RS41-NG",
        "temp": -251.7,
        "humidity": inf,
        "burst_timer": 65535,
        "batt": 2.60,
        "uploader_position": [
            33.280400,
            -96.988700,
            690
        ]
    },

Version and specific configuration:
Seems to be these versions:
image

Additional context
meow.

@dl9rdz
Copy link
Owner

dl9rdz commented Sep 7, 2024

Good observation ... Will be fixed in the next version.

@darksidelemm
Copy link

While it might not be the most ideal approach, the RS decoders used in auto_rx handle these kinds of failures with humidity by clipping the value to either 100 or 0 (depending on the fault).

@mycarda
Copy link
Contributor

mycarda commented Oct 3, 2024

Is the best approach to not send the temperature and humidity values if they are out of range? We don't send temperature and humidity data until we received enough frames to calculate a valid temperature and humidity, so if we know the values are out of range, just don't send data we know is wrong.

@dl9rdz
Copy link
Owner

dl9rdz commented Oct 3, 2024

That is the approach I have taken. If the calculated value is <0 or >100 then the value is set to not available and will not be sent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants