Pro-grade automation for the IKEA ALPSTUGA E2495 Matter Air Quality sensor. This blueprint allows you to trigger specific actions when any environmental metric (CO2, PM2.5, Air Quality Index, Temperature, or Humidity) crosses your custom thresholds.
[!NOTE]
The Air Quality entity is a general âAir Quality Indexâ (AQI) calculated by the device (usually based on PM2.5 and CO2 levels). While the ALPSTUGA does not have a dedicated VOC sensor, this summary state is a great way to trigger whole-room air clear actions.
Manual Import URL
If the button above doesnât work, you can copy the URL below and paste it into the âImport Blueprintâ dialog in Home Assistant: https://github.com/aledziko/HA-blueprints/blob/main/IKEA/Matter/ikea-alpstuga-e2495/ikea-alpstuga-e2495-matter-air-quality-sensor.yaml
Key Features
Five Environmental Triggers: Dedicated actions for CO2, PM2.5, Air Quality summary, Temperature, and Humidity.
Dual-Phase Actions: Set numeric cutoffs (CO2, PM2.5, Temp, Humidity) or state lists (AQI Summary) for both âAlertâ and âNormalâ phases. This allows you to start and stop devices automatically as conditions change.
Stabilization Time: Prevent notification âflappingâ by requiring states to remain active for a configurable duration (e.g., 30 seconds).
Parallel Execution: Handles multiple environmental shifts concurrently (e.g., boosting the air purifier while notifying about high CO2).
Example Use Cases
Air Purification:
Air Quality High: Automatically boost your air purifier to âHighâ when the general air quality index drops.
PM2.5 High: Trigger targeted actions for dust or smoke levels above 25 Âľg/mÂł.
Healthy Sleep & Focus:
CO2 High: Receive an alert or flash a light in your office or bedroom when CO2 levels exceed 1000 ppm, signaling itâs time to open a window.
Ventilation & Recuperation:
High Humidity: Automatically trigger the bathroom fan or a whole-home recuperation system when humidity levels spike.
HVAC Control:
High Temp: Turn on cooling when the room hits 26°C (79°F).
Low Temp: Activate heating when it drops below 18°C (64°F).
Pro Tip: Dynamic Notifications
You can make your alerts smarter by including the actual sensor value or state in your message. When setting up a notification action, use the following template in your message text:
For CO2/PM2.5: CO2 level is now {{ trigger.to_state.state }} ppm
For Air Quality: Air quality status is now {{ trigger.to_state.state }}
Preventing âNotification Stormsâ
If you are receiving too many notifications in a short time, itâs usually caused by the sensor âflappingâ between states. To fix this:
Adjust Trigger States: In the Air Quality settings, ensure you unselect âGoodâ and âFairâ. This prevents getting an alert every time the air improves back to normal.
Use Stabilization Time: Increase the Stabilization Time (e.g., to 30 or 60 seconds). The blueprint will then wait for the sensor to stay at the new state for that duration before alerting you.
Requirements
IKEA ALPSTUGA (E2495) sensor connected via Matter.
Entities for CO2, PM2.5, Air Quality Index, Temperature, and Humidity.
License
Licensed under the MIT License.
Troubleshooting
Troubleshooting
Preventing Repeated Actions?
If you notice actions firing multiple times (e.g., your ventilation toggling on/off or receiving duplicate alerts) even when the air quality is stable, this blueprint has robust filtering built-in:
Strict Logic: Actions only trigger if the value actually crosses the threshold. If CO2 drops from 798 to 797 (both below the default 800 limit), the automation ignores it.
Blip Filtering: Brief âUnavailableâ states from the sensor are automatically filtered out.
Optimization: Use the Action Trigger Stabilization Time (e.g., 30s) to further smooth out noisy data. This ensures your siren or fan doesnât toggle rapidly due to minor sensor fluctuations.
More Blueprints & Community
Check out my other blueprints for IKEA Matter devices on the Home Assistant Community:
Update: Fixed âNotification Stormsâ & Save Errors
Hey everyone, just pushed a solid update to the whole IKEA Matter collection (ALPSTUGA, TIMMERFLOTTE, etc.).
If youâve been getting hammered with duplicate notifications or your fans toggling on/off rapidly, this fixes it.
Added âAction Trigger Stabilization Timeâ: A new global setting (default 0s) to prevent flapping.
Smarter Logic: The blueprints now ignore those 1-second âUnavailableâ blips that happen on Thread networks, so you wonât get false alarms anymore.
Config Fix: You can now leave optional sensors layout blank (like Battery or Illuminance) without getting a save error.
Hi! @ostrymiecz
Thanks for the suggestion! This is a great improvement! It definitely makes sense to silence notifications during sleep hours. I just added the changes to the repo. Whats new:
Added an âEnable Active Hours?â toggle (default OFF).
Added Start Time and End Time inputs.
If you switch the toggle to ON, the automation will strictly run only between those hours. If you leave it OFF, it works 24/7 as before.
Please re-import the blueprint and give it a try!
I thought about another (small) feature which could be useful.
Currently we have triggers for HIGH and LOW threshold values for:
CO2
PM2.5
Air Quality
Temperature
Humidity
There is also Action Trigger Stabilization Time which is great, but one thing is missing.
I thought about adding a checkbox for LOW thresholds â Do not trigger if HIGH threshold is not exceeded again. Such option would be for each LOW threshold to prevent spamming with LOW only triggers fluctuations.
Why such option? Imagine a situation where you have a HIGH threshold for CO2 set to 1200 ppm and a LOW threshold set to 600 ppm. The high threshold triggers, so you ventilate the room and the level drops to 550 ppm, triggering the low threshold. Then the level rises to 610 ppm, then drops again to 590 ppm, triggering the low threshold again!
In such case when fluctuations triggers only low threshold, unnecessary âloopsâ would occur. This option would help stop triggering them.
On second thought â the same thing could happen with HIGH treshold(s)?
So maybe it should be global checkbox? For all thresholds maybe â Do not trigger if one threshold wonât exceed other again. What do You think?
Thank you so much for the brilliant suggestion! You were spot on. Sensor fluctuations near the thresholds were causing unnecessary actions/notification âloops,â especially when values hovered just over or below the limit.
I have just released an update for the entire IKEA Matter collection (ALPSTUGA and TIMMERFLOTTE that introduces a feature called Threshold Bind). Active time window also is ported to other IKEA blueprints.
How it works:
It implements exactly what you described: a âOne-Cycleâ logic.
Once a HIGH threshold is crossed, the alert is âlatched.â
The automation will not trigger another alert until the LOW (Safe) threshold is reached.
This creates a strict alternating cycle that completely eliminates the chatter loops.
Why the Helpers are needed:
To make this work, Iâve added an option to select a Toggle Helper (input_boolean).
Because Home Assistant blueprints are âstatelessâ templates, they donât have a way to remember if they already sent a notification five minutes ago. The Helper acts as the persistent memory for the automation, allowing it to âlockâ its state across triggers and even Home Assistant restarts.
A quick tip on setup:
If you use this feature, please make sure to create a unique Toggle helper for each automation. If you share one helper between two different rooms, one roomâs humidity might âlockâ the alerts for the other!
Iâve updated the READMEs for both blueprints with a detailed setup guide. Let me know how it works for you!
I have 3x ALPSTUGA in 3 different rooms. I have air ventilation in the home with heat exchanger meaning that all âwater roomsâ have air extraction and the other rooms have air insufflation. This is where the problems begin âŚ
I have nasty neighbors who donât know how to use their wood stove so they generate crazy amounts of fumes that end up being injected in the house by the air ventilation.
This kills the air quality, even dirties the ceilings!
I wondered if you had the idea of linking different ALPSTUGA to take an action if several are showing similar reading changes.
If only the living room PM2.5 value explodes then itâs probably because Iâve been adding wood in my own wood stove that sits in the living room.
But if 2 ALPSTUGA in the sleeping rooms also have big PM2.5 increase then I need to take action and stop the air ventilation for one hour then restart it hoping the smoke outside is gone.
Of course I can do my own custom automation to handle this but I wanted to share the use case if you find it interesting and it gives you some ideas to further develop your blueprint or create a new one around ALPSTUGA.
This is really good. It turns alpstuga data in to actionable automation action!
A related thing to consider is keeping the display turned off. Because HA takes the alpstugaâs data and deals with it via exhaust, hvac fan cycling or reminder to open a window, I donât need the distraction of the display
For guests it can be confusing: âWhat is that number mean?â, âDoes it say itâs ok?â. Or my favorite, âYou need to set that clockâ. I didnât buy it to be a clock and I donât need to see anything and would like keep the display shut off. I know I can turn it off, but if it gets unplugged or thereâs a power blip, it auto comes back on.
The thought is an option to manage the on/off toggle for the monitor with the option to keep it off.
@paulbates Unfortunately ALPSTUGA doesnât expose the entity to turn the display off over matter. It has some built-in option that dimms the display during night hours (I donât remember which exactly they are). You need to have the time set on the device to make it work. There is no build in functionality to sync time for Matter devices in Homeassistant but fortunately @Loweack came up with the solution. Please check out his Matter Time Sync add-on on HACS - [MATTER] Sync Time with Matter Devices (e.g. IKEA ALPSTUGA)
Hi @mfo38 your scenario with nasty neighbours is tricky, since normally when PM2.5 is high youâd like to ventilate the house even more, but in your scenario it makes the situation even worse. I donât have the solution out of the box but Iâll think if there is an option to link multiple devices as a trigger into one blueprint. for now you could create a simple automation manually in âAutomations and Scenesâ section in settings, which have possibility multiple triggers/ IF conditions.
Blueprints are generally designed for a 1-to-1 relationship (one sensor per automation) to keep the configuration simple and clean for most users. Adding âMulti-Sensorâ logic directly into the ALPSTUGA blueprint would make the UI too complex for 99% of its users.
However, there is one option you can use right now that is much more robust than a custom automation. You can create a Template Binary Sensor (Go to Settings > Devices & Services > Helpers > Create Helper > Template > Template a binary sensor).
This allows you to treat multiple ALPSTUGAs as a single âSmoke Alertâ entity based on your specific logic.
Use this State Template:
{% set alpstugas = [
states('sensor.alpstuga_air_quality_monitor_pm2_5_1'),
states('sensor.alpstuga_air_quality_monitor_pm2_5_2'),
states('sensor.alpstuga_air_quality_monitor_pm2_5_3')
] %}
{# Check if at least 2 ALPSTUGA sensors are above 35 Âľg/mÂł (High PM2.5 threshold) #}
{{ alpstugas | map('float', 0) | select('>', 35) | list | count >= 2 }}
(Just replace the entity IDs with the actual pm2_5_density names from your ALPSTUGA devices).
Use Cases for this Logic:
This â2-out-of-3â logic perfectly distinguishes between your stove and the neighborâs:
Case 1: Local Spike (e.g. Cooking/Your Stove): Only 1 sensor (Living Room) triggers. The count is 1, so the sensor stays OFF. Your ventilation keeps running (good for clearing your own indoor smoke).
Case 2: Global Spike (e.g. Neighborhood Smoke): PM2.5 rises in multiple rooms (Bedrooms AND Living Room) as the ventilation pulls in smoke from outside. The count hits 2 (or more), and the sensor turns ON.
Creating the Automation:
Once you have this new helper (e.g., binary_sensor.outdoor_smoke_warning), you just need one simple automation to react to it:
Trigger: When binary_sensor.outdoor_smoke_warning goes to on.
Action: Stop your ventilation.
Action: Wait for 1 hour (or until the sensor goes back to off).
Action: Restart ventilation.
This keeps your logic clean and centralized, ensuring your house stays smoke-free!
I have a great update regarding your request to keep the ALPSTUGA display turned off.
Previously, I mentioned that the device didnât seem to reliably expose the entity to turn off the display over Matter. When I tested it back then, triggering the switch manually didnât work. However, there have been a few Thread and Matter updates in Home Assistant recently, and it appears this functionality is now fully working!
I have just released v2.1 of the ALPSTUGA blueprint which adds a new âKeep Display Offâ feature. You can now select your display switch entity and enable this toggle. The blueprint will automatically intercept the event and force the screen to turn back off if it ever turns on (for example, after a power blip or if toggled manually).
Enjoy the update and the distraction-free display!
Manual Import URL
Key Features
Example Use Cases
Air Purification:
Healthy Sleep & Focus:
Ventilation & Recuperation:
HVAC Control:
Preventing âNotification Stormsâ
License
Troubleshooting
More Blueprints & Community
Explore all my blueprints on the HA Forum
Why the Helpers are needed:
