NetAtmo Events gehen nicht mehr/Dauerhafte Meldungen "Websocket error"
SchlumpfIOB opened this issue · 9 comments
Hallo an alle,
bei mir läuft seit 3 oder 4 Tagen das Log voll mit folgender Info von Netatmo:
Websocket error: websocket error, Error: websocket error at WS.Transport.onError (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:64:13) at WebSocket.ws.onerror (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:149:10) at WebSocket.onError (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:452:14) at WebSocket.emit (node:events:527:28) at WebSocket.emit (node:domain:475:12) at ClientRequest.response (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:721:12) at Object.onceWrapper (node:events:642:26) at ClientRequest.emit (node:events:539:35) at ClientRequest.emit (node:domain:475:12) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:631:27)
Kann mir jemand sagen was da los ist und wie ich die Meldung wieder los bekomme?
Gruß
Jan
Danke das du ein Issues eröffnet hast. Genau das gleiche Frage ich mich auch. Der Log ist mittlerweile vollständig nur mit diesem Adapter gefüllt. Und das alle paar (fast schon Milli-)Sekunden. Das nervt gewaltig. Habe den Adapter jetzt leider deaktiviert. Hoffe da wird ein Fix kommen.
Ja, ca. alle 0,2 sec kommt die Meldung. die letzten Tage habe ich Logs von 20 MB, was bei mir extrem viel ist.
Ok, scheinbar ist der Websocket Server undeployed worden .... bzw Heroku bietet kein SSL mehr an for free ... wasn das für ein blödsinn. @PArns Falls Du zeit hast bitte schauen. Ich bin ab jetzt bis Sonntag unterwegs, kann also frühestens nächste Woche etwas schauen. Im zweifel muss ich das woanders deployen. So lange gehen keine events
Ok PArns ist auch nicht verfügbar. Ich schaue Sonntag
Ok Grund und jetzt auch bekannt: Heroku gibts nicht mehr "for free" :-(
Starting November 28th, 2022, free Heroku Dynos, free Heroku Postgres, and free Heroku Data for Redis® will no longer be available. If you have apps using any of these resources, you must upgrade to paid plans by this date to ensure your apps continue to run and to retain your data.
Ich schaue dann mal wo wir den Server künftig hosten können.
Auch mit v 2.1.2 aus dem beta habe ich Websocket error-Meldungen, sobald der CO-Sensor angewählt ist.
Der läuft bei Netatmo meines Wissens auch unter "Security-Produkte".
Wenn ich den Haken beim CO-Sensor wegmache, so dass nur noch die Wetterstation ausgewählt ist, läuft alles ohne die Fehlermeldungen.
"Authentificate with Netatmo" habe ich jeweils neu durchgeführt.
`
netatmo.0 | 4577 | 2022-12-09 12:22:19.370 | info | Websocket error: websocket error, Error: websocket error at WS.Transport.onError (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:64:13) at WebSocket.ws.onerror (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:149:10) at WebSocket.onError (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:452:14) at WebSocket.emit (node:events:513:28) at WebSocket.emit (node:domain:489:12) at ClientRequest.response (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:721:12) at Object.onceWrapper (node:events:628:26) at ClientRequest.emit (node:events:525:35) at ClientRequest.emit (node:domain:489:12) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27) |
---|---|---|---|---|
netatmo.0 | 4577 | 2022-12-09 12:22:18.326 | info | Websocket error: websocket error, Error: websocket error at WS.Transport.onError (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:64:13) at WebSocket.ws.onerror (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:149:10) at WebSocket.onError (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:452:14) at WebSocket.emit (node:events:513:28) at WebSocket.emit (node:domain:489:12) at ClientRequest.response (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:721:12) at Object.onceWrapper (node:events:628:26) at ClientRequest.emit (node:events:525:35) at ClientRequest.emit (node:domain:489:12) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27) |
netatmo.0 | 4577 | 2022-12-09 12:22:18.326 | info | Websocket error: websocket error, Error: websocket error at WS.Transport.onError (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:64:13) at WebSocket.ws.onerror (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:149:10) at WebSocket.onError (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:452:14) at WebSocket.emit (node:events:513:28) at WebSocket.emit (node:domain:489:12) at ClientRequest.response (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:721:12) at Object.onceWrapper (node:events:628:26) at ClientRequest.emit (node:events:525:35) at ClientRequest.emit (node:domain:489:12) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27) |
netatmo.0 | 4577 | 2022-12-09 12:22:18.027 | info | CO-Sensor: Registering realtime events with Socket instance |
netatmo.0 | 4577 | 2022-12-09 12:22:17.907 | info | Successfully authenticated with Netatmo with individual client-ID 632f814bbfdxxxx |
netatmo.0 | 4577 | 2022-12-09 12:22:18.027 | info | CO-Sensor: Registering realtime events with Socket instance |
netatmo.0 | 4577 | 2022-12-09 12:22:17.907 | info | Successfully authenticated with Netatmo with individual client-ID 632f814bbfd08644dxxxx |
netatmo.0 | 4577 | 2022-12-09 12:22:17.906 | info | API Warning: Authenticate refresh error: invalid_grant |
netatmo.0 | 4577 | 2022-12-09 12:22:17.906 | info | API Warning: Authenticate refresh error: invalid_grant |
netatmo.0 | 4577 | 2022-12-09 12:22:17.651 | info | Authenticating with Netatmo using individual client-ID 632f814bbfd08644dxxxx |
netatmo.0 | 4577 | 2022-12-09 12:22:17.649 | info | Using stored tokens to initialize ... {"access_token":"5bfc3e150d0e230a00xxxx|b6f4a8bff3513d5b8acb0442exxxx","refresh_token":"5bfc3e150d0e230a00xxxx|7b241df8a67aa0946ff9bfb50xxxx","scope":"read_carbonmonoxidedetector read_station","client_id":"632f814bbfd08644d80xxxx"} |
netatmo.0 | 4577 | 2022-12-09 12:22:17.651 | info | Authenticating with Netatmo using individual client-ID 632f814bbfd08644d80xxxx |
netatmo.0 | 4577 | 2022-12-09 12:22:17.649 | info | Using stored tokens to initialize ... {"access_token":"5bfc3e150d0e230a00xxxx|b6f4a8bff3513d5b8acb0442edxxxx","refresh_token":"5bfc3e150d0e230a008xxxx|7b241df8a67aa0946ff9bfb50dxxxxx","scope":"read_carbonmonoxidedetector read_station","client_id":"632f814bbfd08644d80xxxx"} |
netatmo.0 | 4577 | 2022-12-09 12:22:17.619 | info | starting. Version 2.1.2 in /opt/iobroker/node_modules/iobroker.netatmo, node: v16.18.1, js-controller: 4.0.23 |
netatmo.0 | 4577 | 2022-12-09 12:22:17.619 | info | starting. Version 2.1.2 in /opt/iobroker/node_modules/iobroker.netatmo, node: v16.18.1, js-controller: 4.0.23 |
Ja wir sind noch dran
FYI Das ist der Plan. https://forum.iobroker.net/post/906953
Diskussion bitte auch dort falls nötig
v3.0.0 geht jetzt raus --> https://forum.iobroker.net/post/909957