I've installed the Air Things Device driver to grab radon (and other) data from the AirThings web site for my AirThings View Radon device. So far so good, but the list at:
Driver Capability List | Hubitat Documentation
shows nothing for radon; I was expecting something like "radonMeasurement". Would it be possible to add to the Hubitat a capability so that radon sensors can advertise themselves properly?
There is no way to add your own capabilities to hub. While this could be considered for the future as something built-in, there is no reason you can't report this measurement in a sensible way at the moment. Just use a custom attribute, such as radonMeasurement
(or whatever you want to call it), in your driver, as described in the developer docs.
Yes, I understood that there's no way for me to add capabilities to the hub. I should perhaps have phrased my question as: how does one request the inclusion of a new capability?
Meanwhile, the Air Things Device driver already does define an attribute "radonShortTermAvg", and it is reported (and now logged) just fine. I wanted to pull the values into Grafana via InfluxDB, so for now, I've hacked on the app InfluxDB Logger to add this attribute to its list for devices having the capability CarbonDioxideMeasurement. Pretty ugly, but I think it will work well enough for now. Too ugly to submit as a patch on InfluxDB Logger, though!
Use the Feature Request category to ask for it to be added as a capability.
Seems like a good idea.
You don’t need to do that. If your current instance is logging via capabilities, create a new one (it can use the exact same db parameters) and instead flip on the “advanced attribute selection” switch. This will let you select any attribute available on the device.
Thanks, done.
I admit that I'm afraid to do that for fear that it will wreck my existing selections, which would take me a while to re-implement. I should have experimented with that before I had so much configuration in place! Is it the case that I can switch back and forth between the two selection modes without destroying previous selections?
(I had initially created a new capability in the InfluxDB Logger, expecting to be able to advertise it in the device driver, but when that turned out not to work, I reverted that change.)
I am not sure, but that’s not what I’m suggesting. Certainly you can’t use both methods for the same app instance.
Instead, install a second instance of InfluxDB Logger. Just use “Add User App” again. You can customize the name of each instance in the app config page.
The second instance can use the same db parameters as the first if that is what you want, but you can set other configurations differently g, e.g. for device selection, etc.
Gotcha. I will consider that! Thanks.