Values are not beeing updated (sync only works in one direction)

[Roellen]

When I change the temperature within the Netatmo Energy "tab" website... it works. The Relais receives the value after ~5 seconds.
But when changing the temperature at the Netatmo Relais itselfs, these changes are not beeing sent to iobroker. No setpoint temperatur, no measured temperatures...

What can I do?

[Homemade-Disaster]

The adapter gets the information out of the official Netatmo API. Depending on the interval you have inserted in the adapter config, the adapter will receive the actual data out of the API. If the Relais (hardware) do not send the changes to the cloud, it is impossible to get these changes back to ioBroker. Please send your reported problem to Netatmo.

[Roellen]

But... the "Energy" app on my iphone is working fine... it receives any changes within seconds. So... not sure how to find the problem right now.

[Roellen]

This came today. Not sure if something needs to be updated?

Authentication update (second notice)

This is a reminder regarding our authentication update following the release initially planned for last fall which we decided to postpone in order to give our users more time. Dear Netatmo developer,
Today, when you refresh an Access Token using the associated endpoint https://api.netatmo.com/oauth2/token, the Netatmo servers respond with a pair of tokens: an Access Token and a Refresh Token. If the previous Access Token is still valid, the newly returned access token is identical but has an expiration time extended by 3 hours.The Refresh Token is not renewed.
Starting May 29, 2024, this behavior will change to comply with the OAuth2 Authorization Framework RFC recommendations (section 10.4) and improve the security of our users' data.When refreshing the tokens, the Access Token and Refresh Token will be different from the previous ones and the old tokens will be invalidated.
What does this mean for you?If you already store the tokens returned by the API when refreshing your tokens, this change will not affect you.If you do not update the tokens when refreshing them, your users will be logged out because the old tokens will be invalidated.If for a given user, you have stored the same token in different places (for example: an application and its widget), you must have a way to synchronize them because the new token will be applied for the entire application.
Sincerely,Legrand - Netatmo - Bticino

Authentication update (second notice)

This is a reminder regarding our authentication update following the release initially planned for last fall which we decided to postpone in order to give our users more time.

Dear Netatmo developer,

Today, when you refresh an Access Token using the associated endpoint https://api.netatmo.com/oauth2/token, the Netatmo servers respond with a pair of tokens: an Access Token and a Refresh Token.

If the previous Access Token is still valid, the newly returned access token is identical but has an expiration time extended by 3 hours.

The Refresh Token is not renewed.

Starting May 29, 2024, this behavior will change to comply with the OAuth2 Authorization Framework RFC recommendations (section 10.4) and improve the security of our users' data.

When refreshing the tokens, the Access Token and Refresh Token will be different from the previous ones and the old tokens will be invalidated.

What does this mean for you?

If you already store the tokens returned by the API when refreshing your tokens, this change will not affect you.

If you do not update the tokens when refreshing them, your users will be logged out because the old tokens will be invalidated.

If for a given user, you have stored the same token in different places (for example: an application and its widget), you must have a way to synchronize them because the new token will be applied for the entire application.

Sincerely,

Legrand - Netatmo - Bticino