You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the sensor reporting the pm2.5 values in real time on the attached display, I don't think modifying the heartbeat will put any additional stress on the sensors / hardware.
I suspect that is making the device push change notifications for temperature and pm2.5 to the Xiaomi servers and this is what they were trying to avoid. By coding that heartbeat in and enabling it only whey their app is in use they don't get flooded with useless data.
Ont he other hand, smoothening the AQI would be useful and I will try to code it in the plugin. It could be annoying and cause some problems when the pm2.5 is moving up and down around the breakpoints causing the aqi automations to be triggered on and off until the value settles.
TBH I am fine with smoothened AQI for automations. They've done a good job with smoothening/throttling except for the low AQI range (<20) where higher sensitivity is needed IMO.
Please don't hate me but I think it makes sense to have that AQI-heartbeat function optional 😄
Arguments for:
If you add a config flag for this, users can choose to have smoothened/throttled AQI or real-time AQI.
The way I personally would use it is to have smoothened AQI above 20 and real-time below 20.
The text was updated successfully, but these errors were encountered: