Adapter is not working any more

[git2206]

Hi,

netatmo adapter 3.1.0 is not woking any more - the events of SmokeAlarm or COAlarm is not recognized from netatmo adapter any more. the iot adapter is working as expected - he recognized new events, but the netatmo adapeter did not. I am not sure, when this problem starts - i think when i updated to js controler 5.x. weeks ago... Since few days a updated to js controller 6.0.11 and nodejs 20.18.1 - i thought this would fix it... But the same issue. IOT adapter works, but netatmo adapter not.

Please can you check the adapter?

THX Flo

[git2206]

Here some additional info... so the connection is working... you can see it in the log file... 2024-11-25 08:59:32.327 - info: netatmo.0 (2109719) Authenticating with Netatmo using individual client-ID XXXXXX 2024-11-25 08:59:32.710 - info: netatmo.0 (2109719) API Warning: Authenticate refresh error: invalid_grant 2024-11-25 08:59:32.710 - info: netatmo.0 (2109719) Successfully authenticated with Netatmo with individual client-ID XXXXXX 2024-11-25 08:59:32.725 - info: netatmo.0 (2109719) Smoke-Detector: Registering realtime events with iot instance 2024-11-25 08:59:32.728 - info: netatmo.0 (2109719) CO-Sensor: Registering realtime events with iot instance

[Apollon77]

Try to re-ogin with Netatmo ia Admin config please to make sure the "Invalid grant" is not the reason

[git2206]

Hi,

yes, netatmo login is working…

2024-11-25 10:25:58.524 - info: host.smarthome instance system.adapter.netatmo.0 in version "3.1.0" started with pid 2197671

2024-11-25 10:26:01.602 - info: netatmo.0 (2197671) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system

2024-11-25 10:26:01.940 - info: netatmo.0 (2197671) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.netatmo, node: v20.18.1, js-controller: 6.0.11

2024-11-25 10:26:01.982 - info: netatmo.0 (2197671) Using stored tokens to initialize ... {„access_token“:“XXXX|XXXX","refresh_token“:“XXXX|XXX","scope":"read_smokedetector read_carbonmonoxidedetector","client_id“:"XXXXXXXXXXXXXXX"}

2024-11-25 10:26:01.995 - info: netatmo.0 (2197671) Authenticating with Netatmo using individual client-ID 6515889010ff797b780181e5

2024-11-25 10:26:02.524 - info: netatmo.0 (2197671) API Warning: Authenticate refresh error: invalid_grant

2024-11-25 10:26:02.524 - info: netatmo.0 (2197671) Successfully authenticated with Netatmo with individual client-ID 6515889010ff797b780181e5

2024-11-25 10:26:02.534 - info: netatmo.0 (2197671) Smoke-Detector: Registering realtime events with iot instance

2024-11-25 10:26:02.537 - info: netatmo.0 (2197671) CO-Sensor: Registering realtime events with iot instance

So er sollte die nötigen Info von netatmo API erhalten können… IOT Instance funktioniert ja - dort erkennt der adapter den Event…

2024-11-25 10:32:00.989 - debug: iot.0 (2202882) Data: "{\"user_id\":\“XXXXX\",\"event_type\":\"sound_test\",\"device_id\":\"70:ee:50:XX:XX:XX\",\"home_id\":\“XXXXX\",\"home_name\":\"SmartHomeNetatmo\",\"camera_id\":\"70:ee:50:XX:XX:XX\",\"event_id\":\“XXXXX\",\"sub_type\":0,\"push_type\":\"NCO-sound_test\"}"

Mit freundlichen Grüßen Flo

Am 25.11.2024 um 10:13 schrieb Ingo Fischer @.***>:

Try to re-ogin with Netatmo ia Admin config please to make sure the "Invalid grant" is not the reason

— Reply to this email directly, view it on GitHubhttps://github.com/PArns/ioBroker.netatmo/issues/204#issuecomment-2497356920, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATLEB3ADWD63KRKJSACGJPD2CLS3LAVCNFSM6AAAAABSMLYN5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJXGM2TMOJSGA. You are receiving this because you authored the thread.Message ID: @.***>

[Apollon77]

Also wie man immLog sieht meldet er sich für CO Events an ... Wenn die anderen Events kommen wüsste ich nicht wo es am Adapter liegen kann das die Events für CO fehlen. Mal einen Alarm was ausgelöst

[git2206]

Hi,

yes, netatmo login is working…

2024-11-25 10:25:58.524 - info: host.smarthome instance system.adapter.netatmo.0 in version "3.1.0" started with pid 2197671 2024-11-25 10:26:01.602 - info: netatmo.0 (2197671) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2024-11-25 10:26:01.940 - info: netatmo.0 (2197671) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.netatmo, node: v20.18.1, js-controller: 6.0.11 2024-11-25 10:26:01.982 - info: netatmo.0 (2197671) Using stored tokens to initialize ... {„access_token“:“XXXX|XXXX","refresh_token“:“XXXX|XXX","scope":"read_smokedetector read_carbonmonoxidedetector","client_id“:"XXXXXXXXXXXXXXX"} 2024-11-25 10:26:01.995 - info: netatmo.0 (2197671) Authenticating with Netatmo using individual client-ID 6515889010ff797b780181e5 2024-11-25 10:26:02.524 - info: netatmo.0 (2197671) API Warning: Authenticate refresh error: invalid_grant 2024-11-25 10:26:02.524 - info: netatmo.0 (2197671) Successfully authenticated with Netatmo with individual client-ID 6515889010ff797b780181e5 2024-11-25 10:26:02.534 - info: netatmo.0 (2197671) Smoke-Detector: Registering realtime events with iot instance 2024-11-25 10:26:02.537 - info: netatmo.0 (2197671) CO-Sensor: Registering realtime events with iot instance

So er sollte die nötigen Info von netatmo API erhalten können… IOT Instance funktioniert ja - dort erkennt der adapter den Event…

2024-11-25 10:32:00.989 - debug: iot.0 (2202882) Data: "{\"user_id\":\“XXXXX\",\"event_type\":\"sound_test\",\"device_id\":\"70:ee:50:XX:XX:XX\",\"home_id\":\“XXXXX\",\"home_name\":\"SmartHomeNetatmo\",\"camera_id\":\"70:ee:50:XX:XX:XX\",\"event_id\":\“XXXXX\",\"sub_type\":0,\"push_type\":\"NCO-sound_test\"}"

Mit freundlichen Grüßen Flo

Am 25.11.2024 um 10:13 schrieb Ingo Fischer @.***>:

Try to re-ogin with Netatmo ia Admin config please to make sure the "Invalid grant" is not the reason

— Reply to this email directly, view it on GitHubhttps://github.com/PArns/ioBroker.netatmo/issues/204#issuecomment-2497356920, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATLEB3ADWD63KRKJSACGJPD2CLS3LAVCNFSM6AAAAABSMLYN5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJXGM2TMOJSGA. You are receiving this because you authored the thread.Message ID: @.***>

[git2206]

Hallo,

naja… das selbe spiel ist auch beim Rauchmelder… also der iot adapter erkennt das event - nur der netatmo adapter reagiert nicht darauf und ändert somit keine objekte im iobroker. Es kommen auch keine logs vom netatmo adapter - sonder nur von iot adapter… sprich der netatmo adapter bekommt nicht mit, dass vom iot adapter neue events angekommen sind…

Laut doku vom netatmo adapter benötigt dieser ja eine iot adapter instance… sonst funktioniert er nicht. (set v3 glaub ich). Es hat ja auch gut geklappt… bis vor einigen wochen bzw ich glaube seit ich von js controller v4 auf v5 umgestiegen bin. Jetzt bin ich seit einigen Tagen auf v6 umgestiegen.. aber das gleiche Bild.

Mit freundlichen Grüßen Flo

Am 25.11.2024 um 11:02 schrieb Ingo Fischer @.***>:

Also wie man immLog sieht meldet er sich für CO Events an ... Wenn die anderen Events kommen wüsste ich nicht wo es am Adapter liegen kann das die Events für CO fehlen. Mal einen Alarm was ausgelöst

— Reply to this email directly, view it on GitHubhttps://github.com/PArns/ioBroker.netatmo/issues/204#issuecomment-2497489991, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATLEB3CPJNJEJS6WILW76TL2CLYSVAVCNFSM6AAAAABSMLYN5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJXGQ4DSOJZGE. You are receiving this because you authored the thread.Message ID: @.***>

[Apollon77]

Na dann bitte mal bei iot UND netatmo debug loggging aktivieren und mir mal so ein joint log Zeigen