qualityControl is omitted from response data

[ndrwrbgs]

Documented here:
https://madis.ncep.noaa.gov/madis_sfc_qc_notes.shtml
Not in the METAR but returned in the API response retrieved

[ndrwrbgs]

Ex:

{
    'type': 'FeatureCollection',
    'features': [{
            'id': 'https://api.weather.gov/stations/KPHL/observations/2025-12-23T04:15:00+00:00',
            'type': 'Feature',
            'geometry': {
                'type': 'Point',
                'coordinates': [-75.25, 39.87]
            },
            'properties': {
                '@id': 'https://api.weather.gov/stations/KPHL/observations/2025-12-23T04:15:00+00:00',
                '@type': 'wx:ObservationStation',
                'elevation': {
                    'unitCode': 'wmoUnit:m',
                    'value': 6
                },
                'station': 'https://api.weather.gov/stations/KPHL',
                'stationId': 'KPHL',
                'stationName': 'Philadelphia, Philadelphia International Airport',
                'timestamp': '2025-12-23T04:15:00+00:00',
                'rawMessage': '',
                'textDescription': 'Cloudy',
                'icon': 'https://api.weather.gov/icons/land/night/ovc?size=medium',
                'presentWeather': [],
                'temperature': {
                    'unitCode': 'wmoUnit:degC',
                    'value': 3,
                    'qualityControl': 'V'
                },
...

[MatthewFlamm]

How do you envision this working? I have two thoughts. One is to create custom subclasses of, for example, float that has this as an attribute. Another is to filter out responses below some qualityControl level, e.g. v. For some reason I thought we already implemented the latter, but maybe it was only planned in my head.

[ndrwrbgs]

I’d rather not filter data out proactively, personally, or at least have a way “out” of that. End to end I’d expected to see it as an attribute on the sensors in homeassistant so that the user has the final call.

Since it’s returned from this library as a dictionary right now, I think maybe the least breaking change could be an opt-in flag, and when that is passed the dictionary has additional items *_quality_control? If breaking changes are okay (eg the main usage is HA and you control that), then perhaps elevating up to a class return type from a float to reflect what NWS is returning in the API.

I should note that this was opened for completeness as a noticed missing item more than a dependency I need. For any particular user the data is likely either good enough not to care, or they move on to another data source. Leaving this as pending more feedback or won’t fix would seem reasonable to me.