Could you restart the app, trigger the then card and send me the diagnostics. Then also not working - please elaborate
Med vänlig hälsning / Best regards
42ee38dd-31b1-4f6e-a26f-784e5bae5b9a
I restarted the app, then tested two different “Then” cards. Each time I do this it show that the triggers didn’t work. See picture below.
Someone replied to your post.
| MathiasT
April 15 |
- | - |
Could you restart the app, trigger the then card and send me the diagnostics. Then also not working - please elaborate
Med vänlig hälsning / Best regards
That helped a bit; i done the needed changes; please test this build; https://homey.app/a/net.tornbloms.blueair/test/
I have updated the widgets as well in this build.
Best Regards,
Mathias Törnblom
Version 3.2.15 is out now! If you are on the edge, give the test version (BlueAir | Homey) a go before everyone else. Please send us your diagnostics and tell us what is going wrong.
Will be away for the next 10 days as I have a regular job. When I get back I’ll do a deep dive into.
Ken
Someone replied to your post.
April 16 |
- | - |
That helped a bit; i med the needed changes; please test this build; https://homey.app/a/net.tornbloms.blueair/test/
I have updated the widgets as well in this build.
Best Regards,
Mathias Törnblom
Brunkebergsåsen 37 C, 192 66 Sollentuna
Tel: +46 709 49 90 10
Noticed that a new update came this morning. I tried it out as I had a few moments. The “Then” cards are still not working.
In flows, they at least show that the command was successful, but unfortunately, the action never reached the purifiers.
Someone replied to your post.
April 16 |
- | - |
That helped a bit; i med the needed changes; please test this build; https://homey.app/a/net.tornbloms.blueair/test/
I have updated the widgets as well in this build.
Best Regards,
Mathias Törnblom
Brunkebergsåsen 37 C, 192 66 Sollentuna
Tel: +46 709 49 90 10
New test version out that adds more logging for now and a app setting to switch the debugging on. So turn that on and run your flow then share your diag with me
23ee7582-97ad-40a3-90ae-5652dbbd7e68
Hi Mathias,
Apologies for the delayed response — it’s been a hectic couple of weeks on my end.
I’ve had a chance to test the basics and can confirm that on/off, auto mode, and sleep mode are all working, which covers my minimum requirements. I’ll continue testing the remaining features and flow cards soon and will report back.
One piece of feedback as the integration matures: the action cards could be a bit more intuitive. For example, turning the purifier off requires setting standby to “on,” which isn’t immediately obvious. Similarly, switching to auto mode when the purifier is off currently requires two separate cards — one to set standby off, and another to enable auto mode. Combining these into single, clearly labeled actions (e.g., “Turn Off” or “Set Auto Mode”) would go a long way toward a smoother user experience.
I appreciate that this is still early in development and you’ve already made great progress. Just wanted to share that feedback while it’s fresh. Thanks again for your continued work on this!
Thanks,
Ken
Someone replied to your post.
April 17 |
- | - |
New test version out that adds more logging for now and a app setting to switch the debugging on. So turn that on and run your flow then share your diag with me
Hi,
I am trying to pair the BlueAir DustMagnet, but I keep getting the message that no new devices have been found. I have reinstalled the BlueAir app, created a new account, and paired it again, but it remains invisible in the Homey app.
Do you have any idea what might be causing this?
Many thanks in advance.
Lennart
I have the same issue 
I have a Blueair DustMagnet 5240i.
Thanks in advance,
Cheers/Carl
I made a test build for you, BlueAir | Homey
I made a test build for you BlueAir | Homey
Thanks Mathias! Now the Dust Magnet is found and I can create the device, but I still get" “Initialization failed” on the device (red triangle with exclamation point). Same problem that was introduced in the last official release when I had to define it as a “Health Protect” in order to find the device).
Hi @MathiasT,
Just wanted to circle back with a positive update — everything is working well with my two Blueair Blue Pure 311i Max purifiers! I should mention that I’m actually running the mainline app rather than the test build you shared earlier. After my initial testing, I went through a significant Homey rebuild migrating from a Homey Pro 2023 to a 2026 hub, which came with quite a few issues that pulled my attention away from the Blueair integration for a while. But I’m back, and the app is performing reliably with both Pure units.
I do have a couple of minor items specific to the Blue Pure 311i Max — no urgency at all, just things that would be nice to have down the road when you have time:
-
PM2.5 reporting — The PM2.5 value appears as an option on the device status indicator, but no value is ever populated. Additionally, the “When PM2.5 changes” condition card doesn’t appear to function, likely because the app isn’t tracking that value to begin with. It would be great to have this working eventually, as it would open up some useful air quality automations.
-
Mode switching in flows — When the Pure 311i Max is in auto mode and I want to switch to night mode or manual fan speed, I always need to include a “Set standby to Off” card first before the mode change takes effect. A small quality-of-life improvement would be if mode-change actions handled waking the device automatically, so a single card could do the job.
Again, none of this is urgent — the app is working great for my core needs with the Blue Pure line. Thank you for all the work you’ve put into this!
Thanks,
Ken
@Ken_Hansen, here’s a new test version for you: BlueAir | Homey
. Please give it a go and switch on debug in the app settings while you’re testing – it should help us track down what’s happening with the PM2.5 bug. The mode switching issue should be sorted now. Thanks so much for flagging this! 
I just installed the test app and turned on Verbose logging. I created a couple of flows to use PM2.5 values and notice that when you use “AND” cards, it does not distinguish between multiple purifiers. The only cards show are global, I’m assuming.
FYI, my wife picked up two more of these for a total of 4 now in the house.
Ken
Someone mentioned you in a post.
July 21 |
- | - |
@Ken_Hansen, here’s a new test version for you: BlueAir | Homey
. Please give it a go and switch on debug in the app settings while you’re testing – it should help us track down what’s happening with the PM2.5 bug. The mode switching issue should be sorted now. Thanks so much for flagging this!
I’ve spotted a little bug! There’s a test release waiting for you at BlueAir | Homey
. Since you’re the only person I know with four machines, I reckon you’re the one who’d catch this – I’ve only got one, so I’d have missed it. If you could share your thoughts here, that would be brilliant!
I ran the diagnostics. The file number is below.
14b85c26-f638-45de-9423-7e739d4005f8
Thanks for sharing the debug logs! It looks like you’re now successfully sending data to each device – brilliant news. Are there any other hiccups you’ve noticed?
Mathias,
The Homey Phone App or using the computer doesn’t show the current PM2.5 values. When I hover over it with the mouse, it says that it hasn’t reported it in over a month. I believe the and card flows are working correctly, its just not reporting/showing the actual values. I’ll need some time to review further as I have been busy at work with not a lot of time to look over.
Also, (When I get a chance to look closer) I noticed that the tiles will highlight when auto is on. At the same time the quick action on/off button is a stanby status. Not sure if this was intended or not. In other words, I can have the purifier on (not on standy) and if auto is off, the tile is grayed yet the purifier is on.
Give me some time to really get into it. We are heading on vacation all of next week so I am hoping to get a good look at this before I leave.
Ken
Someone replied to your post.
July 22 |
- | - |
Thanks for sharing the debug logs! It looks like you’re now successfully sending data to each device – brilliant news. Are there any other hiccups you’ve noticed?
