I couldn't find a way to turn on the back light remotely. I am monitoring the other HA forums, if anyone finds a way to do it, I will certainly add it to this Hubitat driver.
I am still experimenting and deciding which is the best way to distribute the new series of drivers that use Library files. Using HPM will solve the issue for installing releases, but the problem is with installing the Beta versions of the drivers. In this case I have forgotten to update the "importUrl" link inside the driver, so it points to the code version where the libraries used are included at the end of the driver code.
If you look at the driver itself, @kkossev put in a link to the chart being used:
With that being said, I still don't really know what it's measuring. I seem to get really high index values that don't really correspond to smells or pm25.
After a week of using the Vyndstyrka, I'm not sure I trust the Air Quality Index at all... it routinely goes into "hazardous" (very high) levels of TVOC... just from making toasts or cooking spaghetti sauce. If that's enough to bring the air in "hazardous" zone, I don't know what hazardous means...
Above are the plots from the VOC (in ppb) as measured by my AirThings device, and the PM2.5 (in ug/m^3) as read by the Vindstyrka, below is the Air Quality Index, which is supposed to be total VOC...
VINDSTYRKA does not report "Air Quality Index", but VOC or tVOC index values. The same applies to Aqara Air Quality sensor ...
I will do some more research during the weekend and will change the driver, the numeric value attribute will be named "tVOCindex" probably... as it is definitely not a TVOC measured in ppb ( parts of gas per billion parts of air),
Do you think that the 'Index Category' value from the table that you linked corresponds to the "Index Value" as measured by the Ikea sensor?
I do not think they are the same scales. That one was from another vendor, Kaiterra. It seems to be an absolute scale (50 or less is good, 51-100 is moderate, 100-150 is high, …)
By comparison, the sensirion document states
On the VOC Index scale, this offset is always mapped to the value of 100, making the readout as easy as possible: a VOC Index above 100 means that there are more VOCs compared to the average (e.g., induced by a VOC event from cooking, cleaning, breathing, etc.) while a VOC Index below 100 means that there are fewer VOCs compared to the average (e.g., induced by fresh air from an open window, using an air purifier, etc.).
So that sensor produces a measurement which is relative to your own baseline… assuming nothing changed in the air around the sensor, I would expect the sensirion sensor to stabilize at a value of 100, regardless of the actual concentration of VOC in the air. A pretty useless measurement, I think.
For what I understand from reading this is that the sensor does not discriminate between specific VOC nor between harmfull and harmless ones. Furthermore, its sensitivity is not the same across all VOC. So with all those limitations, they decided not trying to report an absolute value which would be misleading and inacurate. Instead they choose to mimic the human nose.
This is more suitable as a trigger for automation related to odors, not air quality per say. (bathroom fan, cooking, cat litter)
Was getting really high IAQ readings in one room. Logs showed it jumped every 15 minutes. Found out my wife put an automatic air freshener right next to the VINDSTYRKA.