Hi Ken,
Thanks again for the detailed follow-up and screenshots — really helpful.
Tile highlighting / auto vs. standby: you were right, and it’s fixed. The device tile was configured to highlight based on “auto mode” instead of the actual power (standby) state, which is exactly the mismatch you described — a purifier that’s on with auto off would show as grayed out. Swapped that so the tile now reflects actual on/off status. Rolling out in the next update.
PM2.5 not reporting: confirmed the 311i Max does have a real PM2.5 sensor on the back (it’s what drives your unit’s own auto-mode fan adjustments), so this isn’t a hardware limitation. Looking at the diagnostic you sent, the specific API response captured at that moment showed no sensor data at all for your unit — not a wrong-field-name bug like I first suspected, just genuinely empty at that snapshot. Since that log happened to be grabbed alongside the fan-speed crash, it’s only a single point in time, so I can’t yet tell if that’s a one-off gap or a persistent issue on the cloud side for your unit.
Whenever you get a chance (genuinely no rush, enjoy your vacation!): could you turn on Verbose logging again and let it sit for 3-5 minutes so it captures 2-3 poll cycles, then grab that log? That’ll tell us whether PM2.5 data ever comes through from BlueAir’s cloud for your unit, or if it’s consistently missing — which would point us at the right next step.
Have a great trip!
Mathias
f0ae53ae-0b9f-4221-b5d5-63773710b628
I cleared the logs and reset the app and let it run. I sprayed some febreze on the Living Room purifier to change the PM2.5 values, but they did not come through and show up on the tile.
Ken
Someone replied to your post.
| MathiasT
July 23 |
Hi Ken,
Thanks again for the detailed follow-up and screenshots — really helpful.
Tile highlighting / auto vs. standby: you were right, and it’s fixed. The device tile was configured to highlight based on “auto mode” instead of the actual power (standby) state, which is exactly the mismatch you described — a purifier that’s on with auto off would show as grayed out. Swapped that so the tile now reflects actual on/off status. Rolling out in the next update.
PM2.5 not reporting: confirmed the 311i Max does have a real PM2.5 sensor on the back (it’s what drives your unit’s own auto-mode fan adjustments), so this isn’t a hardware limitation. Looking at the diagnostic you sent, the specific API response captured at that moment showed no sensor data at all for your unit — not a wrong-field-name bug like I first suspected, just genuinely empty at that snapshot. Since that log happened to be grabbed alongside the fan-speed crash, it’s only a single point in time, so I can’t yet tell if that’s a one-off gap or a persistent issue on the cloud side for your unit.
Whenever you get a chance (genuinely no rush, enjoy your vacation!): could you turn on Verbose logging again and let it sit for 3-5 minutes so it captures 2-3 poll cycles, then grab that log? That’ll tell us whether PM2.5 data ever comes through from BlueAir’s cloud for your unit, or if it’s consistently missing — which would point us at the right next step.
Have a great trip!
Mathias
