The airQualityHealthConcern.supportedAirQualityValues has only three states: “unknown”, “good” and “unhealthy”. It’s going to take a while to figure out how it’s populated, how the airQualityHealthConcern is calculated and the threshold between “good” and “unhealthy”.
I’ll have a look at it later today.
Supported values:
{
"name": "Air Quality Health Concern",
"status": "live",
"attributes": {
"airQualityHealthConcern": {
"schema": {
"type": "object",
"additionalProperties": false,
"properties": {
"value": {
"title": "AirQualityHealthConcern",
"type": "string",
"enum": [
"unknown",
"good",
"moderate",
"slightlyUnhealthy",
"unhealthy",
"veryUnhealthy",
"hazardous"
]
}
},
"required": [
"value"
]
}
},
"supportedAirQualityValues": {
"schema": {
"type": "object",
"additionalProperties": false,
"properties": {
"value": {
"type": "array",
"items": {
"title": "AirQualityHealthConcern",
"type": "string",
"enum": [
"unknown",
"good",
"moderate",
"slightlyUnhealthy",
"unhealthy",
"veryUnhealthy",
"hazardous"
]
}
}
}
}
}
},
"commands": {
},
"id": "airQualityHealthConcern",
"version": 1
}
Now we have to find out why only three values are supported by the device…