Wartung am 15.11. – Forum ab 22:00 Uhr nicht erreichbar

[cash]

@Zefau Die Installation muss doch geklappt haben. Kann nun nur nicht mehr bei Bridge Polling auswählen?

Habe die Callback Datenpunkte manuell gelöscht und die ID manuell auf der Bridge gelöscht. Mit dem Neustart vom Adapter wird der Callback aber auch derzeit nicht angelegt. Es geht also quasi nichts mehr.

Update: Callback hat nach ein paar weiteren Versuchen wieder geklappt. Somit konnte ich den Opener auch wieder wie gewünscht bedienen. Habe aber nur Ring to Open getestet....

[Zefau]

@cash sagte in [Aufruf] Nuki-extended Adapter:

Kann nun nur nicht mehr bei Bridge Polling auswählen?

Habe ich entfernt. Das pollen hält die Nuki Bridge einfach nicht aus. Ist leider kein gutes Stück Hardware.

[miwe]

@Zefau Hi - hast Du möglicherweise einen Lösungsansatz zwischenzeitlich parat?

[Zefau]

@miwe sagte in [Aufruf] Nuki-extended Adapter:

hast Du möglicherweise einen Lösungsansatz zwischenzeitlich parat?

Probiere bitte nochmal die Github version.

[miwe]

@Zefau der Adapter startet nun nicht mehr. Log:

host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:189:7)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at <anonymous>
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at client.mget (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:488:13)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at states.getStates (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5587:17)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at adapter.getStates (/opt/iobroker/node_modules/iobroker.nuki-extended/nuki-extended.js:81:4)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at initNukiAPIs (/opt/iobroker/node_modules/iobroker.nuki-extended/nuki-extended.js:284:41)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at Array.map (<anonymous>)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: at adapter.config.bridges.map (/opt/iobroker/node_modules/iobroker.nuki-extended/nuki-extended.js:289:68)
host.iobroker 2019-10-25 06:41:15.081 error Caught by controller[0]: ReferenceError: bridge_ident is not defined

[Zefau]

@miwe sorry, v2.0.1 sollte es fixen.

[miwe]

@Zefau said in [Aufruf] Nuki-extended Adapter:

@miwe sorry, v2.0.1 sollte es fixen.

Hi, ich habe es hinbekommen - nun stellt sich jedoch folgende Frage:

Warum reagiert das Schloss erst beim 2ten mal? Beim ersten mal positive Rückmeldungen im Log, jedoch ohne Reaktion, beim 2ten mal ausösen funktioniert es. Verbindung zum Schloss ist gegeben und sehr gut.

P.S. - Ich teste mal ob sich dieses Problem mit der 2.01 erledigt hat.

[Zefau]

@miwe sagte in [Aufruf] Nuki-extended Adapter:

Warum reagiert das Schloss erst beim 2ten mal? Beim ersten mal positive Rückmeldungen im Log, jedoch ohne Reaktion, beim 2ten mal ausösen funktioniert es. Verbindung zum Schloss ist gegeben und sehr gut.

Kannst du das vollständige Log posten (ab Adapter-Start), sofern das noch auftritt?

[miwe]

@Zefau nuki-extended.0 2019-10-26 17:48:23.540 info (9733) Successfully triggered action -UNLOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 17:48:22.954 debug (9733) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":0,"ack":true,"ts":1572104902950,"q":0,"from":"system.adapter.nuki-extended.0","user":"system.user.admin","lc":1572104
nuki-extended.0 2019-10-26 17:48:22.951 debug (9733) Action applied on Bridge API.
nuki-extended.0 2019-10-26 17:48:22.951 info (9733) Trigger action -UNLOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 17:48:22.950 debug (9733) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":1,"ack":false,"ts":1572104902949,"q":0,"from":"system.adapter.scenes.0","user":"system.user.admin","lc":1572104902949
admin.0 2019-10-26 17:48:16.872 info (3355) successful connection to socket.io from ::ffff:192.168.2.45
admin.0 2019-10-26 17:48:11.865 info (3355) successful connection to socket.io from ::ffff:192.168.2.45
nuki-extended.0 2019-10-26 17:47:51.836 info (9733) Listening for Nuki events on port 51989.
nuki-extended.0 2019-10-26 17:47:51.830 debug (9733) Callback (with URL http://192.168.2.53:51989/nuki-api-bridge) already attached to Nuki Bridge with name Nuki .
nuki-extended.0 2019-10-26 17:47:51.829 debug (9733) Retrieved current callbacks from Nuki Bridge with name Nuki .
nuki-extended.0 2019-10-26 17:47:51.464 debug (9733) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":0,"ack":true,"ts":1572104871421,"q":0,"from":"system.adapter.nuki-extended.0","user":"system.user.admin","lc":1572104
nuki-extended.0 2019-10-26 17:47:51.454 debug (9733) Updating device smartlocks.wohnungstür with payload: {"deviceType":0,"nukiId":449894709,"name":"Wohnungstür","bridge":"1092735473","state":{"mode":2,"state":1,"batteryCritical":false,"timestam
nuki-extended.0 2019-10-26 17:47:51.454 debug (9733) Updating device openers.haustür with payload: {"deviceType":2,"nukiId":455049994,"name":"Haustür","bridge":"1092735473","state":{"mode":3,"state":1,"batteryCritical":false,"timestamp":"2019-10
nuki-extended.0 2019-10-26 17:47:51.453 debug (9733) getBridgeApi(): [{"deviceType":2,"nukiId":455049994,"name":"Haustür","lastKnownState":{"mode":3,"state":1,"stateName":"online","batteryCritical":false,"timestamp":"2019-10-26T14:36:44+00:00"},
nuki-extended.0 2019-10-26 17:47:51.421 debug (9733) Updating device smartlocks.wohnungstür with payload: {"smartlockId":449894709,"accountId":2145826587,"authId":3431686,"name":"Wohnungstür","favorite":false,"config":{"name":"Wohnungstür","lati
nuki-extended.0 2019-10-26 17:47:51.417 debug (9733) Updating device openers.haustür with payload: {"smartlockId":9044984586,"accountId":2145826587,"authId":3431647,"name":"Haustür","favorite":false,"config":{"name":"Haustür","latitude":50.8858,
nuki-extended.0 2019-10-26 17:47:51.416 debug (9733) getWebApi(): [{"smartlockId":9044984586,"accountId":2145826587,"type":2,"authId":3431647,"name":"Haustür","favorite":false,"config":{"name":"Haustür","latitude":50.8858,"longitude":12.064853,"
nuki-extended.0 2019-10-26 17:47:51.158 info (9733) Polling Nuki Web API deactivated.
nuki-extended.0 2019-10-26 17:47:51.115 info (9733) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.nuki-extended, node: v10.17.0
nuki-extended.0 2019-10-26 17:47:50.688 debug (9733) States connected to redis: 127.0.0.1:9000
nuki-extended.0 2019-10-26 17:47:50.643 debug (9733) statesDB connected
nuki-extended.0 2019-10-26 17:47:50.640 debug (9733) Objects connected to redis: 127.0.0.1:9001
nuki-extended.0 2019-10-26 17:47:50.639 debug (9733) Redis States: Use Redis connection: 127.0.0.1:9000
nuki-extended.0 2019-10-26 17:47:50.638 debug (9733) objectDB connected
nuki-extended.0 2019-10-26 17:47:50.610 debug (9733) Redis Objects: Use Redis connection: 127.0.0.1:9001
host.iobroker 2019-10-26 17:47:50.169 info instance system.adapter.nuki-extended.0 started with pid 9733

[Zefau]

@miwe das Log sieht gut aus. Ist in dem Log der Fehler enthalten, dass das Schloss erst beim zweiten Mal reagiert? Es erscheint ja richtigerweise nur eine Erfolgsmeldung.

In dem Log wird _ACTION 1x mit Wert "1" getriggert (und 2x auf "0" resettet).

[miwe]

@Zefau Was sagt mir das? Ich kann damit nichts anfangen. Ich möchte das Schloss über die Szenen des IOBROKERS steuern. Was muss ich hier machen?

[miwe]

@Zefau said in [Aufruf] Nuki-extended Adapter:

@miwe das Log sieht gut aus. Ist in dem Log der Fehler enthalten, dass das Schloss erst beim zweiten Mal reagiert? Es erscheint ja richtigerweise nur eine Erfolgsmeldung.

In dem Log wird _ACTION 1x mit Wert "1" getriggert (und 2x auf "0" resettet).
nuki-extended.0 2019-10-26 17:52:36.348 debug (9733) system.adapter.admin.0: logging false
nuki-extended.0 2019-10-26 17:52:18.545 debug (9733) system.adapter.admin.0: logging true
nuki-extended.0 2019-10-26 17:52:14.647 debug (9733) system.adapter.admin.0: logging false
admin.0 2019-10-26 17:51:21.169 info (3355) successful connection to socket.io from ::ffff:192.168.2.45
nuki-extended.0 2019-10-26 17:49:48.716 debug (9733) Updating device smartlocks.wohnungstür with payload: {"smartlockId":449894709,"accountId":2145826587,"authId":3431686,"name":"Wohnungstür","favorite":false,"config":{"name":"Wohnungstür","lati
nuki-extended.0 2019-10-26 17:49:48.710 debug (9733) Updating device openers.haustür with payload: {"smartlockId":9044984586,"accountId":2145826587,"authId":3431647,"name":"Haustür","favorite":false,"config":{"name":"Haustür","latitude":50.8858,
nuki-extended.0 2019-10-26 17:49:48.710 debug (9733) getWebApi(): [{"smartlockId":9044984586,"accountId":2145826587,"type":2,"authId":3431647,"name":"Haustür","favorite":false,"config":{"name":"Haustür","latitude":50.8858,"longitude":12.064853,"
nuki-extended.0 2019-10-26 17:49:48.344 debug (9733) Updating device smartlocks.wohnungstür with payload: {"nukiId":449894709,"state":{"deviceType":0,"mode":2,"state":3,"batteryCritical":false,"timestamp":"2019-10-26T15:49:48+00:00","locked":3},
nuki-extended.0 2019-10-26 17:49:48.343 debug (9733) Received payload via callback: {"nukiId":449894709,"state":{"deviceType":0,"mode":2,"state":3,"stateName":"unlocked","batteryCritical":false,"timestamp":"2019-10-26T15:49:48+00:00"}}
nuki-extended.0 2019-10-26 17:49:24.417 info (9733) Successfully triggered action -UNLOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 17:49:17.412 debug (9733) Action applied on Bridge API.
nuki-extended.0 2019-10-26 17:49:17.412 info (9733) Trigger action -UNLOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 17:49:17.412 debug (9733) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":1,"ack":false,"ts":1572104957410,"q":0,"from":"system.adapter.scenes.0","user":"system.user.admin","lc":1572104953664
nuki-extended.0 2019-10-26 17:49:14.079 info (9733) Successfully triggered action -UNLOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 17:49:13.666 debug (9733) Action applied on Bridge API.
nuki-extended.0 2019-10-26 17:49:13.666 info (9733) Trigger action -UNLOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 17:49:13.665 debug (9733) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":1,"ack":false,"ts":1572104953664,"q":0,"from":"system.adapter.scenes.0","user":"system.user.admin","lc":1572104953664
admin.0 2019-10-26 17:49:08.829 info (3355) successful connection to socket.io from ::ffff:192.168.2.45
admin.0 2019-10-26 17:49:05.115 info (3355) successful connection to socket.io from ::ffff:192.168.2.45
nuki-extended.0 2019-10-26 17:48:23.540 info (9733) Successfully triggered action -UNLOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 17:48:22.954 debug (9733) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":0,"ack":true,"ts":1572104902950,"q":0,"from":"system.adapter.nuki-extended.0","user":"system.user.admin","lc":1572104
nuki-extended.0 2019-10-26 17:48:22.951 debug (9733) Action applied on Bridge API.
nuki-extended.0 2019-10-26 17:48:22.951 info (9733) Trigger action -UNLOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 17:48:22.950 debug (9733) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":1,"ack":false,"ts":1572104902949,"q":0,"from":"system.adapter.scenes.0","user":"system.user.admin","lc":1572104902949
admin.0 2019-10-26 17:48:16.872 info (3355) successful connection to socket.io from ::ffff:192.168.2.45
admin.0 2019-10-26 17:48:11.865 info (3355) successful connection to socket.io from ::ffff:192.168.2.45
nuki-extended.0 2019-10-26 17:47:51.836 info (9733) Listening for Nuki events on port 51989.
nuki-extended.0 2019-10-26 17:47:51.830 debug (9733) Callback (with URL http://192.168.2.53:51989/nuki-api-bridge) already attached to Nuki Bridge with name Nuki .
nuki-extended.0 2019-10-26 17:47:51.829 debug (9733) Retrieved current callbacks from Nuki Bridge with name Nuki .
nuki-extended.0 2019-10-26 17:47:51.464 debug (9733) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":0,"ack":true,"ts":1572104871421,"q":0,"from":"system.adapter.nuki-extended.0","user":"system.user.admin","lc":1572104
nuki-extended.0 2019-10-26 17:47:51.454 debug (9733) Updating device smartlocks.wohnungstür with payload: {"deviceType":0,"nukiId":449894709,"name":"Wohnungstür","bridge":"1092735473","state":{"mode":2,"state":1,"batteryCritical":false,"timestam
nuki-extended.0 2019-10-26 17:47:51.454 debug (9733) Updating device openers.haustür with payload: {"deviceType":2,"nukiId":455049994,"name":"Haustür","bridge":"1092735473","state":{"mode":3,"state":1,"batteryCritical":false,"timestamp":"2019-10
nuki-extended.0 2019-10-26 17:47:51.453 debug (9733) getBridgeApi(): [{"deviceType":2,"nukiId":455049994,"name":"Haustür","lastKnownState":{"mode":3,"state":1,"stateName":"online","batteryCritical":false,"timestamp":"2019-10-26T14:36:44+00:00"},
nuki-extended.0 2019-10-26 17:47:51.421 debug (9733) Updating device smartlocks.wohnungstür with payload: {"smartlockId":449894709,"accountId":2145826587,"authId":3431686,"name":"Wohnungstür","favorite":false,"config":{"name":"Wohnungstür","lati
nuki-extended.0 2019-10-26 17:47:51.417 debug (9733) Updating device openers.haustür with payload: {"smartlockId":9044984586,"accountId":2145826587,"authId":3431647,"name":"Haustür","favorite":false,"config":{"name":"Haustür","latitude":50.8858,
nuki-extended.0 2019-10-26 17:47:51.416 debug (9733) getWebApi(): [{"smartlockId":9044984586,"accountId":2145826587,"type":2,"authId":3431647,"name":"Haustür","favorite":false,"config":{"name":"Haustür","latitude":50.8858,"longitude":12.064853,"
nuki-extended.0 2019-10-26 17:47:51.158 info (9733) Polling Nuki Web API deactivated.
nuki-extended.0 2019-10-26 17:47:51.115 info (9733) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.nuki-extended, node: v10.17.0
nuki-extended.0 2019-10-26 17:47:50.688 debug (9733) States connected to redis: 127.0.0.1:9000
nuki-extended.0 2019-10-26 17:47:50.643 debug (9733) statesDB connected
nuki-extended.0 2019-10-26 17:47:50.640 debug (9733) Objects connected to redis: 127.0.0.1:9001
nuki-extended.0 2019-10-26 17:47:50.639 debug (9733) Redis States: Use Redis connection: 127.0.0.1:9000
nuki-extended.0 2019-10-26 17:47:50.638 debug (9733) objectDB connected
nuki-extended.0 2019-10-26 17:47:50.610 debug (9733) Redis Objects: Use Redis connection: 127.0.0.1:9001
host.iobroker 2019-10-26 17:47:50.169 info instance system.adapter.nuki-extended.0 started with pid 9733

Hier das komplette Log mit insgesamt 3 Versuchen . Es hat erst beim 3ten mal diesmals funktioniert.

[Zefau]

@miwe sagte in [Aufruf] Nuki-extended Adapter:

Ich kann damit nichts anfangen. Ich möchte das Schloss über die Szenen des IOBROKERS steuern. Was muss ich hier machen?

Kannst du mal versuchen in den Objekten beim State _ACTION manuell einen Wert (z.B. LOCK oder UNLOCK) zu wählen?

[miwe]

@Zefau Wie geht das? Ich bin da leider nicht so bewandert wie Du und habe keine Lust mir den Broker durch mein gefummel zu zerschiessen

[Zefau]

@miwe einfach in der Navigation Objekte wählen und dort zum State navigieren: nuki-extended.0.smartlocks.wohnungstür._ACTION. Dann rechts wo NO_ACTION(0) steht einen anderen Wert auswählen.

[miwe]

@Zefau

Das kommt dabei heraus - Schloss hat nicht reagiert,
nuki-extended.0 2019-10-26 18:02:28.341 debug (25155) system.adapter.admin.0: logging true
nuki-extended.0 2019-10-26 18:02:23.694 info (25155) Successfully triggered action -LOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 18:02:23.006 debug (25155) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":0,"ack":true,"ts":1572105743002,"q":0,"from":"system.adapter.nuki-extended.0","user":"system.user.admin","lc":157210
nuki-extended.0 2019-10-26 18:02:23.003 debug (25155) Action applied on Bridge API.
nuki-extended.0 2019-10-26 18:02:23.003 info (25155) Trigger action -LOCK- on Nuki Smartlock Wohnungstür (via Bridge API).
nuki-extended.0 2019-10-26 18:02:23.002 debug (25155) State of nuki-extended.0.smartlocks.wohnungstür._ACTION has changed {"val":2,"ack":false,"ts":1572105743000,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1572105743000
nuki-extended.0 2019-10-26 18:01:08.527 info (25155) Listening for Nuki events on port 51989.
nuki-extended.0 2019-10-26 18:01:08.521 debug (25155) Callback (with URL http://192.168.2.53:51989/nuki-api-bridge) already attached to Nuki Bridge with name Nuki .
nuki-extended.0 2019-10-26 18:01:08.520 debug (25155) Retrieved current callbacks from Nuki Bridge with name Nuki .
nuki-extended.0 2019-10-26 18:01:08.312 debug (25155) Updating device smartlocks.wohnungstür with payload: {"smartlockId":449894709,"accountId":2145826587,"authId":3431686,"name":"Wohnungstür","favorite":false,"config":{"name":"Wohnungstür","lat
nuki-extended.0 2019-10-26 18:01:08.308 debug (25155) Updating device openers.haustür with payload: {"smartlockId":9044984586,"accountId":2145826587,"authId":3431647,"name":"Haustür","favorite":false,"config":{"name":"Haustür","latitude":50.8858
nuki-extended.0 2019-10-26 18:01:08.307 debug (25155) getWebApi(): [{"smartlockId":9044984586,"accountId":2145826587,"type":2,"authId":3431647,"name":"Haustür","favorite":false,"config":{"name":"Haustür","latitude":50.8858,"longitude":12.064853,
nuki-extended.0 2019-10-26 18:01:08.141 debug (25155) Updating device smartlocks.wohnungstür with payload: {"deviceType":0,"nukiId":449894709,"name":"Wohnungstür","bridge":"1092735473","state":{"mode":2,"state":3,"batteryCritical":false,"timesta
nuki-extended.0 2019-10-26 18:01:08.140 debug (25155) Updating device openers.haustür with payload: {"deviceType":2,"nukiId":455049994,"name":"Haustür","bridge":"1092735473","state":{"mode":3,"state":1,"batteryCritical":false,"timestamp":"2019-1
nuki-extended.0 2019-10-26 18:01:08.139 debug (25155) getBridgeApi(): [{"deviceType":2,"nukiId":455049994,"name":"Haustür","lastKnownState":{"mode":3,"state":1,"stateName":"online","batteryCritical":false,"timestamp":"2019-10-26T14:36:44+00:00"}
nuki-extended.0 2019-10-26 18:01:07.885 info (25155) Polling Nuki Web API deactivated.
nuki-extended.0 2019-10-26 18:01:07.853 debug (25155) States connected to redis: 127.0.0.1:9000
nuki-extended.0 2019-10-26 18:01:07.842 info (25155) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.nuki-extended, node: v10.17.0
nuki-extended.0 2019-10-26 18:01:07.763 debug (25155) statesDB connected
nuki-extended.0 2019-10-26 18:01:07.760 debug (25155) Objects connected to redis: 127.0.0.1:9001
nuki-extended.0 2019-10-26 18:01:07.759 debug (25155) Redis States: Use Redis connection: 127.0.0.1:9000
nuki-extended.0 2019-10-26 18:01:07.758 debug (25155) objectDB connected
nuki-extended.0 2019-10-26 18:01:07.732 debug (25155) Redis Objects: Use Redis connection: 127.0.0.1:9001
host.iobroker 2019-10-26 18:01:07.312 info instance system.adapter.nuki-extended.0 started with pid 25155

[Zefau]

@miwe Und ging es beim ersten Mal?

[miwe]

@Zefau nein. Ich habe aber auch nur einmal probiert.

[miwe]

@Zefau Jetzt eben nochmal probiert - geht. Seltsam.

[miwe]

@miwe Bis jetzt funktioniert es plötzlich einwandfrei. Wunderheilung? Keine Ahnung. Ich beobachte mal weiter. Besten Dan für deine Mühen und gute Arbeit hier.