Just got my Netatmo weather station today. Disappointed that it’s not working with ST.
Netatmo changed the way they require you to access their API basically without telling a single soul. Pester Netatmo support to have better API documentation and communication about their API changes.
STs is not at fault here.
2 Likes
@Dianoga I heard you recently looked at this. Are others looking at it now?
Is a fix for Netatmo coming anytime soon? It has not been working for quite a while? Is it like Wemo devices and really better to just not bring it into ST?
I looked at it today and the underlying issue isn’t what I thought. I’m working with the platform guys to see if it’s something we can fix on our end. I also sent a message to Netatmo asking if there is anything they can do to correct the problem.
6 Likes
It’s broken these days more than it works and I’m tired of stressing about it. Can you give us a realistic estimation of when this is going to be fixed after the last firmware update and update this ticket with progress. Thanks. 
1 Like
anything new on this? my entire grovestreams setup with useless without the ability to pull in the netatmo data.
Waiting, too, Brian. I still think they either need some public bug tracking issue for easy reference (but I wouldn’t want to do that in their shoes) or at least get a UserVoice or GetSatisfaction thing in for our voting and their centralized feedback to requests and issue reports. I can’t imagine being these guys wading through the forums trying to remember to update us. Netatmo was core to some stuff in my system so I’ve been going rogue for weeks.
i have been using it to track energy usage based on temp’s in several areas of my house. last month i cut my bill over 15 percent from the same time last year and it was hotter last month on average. so this is pretty critical to my dashboard and trend tracking.
1 Like
I contacted NetAtmo regarding this. Here is their answer:
Hi,
We don’t work on any intergration facilities, we distribute our API for free : http://dev.netatmo.com
so any one can create an interface to intergrate our products to their solutions.
So you guessed correct, you will have to contact SmartThings
Meanwhile I have transferd your mail to our dev departmant.If there is anything we can do, we will let you know.
thanks a lot for your understanding and patience.
Cordialement/Sincerely,
Prashanth
Netatmo Customer Service
And this is the last answer I received from SmartThings support on June 11th:
Hi Pierre,
Thanks for following up. The Harmony integration is undergoing beta testing now with the new integration. From my understanding it should be more reliable and secure than the previous LAN integration.
We are currently looking to the cause of Netatmo - it appears to be a server connectivity issue and we are working to determine if the cause is on our end or theirs. I am poking the engineers and will let you know as soon as I have an update.
I sincerely appreciate the patience.
Regards,
Aaron
Guess they’re playing ping pong with who’s at fault…
1 Like
Arf It sucks… I just bought the ST Hub to replace my domoticz setup and use my netatmo properly… Hope this will fixed soon. If the STApp is public with source code, I should be easily fixable.
Guys, why it takes you so long ? On my domoticz setup I currently use a python script using their API which broke when then pass to full SSL. I just had to change URI to use https instead of http. Their CA is trusted and well know so it should work out of the box…
At least, could you point us to a “community” version of NetAtmo Connect which should be fixable in a jiffy.
Thanks…
So, I actually built the Netatmo integration while I was part of the community. I’m now an employee of SmartThings and just as saddened at the lack of functioning integration. And I’m working on fixing it. Unfortunately, it isn’t as simple as switching to https…
The Netatmo API relies on SNI for their API (SNI allows serving multiple https domains on the same IP). The SmartThings platform doesn’t currently play well with SNI. Upgrading things to correct that is a significant undertaking. I’ve also contacted Netatmo to see if they can serve their API on a dedicated API (which would avoid the issue). The response I got from them was that they plan to do so eventually, but not right away.
tl;dr: I’m working on it, but it’s much harder than I would like.
2 Likes
Thanks for the explanation, I’m familiar with SNI as well so I understand the situation, especially when your dealing with Java crap as client. I guess I will have to bounce from my python script for now.
I bought smartthings to lower my time spend to dev things and concentrate on scenarii but looks like the opposite 
anyway I hope it would be fun.
If you need a beta tester I’m in 
1 Like
thanks for the update Brian.
I miss my GroveSteams dash greatly!
Looks that SNI is supported in HTTPClient since 4.3.2 ( https://issues.apache.org/jira/browse/HTTPCLIENT-1119 ) but it requires a JDK 7.
I made a reduction and got the error:
javax.net.ssl.SSLException: hostname in certificate didn't match: != <*.netatmo.com> OR <*.netatmo.com> OR
when trying to get the token from netatmo.
SNI allow then to do this:
openssl s_client -connect api.netatmo.net:443 2>&1 -servername api.netatmo.com | openssl x509 -text | grep -A1 Alter
X509v3 Subject Alternative Name:
DNS:*.netatmo.com, DNS:netatmo.com
openssl s_client -connect api.netatmo.net:443 2>&1 -servername api.netatmo.net | openssl x509 -text | grep -A1 Alter
X509v3 Subject Alternative Name:
DNS:api.netatmo.net, DNS:netatmo.net
By the way both .net and .com are registered to NetAtmo. But only .net is resolved (why…)
But this as to be defined before the SSL handshake if not while requesting the .net suffix it will reply with the .com one which will fail…
So yes two solutions… Either you update your platform in order to make SNI requests pass (recommanded as more and more cloud provider will use it), either NetAtmo provide a non SNI url (which I doubt) or enabled their .com domain. In the mean time, customers are screwed 
A work around should be to host it’s own python/node API server as a relay to NetAtmo API (or maybe a local proxy could do the trick as well hub -> LAN -> http -> proxy -> https -> Internet -> netatmo).
Please keep us posted (estimated ETA should be great).
Thanks
Any update? You should really consider to remove this device from supported devices for now if there is no solution in the following days / week.
2 Likes
this is sad, i got my grove streams bill and I didnt even log in last month because I couldnt get this data.
@Dianoga Could you give out any sort of timeframe for this to start working again?
I was able to wire up a basic ruby api client for netatmo in less than an hour. I may just create a device handler that hits my server’s rest endpoints, but jeez does that seem like overkill or what?
I was wondering if a simple nginx acting as a proxy http -> https will do the trick. And as I manage my own router I can redirect netatmo domain requests to a local ip. But hell yeah it’s overkill for a device which is still in the working device list.