Error: getHomeData error: Application does not have the good scope rights
Closed this issue · 18 comments
Hallo zusammen,
ich bin nach Anleitung vorgegangen den Adapter einzurichten, um Daten vom CO2 Melder zu erhalten und erhalte leider folgende Fehlermeldung im Log:
`
| netatmo.0 | 2022-12-18 21:44:08.042 | error | Error: getHomeData error: Application does not have the good scope rights |
|---|---|---|---|
| netatmo.0 | 2022-12-18 21:44:08.040 | info | API Warning: getHomeData error: Application does not have the good scope rights |
| netatmo.0 | 2022-12-18 21:44:07.762 | info | CO-Sensor: Registering realtime events with iot instance |
| netatmo.0 | 2022-12-18 21:44:07.755 | info | Successfully authenticated with Netatmo with individual client-ID 639f463256e128c2270132c8 |
| netatmo.0 | 2022-12-18 21:44:07.478 | info | Authenticating with Netatmo using individual client-ID xxxxxxxxxxxxxx |
| netatmo.0 | 2022-12-18 21:44:07.476 | info | Using stored tokens to initialize ... {"access_token":"xxxxxxxxxxxxxx|xxxxxxxxxxxxxx","refresh_token":"xxxxxxxxxxxxxx|xxxxxxxxxxxxxx","scope":"read_carbonmonoxidedetector","client_id":"xxxxxxxxxxxxxx"} |
| netatmo.0 | 2022-12-18 21:44:07.398 | info | starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.netatmo, node: v14.19.1, js-controller: 4.0.23 |
Entsprechend werden keine Datenpunkte/Objekte angelegt.
Jemand eine Idee?
Please try to also activate weatherstation in the config (even if you do not have one) ... Does it work then? Or pot other device types? They were reports that this happens ... If I know what needs to be added can do that
PS: Please also try to do the "Authenticate with Netatmo" Once again
Please try to also activate weatherstation in the config (even if you do not have one) ... Does it work then? Or pot other device types? They were reports that this happens ... If I know what needs to be added can do that
I tried all devices in the config and now it works :)
The datapoints are empty but read that they will fill out if an event triggers - right?
Thank you!
@nukleuz80 Hm ... a minimal approach would have helped me more because now I have stiull no idea which additional scopes might be needed :-( But yes smokedetetcor is just filled with new events
OK, i have a CO2 sensor... but it seems to be the same like smoke... So i will produce some CO2 and wait for the event.
Is it possible to get the live data From CO2? I mean the CO2 value from the sensor...
The HomeKit integration shows the values:
Bitte keine Themen mischen! Neues Issue anlegen und bitte sagen welches Plugin da Daten hat ... mir wäre neu das es da Daten gibts die man direkt abfragen kann. Sonst Debug log und in dem anderen neuen Issue posten
Bitte keine Themen mischen! Neues Issue anlegen und bitte sagen welches Plugin da Daten hat ... mir wäre neu das es da Daten gibts die man direkt abfragen kann. Sonst Debug log und in dem anderen neuen Issue posten
OK, sorry - werde ein neues issue anlegen! :)
Closed for now
ich wüsste am Ende doch gern noch welche Scopes man braucht, aber ich adde mal ws ins Readme
das bekomme ich raus zumindest für co2...
nur wetterstation hat nicht gereicht
Im Forum sagte einer Wetterstation + CO-Sensor tat nicht ... aber Wetter + Kamera + CO2 tat ... also vllt die kamera? ... wäre komisch
Wetterstation und CO2 funktioniert nicht - das kann ich von vorhin bestätigen.
Dann kann es wohl was mit den Kategorien zu tun haben: Security, Energy etc. Dann brauch wohl der Sensor CO2 aus Kat. Security ein Gerät wie Cam um zu funktionieren.
Teste das im Laufe des Nachmittags...
ooohhh ... Ich weiss woran es liegt ... melde mich
Fixed on GitHub
I updated from Github and uncheck all options in instance settings except the CO2 sensor and it worked.
A few warnings in the logs in debug mode...
I will give you feedback if i will did my test to get events from CO2 succesfully if you like!? :)
`
| netatmo.0 | 2023-01-06 18:32:45.616 | info | starting. Version 3.0.0 (non-npm: PArns/ioBroker.netatmo#1e974a0da5c44ce2193cdcbd8d3429ce51cbfd12) in /opt/iobroker/node_modules/iobroker.netatmo, node: v14.19.1, js-controller: 4.0.23 |
|---|---|---|---|
| netatmo.0 | 2023-01-06 18:32:38.932 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.931 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.903 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.902 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.901 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.898 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.896 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.894 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.893 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.891 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.889 | warn | get state error: Connection is closed. |
| netatmo.0 | 2023-01-06 18:32:38.825 | info | starting. Version 3.0.0 (non-npm: PArns/ioBroker.netatmo#1e974a0da5c44ce2193cdcbd8d3429ce51cbfd12) in /opt/iobroker/node_modules/iobroker.netatmo, node: v14.19.1, js-controller: 4.0.23 |
| netatmo.0 | 2023-01-06 18:32:38.775 | info | terminating with timeout |
| netatmo.0 | 2023-01-06 18:32:37.772 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason |
Ok,I think these errors were coming from closing the old adapter instance ...
3.1.0 on it's way