Airthings

[mboisson]

This PR adds support for Airthings Radon, Volatile Organic Compounds and Carbon Dioxide sensors as exported from HomeAssistant as supported by the newly released version:
https://www.home-assistant.io/integrations/airthings_ble

[tomwpublic]

@mboisson -- There is a built-in Generic Component Carbon Dioxide Detector. Can you try using that?

It does look like the VOC and Radon sensors will need to be custom. The Radon one seems very specific (short term average reading?). Is there any way to generalize that at all, in case other sensors show up that may want to utilize it? I am not familiar with the typical behaviors or measurements related to radon sensing.

[mboisson]

I'll have a look at the built-in CO2 sensor.

As for Radon, as far as I know, Radon readings are never instantaneous (or if they are, they are unreliable), it varies too much and is always averaged. Typical (approved by health authorities) radon testing is done over at least 3 months and sent to a lab for analysis. The AirThings device reports both short term (1 day average) and long term average (duration undocumented), but no instantaneous reading.

[mboisson]

Nevermind, as I wrote this answer, I figured it out.

[mboisson]

I have an idea to make the Radon sensor more generic

[mboisson]

Oh, shoot. The Generic Carbon Dioxide Detector does not work for automation. The "carbonDioxide" attribute does not seem to support numbers. According to the Rule 5.1 engine, "carbonDioxide" attribute takes values "detected", "tested" or "clear", so that won't work. I guess that's why it is a "Detector" and not a "Sensor".

I will revert my two previous commits.

.

[mboisson]

Ok, I made the radon sensor more generic. There is no need to be as specific in the name of the attribute or the name of the sensor. The fact that it is a 1 day average or a long term average is carried through in the label of the sensor exported by HA and is in practice device specific