WICHTIGE Info für Nutzer des RWE-SmartHome Adapters (Innogy-SmartHome)!

[Rainer08]

Hallo PArt,

erstmal "Daumen hoch" für Deine Arbeit.

Ich habe iobroker erst seit zwei Wochen im Einsatz und das auch nur als Connector zum Innogy-System.

Heute habe ich folgende Fehler-Meldungen im Log gefunden:

! innogy-smarthome.0 2017-02-02 20:07:47.394 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at TLSWrap.onread (net.js:523:20)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at TLSSocket.Readable.push (_stream_readable.js:110:10)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at readableAddChunk (_stream_readable.js:146:16)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at TLSSocket.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at TLSSocket.socketOnData (_http_client.js:302:20)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:412:21)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at ClientRequest.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at ClientRequest.g (events.js:260:16)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error at ClientRequest.response (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/node_modules/ws/lib/WebSocket.js:719:15)
! innogy-smarthome.0 2017-02-02 20:07:47.392 error STACK:Error: unexpected server response (503)
! innogy-smarthome.0 2017-02-02 20:07:47.390 error GOT AN ERROR:{}
! innogy-smarthome.0 2017-02-02 20:07:37.321 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at TLSWrap.onread (net.js:523:20)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at TLSSocket.Readable.push (_stream_readable.js:110:10)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at readableAddChunk (_stream_readable.js:146:16)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at TLSSocket.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at TLSSocket.socketOnData (_http_client.js:302:20)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:412:21)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at ClientRequest.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at ClientRequest.g (events.js:260:16)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error at ClientRequest.response (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/node_modules/ws/lib/WebSocket.js:719:15)
! innogy-smarthome.0 2017-02-02 20:07:37.320 error STACK:Error: unexpected server response (503)
! innogy-smarthome.0 2017-02-02 20:07:37.317 error GOT AN ERROR:{}
! innogy-smarthome.0 2017-02-02 20:07:26.940 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at TLSWrap.onread (net.js:523:20)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at TLSSocket.Readable.push (_stream_readable.js:110:10)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at readableAddChunk (_stream_readable.js:146:16)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at TLSSocket.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at TLSSocket.socketOnData (_http_client.js:302:20)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:412:21)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at ClientRequest.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at ClientRequest.g (events.js:260:16)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error at ClientRequest.response (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/node_modules/ws/lib/WebSocket.js:719:15)
! innogy-smarthome.0 2017-02-02 20:07:26.939 error STACK:Error: unexpected server response (503)
! innogy-smarthome.0 2017-02-02 20:07:26.936 error GOT AN ERROR:{}
! innogy-smarthome.0 2017-02-02 20:07:16.877 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at TLSWrap.onread (net.js:523:20)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at TLSSocket.Readable.push (_stream_readable.js:110:10)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at readableAddChunk (_stream_readable.js:146:16)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at TLSSocket.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at TLSSocket.socketOnData (_http_client.js:302:20)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:412:21)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at ClientRequest.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at ClientRequest.g (events.js:260:16)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error at ClientRequest.response (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/node_modules/ws/lib/WebSocket.js:719:15)
! innogy-smarthome.0 2017-02-02 20:07:16.875 error STACK:Error: unexpected server response (503)
! innogy-smarthome.0 2017-02-02 20:07:16.873 error GOT AN ERROR:{}
! innogy-smarthome.0 2017-02-02 20:07:06.784 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at TLSWrap.onread (net.js:523:20)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at TLSSocket.Readable.push (_stream_readable.js:110:10)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at readableAddChunk (_stream_readable.js:146:16)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at TLSSocket.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at TLSSocket.socketOnData (_http_client.js:302:20)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:412:21)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at ClientRequest.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at ClientRequest.g (events.js:260:16)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error at ClientRequest.response (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/node_modules/ws/lib/WebSocket.js:719:15)
! innogy-smarthome.0 2017-02-02 20:07:06.783 error STACK:Error: unexpected server response (503)
! innogy-smarthome.0 2017-02-02 20:07:06.780 error GOT AN ERROR:{}
! innogy-smarthome.0 2017-02-02 20:06:56.692 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at TLSWrap.onread (net.js:523:20)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at TLSSocket.Readable.push (_stream_readable.js:110:10)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at readableAddChunk (_stream_readable.js:146:16)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at TLSSocket.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at TLSSocket.socketOnData (_http_client.js:302:20)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:412:21)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at ClientRequest.emit (events.js:169:7)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at emitOne (events.js:77:13)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at ClientRequest.g (events.js:260:16)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error at ClientRequest.response (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/node_modules/ws/lib/WebSocket.js:719:15)
! innogy-smarthome.0 2017-02-02 20:06:56.692 error STACK:Error: unexpected server response (503)
! innogy-smarthome.0 2017-02-02 20:06:56.689 error GOT AN ERROR:{}
! innogy-smarthome.0 2017-02-02 20:06:46.614 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:06:46.613 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 20:06:46.613 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 20:06:46.613 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 20:06:46.613 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 20:05:19.745 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:05:19.744 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 20:05:19.744 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 20:05:19.744 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 20:05:19.743 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 20:04:43.774 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:04:43.773 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 20:04:43.773 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 20:04:43.773 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 20:04:43.773 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 20:04:21.445 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:04:21.444 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 20:04:21.444 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 20:04:21.444 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 20:04:21.443 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 20:03:19.836 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:03:19.835 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 20:03:19.835 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 20:03:19.835 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 20:03:19.833 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 20:02:20.435 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:02:20.434 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 20:02:20.434 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 20:02:20.434 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 20:02:20.433 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 20:01:18.835 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:01:18.835 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 20:01:18.835 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 20:01:18.835 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 20:01:18.834 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 20:00:38.296 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 20:00:38.295 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 20:00:38.295 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 20:00:38.295 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 20:00:38.294 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 19:59:14.781 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 19:59:14.780 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 19:59:14.780 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 19:59:14.780 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 19:59:14.779 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 19:58:17.869 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 19:57:15.941 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 19:57:15.940 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 19:57:15.940 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 19:57:15.940 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 19:57:15.939 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 19:56:33.793 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 19:55:59.810 error GOT AN ERROR:{'error':'closing socket','code':1006}
! innogy-smarthome.0 2017-02-02 19:55:59.808 error at TLSWrap.onread (net.js:544:26)
! innogy-smarthome.0 2017-02-02 19:55:59.808 error at exports._errnoException (util.js:870:11)
! innogy-smarthome.0 2017-02-02 19:55:59.808 error STACK:Error: read ECONNRESET
! innogy-smarthome.0 2017-02-02 19:55:59.805 error GOT AN ERROR:{'code':'ECONNRESET','errno':'ECONNRESET','syscall':'read'}
! innogy-smarthome.0 2017-02-02 19:55:11.197 error GOT AN ERROR:{'error':'closing socket','code':1006}

Vielleicht kannst Du Dir einen Reim darauf machen.

Gruß

Rainer

[PArt]

Ihr erratet es nie, aber die API ist gerade down

Super Gelegenheit mal wieder den Adapter zu patchen … Ich habe nun einen reconnect eingebaut, der erkennt, wenn keine States mehr kommen!

Update sollte in ein paar Minuten verfügbar sein bzw. dann, wenns bei mir sauber reconnected

[torstenh]

…..passiert ja nicht so oft! :lol:

[torstenh]

DITO!" Ihr werdet es kaum glauben…..." :lol: :lol: :lol:

Heute wieder!

PArt,

in der Version 0.1.7 ist der Adapter "gelb"? Aber verbunden bin ich.... (Verbunden mit Innogy=falsch)

Hat das eine Bedeutung?

"Mit diesem Hersteller ist man bestraft genug"

Grüße,

Torsten

[PArt]

Das gelbe Icon deutet darauf hin, das die Socket Verbindung nicht aktiv ist, ergo du keine RealtimeUpdates erhältst. Das sollte der Adapter aber eigentlich erkennen und dann neu starten bzw. die Init-Funktion erneut aufrufen (alle 10 Minuten)

Schau mal im log, ob du ein CLOSED oder DISCONNECTED ohne entsprechendes CONNECT findest und hier eventuell wieder mal eine neue Fehlermeldung ausgegeben wird

[PArt]

Anscheinend sind beim gestrigen Update der API die RefreshToken "kaputt" gegangen. Mein Adapter konnte sich ebenfalls nicht mehr sauber verbinden. Sollte er bei euch immer noch gelb sein, dann einfach noch einmal authorisieren

Sorry, ich wünschte auch, das wir so langsam mal ne stabile Version hätten

[csamaggi]

Irgendwie scheint es noch immer Probleme mit der Authorizierung.

Erst wenn ich mein iobroker PI neustartet dann geht es wieder einige Stunden, dann irgendwann wird die Lampe gelb und ich muss dann die ioBroker Instanz neu starten.

MFG Maggi

[PArt]

Hi, ja das habe ich gerade auch gesehen und gedebuggt.

Anscheinend ist mit dem letzten Update der Zentrale die Funktion APIseitig gekillt worden, mit der man Sessions beendet. Hierdurch konnte sich der Adapter nicht neu verbinden, da die vom Adapter erzeugte Session ebenfalls nicht sauber wieder neu reinitialisiert werden konnte.

Ich habe jetzt einen Workaround für dieses Problem eingebaut und den Fehler an Innogy gemeldet!

[torstenh]

Hallo PArt,

…ich kann mich heute nicht mehr autorisieren?

App funktioniert aber auch nicht :mrgreen:

Grüße,

Torsten

[torstenh]

Hallo zusammen,

ich habe jetzt auch einen UP Dimmer aber ich bekomme ihn nicht zum laufen. Lesend kann ich zugreifen aber schreiben nicht.

! {
! "type": "state",
! "common": {
! "name": "DimLevel",
! "type": "string",
! "role": "unknown",
! "read": true,
! "write": true
! },
! "native": {
! "id": "c2de7736b3de4347a1f06c8b746eebb4",
! "type": "/types/percent"
! },
! "_id": "innogy-smarthome.0.Wohnzimmer.Wandleuchte.DimLevel",
! "acl": {
! "object": 1638,
! "state": 1638
! }
! }

Kann mir jemand helfen?

Grüße,

Torsten

[PArt]

Percent kann der Adapter noch nicht … Bau ich dir nächste Woche ein!

Bin leider diese Woche beruflich unterwegs und kann nichts testen, sorry

Und das Authorisieren hängt natürlich mit der API zusammen, kanns die App auch nicht, ist leider sense

[torstenh]

Hallo PArt,

ja OK geht klar! Danke dir für die Hilfe! :roll:

…und wie soll es anders sein als das Innogy einen Strich durch die Rechnung macht! Ich dachte es mir schon...... :lol:

Grüße,

Torsten

[PArt]

Dieses Mal muss ich die Jungs in Schutz nehmen, ich hab noch keine Percentage Werte eingebaut

[torstenh]

…ich meinte nur den reconnect! Der funktioniert auch noch nicht so wie man es sich wünschen würde!

Grüße,

Torsten

[PArt]

Update ist raus!

Kannst du mir bitte noch einmal dein Log posten?

Der Adapter läuft bei mir seit gut 1 Woche ohne Probleme durch

[torstenh]

Hallo PArt,

ich habe ja auch das Problem mit der App das sie sich nicht reconnected. Ich habe jetzt das Update rübergespielt und er funktioniert (Dimmer) sobald ich wieder ein Log habe poste ich ihn hier.

Eigenartig aber hat bestimmt nichts miteinander zu tun, wenn ich mich über die App anmelde funktioniert die Anmeldung über den Adapter sonst bleibt er gelb. Vltt bin ich auch zu ungeduldig? …..und starte dann den Adapter zu früh wieder neu...

Grüße,

Torsten

[torstenh]

Hallo PArt,

Hatte heute wieder ein Problem mit reconnect.

! innogy-smarthome.0 2017-02-19 04:33:56.364 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-19 04:33:26.350 warn Adapter is not connected … Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-19 04:28:56.345 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-19 04:28:26.330 warn Adapter is not connected ... Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-19 04:23:56.342 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-19 04:23:26.312 warn Adapter is not connected ... Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-19 04:18:56.307 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-19 04:18:26.293 warn Adapter is not connected ... Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-19 04:13:56.288 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-19 04:13:26.273 warn Adapter is not connected ... Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-19 04:08:56.268 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-19 04:08:26.254 warn Adapter is not connected ... Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-19 04:03:56.249 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-19 04:03:26.235 warn Adapter is not connected ... Will recheck in 30 seconds!

App war auch nicht erreichbar, erst nach Neustart des Adapters hat er sich wieder verbunden

Grüße,

Torsten

[PArt]

Sonst hast du nichts im Log? Hm, sehr komisch…

[torstenh]

Hallo PArt,

also heute noch einmal getestet da ich keinen reconnect hinbekommen habe. Es ist wirklich so das ich erst reconnecten kann wenn ich mich bei der App angemeldet habe.

! innogy-smarthome.0 2017-02-20 17:31:42.218 info starting. Version 0.1.11 in C:/ioBroker/node_modules/iobroker.innogy-smarthome
! innogy-smarthome.0 2017-02-20 17:31:41.859 error no connection to objects DB
! host.POETNITZ15 2017-02-20 17:31:33.482 info instance system.adapter.innogy-smarthome.0 started with pid 9728
! host.POETNITZ15 2017-02-20 17:31:30.970 info instance system.adapter.innogy-smarthome.0 terminated with code null ()
! host.POETNITZ15 2017-02-20 17:31:30.970 warn instance system.adapter.innogy-smarthome.0 terminated due to SIGTERM
! host.POETNITZ15 2017-02-20 17:31:30.955 info stopInstance system.adapter.innogy-smarthome.0 killing pid 8580
! host.POETNITZ15 2017-02-20 17:31:30.955 info stopInstance system.adapter.innogy-smarthome.0
! host.POETNITZ15 2017-02-20 17:31:30.955 info object change system.adapter.innogy-smarthome.0
! host.POETNITZ15 2017-02-20 17:31:26.103 info instance system.adapter.innogy-smarthome.0 started with pid 8580
! host.POETNITZ15 2017-02-20 17:30:56.073 info Restart adapter system.adapter.innogy-smarthome.0 because enabled
! host.POETNITZ15 2017-02-20 17:30:56.073 error instance system.adapter.innogy-smarthome.0 terminated with code 0 (OK)
! innogy-smarthome.0 2017-02-20 17:30:56.026 info cleaned everything up…
! Error: 2017-02-20 17:30:56.011 error at Promise._settlePromises (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\simple-oauth2\node_modules\bluebird\js\main\promise.js:700:14)
! Error: 2017-02-20 17:30:56.011 error at Promise._settlePromiseAt (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\simple-oauth2\node_modules\bluebird\js\main\promise.js:582:21)
! Error: 2017-02-20 17:30:56.011 error at Promise.successAdapter (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\simple-oauth2\node_modules\bluebird\js\main\nodeify.js:23:30)
! Error: 2017-02-20 17:30:56.011 error at tryCatcher (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\simple-oauth2\node_modules\bluebird\js\main\util.js:26:23)
! Error: 2017-02-20 17:30:56.011 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:43:17
! Error: 2017-02-20 17:30:56.011 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\main.js:35:31
! Error: 2017-02-20 17:30:56.011 error at SmartHome.init (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:84:17)
! Error: 2017-02-20 17:30:56.011 error at SmartHome._initialize (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:293:12)
! Error: 2017-02-20 17:30:56.011 error at new Promise (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:77:14)
! Error: 2017-02-20 17:30:56.011 error at Promise._resolveFromExecutor (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:481:18)
! Error: 2017-02-20 17:30:56.011 error at Promise.cancellationExecute [as _execute] (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\debuggability.js:321:9)
! Error: 2017-02-20 17:30:56.011 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:294:25
! Error: 2017-02-20 17:30:56.011 error at Requestor.call (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:42:17)
! Error: 2017-02-20 17:30:56.011 error at Requestor.doRequest (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:48:12)
! Error: 2017-02-20 17:30:56.011 error at new Promise (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:77:14)
! Error: 2017-02-20 17:30:56.011 error at Promise._resolveFromExecutor (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:481:18)
! Error: 2017-02-20 17:30:56.011 error at Promise.cancellationExecute [as _execute] (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\debuggability.js:321:9)
! Error: 2017-02-20 17:30:56.011 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:49:22
! Error: 2017-02-20 17:30:56.011 error at Object.getAuthorizationStatus (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:171:20)
! Error: 2017-02-20 17:30:56.011 error at getAuthorizationStatus (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:161:13)
! Error: 2017-02-20 17:30:56.011 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:51:41
! Error: 2017-02-20 17:30:56.011 error at Object.startAuthorization (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:174:20)
! Error: 2017-02-20 17:30:56.011 error at startAuthorization (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:55:26)
! Error: 2017-02-20 17:30:56.011 error at Server.listen (net.js:1391:5)
! Error: 2017-02-20 17:30:56.011 error at listen (net.js:1295:10)
! Error: 2017-02-20 17:30:56.011 error at Server._listen2 (net.js:1259:14)
! Error: 2017-02-20 17:30:56.011 error at exports._exceptionWithHostPort (util.js:1045:20)
! Error: 2017-02-20 17:30:56.011 error at Object.exports._errnoException (util.js:1022:11)
! Error: 2017-02-20 17:30:56.011 error listen EADDRINUSE :::3000
! uncaught 2017-02-20 17:30:56.011 error exception: listen EADDRINUSE :::3000
! innogy-smarthome.0 2017-02-20 17:30:55.980 warn Adapter is not configured or needs reauthorization! Please go to the adapter settings and start the authorization
! innogy-smarthome.0 2017-02-20 17:27:16.923 warn Adapter is not configured or needs reauthorization! Please go to the adapter settings and start the authorization
! innogy-smarthome.0 2017-02-20 17:26:32.727 info starting. Version 0.1.11 in C:/ioBroker/node_modules/iobroker.innogy-smarthome
! innogy-smarthome.0 2017-02-20 17:26:32.290 error no connection to objects DB
! host.POETNITZ15 2017-02-20 17:26:12.495 info instance system.adapter.innogy-smarthome.0 started with pid 9348
! host.POETNITZ15 2017-02-20 17:26:09.983 info instance system.adapter.innogy-smarthome.0 terminated with code null ()
! host.POETNITZ15 2017-02-20 17:26:09.983 warn instance system.adapter.innogy-smarthome.0 terminated due to SIGTERM
! host.POETNITZ15 2017-02-20 17:26:09.937 info stopInstance system.adapter.innogy-smarthome.0 killing pid 4472
! host.POETNITZ15 2017-02-20 17:26:09.937 info stopInstance system.adapter.innogy-smarthome.0
! host.POETNITZ15 2017-02-20 17:26:09.921 info object change system.adapter.innogy-smarthome.0
! innogy-smarthome.0 2017-02-20 17:26:00.451 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-20 17:25:30.436 warn Adapter is not connected … Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-20 17:21:00.430 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-20 17:20:30.415 warn Adapter is not connected ... Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-20 17:16:00.409 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-20 17:15:30.395 warn Adapter is not connected ... Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-20 17:11:00.388 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-20 17:10:30.374 warn Adapter is not connected ... Will recheck in 30 seconds!
! innogy-smarthome.0 2017-02-20 17:06:00.368 warn Adapter is still not connected to the Innogy API, restarting!
! innogy-smarthome.0 2017-02-20 17:05:30.354 warn Adapter is not connected ... Will recheck in 30 seconds!

hier mein log!

Grüße,

Torsten

[csamaggi]

Guten Morgen,

muss sagen der Adapter läuft echt gut.

Mal eine Frage ist es eigentlich möglich auch den Batteriestatus der Geräte abzufragen?

MFG Maggi