Page 13 of 21

Re: Netatmo authentication changes Oct 2022

Posted: Monday 17 March 2025 6:02
by sailmich
Good morning,
I had this message
3) "Error: Netatmo: No access granted, check credentials.
I'm on latest beta. Disable Netatmo in hardware tab, reboot Domoticz wait a while and enable Netatmo. That helped me.
Cheers

Re: Netatmo authentication changes Oct 2022

Posted: Monday 17 March 2025 9:34
by leef22
Since yesterday, i have the same issue: " Error: Netatmo: Invalid/no data received...". Reauthentication does't work. :(

Re: Netatmo authentication changes Oct 2022

Posted: Monday 17 March 2025 10:58
by polo2292
This morning I have restarted my domoticz application and reauthentified Netatmo plugin.

It is functioning properly presently :-)

Version 2024.7 on TV Box X96 Mini

Re: Netatmo authentication changes Oct 2022

Posted: Monday 17 March 2025 12:56
by jpcasta
I installed the latest beta version, I updated the Raspbian, I restarted Domoticz and the Pi, I renewed the Netatmo connection but no improvement.
I am still getting the same error message "Error: Netatmo: Invalid/no data received..." :(

Re: Netatmo authentication changes Oct 2022

Posted: Monday 17 March 2025 18:51
by homeJLB
For everybody who has still trouble connecting with the latest beta. Disable your hardware for a few hours and then re-authenticate

Kind regards

Re: Netatmo authentication changes Oct 2022

Posted: Monday 17 March 2025 19:03
by Rob67ert
Look like it's all working again in the latest Version: 2025.1 (build 16579

Re: Netatmo authentication changes Oct 2022

Posted: Tuesday 18 March 2025 6:23
by chrominator
Compiled from last source including PR from JurgenLB Return message when data is invalid. (#6276).

Error message is

Code: Select all

2025-03-18 06:26:14.244 Status: Netatmo: Worker started...
2025-03-18 06:26:19.245 Status: Netatmo: Use refresh token from database...
2025-03-18 06:26:19.245 Status: Netatmo: Requesting refreshed tokens
2025-03-18 06:26:19.402 Error: Netatmo: Invalid/no data received (refresh tokens)... HTTP/2 403 
Tried to renew authentication, use new app, reset keys - No change, still HTTP/2 403

Access token failed ?

Re: Netatmo authentication changes Oct 2022

Posted: Tuesday 18 March 2025 15:59
by phil35
Hi,
This morning, update the raspberry pi, stop domoticz, reboot,
domoticz was not updated so always 2024.7

Before, when there is an issue with authentification the message was clear "Error: Netatmo: No access granted, check credentials..."
Now: " Error: Netatmo: Invalid/no data received..."
And nothing on the netatmo status webpage: https://helpcenter.netatmo.com/hc/en-us ... 5-31-01-25

to be transparent:
- I use netatmo to get information about station data and so on: this is broken
- I use a personal script (see https://github.com/Phil353556/netatmo-manage-tokens) to manage tokens to be use by a bouton (one click, two clicks) to swith on or off the light of camera.. there is no problem with the API, still works without any problem
any advise will be greathly appreciated
Phil

Re: Netatmo authentication changes Oct 2022

Posted: Tuesday 18 March 2025 18:23
by dgilbert2
This was the response from the developers regarding this issue:
---------------------------------
@waltervl
left a comment
(domoticz/domoticz#6275)
Known issue. Please look into the forum for a solution viewtopic.php?t=38968&start=200

----------------------------------
This links back to all these posts. I guess all we can do is keep plugging away at this issue until an assured workaround is discovered.

Re: Netatmo authentication changes Oct 2022

Posted: Tuesday 18 March 2025 18:48
by waltervl
@dgilber12 Follow the comments of user homeJLB as he is trying to fix this for you.....
homeJLB wrote: Monday 17 March 2025 18:51 For everybody who has still trouble connecting with the latest beta. Disable your hardware for a few hours and then re-authenticate

Kind regards

Re: Netatmo authentication changes Oct 2022

Posted: Tuesday 18 March 2025 19:06
by DomoFlits
waltervl wrote: Tuesday 18 March 2025 18:48 @dgilber12 Follow the comments of user homeJLB as he is trying to fix this for you.....
homeJLB wrote: Monday 17 March 2025 18:51 For everybody who has still trouble connecting with the latest beta. Disable your hardware for a few hours and then re-authenticate

Kind regards
Unfortunately this has only helped a very few.
So the problem is still not solved in general.
Especially not for the stable users on 2024.7

Re: Netatmo authentication changes Oct 2022

Posted: Tuesday 18 March 2025 19:35
by waltervl
When staying on stable you have little options I presume to solve this... So first action you can take is to update to latest beta as things have changed in Netatmo integration.You can always return to stable as a backup of your Domoticz environment is created while updating.

Re: Netatmo authentication changes Oct 2022

Posted: Tuesday 18 March 2025 20:08
by dgilbert2
waltervl wrote: Tuesday 18 March 2025 18:48 @dgilber12 Follow the comments of user homeJLB as he is trying to fix this for you.....
homeJLB wrote: Monday 17 March 2025 18:51 For everybody who has still trouble connecting with the latest beta. Disable your hardware for a few hours and then re-authenticate

Kind regards
Excellent news, thanks @homeJLB for your work to fix this. Fingers crossed that the latest beta + an offline period finally brings us all a workaround when the Netatmo API stops playing ball ;-)

Re: Netatmo authentication changes Oct 2022

Posted: Tuesday 18 March 2025 20:47
by DomoFlits
Ok, I did the following:
  • The Netatmo hardware had been disabled for a day or more now.
  • I subscribed to beta instead of stable in the settings menu
  • Check for updates in the menu
  • Installed the latest beta
  • Filled in the details in the new Netatmo hardware details
  • Used the login button
  • Enabled the Netatmo hardware.

The log gives:

Code: Select all

2025-03-18 20:20:16.187 Status: Netatmo2: Worker started...
2025-03-18 20:20:21.188 Status: Netatmo2: Use refresh token from database...
2025-03-18 20:20:21.188 Status: Netatmo2: Requesting refreshed tokens
2025-03-18 20:20:21.378 Error: Netatmo2: Invalid/no data received (refresh tokens)... HTTP/2 403 
   
So at least I have a slightly different error now.
Used the login button again in the hardware tab
Same result.
Will disable the hardware again and try again tomorrow.

Re: Netatmo authentication changes Oct 2022

Posted: Wednesday 19 March 2025 6:09
by DomoFlits
After having the night the Domoticz hardware disabled, I've enabled it again and used the login button.

Still the same error:

Code: Select all

2025-03-19 05:56:35.186 Status: Netatmo2: Worker stopped...
2025-03-19 05:56:35.186 Status: Netatmo2: Worker started...
2025-03-19 05:56:40.187 Status: Netatmo2: Use refresh token from database...
2025-03-19 05:56:40.187 Status: Netatmo2: Requesting refreshed tokens
2025-03-19 05:56:40.332 Error: Netatmo2: Invalid/no data received (refresh tokens)... HTTP/2 403
So with the latest beta and having the hardware disabled for multiple hours, I still can't get it working.

By the way:
This part of the wiki leaves me puzzled the way it was written:

The Redirect_URI has to contain; ""

I've left the redirect_URI field empty

Re: Netatmo authentication changes Oct 2022

Posted: Wednesday 19 March 2025 6:40
by chrominator
chrominator wrote: Tuesday 18 March 2025 6:23 Compiled from last source including PR from JurgenLB Return message when data is invalid. (#6276).

Error message is

Code: Select all

2025-03-18 06:26:14.244 Status: Netatmo: Worker started...
2025-03-18 06:26:19.245 Status: Netatmo: Use refresh token from database...
2025-03-18 06:26:19.245 Status: Netatmo: Requesting refreshed tokens
2025-03-18 06:26:19.402 Error: Netatmo: Invalid/no data received (refresh tokens)... HTTP/2 403 
I've made it working after a while, after a new compilation to be able to watch at the result of the posting for the renewal of the token.
This last until 3:45 this morning.
Now I've got the same error, with this html page as a result instead of the token refreshed.
Capture d'écran 2025-03-19 064650.png
Capture d'écran 2025-03-19 064650.png (8 KiB) Viewed 974 times
In the transition between the expected behaviour and now, no change in Netatmo app nor in dz settings.
Hard to understand what makes now Netatmo blocking the request.

Hereunder the netatmo.cpp source modification, nothing magic in itself ;)
Capture d'écran 2025-03-19 064331.png
Capture d'écran 2025-03-19 064331.png (45.99 KiB) Viewed 974 times

What is really weird is when I'm using with curl the content of the field httpData from my log after this failure, the Netatmo server send me back the expected refreshed token.

Re: Netatmo authentication changes Oct 2022

Posted: Wednesday 19 March 2025 8:37
by Thuis
Well i keep trying, but i do not know if it has anything to do with it. When i login, go to netatmo site, accept my weather station, it returns to domoticz, then when i press add new hardware. It tells me i need to login? But i am logged in, i am on the same network. Maybe could it be to do something with the login of domoticz, that it does not accept the new tokens ? I did not change anything in the authentification, also my local lan ip is in the "Vertrouwde netwerken (Geen gebruikersnaam/wachtwoord):" and i did not change this.

I was getting the "Error: Netatmo Thuis: Invalid/no data received (refresh tokens)..." time after time, and thought, what would happen if i did "ADD" in the netatmo hardware, but then i need to be logged in to domoticz, but i am already logged in. As i said, could it have something to do with this warning that i need to be logged in, but i am...

Re: Netatmo authentication changes Oct 2022

Posted: Wednesday 19 March 2025 8:45
by dgilbert2
Same at my end, leaving Netatmo hardware disabled in Domoticz for a few hours still gives me the error Invalid/no data received when I re-enabled it :-(

Re: Netatmo authentication changes Oct 2022

Posted: Wednesday 19 March 2025 8:49
by Thuis
Yes, but i do not understand why domoticz says i am not logged into domoticz, as i am sure i am logged in to domoticz .

Re: Netatmo authentication changes Oct 2022

Posted: Wednesday 19 March 2025 15:15
by wrietvel
Same issue here: It worked temporarily last week, but since yesterday I tried multiple times, without result. Is somebody working on this?