Ok, so indeed something to think about, it may be redundant with what we have natively in Gladys, but it might also be appreciated to allow Gladys to modify the schedule on the fly in case of change: you come back from vacation earlier: change the schedule so that it’s warm when you get back, that kind of thing.
We’ll see how we want to integrate it and what the specific needs are
Well actually the Netatmo app is really well done I find, so might as well take advantage of it and just choose the schedule on Gladys without necessarily modifying it.
Yes And besides, @Terdious ordered Nest so we’ll be able to make a service for Nest after the one for Netatmo and therefore think a bit more about heating
The day’s progress also included the integration of Aircare, the Healthy Home Coach with the following features:
Temperature,
Humidity,
CO2,
Noise,
Pressure,
Absolute Pressure,
Health Index
Thanks! We can make a small video about it, but the best thing would be to discuss it directly with @Terdious! He has everything! He’s the best tester for Netatmo, haha!
We still have a bit of work to do, but we’re almost there.
If I have time before the end of the year, I will test the test version.
Have you set up sentences in the brain?
« What is the temperature of the room (valve 1)? »
« The temperature of the room is 19°C. »
Not problems, just that we were unnecessarily calling functions. So now we’ve done something much more optimized and cleaner. Split all function calls, etc.
Concretely, @Terdious’s installation works very well, no lag / performance issues.
We wanted to go further, test a poll every 10 seconds to « stress » Gladys. It works except when netatmo sends us away because (too many requests).
I’m reaching out to see if you’ve had a chance to test the Netatmo service on your end? For your information, we’ve made significant code updates. If you had already pulled the PR for testing in dev, you can pull it again to be up to date.
Has anyone else been able to test it? @spenceur, maybe?