I’m running the Homey Bridge, and because of that is restricted to run the official Netatmo Homey cloud app.
Back in the days the integration between the Netatmo weather station and Homey was more frequently updated. Lately it has changed to several hours.
As an example, the CO2 level inside my living room isn’t updated for several hours. The same goes for temperature readings. I’m logging this to a spreadsheet “when the CO2 level changed”. One of the CO2 readings was changed by the Netatmo-Homey integration at 10:32am, reading 1060 ppm. Next change was 1:42pm (> 3 hours), reading 764 ppm. When reading the Netatmo app directly, it was several updates during this time frame.
The reason for my more frequent updates request is that I would like to increase the ventilation when the PPM level rises above levels.
Maybe the reduced update frequency is related to the cloud version of Homey. However that would be odd, as the Netatmo app is the same and regardless of the type of Homey platform, the data is obtained via the Netatmo cloud connection.
That wouldn’t be odd, because the Hue app does the same: the Homey Cloud update interval is significantly larger than the Homey Pro update interval (or at least it was last time I checked), because of rate limiting.
Nothing personal, but in general I am concerned about the level of trust people have in wireless & “cloud” technology combined with (personal) safety.
A (wireless?) CO2 sensor sends it’s data to a “Netatmo cloud” somewhere, and that “cloud” relays that data to “your cloud” (Homey Cloud). Your programmed automation sends alerts to another wireless device, a fan.
What can go wrong?
I have had many issues with the “rate limited” error message, in particular from the Netatmo-Homey integration.
Do you know if the “rate limited” is a Homey-, Netatmo- or Netamo Homey app developer issue? I.e. who do I ask if they can do something with the issue?
