New Netatmo binding (starting OH 3.3 M5)

chill.kroete · April 27, 2023, 7:34am

For me it broke this mornign again. Receiving again:

2023-04-27 09:32:55.581 [INFO ] [andler.capability.SecurityCapability] - Monitoring changes can only be done on local camera.
2023-04-27 09:32:55.585 [INFO ] [andler.capability.SecurityCapability] - Monitoring changes can only be done on local camera.

Because of reasons I just cannot understand my Node.js implementation is working now. This failed to set the state beforehand…

DrRSatzteil · May 6, 2023, 10:42am

It failed again yesterday. I’m not able to control the monitoring property anymore via openhab. Works well through the Netatmo app though.

Hammar · May 7, 2023, 4:13am

Hi - I have the same issue. Did you find a solution? I searched but can’t seem to identify what has caused this.

Thanks

DrRSatzteil · May 7, 2023, 7:13am

It started working again yesterday without any changes. I have no clue why this happens unfortunately.

Faro · June 6, 2023, 7:42am

Hello there,

unfortunatly I have an Issue with the Binding.

Yesterday I found out, that it stopped working. Untill then I have not made any changes to the settings, so I can´t figure out what happend.
To fix the problem I have generated a new secret and a new refresh token and inserted these in the bindings settings. Still it doesn´t work.

I get the following error: Unexpected error deserializing ‘{“error”:“invalid_request”,“error_description”:“Scope is not identical as the one granted by the user”}’

A few weeks ago I received a mail saying the tokens can expire.

Does anybody have an idea how I can get reconnected.

The Binding has the versionnumber 3.3.0. I am only using the weatherstation.

Thanks

laursen · June 6, 2023, 3:09pm

You need to upgrade to 3.4, see:

github.com/openhab/openhab-addons

[netatmo] Make OAuth2 token refresh RFC compliant

openhab:3.4.x ← clinique:netatmo_oauth_14546_34X

opened 04:18PM - 10 Mar 23 UTC

clinique

+101 -78

Cherry picking PR #14548 in branch 3.4.x Fixes #14546

Faro · June 7, 2023, 9:25am

Thanks for quick reply.

Maybe it is because I´m new to this system, but I can´t find the jar-file or comparable. Is there any?
I forgot to mention that I run OH on a Synology Nas and I am only experienced in installing bindings via the UI or by adding the jar-file into the addons-folder.

laursen · June 7, 2023, 9:28am

If you upgrade openHAB itself to 3.4 which is currently the latest (and best) version, you will automatically have the binding upgraded as well without manually installing a JAR. And welcome to openHAB!

Faro · June 10, 2023, 7:53pm

Thanks. OH is pretty complex and sometimes confusing. But I guess I step by step get deeper into it. Some of my needs allready work well.

The Upgrade worked well and I got the binding in version 3.4.4. Unfortunatly the bridge still won´t work and gives me this error: "Configuration incomplete, please grant the binding to Netatmo Connect. ".

Where is my mistake? EDIT: Found it!

joerg_asma · June 11, 2023, 4:15pm

Hi Fabian,
looks like I am enjoying the same error. Netatmo stopped working, Installed the Bridge new, but now cant make it work, receiving the same error as you did.
Any hints where to look at?
kind regards
Joerg

Faro · June 12, 2023, 10:58am

I forgot one of the steps mentioned in the description for the config:

The bridge thing will go OFFLINE / CONFIGURATION_ERROR - this is fine. You have to authorize this bridge with Netatmo Connect.
Go to the authorization page of your server. http://<your openHAB address>:8080/netatmo/connect/<_CLIENT_ID_> . Your newly added bridge should be listed there (no need for you to expose your openHAB server outside your local network for this).

John_Galt · June 22, 2023, 3:50pm

Hi! I don’t know, I might do something really stupid or am missing something but…
I have been trying to upgrade to 3.4 for the last two days, and trying to move to the new Netatmo binding. I install the binding, since I have used .things-files before, I setup a new bridge according to the instructions and I register as is supposed. The bridge goes online but after a while it goes offline with a

COMMUNICATION_ERROR
Bad Request

I try again to register but now it says

Sorry
Requested content not found.

When I go into the settings fo the Bridge there is no “Show advanced” tickbox so there is no way to delete erroneous tokens as some have suggested.

I have tried with my old installation and also on a totally new OpenHABian setup.

I also tried to setup a Bridge using GUI which worked for a while, then, when I changed the label of it, it broke and now I can’t get it to work again.

Not sure how to proceed now.

Addiotion. Finally managed to remeber how to change log-level…

2023-06-22 18:07:18.537 [DEBUG] [mo.internal.handler.ApiBridgeHandler] - Initializing Netatmo API bridge handler.
2023-06-22 18:07:18.538 [DEBUG] [mo.internal.handler.ApiBridgeHandler] - Connecting to Netatmo API.
2023-06-22 18:07:18.654 [DEBUG] [mo.internal.handler.ApiBridgeHandler] - Error deserializing payload from error response
org.openhab.binding.netatmo.internal.api.NetatmoException: Unexpected error deserializing '{"error":"invalid_grant"}'

laursen · June 22, 2023, 7:00pm

Just to be sure: Are you on 3.4.0 (release version) or 3.4.4 (latest hotfix)?

John_Galt · June 22, 2023, 7:05pm

I am on 3.4.4

laursen · June 22, 2023, 7:29pm

Okay, this confirms that the version you are using supports the new OAuth2 requirements.

The log output above is caused by a bug in the binding’s error handling.

To remove your token, you can delete the file(s) OPENHAB_USERDATA/netatmo/refreshToken_*, for example in openHABian for a bridge called home: /var/lib/openhab/netatmo/refreshToken_netatmo_account_home.

After deleting this, you can reauthorize as described in the documentation. This works at least for some cases of “Bad Request”.

FYI, in 4.0 the OAuth2 implementation has changed:

github.com/openhab/openhab-addons

[netatmo] Consolidate OAuth2 by using core implementation and storage

openhab:main ← jlaur:14755-netatmo-consolidate-oauth2

opened 08:29PM - 10 Apr 23 UTC

jlaur

+231 -160

This replaces the custom OAuth2 authorization requests and storage by the implem…entation in [org.openhab.core.auth.client.oauth2](https://www.openhab.org/javadoc/latest/org/openhab/core/auth/client/oauth2/package-summary.html). This has some benefits: - Only one implementation to maintain and with full feature set. - Shared **jsondb** storage for all implementations, which will be included in backups. Additionally, the behavior of multiple fighting clients have changed. Previously, the bridge would get status "OFFLINE (COMMUNICATION_ERROR): Bad Request" when reinitializing the bridge handler after authorizing another client. I noticed this on my OH 3.4 production system while testing the authorization flow on a 4.0 system. Now, the reauthorization flow will be correctly started. After completing the authorization flow successfully, the servlet will now be disposed. Depends on openhab/openhab-core#3537 Fixes #14755

So just be aware that you need to reauthorize again when upgrading to 4.0. The good news is that the new implementation uses the standard OAuth2 implementation in openHAB, and you no longer need this custom token file. I believe the “Bad Request” issue is fixed, and I’m also hoping for this to be fixed:

github.com/openhab/openhab-addons

[netatmo] Unable to recover from service issues/downtime

opened 06:17AM - 14 Jun 23 UTC

jlaur

bug

The Netatmo services were down 13.06.2023 around 22:00 CET until around 00:20. U…nfortunately the binding was not able to recover, but needed to be restarted manually. ## Expected Behavior When services are up again, the binding should resume receiving data. ## Current Behavior The binding was apparently stuck in a bad state which it was not able to recover from. Unfortunately I didn't have debug or trace logging enabled. What last appeared in the logs before and after the service came up again: ``` 2023-06-14 00:00:30.965 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Service Unavailable 2023-06-14 00:02:20.174 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Service Unavailable 2023-06-14 00:02:31.010 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Service Unavailable 2023-06-14 00:04:20.474 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Service Unavailable 2023-06-14 00:04:33.318 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Service Unavailable 2023-06-14 00:06:20.712 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Service Unavailable 2023-06-14 00:06:33.355 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Service Unavailable 2023-06-14 00:08:20.980 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Bad Request 2023-06-14 00:08:33.407 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Bad Request 2023-06-14 00:10:21.245 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Service Unavailable 2023-06-14 00:10:33.443 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Service Unavailable 2023-06-14 00:12:21.483 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Service Unavailable 2023-06-14 00:12:33.479 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Service Unavailable 2023-06-14 00:14:21.718 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Service Unavailable 2023-06-14 00:14:33.517 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Service Unavailable 2023-06-14 00:16:21.975 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Bad Request 2023-06-14 00:16:33.569 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Bad Request 2023-06-14 00:18:25.356 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Service Unavailable 2023-06-14 00:18:33.611 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Service Unavailable 2023-06-14 00:20:25.617 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Bad Request 2023-06-14 00:20:35.222 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Bad Request 2023-06-14 00:22:25.860 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Bad Request 2023-06-14 00:22:35.315 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Bad Request 2023-06-14 00:24:26.124 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Bad Request 2023-06-14 00:24:35.371 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Bad Request 2023-06-14 00:26:26.379 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:01' : Bad Request 2023-06-14 00:26:35.424 [WARN ] [handler.capability.WeatherCapability] - Error retrieving weather data 'xx:xx:xx:xx:xx:00' : Bad Request ``` Hereafter only "Bad Request" is logged, so this is the symptom where the binding did something wrong while the services were up. I also noticed while the services were still down that all my things (including bridges) were ONLINE. ## Possible Solution I'm not sure if this is related to OAuth2 or is a more general problem. In case of OAuth2 it might have changed with #14780. ## Steps to Reproduce The Netatmo are not often down, so this is tricky. However, it might be possible to emulate some similar behavior in the code. ## Your Environment * Version used: 3.4.4

John_Galt · June 22, 2023, 7:39pm

Thanks a lot @laursen , not sure if this will take me the whole way but at least I know how to proceed.

stadelmannj · June 24, 2023, 9:10am

Same issue. has this ever been solved ? can’t find an answer in this Thread

FreddyM · June 24, 2023, 3:25pm

I use now OH 3.4.4 and have no problems

jannegpriv · July 8, 2023, 9:00am

Same here, I’m on OH3.4.4 and the binding has been stable for more than 2 weeks now.

chill.kroete · July 9, 2023, 2:49pm

Having the same issue on OH 4.0.0 M4.