Include a Local API

hallerjo97

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

18

Comments

20 comments

  • Comment author
    benny.dormaels

    totally agree

    3
  • Comment author
    hallerjo97

    I guess @netatmo does not care

    3
  • Comment author
    gergelyxmolnar

    Is Legrand CX3 not compatible with https://developer.legrand.com/Documentation/client-download/ ?

    Wondering if it uses OpenWebNet in the background, just not documented. Local API of some form would be great.

    -1
  • Comment author
    hallerjo97

    Nope, does not work

    0
  • Comment author
    adrien

    Would it be possible to have Netatmo’s view on this ?

    0
  • Comment author
    Leslie Community moderator

    Hello,

    The only local API we have is OpenWebNet to manage MyHOME devices (https://developer.legrand.com/local-interoperability/#PDF%20documentation). It's not planned for now to provide local APIs for other Legrand - Netatmo - Bticino devices

    Have a good day,

    Leslie - Community Manager

    -8
  • Comment author
    dries

    This is actually unacceptable.
    The Netatmo Thermostat has become my worst 'smart' purchase in a very connected house in years. 

    Apparently everything my thermostat does, has to go trough Netatmo's servers. 
    Last year there was a Netatmo server issue, in the middle of the winter. When waking up my house was Icecold and the thermostat didn't change from 'night temperature' to 'day temperature' because Netatmo's server was down. 
    Since I had the manual override with the button's set to 1 hour. I had to change the temperature every hour that day because there was a server down at Netatmo's end. 

    At this very moment. There is a problem with my internet provider and I'm having one week without internet. Turns out, I cannot control it with the app, although my local wifi network is up and I can locally control all my other devices, plugs, lights, waterpomp, do anything. My thermostat becomes uncontrollable. Again, all my other smart products work without problems without internet. Because they are controlled locally and they don't need a cloud server somewhere out of my house to do basic stuff.

    It won't go to night mode, I'm unable to set it to 'out of house'. I cannot change my schemes in the app, I cannot turn the 'override window' to more then it is now, because the APP NEEDS the relais to connect with Netatmo to change something locally. When I go to bed, I can manually use the +/- buttons to turn down the heating, but after 1 hour (my override time) it just goes back to heating (the last program before the internet shut down) the entire night.

    At least, give homekit something more then just turn the thermostat to a given temperature or turn it completely off. Out of home would be a great start. But even that is too much apearently after all these years. I guess the data of the users is just too important for Netatmo.

    This is unacceptable.
    At a side, I'm very, very worried about my privacy as well. Since Netatmo knows when I go to bed, when I'm not at home. When I'm up late. When I sleep in, when I'm cold and when I'm warm.

    I'm having a very bad week, and Netatmo made it worse.


    3
  • Comment author
    hallerjo97

    Hello Leslie and Netatmo Team,

    Thank you for taking the time to respond. I understand that maintaining various APIs can be resource-intensive and that security is a priority. However, as a dedicated user of Netatmo products, I must reiterate how important a local API is to the community, particularly for essential devices like thermostats.

    A cloud-dependent approach poses several issues, especially in critical situations. For example, during server outages or connectivity issues, users have reported being unable to adjust their thermostats, leading to uncomfortable and sometimes unsafe situations. It’s clear that having a local control option would significantly enhance both reliability and user satisfaction, allowing us to operate devices even when external factors disrupt connectivity.

    Furthermore, there are serious privacy concerns. Many of us are cautious about sharing usage data over the internet for security reasons. A local API would alleviate such concerns by keeping device control within our local network.

    I urge you to reconsider the development of a local API, particularly for core devices like the thermostat. It would bring a great deal of trust and flexibility to Netatmo's offerings, ultimately benefiting both the users and the brand's reputation.

    Thank you for considering this feedback, and I hope to see more solutions that prioritize user control and data privacy.

    Best regards,
    Hallerjo97

    1
  • Comment author
    bjorn

    I have several Legrand dimmers and would like to manage them using a local API.  I don't see any reason why an internet connection should be required to manage local devices in my home.  Just another vote for adding such an API.

    0
  • Comment author
    hallerjo97

    I think we need to make this public so they’ll respond to the customers who bring in their revenue.

    1
  • Comment author
    enrico80bo
    • Edited

    It is outrageous that in 2024 there are still smart home devices that do not support use within the LAN. I bought the Netatmo Weather Station and Security years ago, when I had no experience with home automation and didn’t realize it operated exclusively in the cloud. Today, I am progressively phasing out all Netatmo devices, replacing them with more compatible products, and I am discouraging the purchase of Netatmo devices on every available situation and platform (friends, forums, Home Assistant community, etc.).

    It's a shame because these are high-quality products, and it would take very little to make them compatible with the needs of the community. Even more critical devices, such as Nuki smart locks, offer this functionality.

    1
  • Comment author
    hallerjo97
    • Edited

    @netatmo we are more than just one customer complaining..

    1
  • Comment author
    lars

    I am so full of:

    code=500, reason=Internal Server Error, body=b'{"error":{"code":500,"message":"Internal Server Error"}}'

    Please give access to local API. 
    You will loose a lot of customers and get few new one as it is now.

    1
  • Comment author
    dries
    • Edited

    I've started e-mail techblogs who are covering Netatmo in their smart thermostat articles. Hope they will pick it up.

    This is something buyers should know before they make the purchase and not in the winter when there is an internetproblem or after their whereabouts leaked on the dark web.

    1
  • Comment author
    troels

    I'd second this feature request. I would make it much easier to build smart home automation if there for example was a local MQTT client or server I could either subscribe to or configure to publish. There is tons of embedded C examples for how to do it on low-end micro controllers such as STM32 or ESP32.

    1
  • Comment author
    nicolas

    I fully agree with this request, it would be more secure, eco friendly, and, most importantly, solve the problem of authentication not working one day a week (400 invalid grant).

    1
  • Comment author
    nick2k3

    Completely agree, the basic functions should be available on local api, the cloud based one is so unresponsive that it is barely usable for any home automation.

    I think Legrand should think a bit further than their economic interests: unless there is a strong commitment on keeping the cloud API in high availability  and responsiveness and for a very long time after product retirement, local API should be the norm.

     

     

    2
  • Comment author
    david.nordin

    I agree @Netatmo.. 

    Local API is the *only* way forward.
    I have your whole setup but I'm ready to throw it in the garbage bin.

    If you lose your fanbase your product is dead... come on

    1
  • Comment author
    embinet

    I also totally agree with this request for privacy and stability reasons but more important : for the carbon footprint !!!!!!!.

    Très sérieusement, il est inacceptable de la part de Legrand de ne pas avoir développé un accès local à la station météo. Je la consulte des dizaines de fois par jour; ce sont autant de data qui transitent sur les réseaux et qui consomment de l'énergie.

    Réagissez et modifiez les firmwares afin que l'on puisse accéder au produit netatmo en local quand cela en possible.

     

     

     

    1
  • Comment author
    dante.flodstrom

    My internet connection was physically severed last week. I was painfully introduced to my Netatmo products reliance on server connection; which is a bit of a bummer when your thermostat wont work in Sweden in January... I must admit I'm disappointed that none of your products work locally, the thermostat both considering the economic side of not being able to control heating; but it also makes me a bit worried when I'm relying on your smoke alarms for my personal safety! 

    I would have thought that local connection over LAN would be standard; more or less every other smart device I own is. Not everyone lives with stable internet connection. If that is a requirement for conventional use of your products, that should be clearly stated on the product packaging; something I can't see on the anemometer-packaging in front of me. 

    2

Please sign in to leave a comment.