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.
I did the match up and update via HPM and now for some reason the new 'sensirionVOCindex' attribute isn't triggering events for Maker API where almost everything else is? I'm seeing this on 2 different hubs (2.3.5.152):
Edit: Seems removing and then re-adding the device to the MakerAPI instance did the trick. That's interesting. I wonder how many other of my devices that have gotten new states aren't pushing the data...
I haven't tried the E1743 on/off dimmer yet (this is what we use the most), but it would be great if I could.
Right now I'm running my Ikea buttons through my SmartThings hub.
My long term hope is to be able to use Matter between HE and the Dirigera, but direct pairing to HE (without battery issues) would be even better.
Works amazing with your Tuya ZigBee Button Driver and the HE Button Controller app.
I've been having issues with these buttons lately on SmartThings since the last ST firmware update.
If they don't eat batteries while connected to HE, this could ultimately remove another piece of hardware from my setup once I find a way to use my Ikea motion sensors.
