um, were gonna need detailed instructions for dummies on this one… 
That won’t fix anything. The issue is with SNI. Either SmarThings fixes it, or you proxy the entire netatmo api.
That would just break the netatmo app.
Right it’s a cloud to cloud interconnection. Unless rewriting an entire app.
For now I use a python script which push netatmo values to a smart app which update virtual devices…
That’s what I started working on, but with ruby instead.
@Dianoga can you make the netatmo code available in the shared code repository?
Has there been any time frame announced for a fix?
I guess this whole Netatmo situation also means that developing a device handler for their Thermostat is out of the question then?
@Dianoga any chances you could share the DH code so I could at least try to write my own for the thermostat in any event?
Thanks!
I emailed again the Netatmo support pushing for an answer. It’s been over 6 weeks since i first reported the problem and nothing happened on their side (yet). That’s not a good selling point for future purchases.
I received a reply from Netatmo’s support, and they pretty much deny any problem on their side not assuming any responsability either. Here’s the actual reply i received (in french): "Bonjour,
Si le problème persiste actuellement, cela provient probablement de Smartthing car nous ne rencontrons actuellement aucune panne sur nos serveurs.
Merci pour votre compréhension."
The issue is not on netatmo side. It’s on ST side as they cannot support SNI on their java backend which seems to be a little bit outdated. If tomorrow logitech or other API providers switches to SNI, ST integration will fail as well.
I understand the issue could be complicated especially if they need to update a big part of their infrastructure.
Thanks for the explanation, but who changed what, is it ST or Netatmo that changed their implementation?
Netatmo changed their API service to require calls go over https.
Ok. But do you have any idea when a fix is coming? Lots of API’s require https.
That’s true, but most APIs aren’t exposed in quite the same way as Netatmo chose. Their API is available at api.netatmo.net. That is an alias for front.netatmo.net (which has 3 IPs; presumably for load balancing). The default ssl certificate returned for those machines is for netatmo.com and *.netatmo.com. If their API was accessible via api.netatmo.com, it would work fine.
api.netatmo.net should work with any system that support SNI (which allows multiple ssl domains on a single IP). Unfortunately, our platform doesn’t currently support that and upgrading is a major task.
No I don’t. I’m still working on it, but I don’t know when it will be fixed.
Posted a comment in their Dev Forum on the thread announcing the change to HTTPS with the details @Dianoga posted above and at least I got a “we are working on it” response
http://forum.netatmo.com/viewtopic.php?f=5&t=4593&p=19494#p19494
Hello,
We work on it, I hope we will find a good solution with Smarthings soon.
Thomas Rosenblatt, Netatmo Team.
@Dianoga
Ask and ye shall receive…Looks like they’ve set up the .com now too
For the record we have open api.netatmo.com, I hope Smartthings will replace api.netatmo.net very soon.
Do not hesitate to ask them
Somewhere in the vines, I heard something about the community contributing awareness with Netatmo + ST.
Just wanted to say, thanks guys!
Awesome move from Netatmo. @Dianoga looks like an easy fix ! Can’t wait ! But guys don’t forget to plan SNI support for upcoming release as it will be used by more and more third party cloud API.
I heard rumors of getting the rain gauge for my birthday, so this working would be sweeeeet!
We just pushed out the update that takes advantage of the changes Netatmo made for us. Give it a try and let us know if it’s working.
Note: You may need to remove the SmartApp and reinstall it.
It Works Again!!! Thanks @Dianoga. I had to ‘reinitialize’ it by going through the Netatmo Connect menu, but it started working immediately afterwards