NEWS
WICHTIGE Info für Nutzer des RWE-SmartHome Adapters (Innogy-SmartHome)!
-
Hallo PArt,
…ich kann mich heute nicht mehr autorisieren?
App funktioniert aber auch nicht :mrgreen:
Grüße,
Torsten
-
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
-
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
-
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
-
Dieses Mal muss ich die Jungs in Schutz nehmen, ich hab noch keine Percentage Werte eingebaut
-
…ich meinte nur den reconnect! Der funktioniert auch noch nicht so wie man es sich wünschen würde!
Grüße,
Torsten
-
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
-
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
-
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
-
Sonst hast du nichts im Log? Hm, sehr komisch…
-
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
-
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
-
Hallo Part,
hier noch einmal ein log:
! host.POETNITZ15 2017-02-22 20:15:41.638 info Restart adapter system.adapter.innogy-smarthome.0 because enabled
! host.POETNITZ15 2017-02-22 20:15:41.638 error instance system.adapter.innogy-smarthome.0 terminated with code 0 (OK)
! innogy-smarthome.0 2017-02-22 20:15:41.576 info cleaned everything up…
! Error: 2017-02-22 20:15:41.576 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-22 20:15:41.576 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-22 20:15:41.576 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-22 20:15:41.576 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-22 20:15:41.576 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:43:17
! Error: 2017-02-22 20:15:41.576 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\main.js:35:31
! Error: 2017-02-22 20:15:41.576 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-22 20:15:41.576 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-22 20:15:41.576 error at new Promise (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:77:14)
! Error: 2017-02-22 20:15:41.576 error at Promise._resolveFromExecutor (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:481:18)
! Error: 2017-02-22 20:15:41.576 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-22 20:15:41.576 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:294:25
! Error: 2017-02-22 20:15:41.576 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-22 20:15:41.576 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-22 20:15:41.576 error at new Promise (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:77:14)
! Error: 2017-02-22 20:15:41.576 error at Promise._resolveFromExecutor (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:481:18)
! Error: 2017-02-22 20:15:41.576 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-22 20:15:41.576 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:49:22
! Error: 2017-02-22 20:15:41.576 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-22 20:15:41.576 error at getAuthorizationStatus (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:161:13)
! Error: 2017-02-22 20:15:41.576 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:51:41
! Error: 2017-02-22 20:15:41.576 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-22 20:15:41.576 error at startAuthorization (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:55:26)
! Error: 2017-02-22 20:15:41.576 error at Server.listen (net.js:1391:5)
! Error: 2017-02-22 20:15:41.576 error at listen (net.js:1295:10)
! Error: 2017-02-22 20:15:41.576 error at Server._listen2 (net.js:1259:14)
! Error: 2017-02-22 20:15:41.576 error at exports._exceptionWithHostPort (util.js:1045:20)
! Error: 2017-02-22 20:15:41.576 error at Object.exports._errnoException (util.js:1022:11)
! Error: 2017-02-22 20:15:41.576 error listen EADDRINUSE :::3000
! uncaught 2017-02-22 20:15:41.576 error exception: listen EADDRINUSE :::3000Grüße,
Torsten
-
Bei dir geht anscheinend die Authorisierung flöten!
Der Fehler tritt im Moment auf, da der Auth-Service anscheinend mehrfach gestartet ist … Schau ich mir auf jeden Fall noch einmal an.
Und nein, die Batterie kann man leider nicht auslesen, zumindest nicht, das ich wüsste
-
Hallo PArt,
ich habe aktuell das Problem, dass ich weder über die iobroker-Oberfläche noch über z.B. simple-api Werte auslesen kann.
Im Log steht nichts (also wirklich leer) und der Adapter zeigt auch grün an.
Lediglich in der Objekt-Darstellung wird der nicht mehr korrekte Werte rot dargestellt.
Bsp: Temp. am Heizkörper steht auf 7 Grad und wird auch so angezeigt. Ändere ich die am Thermostat auf 9 Grad, wird in der Objekt-Darstellung der Wert 7 rot gargestellt.
Ein Zugriff über simple-api liefert 7 Grad.
Starte ich den Adapter neu, dann geht's wieder.
Hast du eine Idee?
Gruß
Rainer
-
Hallo PArt,
hier noch ein log:
! Error: 2017-02-27 07:51:27.981 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-27 07:51:27.981 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-27 07:51:27.981 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-27 07:51:27.981 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-27 07:51:27.981 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:43:17
! Error: 2017-02-27 07:51:27.981 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\main.js:35:31
! Error: 2017-02-27 07:51:27.981 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-27 07:51:27.981 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-27 07:51:27.981 error at new Promise (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:77:14)
! Error: 2017-02-27 07:51:27.981 error at Promise._resolveFromExecutor (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:481:18)
! Error: 2017-02-27 07:51:27.981 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-27 07:51:27.981 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:294:25
! Error: 2017-02-27 07:51:27.981 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-27 07:51:27.981 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-27 07:51:27.981 error at new Promise (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:77:14)
! Error: 2017-02-27 07:51:27.981 error at Promise._resolveFromExecutor (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\bluebird\js\release\promise.js:481:18)
! Error: 2017-02-27 07:51:27.981 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-27 07:51:27.981 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:49:22
! Error: 2017-02-27 07:51:27.981 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-27 07:51:27.981 error at getAuthorizationStatus (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:161:13)
! Error: 2017-02-27 07:51:27.981 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:51:41
! Error: 2017-02-27 07:51:27.981 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-27 07:51:27.981 error at startAuthorization (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:55:26)
! Error: 2017-02-27 07:51:27.981 error at Server.listen (net.js:1391:5)
! Error: 2017-02-27 07:51:27.981 error at listen (net.js:1295:10)
! Error: 2017-02-27 07:51:27.981 error at Server._listen2 (net.js:1259:14)
! Error: 2017-02-27 07:51:27.981 error at exports._exceptionWithHostPort (util.js:1045:20)
! Error: 2017-02-27 07:51:27.981 error at Object.exports._errnoException (util.js:1022:11)
! Error: 2017-02-27 07:51:27.981 error listen EADDRINUSE :::3000
! uncaught 2017-02-27 07:51:27.981 error exception: listen EADDRINUSE :::3000Grüße,
Torsten
-
Hallo ihr zwei, danke für die Info…
@Rainer, kannst du den Adapter bitte mal auf Debug stellen?
Und Thorsten, den Fehler habe ich bis jetzt nur 1x gesehen ... Werde mir aber was einfallen lassen! Bei dir scheint aber die Authorisierung immer wieder flöten zu gehen!
Sorry, bin gerade etwas beruflich sehr eingespannt und kann deshalb leider nicht so an dem Adapter arbeiten, wie ich das gerne würde
-
Hallo PArt,
ich muss jetzt mal kleinlaut fragen, wie ich den Adapter auf Debug stellen kann?
Gruß
Rainer
-
Hallo Rainer,
im Reiter Instanzen, den Expertenmodus wählen und dann in der nun sichtbaren Spalte "Log Stufe" auf debug umschalten.
Gruß
Rainer
-
Hallo PArt,
ist kein Problem, ich muß michjeden Tag neu anmelden aber das geht schon. Aufgefallen ist mir, das ich den Adapter neu starten muß und wenn ich ihn dann neu gestartet habe klappt die erste Anmeldung nicht. Wenn ich mich dann das zweite mal anmelde geht es wieder für einen Tag.
Grüße,
Torsten