[ NUKI Smartlock ] 73_NUKIBridge.pm und 74_NUKDevice.pm

Begonnen von CoolTux, 18 Juli 2016, 23:50:11

Vorheriges Thema - Nächstes Thema

CoolTux

Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

CoolTux

@Cobra
Zitat
Hi!

Wenn du gar keine Callbacks bekommst: Hast du schon versucht, das Smart Lock aus der Bridge zu entfernen und neu zu pairen?

Das Szenario, dss überhaupt keine Callbacks mehr gehen (die mit v.1 noch funktioniert) haben, konnte ich nicht reproduzieren. Bei mir tritt das Problem tatsächlich nur bei Sperrungen via Bridge/HTTP API auf, wie es auch Niklas Neesen beschreibt.

lg,
Stephan

Kannst Du das bitte noch einmal verifizieren? Vielen Dank.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Cobra

#1082
Also ich habe jetzt folgendes gemacht:

Das Stmartlock aus der Bridge entfernt und neu hinzugefügt.
Danach nochmal Autocreate in FHEM (das alte Device in FHEM habe ich nicht gelöscht, somit wurde auch kein neues Device angelegt)
CallBack aus der Bridge und die Attribute im Device gelöscht und neu angelegt.

Leider immer noch selbes Spiel.
Hier das Log von der Bridge auch mit einmal Aufschließen und einmal Abschließen über die Nuki-App:

timestamp: 2018-11-14T09:44:12+00:00 type: HTTP-Log
timestamp: 2018-11-14T09:44:12+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T09:44:10+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T09:44:10+00:00 type: HTTP-Info
timestamp: 2018-11-14T09:44:10+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T09:44:08+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T09:44:07+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T09:44:05+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T09:44:05+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T09:43:55+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T09:43:55+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T09:43:55+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:55+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:54+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T09:43:54+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T09:43:52+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:52+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T09:43:52+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T09:43:52+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDF
timestamp: 2018-11-14T09:43:52+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T09:43:52+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T09:43:51+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 96
timestamp: 2018-11-14T09:43:51+00:00 type: BLE-SendingSSE bytes: 96 auth: 00345CDF
timestamp: 2018-11-14T09:43:51+00:00 type: WLAN-SocketConnected connection: 3
timestamp: 2018-11-14T09:43:50+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T09:43:50+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T09:43:50+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDF
timestamp: 2018-11-14T09:43:50+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T09:43:50+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T09:43:50+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T09:43:50+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T09:43:50+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDF
timestamp: 2018-11-14T09:43:49+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T09:43:49+00:00 type: BLE-Connect handles: ARRAY(0x6089750)
timestamp: 2018-11-14T09:43:49+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:49+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T09:43:49+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:49+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T09:43:49+00:00 type: SSE-KeyturnerEventResp nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:49+00:00 type: HTTP-PostStart
timestamp: 2018-11-14T09:43:49+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:49+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:48+00:00 type: SSE-KeyturnerEventReq nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:48+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000C
timestamp: 2018-11-14T09:43:48+00:00 type: BLE-SendingMsg nukiId: 14BAEC05 cmdId: 0001
timestamp: 2018-11-14T09:43:48+00:00 type: BLE-Connect handles: ARRAY(0x6122ea0)
timestamp: 2018-11-14T09:43:48+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:48+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T09:43:48+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:48+00:00 type: BLE-StatusUpdate nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:34+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T09:43:34+00:00 type: HTTP-Info
timestamp: 2018-11-14T09:43:34+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T09:43:24+00:00 type: BLE-EarlyDisconnect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:24+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 87
timestamp: 2018-11-14T09:43:24+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:24+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:24+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T09:43:24+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:23+00:00 type: BLE-Retry nukiId: 14BAEC05 count: 3
timestamp: 2018-11-14T09:43:23+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:23+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:19+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T09:43:19+00:00 type: HTTP-Info
timestamp: 2018-11-14T09:43:19+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T09:43:19+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:19+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T09:43:19+00:00 type: BLE-Retry nukiId: 14BAEC05 count: 2
timestamp: 2018-11-14T09:43:19+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:19+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:18+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T09:43:18+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:18+00:00 type: BLE-Retry nukiId: 14BAEC05 count: 1
timestamp: 2018-11-14T09:43:18+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:18+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:15+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T09:43:15+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:15+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T09:43:13+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T09:43:12+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T09:43:03+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T09:43:01+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T09:43:01+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T09:42:59+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T09:42:58+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T09:42:58+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T09:42:58+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDF
timestamp: 2018-11-14T09:42:58+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T09:42:58+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T09:42:58+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T09:42:58+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 96
timestamp: 2018-11-14T09:42:58+00:00 type: BLE-SendingSSE bytes: 96 auth: 00345CDF
timestamp: 2018-11-14T09:42:57+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T09:42:57+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T09:42:57+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDF
timestamp: 2018-11-14T09:42:57+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T09:42:57+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T09:42:56+00:00 type: WLAN-SocketConnected connection: 3
timestamp: 2018-11-14T09:42:56+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T09:42:56+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212


Was mir aufgefallen ist:
Wenn ich einen CallBack aus der Bridge über FHEM lösche meldet er mit dass es einen Fehler gab, allerdings ist dann der CallBack trotzdem verschwunden.
Im Log taucht folgendes auf:
2018.11.14 10:44:05 3: NUKIBridge (NukiBridge) - JSON error while request: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "HTTP 503 Unavailable") at ./FHEM/73_NUKIBridge.pm line 752.
FHEM in Docker auf Synology, CCU3,
Diverse HM-Komponenten, Netatmo, Hue, Sonos, Nuki

CoolTux

Cool, Super. Genau das brauchte ich.

Entscheidend

timestamp: 2018-11-14T09:44:08+00:00 type: HTTP-PostFailed urlId: 0
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

CoolTux

Antwort vom Support
Zitat
HTTP-PostStart zeigt, dass der Callback gesendet wurde.

HTTP-PostFailed   urlId: 0
heißt normal, dass die URL für den 1. eingestellten Callback nicht erreichbar war.

Kannst Du das Nuki Device in FHEM bitte einmal auf verbose 5 stellen. Eventuell kommt dann etwas.
Den webhook selbst hast Du nicht verändert nehme ich mal an. Also das FHEMWEB Device ist geblieben. Kein crfs Token abgefragt keine Passwort oder HTTPS?



Grüße
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Cobra

#1085
Bridge und Smartlock auf Verbose 5 und dann einmal Aufschließen und einmal Abschließen in der Nuki-App:

018.11.14 11:44:09 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 11:44:09 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 11:44:09 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 11:44:09 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 2870, "currentTime": "2018-11-14T10:44:08+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 11:44:08 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 11:44:08 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 11:44:08 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 11:44:08 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 11:43:49 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.14 11:43:49 5: NUKIBridge (NukiBridge) - Response CODE: 503
2018.11.14 11:43:49 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 11:43:49 5: NUKIBridge (NukiBridge) - Response JSON: HTTP 503 Unavailable
2018.11.14 11:43:49 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 11:43:49 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 11:43:49 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 11:43:49 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 11:43:30 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 11:43:30 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 11:43:30 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 11:43:30 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 2832, "currentTime": "2018-11-14T10:43:30+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 11:43:30 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 11:43:30 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 11:43:30 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 11:43:30 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 11:43:15 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 11:43:15 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 11:43:15 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 11:43:15 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 2815, "currentTime": "2018-11-14T10:43:13+00:00", "serverConnected": true, "scanResults": []}


Dann noch das Log der Bridge:

timestamp: 2018-11-14T10:45:32+00:00 type: HTTP-Log
timestamp: 2018-11-14T10:45:32+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T10:45:16+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T10:45:16+00:00 type: HTTP-Info
timestamp: 2018-11-14T10:45:16+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T10:44:52+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T10:44:52+00:00 type: HTTP-Info
timestamp: 2018-11-14T10:44:52+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T10:44:34+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T10:44:33+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T10:44:28+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T10:44:28+00:00 type: HTTP-Info
timestamp: 2018-11-14T10:44:28+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T10:44:21+00:00 type: HTTP-PostTimeout
timestamp: 2018-11-14T10:44:21+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:21+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:18+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:18+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T10:44:18+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T10:44:18+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDF
timestamp: 2018-11-14T10:44:17+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T10:44:17+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T10:44:17+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 96
timestamp: 2018-11-14T10:44:17+00:00 type: BLE-SendingSSE bytes: 96 auth: 00345CDF
timestamp: 2018-11-14T10:44:17+00:00 type: WLAN-SocketConnected connection: 3
timestamp: 2018-11-14T10:44:16+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T10:44:16+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T10:44:16+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDF
timestamp: 2018-11-14T10:44:16+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T10:44:16+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T10:44:16+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T10:44:16+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T10:44:16+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDF
timestamp: 2018-11-14T10:44:15+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T10:44:15+00:00 type: BLE-Connect handles: ARRAY(0x2146188)
timestamp: 2018-11-14T10:44:15+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:15+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T10:44:15+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:15+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T10:44:15+00:00 type: SSE-KeyturnerEventResp nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:15+00:00 type: HTTP-PostStart
timestamp: 2018-11-14T10:44:15+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:15+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:14+00:00 type: SSE-KeyturnerEventReq nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:14+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000C
timestamp: 2018-11-14T10:44:14+00:00 type: BLE-SendingMsg nukiId: 14BAEC05 cmdId: 0001
timestamp: 2018-11-14T10:44:14+00:00 type: BLE-Connect handles: ARRAY(0x5fe9ac0)
timestamp: 2018-11-14T10:44:14+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:14+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T10:44:14+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:14+00:00 type: BLE-StatusUpdate nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:10+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T10:44:08+00:00 type: HTTP-Info
timestamp: 2018-11-14T10:44:08+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T10:44:06+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:06+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T10:44:03+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T10:44:03+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T10:44:03+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDD
timestamp: 2018-11-14T10:44:03+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T10:44:03+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDD
timestamp: 2018-11-14T10:43:59+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T10:43:58+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T10:43:57+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T10:43:57+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDD
timestamp: 2018-11-14T10:43:57+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T10:43:57+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDD
timestamp: 2018-11-14T10:43:57+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 92
timestamp: 2018-11-14T10:43:57+00:00 type: BLE-SendingSSE bytes: 92 auth: 00345CDD
timestamp: 2018-11-14T10:43:56+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T10:43:56+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T10:43:56+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDD
timestamp: 2018-11-14T10:43:56+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDD
timestamp: 2018-11-14T10:43:56+00:00 type: BLE-Connect handles: ARRAY(0x5b39300)
timestamp: 2018-11-14T10:43:56+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T10:43:56+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T10:43:56+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T10:43:56+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T10:43:49+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T10:43:49+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T10:43:46+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T10:43:46+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T10:43:44+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T10:43:43+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T10:43:43+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T10:43:43+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDF
timestamp: 2018-11-14T10:43:43+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T10:43:43+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T10:43:43+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T10:43:43+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T10:43:43+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 96
timestamp: 2018-11-14T10:43:43+00:00 type: BLE-SendingSSE bytes: 96 auth: 00345CDF
timestamp: 2018-11-14T10:43:42+00:00 type: WLAN-SocketConnected connection: 3
timestamp: 2018-11-14T10:43:42+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T10:43:42+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T10:43:42+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDF
timestamp: 2018-11-14T10:43:42+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T10:43:42+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T10:43:41+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T10:43:41+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212


Am Webhook wurde nix geändert. Kein crfs und kein HTTPS.

EDIT:
Mist, ich hab mich geirrt. WEBTablet hat doch nen cris-Token. Aber auch wenn ich dort auf "None" setze funktioniert es nicht.
Oder muss ich nach dem auf "None" setzen nochmal was beachten?
Aber mit dem alten SmartLock hat es ja auch mit dem Token geklappt.
FHEM in Docker auf Synology, CCU3,
Diverse HM-Komponenten, Netatmo, Hue, Sonos, Nuki

CoolTux

Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Cobra

Hier das List:

Internals:
   CFGFN     
   DEF        347794437 IODev=NukiBridge
   IODev      NukiBridge
   NAME       NUKIDevice347794437
   NR         6348
   NUKIID     347794437
   STATE      unlock
   TYPE       NUKIDevice
   VERSION    0.6.3
   WEBHOOK_COUNTER 0
   WEBHOOK_PORT 8085
   WEBHOOK_REGISTER sent
   WEBHOOK_URI /fhem/NUKIDevice
   WEBHOOK_URL http://192.168.178.5:8085/fhem/NUKIDevice-347794437
   READINGS:
     2018-11-13 13:50:45   battery         ok
     2018-11-13 13:50:45   batteryCritical 0
     2018-11-13 13:50:45   batteryState    ok
     2018-11-14 07:44:24   lockState       unlock
     2018-11-14 11:55:19   name            Nuki_14BAEC05
     2018-11-14 11:55:19   paired          1
     2018-11-14 11:55:19   rssi            -71
     2018-11-14 07:44:24   state           unlock
     2018-11-14 10:57:23   success         1
   helper:
     fromAutocreate 1
Attributes:
   IODev      NukiBridge
   alias      CobraDoor
   devStateIcon unlocked:secur_open@green locked:secur_locked@red
   icon       1_nuki
   room       1.5_Flur
   verbose    3
   webCmd     lock:unlock:unlatch
   webhookFWinstance WEBtablet
   webhookHttpHostname 192.168.178.5


Hab dir oben noch was zum crfs ergänzt.
FHEM in Docker auf Synology, CCU3,
Diverse HM-Komponenten, Netatmo, Hue, Sonos, Nuki

CoolTux

Zitat von: Cobra am 14 November 2018, 11:47:09
EDIT:
Mist, ich hab mich geirrt. WEBTablet hat doch nen cris-Token. Aber auch wenn ich dort auf "None" setze funktioniert es nicht.
Oder muss ich nach dem auf "None" setzen nochmal was beachten?
Aber mit dem alten SmartLock hat es ja auch mit dem Token geklappt.

Hatte nur aus Reflex gefragt, sorry. crfs ist in der Tat unwichtig.
Was mich bisschen wundert

FHEM - NUKIID     347794437
BRIDGELOG - BLE-Disconnected       nukiId:    14BAEC05

Muss aber nichts heißen. Ich wunder mich warum am webhook rein gar nichts an kommt und das Bridgelog behauptet das keiner auf der anderen Seite angenommen hat.

Sorry aber ich muss da noch mal drüber schlafen.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

CoolTux

Kannst Du bitte noch mal ein

get callbackList bei der Bridge machen und mir das Ergebnis hier posten
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Cobra

Aber sicher doch:
Callback-ID Callback-URL
0 http://192.168.178.5:8085/fhem/NUKIDevice-347794437
FHEM in Docker auf Synology, CCU3,
Diverse HM-Komponenten, Netatmo, Hue, Sonos, Nuki

CoolTux

Auch sauber.

Du hast vom FHEM Log nur direkt Nuki rausgegeben. Hast Du noch andere Einträge, speziell FHEMWEB oder allowed?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Cobra

#1092
Das waren alle Logeinträge die zu dieser Zeit kamen.
Das entsprechende FHEMWEB ist auch nicht irgendwie durch allowed eingeschränkt.
FHEM in Docker auf Synology, CCU3,
Diverse HM-Komponenten, Netatmo, Hue, Sonos, Nuki

CoolTux

ok, vielen Dank

Vielleicht kannst Du ja bei Gelegenheit das betreffende FHEMWEB Device auch auf verbose 5 setzen und noch einmal testen.



Grüße
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Cobra

#1094
So, einmal FHEM-Log mit Bridge, Smartlock und FHEMWEB auf Verbose 5, einmal schließen und einmal öffnen:

2018.11.14 12:56:40 4: Connection closed for WEBtablet_192.168.178.23_25867: EOF
2018.11.14 12:56:37 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.14 12:56:37 5: NUKIBridge (NukiBridge) - Response CODE: 503
2018.11.14 12:56:37 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 12:56:37 5: NUKIBridge (NukiBridge) - Response JSON: HTTP 503 Unavailable
2018.11.14 12:56:37 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 12:56:37 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 12:56:37 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 12:56:37 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 12:56:27 4: WEBtablet: /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 3, "stateName": "unlocked", "batteryCritical": false} / RL:8041 / text/html; charset=UTF-8 /  /
2018.11.14 12:56:27 4: WEBtablet_192.168.178.23_25867 POST /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 3, "stateName": "unlocked", "batteryCritical": false}; BUFLEN:0
2018.11.14 12:56:25 4: Connection accepted from WEBtablet_192.168.178.23_25867
2018.11.14 12:56:19 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 12:56:19 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 12:56:19 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 12:56:19 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 7201, "currentTime": "2018-11-14T11:56:18+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 12:56:19 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 12:56:19 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 12:56:19 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 12:56:19 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 12:56:05 4: Connection closed for WEBtablet_192.168.178.23_38662: EOF
2018.11.14 12:56:01 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.14 12:56:01 5: NUKIBridge (NukiBridge) - Response CODE: 503
2018.11.14 12:56:01 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 12:56:01 5: NUKIBridge (NukiBridge) - Response JSON: HTTP 503 Unavailable
2018.11.14 12:56:01 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 12:56:01 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 12:56:01 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 12:56:01 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 12:55:51 4: WEBtablet: /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 1, "stateName": "locked", "batteryCritical": false} / RL:8041 / text/html; charset=UTF-8 /  /
2018.11.14 12:55:51 4: WEBtablet_192.168.178.23_38662 POST /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 1, "stateName": "locked", "batteryCritical": false}; BUFLEN:0
2018.11.14 12:55:49 4: Connection accepted from WEBtablet_192.168.178.23_38662
2018.11.14 12:55:33 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 12:55:33 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 12:55:33 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 12:55:33 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 7155, "currentTime": "2018-11-14T11:55:32+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 12:55:33 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 12:55:33 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 12:55:33 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 12:55:33 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 12:55:05 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 12:55:05 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 12:55:05 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 12:55:05 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 7127, "currentTime": "2018-11-14T11:55:04+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 12:53:59 3: CUL_HM set SD.Flur_Dis displayEP Fenster\_zu,ok


Log der Bridge:

timestamp: 2018-11-14T11:58:19+00:00 type: HTTP-Log
timestamp: 2018-11-14T11:58:19+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T11:57:56+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T11:57:56+00:00 type: HTTP-Info
timestamp: 2018-11-14T11:57:56+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T11:57:39+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T11:57:37+00:00 type: HTTP-Info
timestamp: 2018-11-14T11:57:37+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T11:57:18+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T11:57:18+00:00 type: HTTP-Info
timestamp: 2018-11-14T11:57:18+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T11:57:02+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T11:57:02+00:00 type: HTTP-Info
timestamp: 2018-11-14T11:57:02+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T11:56:41+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T11:56:40+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T11:56:36+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T11:56:36+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T11:56:29+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:29+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:26+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:26+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T11:56:26+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T11:56:26+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDF
timestamp: 2018-11-14T11:56:25+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T11:56:25+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T11:56:25+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 96
timestamp: 2018-11-14T11:56:25+00:00 type: BLE-SendingSSE bytes: 96 auth: 00345CDF
timestamp: 2018-11-14T11:56:24+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T11:56:24+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T11:56:24+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDF
timestamp: 2018-11-14T11:56:24+00:00 type: WLAN-SocketConnected connection: 3
timestamp: 2018-11-14T11:56:24+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T11:56:24+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T11:56:24+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T11:56:24+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T11:56:24+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDF
timestamp: 2018-11-14T11:56:23+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T11:56:23+00:00 type: BLE-Connect handles: ARRAY(0x71c3808)
timestamp: 2018-11-14T11:56:23+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:23+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T11:56:23+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:23+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T11:56:23+00:00 type: SSE-KeyturnerEventResp nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:23+00:00 type: HTTP-PostStart
timestamp: 2018-11-14T11:56:23+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:23+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:22+00:00 type: SSE-KeyturnerEventReq nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:22+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000C
timestamp: 2018-11-14T11:56:22+00:00 type: BLE-SendingMsg nukiId: 14BAEC05 cmdId: 0001
timestamp: 2018-11-14T11:56:22+00:00 type: BLE-Connect handles: ARRAY(0x5e9a3b8)
timestamp: 2018-11-14T11:56:22+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:21+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T11:56:21+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:21+00:00 type: BLE-StatusUpdate nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:19+00:00 type: SSE-PushNukisResponse error: 0
timestamp: 2018-11-14T11:56:19+00:00 type: SSE-PushNukisRequest count: 1
timestamp: 2018-11-14T11:56:18+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T11:56:18+00:00 type: HTTP-Info
timestamp: 2018-11-14T11:56:18+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T11:56:14+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:14+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:11+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T11:56:11+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T11:56:11+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDD
timestamp: 2018-11-14T11:56:11+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T11:56:11+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDD
timestamp: 2018-11-14T11:56:05+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T11:56:05+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T11:56:05+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDD
timestamp: 2018-11-14T11:56:05+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T11:56:05+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDD
timestamp: 2018-11-14T11:56:04+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 92
timestamp: 2018-11-14T11:56:04+00:00 type: BLE-SendingSSE bytes: 92 auth: 00345CDD
timestamp: 2018-11-14T11:56:04+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T11:56:04+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T11:56:04+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDD
timestamp: 2018-11-14T11:56:04+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T11:56:03+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T11:56:03+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDD
timestamp: 2018-11-14T11:56:03+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T11:56:03+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T11:56:03+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDD
timestamp: 2018-11-14T11:56:02+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDD
timestamp: 2018-11-14T11:56:02+00:00 type: BLE-Connect handles: ARRAY(0x5f01ee0)
timestamp: 2018-11-14T11:56:02+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:02+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T11:56:02+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T11:56:02+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T11:56:00+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T11:56:00+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T11:55:52+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T11:55:52+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T11:55:50+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T11:55:49+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T11:55:49+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T11:55:49+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDF
timestamp: 2018-11-14T11:55:49+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T11:55:49+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T11:55:49+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 96
FHEM in Docker auf Synology, CCU3,
Diverse HM-Komponenten, Netatmo, Hue, Sonos, Nuki