New API

[slajgaj]

Hello! I working with Netatmo plugin (Micasaverde 3) From junius not working. The Natatmo "said" , have a new API structure. Can you planning make your plugin ?

[akbooer]

You need to use the latest version, which was updated at the start of 2023, to use the latest API.

If you still have an error, then I need to see more information about it.

[slajgaj]

I replaced the 2 jsons and now have error

[akbooer]

Some of the other files have changed. In particular, the Lua file. Update them all and restart to try again.

I see you are running UI5. This is very old, and it’s possible that some of the Lua modules to do with secure HTTP are not new enough versions. I don’t have a Vera with UI5 any more myself.

I would suggest you also try asking at the Smarthome forum https://smarthome.community/ if updating the files doesn’t work.

[slajgaj]

Ok thank you Than i trying the Vera upgrade from UI5 to

[Tim88-8]

Hi. I hope you are still supporting this for Vera. My Netatmo had been running fine until recent and now I am currently having a problem where Vera is reporting 'Not Authorized' and when I click the Authorize button and sign in using my Netatmo credentials I get the following error: 'Failed to retrieve access token using authorization code'. Hopefully are still supporting this and can lend a hand.
Regards, Tim

[akbooer]

I don't run Vera any more, but use this daily under openLuup. Have just fired up a test version and everything worked as expected. I haven't been informed of any recent changes from Netatmo. Has something on the Vera side changed recently?

[Tim88-8]

Thank you for the reply. I don’t believe anything has changed on the Vera side. I know I haven’t make any changes or added anything additional in quite some time. I even tried restoring a backup of the controller and when it finished I got the same message and errors so I just restored back to the current. I wonder if it’s something on Vera’s backend, I think they recently implemented new relay servers not sure if something there may be causing an issue.

Regards, Tim

On Wed, Jul 3, 2024 at 4:36 AM AK @.***> wrote:

I don't run Vera any more, but use this daily under openLuup. Have just fired up a test version and everything worked as expected. I haven't been informed of any recent changes from Netatmo. Has something on the Vera side changed recently?

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2205423060, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PRY5F2V3GJHKUDV6STZKOZXJAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBVGQZDGMBWGA . You are receiving this because you commented.Message ID: @.***>

[akbooer]

The Vera backend shouldn't be involved – it's simply a direct HTTPS call to the Netatmo website. I'm assuming that Vera hasn't made any firmware changes recently. It may just be a security level issue with an old library. What Vera, what firmware?

What output is produced when you run this code in Lua Test:

local socket  = require "socket"
local https     = require "ssl.https"

print(socket._VERSION)
print(https._VERSION)

For further support on this, it might be good if we switch the conversation to smarthome.community since there may be others who can contrubte.

[Tim88-8]

It’s a Vera Plus running firmware version 1.7.5186(7.31) I ran the commands and checked the log but the print commands don’t seem to be returning anything.

On Wed, Jul 3, 2024 at 7:49 AM AK @.***> wrote:

The Vera backend shouldn't be involved – it's simply a direct HTTPS call to the Netatmo website. I'm assuming that Vera hasn't made any firmware changes recently. It's may just be a security level issue with an old library. What Vera, what firmware?

What output is produced when you run this code in Lua Test:

local socket = require "socket" local https = require "ssl.https"

print(socket._VERSION) print(https._VERSION)

For further support on this, it might be good if we switch the conversation to smarthome.community since there may be others who can contrubte.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2205892604, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PUPNODUWTYMSEUDXITZKPQOJAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBVHA4TENRQGQ . You are receiving this because you commented.Message ID: @.***>

[Tim88-8]

I got it. Had to use luup.log instead of print Socket version = LuaSocket 3.0-rc1 HTTPS version = 0.4

On Wed, Jul 3, 2024 at 7:49 AM AK @.***> wrote:

The Vera backend shouldn't be involved – it's simply a direct HTTPS call to the Netatmo website. I'm assuming that Vera hasn't made any firmware changes recently. It's may just be a security level issue with an old library. What Vera, what firmware?

What output is produced when you run this code in Lua Test:

local socket = require "socket" local https = require "ssl.https"

print(socket._VERSION) print(https._VERSION)

For further support on this, it might be good if we switch the conversation to smarthome.community since there may be others who can contrubte.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2205892604, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PUPNODUWTYMSEUDXITZKPQOJAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBVHA4TENRQGQ . You are receiving this because you commented.Message ID: @.***>

[akbooer]

My bad.... I think the Vera doesn't support print (whereas openLuup does!)

I get

Socket version = LuaSocket 3.0-rc1
HTTPS version = 0.9

I don't know if that's a smoking gun, or how long Vera has used 0.4.

I will try and investigate further...

[Tim88-8]

I guess it’s possible Netatmo may not support the older version anymore. Maybe it’s time to look for a different solution. The Ezlo controller is a huge disappointment so far. I bought one and it just sits doing nothing because that’s about all it can do.

On Wed, Jul 3, 2024 at 12:38 PM AK @.***> wrote:

My bad.... I think the Vera doesn't support print (whereas openLuup does!)

I get

Socket version = LuaSocket 3.0-rc1 HTTPS version = 0.9

I don't know if that's a smoking gun, or how long Vera has used 0.4.

I will try and investigate further...

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2206768440, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PXQLLFLOJJWUN2JD2LZKQSKBAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBWG43DQNBUGA . You are receiving this because you commented.Message ID: @.***>

[SinSharks]

Sorry for the likely dumb question.

I was watching the web traffic when trying to "Authorize" or in this case re-"Authorize" my plugin and noticed the website does send an access token/refresh token it just doesn't appear to be updating in the "RefreshToken" field in Vera for whatever reason.

I tried to input in the field manually and that unfortunately didn't appear to take. I then restarted LUUP and am now getting this error on the netatmo site: "Array is not allowed scope for oepnLuup."

That is likely from me messing with RefreshToken Variable and trying to put the new token on top of the previous using this format: "Nothereallytoken|refreshtokennotreal"

akbooer -- Would it be possible to just input the token manually somewhere?

Thank you for akbooer for time and effort you put into making this wonderful plugin.

[akbooer]

@SinSharks

The RefreshToken variable is only for the refresh token, and it's only there so that the plugin survives Luup restarts without needing to be re-authorized (so long as the token has not expired.) The access token is never stored. Just entering a valid refresh token should work on restart.

Has this problem just started? You're on openLuup, so this might be a clue. Why were you looking at the web traffic? Did you originally get an authourize failure?

[SinSharks]

Hello akbooer,

I find myself in a situation similar to Tim88-8, using a Vera Plus with firmware version 1.7.5186(7.31). I started by examining web traffic to pinpoint where the issue with the original error 'Failed to retrieve access token using authorization code' might be. I wanted to verify whether the token was not being retrieved at all or if it was retrieved successfully but Netatmo made slight changes causing Vera to not recognize the token. (Netatmo recently underwent significant GUI changes for both their app and web interface, leading me to consider they might have inadvertently altered something on the API side during these updates, that is not yet listed in their documentation.)

[akbooer]

Can you both confirm that:

1. you are using the latest version 2023.01.08
2. you have deleted the old variables ClientID and ClientSecret

[Tim88-8]

I checked the variables and it’s the correct version and I didn’t see those variables listed. I remember having to update the version some time last year to authorize.

On Thu, Jul 4, 2024 at 7:39 AM AK @.***> wrote:

Can you both confirm that:

1. you are using the latest version 2023.01.08
2. you have deleted the old variables ClientID and ClientSecret

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2208754564, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PQTJYHSEZCUWCNZ4T3ZKUX5ZAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYG42TINJWGQ . You are receiving this because you commented.Message ID: @.***>

[Tim88-8]

Do I need to delete my app from the dev.netatmo.com site? I know I needed to create that in the older version of the plugin. The ClientID and ClientSecret still exist under my apps.

On Thu, Jul 4, 2024 at 7:39 AM AK @.***> wrote:

Can you both confirm that:

1. you are using the latest version 2023.01.08
2. you have deleted the old variables ClientID and ClientSecret

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2208754564, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PQTJYHSEZCUWCNZ4T3ZKUX5ZAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYG42TINJWGQ . You are receiving this because you commented.Message ID: @.***>

[Tim88-8]

These are the only entries I see in the vera log

50 07/04/24 12:35:52.497 luup_log:75: Netatmo: HTTPS error = nil <0x71da1520> 50 07/04/24 12:35:52.497 luup_log:75: Error: Failed to retrieve access token using authorization code <0x71da1520>

On Thu, Jul 4, 2024 at 12:27 PM Tim @.***> wrote:

Do I need to delete my app from the dev.netatmo.com site? I know I needed to create that in the older version of the plugin. The ClientID and ClientSecret still exist under my apps.

On Thu, Jul 4, 2024 at 7:39 AM AK @.***> wrote:

Can you both confirm that:

1. you are using the latest version 2023.01.08
2. you have deleted the old variables ClientID and ClientSecret

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2208754564, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PQTJYHSEZCUWCNZ4T3ZKUX5ZAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYG42TINJWGQ . You are receiving this because you commented.Message ID: @.***>

[akbooer]

@Tim88-8 The plugin is designed to use your own ClientID and ClientSecret if they're specified in the device variables, and the app is enabled in your account on the DEV website. The fact that it's been working (I presume) probably indicates that it's something else which has recently changed. What's bothering me is that I'm having no problems right now (the app is refreshing every 2 hours.)

I may need to extend the diagnostics to discover more. Sorry about this!

[akbooer]

OK, I have set up a new openLuup installation, installed the Netatmo plugin, and now it times out when trying to authorize. It's doesn't actually get to asking for login credentials, which seems wrong.

So something with their site HAS changed. I'm signed up to developer emails, but haven't heard anything about an API change. So it's not anything you're doing wrong.

[akbooer]

Further to this, I've seen this comment on the HA website

"I just received an email from Netatmo that they will update their policy regarding API keys and Access/Refresh Tokens as per May 29, 2024. "

It may be the issue. Why I never got this message, I don't know, but I will dig into this further.

[Tim88-8]

Thanks. I kind of figured something may have changed on their end. Like you said it’s been working. Be interested to see what you find.

On Thu, Jul 4, 2024 at 12:55 PM AK @.***> wrote:

OK, I have set up a new openLuup installation, installed the Netatmo plugin, and now it times out when trying to authorize.

So something with their site HAS changed. I'm signed up to developer emails, but haven't heard anything about an API change. So it's not anything you're doing wrong.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2209348385, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PXALWQ4IRRDIEHRGLDZKV5AJAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGM2DQMZYGU . You are receiving this because you were mentioned.Message ID: @.***>

[Tim88-8]

I do really appreciate your quick response and spending the time to look into this.

On Thu, Jul 4, 2024 at 1:02 PM AK @.***> wrote:

Further to this, I've seen this comment on the HA website https://github.com/home-assistant/core/issues/111938

"I just received an email from Netatmo that they will update their policy regarding API keys and Access/Refresh Tokens as per May 29, 2024. "

It may be the issue. Why I never got this message, I don't know, but I will dig into this further.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2209355639, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PV6VXIPMBLC2FFG5KTZKV535AVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGM2TKNRTHE . You are receiving this because you were mentioned.Message ID: @.***>

[Tim88-8]

When you find out what's going on and come up with a solution, I'd be more than happy to test it on my Vera controller.

On Thu, Jul 4, 2024 at 1:19 PM Tim @.***> wrote:

I do really appreciate your quick response and spending the time to look into this.

On Thu, Jul 4, 2024 at 1:02 PM AK @.***> wrote:

Further to this, I've seen this comment on the HA website https://github.com/home-assistant/core/issues/111938

"I just received an email from Netatmo that they will update their policy regarding API keys and Access/Refresh Tokens as per May 29, 2024. "

It may be the issue. Why I never got this message, I don't know, but I will dig into this further.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2209355639, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PV6VXIPMBLC2FFG5KTZKV535AVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGM2TKNRTHE . You are receiving this because you were mentioned.Message ID: @.***>

[SinSharks]

I do really appreciate your quick response and spending the time to look into this. … On Thu, Jul 4, 2024 at 1:02 PM AK @.> wrote: Further to this, I've seen this comment on the HA website <home-assistant/core#111938> "I just received an email from Netatmo that they will update their policy regarding API keys and Access/Refresh Tokens as per May 29, 2024. " It may be the issue. Why I never got this message, I don't know, but I will dig into this further. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PV6VXIPMBLC2FFG5KTZKV535AVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGM2TKNRTHE . You are receiving this because you were mentioned.Message ID: @.>

100% agree thank you so much for looking at this.

When you find out what's going on and come up with a solution, I'd be more than happy to test it on my Vera controller. … On Thu, Jul 4, 2024 at 1:19 PM Tim @.> wrote: I do really appreciate your quick response and spending the time to look into this. On Thu, Jul 4, 2024 at 1:02 PM AK @.> wrote: > Further to this, I've seen this comment on the HA website > <home-assistant/core#111938> > > "I just received an email from Netatmo that they will update their > policy regarding API keys and Access/Refresh Tokens as per May 29, 2024. " > > It may be the issue. Why I never got this message, I don't know, but I > will dig into this further. > > — > Reply to this email directly, view it on GitHub > <#3 (comment)>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/BJTX5PV6VXIPMBLC2FFG5KTZKV535AVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGM2TKNRTHE > . > You are receiving this because you were mentioned.Message ID: > @.***> >

I'd also be more than willing to attempt any debug/testing. (Sadly, I'm not a super skilled at programming but can certainly help test anything you would like on my Vera and send debug logs.)

[akbooer]

Just an update: All appears to be working on my production system (openLuup in a Docker environment) and in my development system (openLuup in an iMac.) I have dug around in a junk box and found an old Vera Edge which I'll agtempt to fire up and try it on there. Most odd.

[Tim88-8]

Sounds like it might be coming down to the SSL version.

On Fri, Jul 5, 2024 at 8:22 AM AK @.***> wrote:

Just an update: All appears to be working on my production system (openLuup in a Docker environment) and in my development system (openLuup in an iMac.) I have dug around in a junk box and found an old Vera Edge which I'll agtempt to fire up and try it on there. Most odd.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2210782254, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PSCVW6F4FEGXAIZW6TZK2FZHAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQG44DEMRVGQ . You are receiving this because you were mentioned.Message ID: @.***>

[akbooer]

...not so sure now. It didn't work on Vera, but now it's failing on both my production system and development system. It;s obviously them, not us, but I have no idea how to proceed.

[akbooer]

Aha! We are not the only ones... Netatmo Help Centre

[Tim88-8]

Interesting. It looks like it potentially started about a month ago.

On Fri, Jul 5, 2024 at 1:35 PM AK @.***> wrote:

Aha! We are not the only ones... Netatmo Help Centre https://helpcenter.netatmo.com/hc/en-us/community/posts/19320250276626-API-invalid-grant-at-random-intervals

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2211194924, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PXDZPD6B7CPM2UILRLZK3KMNAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGE4TIOJSGQ . You are receiving this because you were mentioned.Message ID: @.***>

[Tim88-8]

In reading the moderators responses it sounds like it may be related to that e-mail about the oauth2 changes.

On Fri, Jul 5, 2024 at 1:35 PM AK @.***> wrote:

Aha! We are not the only ones... Netatmo Help Centre https://helpcenter.netatmo.com/hc/en-us/community/posts/19320250276626-API-invalid-grant-at-random-intervals

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2211194924, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PXDZPD6B7CPM2UILRLZK3KMNAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGE4TIOJSGQ . You are receiving this because you were mentioned.Message ID: @.***>

[akbooer]

Yes, there seems to be an element of confusion here, I had tried reverting to a private ClientSecret and ClientID using your own app on the Netatmo site, as originally, but that hasn't worked either. I'm really annoyed my standard installation has just started to fail!

[akbooer]

Appreciate the offers for help with testing. At the moment, I'm working in the openLuup environment. So far, I find that the authentication viw the Netatmo website works OK and returns access and refresh tokens. However, using those tokens results in an "invalid grant" response. This looks like the tokens have expired, but they're the new ones, so, again, I'm at a bit of a loss.

[Tim88-8]

Sounds like they broke something with this new requirement.

On Sat, Jul 6, 2024 at 11:19 AM AK @.***> wrote:

Appreciate the offers for help with testing. At the moment, I'm working in the openLuup environment. So far, I find that the authentication viw the Netatmo website works OK and returns access and refresh tokens. However, using those tokens results in an "invalid grant" response. This looks like the tokens have expired, but they're the new ones, so, again, I'm at a bit of a loss.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2211795690, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PXIZJODEFUJVJDL7PDZLADHPAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRG44TKNRZGA . You are receiving this because you were mentioned.Message ID: @.***>

[Tim88-8]

It’s not related to this issue but I’ve been contemplating moving away from the Vera platform for several reasons one being it seems to just not manage battery life well for zigbee devices. Would you have any recommendations on a good zwave/zigbee hub and what you might use as a front end? Regards, Tim

On Sat, Jul 6, 2024 at 11:19 AM AK @.***> wrote:

Appreciate the offers for help with testing. At the moment, I'm working in the openLuup environment. So far, I find that the authentication viw the Netatmo website works OK and returns access and refresh tokens. However, using those tokens results in an "invalid grant" response. This looks like the tokens have expired, but they're the new ones, so, again, I'm at a bit of a loss.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2211795690, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PXIZJODEFUJVJDL7PDZLADHPAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRG44TKNRZGA . You are receiving this because you were mentioned.Message ID: @.***>

[akbooer]

Again, I would refer you to smarthome.community for opinions other than my own (and mine too!)

[Tim88-8]

I tried creating an account the other day but I never got a verification code so I sent an e-mail to support as it suggests but I haven’t gotten a response.

On Sun, Jul 7, 2024 at 11:30 AM AK @.***> wrote:

Again, I would refer you to smarthome.community for opinions other than my own (and mine too!)

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2212486028, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PRRSFT7OBPO4AJFJQ3ZLFNI3AVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJSGQ4DMMBSHA . You are receiving this because you were mentioned.Message ID: @.***>

[akbooer]

Oh, that’s not good. I’ll try to notify them myself.

[smkess]

Looks like this was resolved??? I was just able to authorize via my vera for the first time in a couple of months. Didn't change anything in my config.

[Tim88-8]

I just tried it said access granted and to restart luup engine and I did and I still get the not authorized at the top and username or password net set.

On Fri, Jul 19, 2024 at 3:18 PM smkess @.***> wrote:

Looks like this was resolved??? I was just able to authorize via my vera for the first time in a couple of months. Didn't change anything in my config.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2239967372, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PXJR7QTRDEQ5Y4OMI3ZNFRABAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZZHE3DOMZXGI . You are receiving this because you were mentioned.Message ID: @.***>

[SinSharks]

I'm not having any luck either I get this message: but when I go back and check it still hasn't received the refresh token (with and without rebooting the luup engine.) and it still says it can't connect: When I look at the Device Tree & Device List page I see this error: [string "--module ("L_Netatmo", package.seeall) --..."]:572: bad argument #1 to 'pairs' (table expected, got nil) and the Diagnostics page just displays this: NETATMO CONFIGURATION PAGE at Sat Jul 20 04:20:16 2024

I really wish they would just roll this changes back... :(

[smkess]

Mine still working…..yesterday, after I got the “access granted…..restart LUUP engine” I didn’t just restart LUUP, I rebooted the Vera ( for quite a while now I’ve noticed that whenever I change anything like add or remove a device, etc. if I don’t reboot the Vera the changes don’t get applied properly). After the reboot, initially the netatmo data came in but it was the data from the last time it refreshed before the auth failure and then a couple of minutes later it refreshed by itself to the current data and it’s been bringing current data in as recently as about two minutes ago. Don’t know if it will last or start failing again at some point but it’s working for now. Not sure why based on what you all are saying.

[akbooer]

Sadly, mine not working either.

In the circumstances, there doesn't seem any point in trying to fiddle with the code.

I have no idea what is going on here.

[Tim88-8]

Ok some interesting notes here. I was able to get the weather station to authorize on my Vera controller. What's interesting is I tried logging on to http://dev.netatmo.com and it redirected me to http://home.netatmo.com so it seems that the dev account that I had created is no longer necessary as I can not access it any longer. After the redirect I went to the partner apps section under my account ( 'Settings\My Account\Partner Apps') and noticed there were several entries for 'OpenLuup' so what I did was remove the oldest entry and it removed all the entries. There are also 5 entries named Tim's Netatmo Weather Station all with the same date. I did not remove these for fear of breaking something as I'm not sure what these are. After removing the entries I went back to the Netatmo app in my Vera controller and clicked authorize again and this time the device came back on line and is responding again.

On Sat, Jul 20, 2024 at 3:49 PM AK @.***> wrote:

Sadly, mine not working either.

In the circumstances, there doesn't seem any point in trying to fiddle with the code.

I have no idea what is going on here.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2241276905, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PSNAAL3MUDDL647SK3ZNK5MVAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGI3TMOJQGU . You are receiving this because you were mentioned.Message ID: @.***>

[SinSharks]

Ok some interesting notes here. I was able to get the weather station to authorize on my Vera controller. What's interesting is I tried logging on to http://dev.netatmo.com and it redirected me to http://home.netatmo.com so it seems that the dev account that I had created is no longer necessary as I can not access it any longer. After the redirect I went to the partner apps section under my account ( 'Settings\My Account\Partner Apps') and noticed there were several entries for 'OpenLuup' so what I did was remove the oldest entry and it removed all the entries. There are also 5 entries named Tim's Netatmo Weather Station all with the same date. I did not remove these for fear of breaking something as I'm not sure what these are. After removing the entries I went back to the Netatmo app in my Vera controller and clicked authorize again and this time the device came back on line and is responding again. … On Sat, Jul 20, 2024 at 3:49 PM AK @.> wrote: Sadly, mine not working either. In the circumstances, there doesn't seem any point in trying to fiddle with the code. I have no idea what is going on here. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PSNAAL3MUDDL647SK3ZNK5MVAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGI3TMOJQGU . You are receiving this because you were mentioned.Message ID: @.>

More updates:

I tried your method/suggestions and it appears to have worked for moment. Yay!

Some things that differed in my case:

1. I did not have something called "Sharks" weather station in my partner apps just 5 openluup entries.
2. All of my openluup entries were from 2024/07/20.

-break When I deleted one of the openluup entries they all got deleted same as yours.

Other items worth noting: Device Tree & Device List - Display nothing just a white screen. Diagnostics = Displays properly displays the same as it had before the whole token issue.

This worked about 20 mins ago I'll give another update if it holds for 24-48 hours.

[Tim88-8]

As today mine is still working. I’m thinking that the entries titled ‘Tim's Netatmo Weather Station’ are possibly from when I created the dev account so I could get the tokens to authorize when I set the Netatmo up on my Vera years ago as they were dated 2020. I deleted them this morning so I’ll see what breaks, hopefully they were not needed.

Regards, Tim

On Wed, Jul 24, 2024 at 1:07 AM SinSharks @.***> wrote:

Ok some interesting notes here. I was able to get the weather station to authorize on my Vera controller. What's interesting is I tried logging on to http://dev.netatmo.com and it redirected me to http://home.netatmo.com so it seems that the dev account that I had created is no longer necessary as I can not access it any longer. After the redirect I went to the partner apps section under my account ( 'Settings\My Account\Partner Apps') and noticed there were several entries for 'OpenLuup' so what I did was remove the oldest entry and it removed all the entries. There are also 5 entries named Tim's Netatmo Weather Station all with the same date. I did not remove these for fear of breaking something as I'm not sure what these are. After removing the entries I went back to the Netatmo app in my Vera controller and clicked authorize again and this time the device came back on line and is responding again. … <#m8195025257524341965> On Sat, Jul 20, 2024 at 3:49 PM AK @.> wrote: Sadly, mine not working either. In the circumstances, there doesn't seem any point in trying to fiddle with the code. I have no idea what is going on here. — Reply to this email directly, view it on GitHub <#3 (comment) https://github.com/akbooer/Netatmo/issues/3#issuecomment-2241276905>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PSNAAL3MUDDL647SK3ZNK5MVAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGI3TMOJQGU https://github.com/notifications/unsubscribe-auth/BJTX5PSNAAL3MUDDL647SK3ZNK5MVAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGI3TMOJQGU . You are receiving this because you were mentioned.Message ID: @.>

More updates:

I tried your method/suggestions and it appears to have worked for moment. Yay!

Some things that differed in my case:

1. I did not have something called "Sharks" weather station in my partner apps just 5 openluup entries.
2. All of my openluup entries were from 2024/07/20 when I deleted one they all got deleted.

Other items worth noting: Device Tree & Device List - Display nothing just a white screen. Diagnostics = Displays properly displays the same as it had before the whole token issue.

This worked about 20 mins ago I'll give another update if it holds for 24-48 hours.

— Reply to this email directly, view it on GitHub https://github.com/akbooer/Netatmo/issues/3#issuecomment-2246903520, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJTX5PV5L5F6YD3QF7OMRA3ZN4Y7ZAVCNFSM6AAAAABKIPPIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBWHEYDGNJSGA . You are receiving this because you were mentioned.Message ID: @.***>

[smkess]

Same here........Still up and running as of 5mins ago. Netatmo must have changed something or rolled the changes back so the plugin started working again with a clean environment. I didn't change anything or reinstall anything. The only thing I did was try to reauthorize it and reboot the vera after.

[SinSharks]

Giving my update, system still seems to be working after 2 days, my scenes/triggers are all functioning as desired again. I'm not sure what Netatmo did on the back-end but whatever seems to be fixed the issue.

[akbooer]

@SinSharks

So, just to confirm, you have no private authorization apps, and you’re using the default one with no specified ClientID and ClientSecret.