Error: getHomeData error: Operation is forbidden

[Sandmanyz]

Since yesterday (Apr. 10, 2025) i get this error every 10 minutes in ioBroker:
Error: getHomeData error: Operation is forbidden

If I remove the checkmark from the checkbox "netatmoCOSensor" the error does not appear.

[Claus1985]

Error also appears if only iDiamant/Bubendorff option is selected

[Apollon77]

Did you tried to renew the Authentication? DGo to Admin. check setting. klick the button to Login, login to Netatmo in the new Window/Tab (pot allow popup blocker) and finish the process. is the error the same then?

If yes please post a full Debug log of a start of the adapter

[Claus1985]

Still get the same error. Adapter still functions (is shown as status green and also commands to shutters still work) but non the less the error in log is shown regularly, here is the debug log from adapter start:

• netatmo.0 2025-04-18 13:25:44.810 error Error: getHomeData error: Operation is forbidden
• netatmo.0 2025-04-18 13:25:44.666 info Successfully authenticated with Netatmo with individual client-ID XXXX
• netatmo.0 2025-04-18 13:25:44.664 debug Update Refresh tokens: XXXX | XXXX
• netatmo.0 2025-04-18 13:25:44.663 debug Access Token: XXXX | XXXX
• netatmo.0 2025-04-18 13:25:44.355 debug netatmo: authenticate_refresh: {"grant_type":"refresh_token","refresh_token":"XXXX | XXXX","client_id":"XXXX","client_secret":"XXXX"}
• netatmo.0 2025-04-18 13:25:44.352 info Authenticating with Netatmo using individual client-ID XXXX
• netatmo.0 2025-04-18 13:25:44.349 info Using stored tokens to initialize ... {"access_token":"XXXX | XXXX","refresh_token":"XXXX | XXXX","scope":"read_bubendorff write_bubendorff","client_id":"XXXX"}
• netatmo.0 2025-04-18 13:25:44.345 debug Use individual ID/Secret
• netatmo.0 2025-04-18 13:25:44.301 info starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.netatmo, node: v20.19.0, js-controller: 7.0.6
• netatmo.0 2025-04-18 13:25:43.852 debug Plugin sentry Initialize Plugin (enabled=true)
• netatmo.0 2025-04-18 13:25:43.808 debug States connected to redis: 127.0.0.1:6379
• netatmo.0 2025-04-18 13:25:43.794 debug States create User PubSub Client
• netatmo.0 2025-04-18 13:25:43.792 debug States create System PubSub Client
• netatmo.0 2025-04-18 13:25:43.783 debug Redis States: Use Redis connection: 127.0.0.1:6379
• netatmo.0 2025-04-18 13:25:43.710 debug Objects connected to redis: 127.0.0.1:9001
• netatmo.0 2025-04-18 13:25:43.700 debug Objects client initialize lua scripts
• netatmo.0 2025-04-18 13:25:43.584 debug Objects create User PubSub Client
• netatmo.0 2025-04-18 13:25:43.582 debug Objects create System PubSub Client
• netatmo.0 2025-04-18 13:25:43.580 debug Objects client ready ... initialize now
• netatmo.0 2025-04-18 13:25:43.513 debug Redis Objects: Use Redis connection: 127.0.0.1:9001

[Claus1985]

ok as of today the adapter stopped working. This is not visible in log even in debug mode it just shows the correct commands:
stateChange netatmo.XXXX.open {"val":true,"ack":false,"ts":XXXX,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":XXXX}

Also reauthentification does not help:

• netatmo.0 2025-04-19 07:47:12.535 error Error: getHomeData error: Operation is forbidden
• netatmo.0 2025-04-19 07:47:12.380 info Successfully authenticated with Netatmo with individual client-ID XXXX

Adapter shows green and connected only problem is nothing happens - devices don´t move.

[Claus1985]

Something must have changed with the api. Do you have any idea what should be done as workaround?

[Apollon77]

As rewuested please do a NEW "login with netatmo" via admin and newly approve all scopes and devices on the page that opens. And post a Debug log of this. The log above is not showing this process but just a normal token refresh

[Claus1985]

See attachment for log. I created a new app in netatmo portal and used this for authentication but gives me the same error in the end.

I also tried deleting the netatmo object tree, problem is its not getting created again (which makes sense since the error states that I don't have access).

Same happens without individual client id:

[mhuber77]

Hi all,

any news about this, I tried all the sugested solutions but the problem still exists.
@Apollon77 would be great if you can help.

thanks

[Apollon77]

The above log is still not showing a new login with debug log. So either the debug log is simply cutted because of the fact that a screenshot is used, or it was not really done correctly

so:

• turn on debug logging
• enter client credentials in admin
• klick "Authenticate with netatmo"
• a popup/new tab will open - if not check your popupblocker settings
• login there and approve all rights anew
• a success message will be shown in the webpage
• adapter restarts
  I need a debug log from this whole flow.

Thank you

[Claus1985]

Here is a complete copy of the log anonymized:

2025-05-24 12:28:13.623 - debug: netatmo.0 (133676) Redis Objects: Use Redis connection: 127.0.0.1:9001

2025-05-24 12:28:13.685 - debug: netatmo.0 (133676) Objects client ready ... initialize now

2025-05-24 12:28:13.688 - debug: netatmo.0 (133676) Objects create System PubSub Client

2025-05-24 12:28:13.689 - debug: netatmo.0 (133676) Objects create User PubSub Client

2025-05-24 12:28:13.801 - debug: netatmo.0 (133676) Objects client initialize lua scripts

2025-05-24 12:28:13.811 - debug: netatmo.0 (133676) Objects connected to redis: 127.0.0.1:9001

2025-05-24 12:28:13.886 - debug: netatmo.0 (133676) Redis States: Use Redis connection: 127.0.0.1:6379

2025-05-24 12:28:13.895 - debug: netatmo.0 (133676) States create System PubSub Client

2025-05-24 12:28:13.897 - debug: netatmo.0 (133676) States create User PubSub Client

2025-05-24 12:28:13.910 - debug: netatmo.0 (133676) States connected to redis: 127.0.0.1:6379

2025-05-24 12:28:13.946 - debug: netatmo.0 (133676) Plugin sentry Initialize Plugin (enabled=true)

2025-05-24 12:28:14.412 - info: netatmo.0 (133676) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.netatmo, node: v20.19.2, js-controller: 7.0.7

2025-05-24 12:28:14.445 - debug: netatmo.0 (133676) Use individual ID/Secret

2025-05-24 12:28:14.448 - info: netatmo.0 (133676) Using stored tokens to initialize ... {"access_token":"XX|XX","refresh_token":"XX|XX","scope":"read_bubendorff write_bubendorff","client_id":"XX"}

2025-05-24 12:28:14.450 - info: netatmo.0 (133676) Authenticating with Netatmo using individual client-ID XX

2025-05-24 12:28:14.452 - debug: netatmo.0 (133676) netatmo: authenticate_refresh: {"grant_type":"refresh_token","refresh_token":"XX|XX","client_id":"XX","client_secret":"XX"}

2025-05-24 12:28:14.751 - debug: netatmo.0 (133676) Access Token: XX|XX

2025-05-24 12:28:14.752 - debug: netatmo.0 (133676) Update Refresh tokens: XX|XX

2025-05-24 12:28:14.754 - info: netatmo.0 (133676) Successfully authenticated with Netatmo with individual client-ID XX

2025-05-24 12:28:14.946 - error: netatmo.0 (133676) Error: getHomeData error: Operation is forbidden

2025-05-24 12:28:21.754 - debug: netatmo.0 (133676) Received OAuth start message: {"client_id":"XX","client_secret":"XX","redirect_uri_base":"https://192.168.178.XX","scopes":{"netatmoCoach":false,"netatmoWeather":false,"netatmoWelcome":false,"netatmoSmokedetector":false,"netatmoCOSensor":false,"netatmoDoorBell":false,"netatmoBubendorff":true}}

2025-05-24 12:28:21.756 - debug: netatmo.0 (133676) Get OAuth start link data: {"client_id":"XX","client_secret":"XX","scopes":{"netatmoCoach":false,"netatmoWeather":false,"netatmoWelcome":false,"netatmoSmokedetector":false,"netatmoCOSensor":false,"netatmoDoorBell":false,"netatmoBubendorff":true},"scope":"read_bubendorff write_bubendorff","redirect_uri":"https://192.168.178.XX/oauth2_callbacks/netatmo.0/"}

2025-05-24 12:28:21.757 - debug: netatmo.0 (133676) Get OAuth start link: https://api.netatmo.com/oauth2/authorize?client_id=XX&redirect_uri=https%3A%2F%2F192.168.178.XX%2Foauth2_callbacks%2Fnetatmo.0%2F&scope=read_bubendorff%20write_bubendorff&state=XX

2025-05-24 12:28:34.925 - debug: netatmo.0 (133676) OAuthRedirectReceived: {"state":"XX","code":"XX"}

2025-05-24 12:28:34.926 - debug: netatmo.0 (133676) netatmo: authenticate: {"code":"XX","redirect_uri":"https://192.168.178.XX/oauth2_callbacks/netatmo.0/","grant_type":"authorization_code","client_id":"XX","client_secret":"XX","scope":"read_bubendorff write_bubendorff"}

2025-05-24 12:28:35.083 - debug: netatmo.0 (133676) netatmo: authenticate err null

2025-05-24 12:28:35.084 - debug: netatmo.0 (133676) netatmo: authenticate status 200

2025-05-24 12:28:35.084 - debug: netatmo.0 (133676) netatmo: authenticate body {"access_token":"XX|XX","refresh_token":"XX|XX","expires_in":10800,"expire_in":10800,"scope":["read_bubendorff","write_bubendorff"]}

2025-05-24 12:28:35.085 - debug: netatmo.0 (133676) Access Token: XX|XX

2025-05-24 12:28:35.085 - debug: netatmo.0 (133676) Update Refresh tokens: XX|XX

2025-05-24 12:28:35.086 - info: netatmo.0 (133676) Successfully authenticated with Netatmo with individual client-ID XX

2025-05-24 12:28:35.089 - info: netatmo.0 (133676) Save OAuth data: {"access_token":"XX|XX","refresh_token":"XX|XX","scope":"read_bubendorff write_bubendorff","client_id":"XX"}

2025-05-24 12:28:35.091 - info: netatmo.0 (133676) Update data in adapter configuration ... restarting ...

2025-05-24 12:28:35.117 - info: netatmo.0 (133676) Got terminate signal TERMINATE_YOURSELF

2025-05-24 12:28:35.120 - info: netatmo.0 (133676) cleaned everything up...

2025-05-24 12:28:35.120 - info: netatmo.0 (133676) terminating

2025-05-24 12:28:35.122 - debug: netatmo.0 (133676) Plugin sentry destroyed

2025-05-24 12:28:35.122 - info: netatmo.0 (133676) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

2025-05-24 12:28:35.623 - info: netatmo.0 (133676) terminating

2025-05-24 12:28:41.439 - debug: netatmo.0 (133698) Redis Objects: Use Redis connection: 127.0.0.1:9001

2025-05-24 12:28:41.519 - debug: netatmo.0 (133698) Objects client ready ... initialize now

2025-05-24 12:28:41.523 - debug: netatmo.0 (133698) Objects create System PubSub Client

2025-05-24 12:28:41.525 - debug: netatmo.0 (133698) Objects create User PubSub Client

2025-05-24 12:28:41.652 - debug: netatmo.0 (133698) Objects client initialize lua scripts

2025-05-24 12:28:41.667 - debug: netatmo.0 (133698) Objects connected to redis: 127.0.0.1:9001

2025-05-24 12:28:41.751 - debug: netatmo.0 (133698) Redis States: Use Redis connection: 127.0.0.1:6379

2025-05-24 12:28:41.764 - debug: netatmo.0 (133698) States create System PubSub Client

2025-05-24 12:28:41.767 - debug: netatmo.0 (133698) States create User PubSub Client

2025-05-24 12:28:41.785 - debug: netatmo.0 (133698) States connected to redis: 127.0.0.1:6379

2025-05-24 12:28:41.834 - debug: netatmo.0 (133698) Plugin sentry Initialize Plugin (enabled=true)

2025-05-24 12:28:42.290 - info: netatmo.0 (133698) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.netatmo, node: v20.19.2, js-controller: 7.0.7

2025-05-24 12:28:42.317 - debug: netatmo.0 (133698) Use individual ID/Secret

2025-05-24 12:28:42.320 - info: netatmo.0 (133698) Using stored tokens to initialize ... {"access_token":"XX|XX","refresh_token":"XX|XX","scope":"read_bubendorff write_bubendorff","client_id":"XX"}

2025-05-24 12:28:42.321 - info: netatmo.0 (133698) Authenticating with Netatmo using individual client-ID XX

2025-05-24 12:28:42.323 - debug: netatmo.0 (133698) netatmo: authenticate_refresh: {"grant_type":"refresh_token","refresh_token":"XX|XX","client_id":"XX","client_secret":"XX"}

2025-05-24 12:28:42.622 - debug: netatmo.0 (133698) Access Token: XX|XX

2025-05-24 12:28:42.623 - debug: netatmo.0 (133698) Update Refresh tokens: XX|XX

2025-05-24 12:28:42.624 - info: netatmo.0 (133698) Successfully authenticated with Netatmo with individual client-ID XX

2025-05-24 12:28:42.791 - error: netatmo.0 (133698) Error: getHomeData error: Operation is forbidden

@Apollon77 Hope this helps. In objects nothing has been created after this process.

[Apollon77]

Ok, I think understood now ... One call was deprecated and seems to be removed now, but we still used it because the new call missed details on persons.
So ok I removed the legacy stuff now ... lets see which issues that now brings

[Apollon77]

Please try GitHub version. Version number does not change, so pot restart after update please

[Claus1985]

Awesome, thx for the quick fix, this did the trick! Works like a charm. 👍