Include a Local API
Hello Netatmo Community and Development Team,
I hope this message finds you well. As an avid user and promoter of Netatmo's innovative range of products, I've deeply appreciated the thoughtfulness put into their design and functionality. The integration of Netatmo devices into our daily lives has undoubtedly set a high bar for smart home technology. However, there's one particular enhancement that I, along with many fellow enthusiasts in our community, would like to discuss the introduction of a local API for Netatmo devices.
The Value of a Local API
Improved Privacy and Security: A local API would allow users to interact with their devices directly over their local network without needing to send commands through external servers. This not only speeds up the communication but significantly enhances privacy and security, a growing concern among smart home users.
Enhanced Reliability: Relying on cloud services can sometimes lead to latency or downtime due to server issues or internet connectivity problems. A local API ensures that basic functionalities remain operational, providing a reliable fallback when the cloud service is unreachable.
Integration Flexibility: Many users employ home automation servers like Home Assistant, OpenHAB, or Domoticz, which can directly communicate with smart devices via local APIs. This integration empowers users to create more complex automation rules that are not possible through the official app alone.
Community Development: Opening up a local API can lead to community-developed applications and integrations, further enriching the Netatmo ecosystem. It enables hobbyists and developers to experiment and innovate, potentially bringing to light new use cases and enhancements.
A Call to Action
We understand that developing and maintaining a local API comes with its challenges, including ensuring security and providing support. However, we believe that the benefits significantly outweigh these challenges, not only for the users but also for Netatmo as a brand, by reinforcing customer trust and satisfaction.
We kindly request the Netatmo development team to consider our proposal for introducing a local API. Such a feature would undeniably make Netatmo products even more appealing to a broader audience, from tech enthusiasts to privacy-conscious consumers.
Closing Thoughts
In conclusion, the inclusion of a local API would be a significant step forward in making Netatmo devices more versatile, secure, and user-friendly. We are excited about the possibility of this feature and eagerly await your thoughts and hopefully, your action on this proposal.
Thank you for considering our request and for your continuous efforts to improve the Netatmo user experience. We look forward to your response and to the possibility of even more remarkable innovations from Netatmo.
Best Regards
Commentaires
48 commentaires
Also still waiting....
+1 on this
+1 on this.
Local API is a Need for the community!
We need at lest the capability to change the basic settings and the set point.
You have a great product, and claiming you provide also local control should be a diffezenziation plus on the marker with your direct competitor
The community around self maintained smart home "servers" is growing and those systems are becoming very user friendly.
If you provide local control, the word inside the community will spread quickly.
And a quality product with local control is the way we go.
Today people are more conscious than years ago on the value of the local control.
I, and we, hope you can take in account this change in your customers needs.
I think also your business could be benefited.
given the recent WAF changes many if not all of my automations now don't work very frequently due to 429 errors that are NOT the result of me overloading (e.g. a single toggle of a switch upon activity early in the morning fails). Local integration would not only be better for the users but also remove the need for the @netatmo servers to be highly available/performant.
Looks like the latest Azure downtime showed us all again, how useful and important a local API would be.
Local API is technically possible as Apple HomeKit (thermostat, cameras, Legrand Netatmo electrical) was still working just fine, even remotely, during the recent downtime.
I fully agree a local API should be included, considering how expensive these products are.
It looks like Netatmo simply doesn't care about consumers' wishes.
Agreed. Local API is a must!
All my light switches in my house are BTicino Living Now and I control them via Home Assistant so they turn on and off when I pass through or stay in various rooms. I get API limit cap messages EVERY SINGLE DAY, which means all my light-related automations BREAK EVERY SINGLE DAY, mostly in the evening when API usage starts to accrue and pass the limits. Please, PLEASE make a local-first version for your devices, you will not only gain consumer karma, you'll get a major reason for all smart home enthusiasts to recommend your devices, that are excellent in their own right, except for the requirement to use a web-based API to automate.
@Viorel i guess they do not really care about their Customers as it seems.
Hello,
I own a Drivia Eco Compteur (412032) and face a major limitation with the cloud-only API.
The Issue
The Netatmo API allows only 20 requests/hour shared across all data types (HOME, EVENT, ENERGY, etc.). For a typical setup, this quota is already exceeded, forcing the integration to stretch intervals. As a result, energy data updates only every 2-3 hours instead of 30 minutes.
Worse, the total and individual circuit sensors update at different times within each batch (up to 15-minute gaps). This causes Home Assistant's Energy Dashboard to display negative "untracked" consumption — a calculation impossibility that renders the data useless.
The Solution That Existed
The previous Eco Compteur (412000) had a local API (
http://<ip>/inst.jsonand/data.json) allowing real-time, synchronized polling without rate limits. Why was this removed?Request
Could you consider a hybrid approach?
This device costs €150+ yet cannot properly integrate with Home Assistant, while the older, cheaper model could. The Home+ app is not a substitute for advanced energy monitoring.
Thank you for considering this improvement.
The only way I managed to make Netatmo API local is by using Homekit integration on Home Assistant + matterbridge to expose entities via Matter protocol to compatible assistant (for instance Amazon Echo).
-> https://www.hacf.fr/integration-homekit/
-> https://github.com/t0bst4r/matterbridge-home-assistant
All my Light switches are BTicino Living Now same as Viorel above. I have spent a lot of $ on what is otherwise an awesome product. I do not have any of the devices that would "need" an API for any extended services, these are light switches. Why??
Seems like theres no reaction from the manufacturer. And it was out this week. Glad I dont have thermostat otherwise I would be in trouble. But time to change out the netatmo gear. Any recommendations for wind and rain sensors?
Yep, it's like clockwork, every winter again... Snow outside, temperatures below zero. And I come home to a cold house with no option to change from 'away' to 'schedule'.
My manual override time with the + and - buttons is set to 1 hour, so this means I have to walk to the thermostat and change the temperature every hour of a freezing cold day just to have heating. This is unacceptable.
Netatmo is not interested at all in their clients. The data they collect seems is what their product is about, not the product itself. The only thing we can do is to write as many reviews as we can to inform people not to go with Netatmo and hope this will hurt sales. But it feels like David VS Goliath here. They don't listen, they don't response, they just don't care...
Hello @Viorel, @delelaber,
Your 429 errors problem is linked to HA Cloud. I invite you to check my post here : https://helpcenter.netatmo.com/hc/en-us/community/posts/29846852785298-Inconsistent-Rate-Limits-for-Netatmo-Home-Control-API
@dries, you still have the possibility to get out from the away mode by using the native Home + Control app. But it's true that in case of a cloud issue on our side, you will get stuck in the mode
Have a good day,
Leslie - Community Manager
@Leslie, of course I'm talking about being stuck and not being able to control my own heating because of a problem on your servers. That's the whole point of this thread, the fact that basic operations are depended on your servers. That's exactly why this needs to be local and this thread exists.
Of course I am aware I can use your home + app without a problem,... when there is no problem...
Vous devez vous connecter pour laisser un commentaire.