Excellent ![]()
Just a comment after using for a couple of weeks. The Alpstuga sensor responds very quickly and is quite accurate but doesnât seem to show correctly the tile Air Quality Level. I think this is an IKEA bug as my PM2.5 virtual Air Quality sensor does display the correct level.
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âŚ
This might give a clue as to why my Sonoff virtual sensor which comes across in Matter, shown here functioning correctly, will not map correctly for all states.
Would seem more logical 3 active states as per IKEAâs green, ambar and red?
Going off- thread here but if youâre interested you can see the problems in Matter implementacion of air quality on the Sonoff iHost thread here
New IKEA matter over thread light announced
Quick update after trying some more of the new IKEA Matter stuff:
- KAJPLATS bulb, E14 tunable-white version - works, dimming and full color range 2200-6500 available from SmartThings, acts as Thread forwarder.
- MYGGSPRAY motion and light sensor - see above, works well with good reaction time. Ambient brightness sensor reports very low values, not sure about that one as yet.
- KLIPPBOK water leak sensor - works, hooks into Home Monitoring, low trigger threshold (finger on contacts triggers it).
- BILRESA two-button remote - works; both buttons support single, double, triple press plus hold.
- BILRESA rotary dial remote - not fully supported. Reports as three button instances (the rotary acting as pushbutton, pushing below the three LEDs switches between 1-2-3). Rotary dial not represented. [An announcement from CES today has it that this will be added very soon.]
In only slightly related news, the dual button BILRESA also is the very first momentary (stateless) button that Iâve ever seen work directly on an Alexa Echo. Only single-press supported on either button, but itâs a start.
The water leak sensor pulled a firmware update straight out of the box, the others did not.
Here endeth my report.
regards,
Peter
I want to try that one, the 1521 lm one was disappointing with green-ish cool whites and strange orange-ish warm temperatures. Are the colour temperatures other than 2700 K easy on the eyes?
You can use the scroll wheel rotation with my custom driver and automate it in multiple ways as well as expose more events and add more features for both BILRESA models.
They added support for Matter buttons recently, Google Home still does not support them though.
On the bulb - 2700 looks pretty identical to the Hue 1100 white in the other lamp. Yes 6500 is stone cold but doesnât look greenish to me. 2200 is very orange as itâs supposed to be, pretty much in line with the LEDVANCE Sun@Home ceiling lamp in the same room.
The rotary BILRESA is back in the box until official support comes through. Thanks for the pioneering work though!
Echo - did not support stateless buttons of any kind besides the long defunct Echo Button. Zigbee buttons (e.g. Sonoff) detected as a âswitchâ and didnât work at all. The Matter button reports as a âremoteâ and actually does work. This fills a big gap in the Alexa/Echo system (albeit poorly).
Exactly, the Alpstuga shows these options for a routine
while my Matter virtual sensor shows these - although I canât use them!
I donât know what that is, but Iâm guessing you created it on the âiHostâ platform? A virtual device can support whatever the developer wants, of course. I could just as well build a virtual air-quality Edge driver that reports completely made-up supported values.
It would be easy to figure out whatâs going on if we had the logcat output from when the device is added. Matter drivers usually probe the device to populate the list of supported values. The problem is that I donât want to delete my devices, because Iâm collecting long-term air-quality data.
Iâll read through the code later today, though.
From a first look:
It starts with a baseline set:
unknown,good,unhealthy
Then it adds more enum values only if the device reports the corresponding Matter feature bit:
- If the Air Quality cluster supports FAIR â add
moderate - If it supports MODERATE â add
slightlyUnhealthy - If it supports VERY_POOR â add
veryUnhealthy - If it supports EXTREMELY_POOR â add
hazardous
So the supported-values list gets âricherâ only when the underlying cluster says those extra levels are meaningful for that device.
This means that the device doesnât âreportâ these values in the feature map. Interestingly, I have seen the value âunhealthyâ reported in the event history before.
Klippbok firmware update.
Any tips on getting this to actually complete.
SmartThings keeps prompting me to update , I click the update butting and the device card suggests itâs âupdatingâŚâ but it never seems to complete and then prompts again later. I tried placing the sensor within 1 metre of the hub, no difference
Iâve been attempting updated via the app, because it keeps prompting there. Will try AWA too when latest attempt finishes
Wake the device up, right before you start the firmware update. Yes, that means to trigger the sensor⌠Edit: or remove the batteries for a few seconds.
Tried triggering Device to wake it up, also batteries out and back in, no joy.
![]()
Since the firmware is temporarily stored on the hub before the device downloads it, Iâd reboot the hub. Who knows if itâs stored in the /tmp partitionâŚ
![]()
Rebooted and the update applied itself after the reboot.
Iâm noticing I am needing to reboot a lot these days to add new devices or for update firmware ![]()
![]()






