define NukiBridge NUKIBridge <host> <api-token>
Spender | Betrag |
Fred_Feuerstein | 50€ |
aheissenberger | 50€ |
Cobra | 20€ |
kkoeniger | 10€ |
jiggi | 10€ |
Stephan1965 | 10€ |
spacecowboy.21 | 20€ |
CoolTux | 100€ |
Sascha_F | 20€ |
Gesamt alt: | 290€ |
Nuki Set gekauft: | -230€ |
Gesamt neu: | 60€ |
Zitat von: Steeeve am 22 Juli 2016, 09:45:06
Irgendwie unfair - hatte bei Kickstarter das Schloss bestellt und nachträglich noch ein Bundle aus Bridge und Schloss - Schlösser sind diese Woche beide gekommen...
Dazu gibts dann noch einen 30 Eur Gutschein, der ab 80 Eur einkauf gilt (2 Fobs kosten 58 eur, somit kann man für sowas keinen Gutschein einlösen)
Zitat von: Steeeve am 22 Juli 2016, 09:45:06
Irgendwie unfair - hatte bei Kickstarter das Schloss bestellt und nachträglich noch ein Bundle aus Bridge und Schloss - Schlösser sind diese Woche beide gekommen...
Dazu gibts dann noch einen 30 Eur Gutschein, der ab 80 Eur einkauf gilt (2 Fobs kosten 58 eur, somit kann man für sowas keinen Gutschein einlösen)
Zitat
Hallo Leon,
letztlich ist deine Anfrage bei mir gelandet. Ich bin für den Developer Support zuständig. Da wir derzeit total ausverkauft sind, schaut es mit Demo Units sehr schlecht aus. Was ich im Regelfall aber schon hinbringe ist Bestellungen vorzuziehen. D.h. wenn du im Nuki Shop ein Smartlock bestellst, dann kann ich die Bestellung vorreihen so dass es sofort verschickt wird.
Lass mich bitte wissen ob das geht. Wenn nein, dann musst du leider warten bis wir Demounits haben. Genauen Zeitplan dafür kann ich keinen nennen, da wir derzeit nur ein sehr begrenztes Set haben und da so schnell auch nicht mehr werden wird.
Grüße
Jürgen
---------------------------------------------
Jürgen Pansy
Product & Strategy
Nuki Home Solutions GmbH
Münzgrabenstrasse 92/4
8010 Graz, Austria
M: +43 676 6688650
F: +43 316 22841250
www.nuki.io
list $NUKIDEVICE
tail -f /opt/fhem/log/fhem-2016-09.log | grep NUKI >> /opt/fhem/log/NUKI.log
2016.10.08 07:38:36 3: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=sdfdsdsfdf&nukiId=9ofdsnaofdnsaofdn
2016.10.08 07:38:36 3: NUKIDevice (NUKIDevice9ddsdddd211) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 07:38:36 3: NUKIDevice (NUKIDevice9ddddddd211) - Call NUKIDevice_GetUpdate
2016.10.08 07:38:36 3: NUKIDevice (NUKIDevice9ddddddd211) - Call InternalTimer
2016.10.08 07:38:39 3: parse status message for NUKIDevice9ddddddd211
2016.10.08 07:38:39 3: readings set for NUKIDevice9ddddddd211
2016.10.08 20:07:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:07:42 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:08:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:08:42 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:09:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/list?token=mmnnmm
2016.10.08 20:09:12 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.08 20:09:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:09:12 4: NUKIBridge (NukiBridge) - error while requesting: http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678: empty answer received
2016.10.08 20:09:15 5: NUKIBridge (NukiBridge) - Bridge ist online
2016.10.08 20:09:42 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:10:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:10:42 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:11:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:11:42 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:12:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/list?token=mmnnmm
2016.10.08 20:12:12 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.08 20:12:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:12:12 4: NUKIBridge (NukiBridge) - error while requesting: http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678: empty answer received
2016.10.08 20:12:23 4: NUKIBridge (NukiBridge) - Bridge ist offline
2016.10.08 20:12:42 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:13:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:13:45 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:14:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:14:45 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:15:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/list?token=mmnnmm
2016.10.08 20:15:12 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.08 20:15:15 5: NUKIBridge (NukiBridge) - Bridge ist online
2016.10.08 20:15:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:15:15 4: NUKIBridge (NukiBridge) - error while requesting: http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678: empty answer received
2016.10.08 20:15:45 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:16:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/lockState?token=mmnnmm&nukiId=12345678
2016.10.08 20:20:15 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:20:15 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:20:15 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:20:17 5: parse status message for NUKIDevice12345678
2016.10.08 20:20:17 5: readings set for NUKIDevice12345678
2016.10.08 20:20:45 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:20:45 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:20:45 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:20:46 5: parse status message for NUKIDevice12345678
2016.10.08 20:20:46 5: readings set for NUKIDevice12345678
2016.10.08 20:21:15 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:21:15 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:21:15 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:21:45 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:21:45 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:21:45 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:21:47 5: parse status message for NUKIDevice12345678
2016.10.08 20:21:47 5: readings set for NUKIDevice12345678
2016.10.08 20:22:15 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:22:15 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:22:15 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:22:16 5: parse status message for NUKIDevice12345678
2016.10.08 20:22:16 5: readings set for NUKIDevice12345678
2016.10.08 20:22:45 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:22:45 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:22:45 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:22:47 5: parse status message for NUKIDevice12345678
2016.10.08 20:22:47 5: readings set for NUKIDevice12345678
2016.10.08 20:23:15 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:23:15 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:23:15 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:23:16 5: parse status message for NUKIDevice12345678
2016.10.08 20:23:16 5: readings set for NUKIDevice12345678
2016.10.08 20:23:45 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:23:45 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:23:45 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:23:47 5: parse status message for NUKIDevice12345678
2016.10.08 20:23:47 5: readings set for NUKIDevice12345678
2016.10.08 20:24:15 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:24:15 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:24:15 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:24:17 5: parse status message for NUKIDevice12345678
2016.10.08 20:24:17 5: readings set for NUKIDevice12345678
2016.10.08 20:24:45 5: NUKIDevice (NUKIDevice12345678) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.10.08 20:24:45 5: NUKIDevice (NUKIDevice12345678) - Call NUKIDevice_GetUpdate
2016.10.08 20:24:45 5: NUKIDevice (NUKIDevice12345678) - Call InternalTimer
2016.10.08 20:24:46 5: parse status message for NUKIDevice12345678
2016.10.08 20:24:46 5: readings set for NUKIDevice12345678
cd /opt/fhem/
/usr/bin/perl contrib/commandref_join.pl
/usr/bin/perl contrib/commandref_join.pl
root@RaZberryTFT:/opt/fhem/contrib# /usr/bin/perl contrib/commandref_join.pl
Can't open perl script "contrib/commandref_join.pl": Datei oder Verzeichnis nicht gefunden
/usr/bin/perl commandref_join.pl
cd /opt/fhem/contrib/
cd /opt/fhem/
Zitat von: fred_feuerstein am 10 Oktober 2016, 15:05:05
Anbei die beiden Übersetzungen fürs Modul
lastError
http://10.0.0.209:8080/lockState?token=nope&nukiId=123456789: empty answer received
2016-10-12 10:14:36
Internals:
CFGFN
DEF 123123132 IODev=NukiBridge
INTERVAL 120
IODev NukiBridge
NAME NUKIDevice63125289
NR 474
NUKIID 123132123
STATE locked
TYPE NUKIDevice
VERSION 0.2.1
Readings:
2016-10-12 12:40:59 battery ok
2016-10-12 12:40:59 batteryCritical false
2016-10-12 12:40:59 lockState locked
2016-10-12 12:40:59 state locked
2016-10-12 12:40:59 success true
Helper:
fromAutocreate 1
Attributes:
IODev NukiBridge
alias Wohnungstür
interval 120
room NUKI,Wohnung
2016.10.16 14:49:50 4 : NUKIBridge (NukiBridge1) - Send HTTP POST with URL http://192.168.x.x:8080/list?token=xxxxxxx
2016.10.16 14:49:50 4 : NUKIBridge (NukiBridge1) - Send HTTP POST with URL http://192.168.x.x:8080/list?token=xxxxxxx
2016.10.16 14:49:50 4 : NUKIBridge (NukiBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.16 14:49:50 4 : NUKIBridge (NukiBridge1) - Call NUKIBridge_Get
2016-10-16 14:49:50 NUKIBridge NukiBridge1 autocreate
2016.10.16 14:49:50 5 : NUKIBridge (NukiBridge1) - Bridge ist online
2016-10-16 14:49:50 NUKIBridge NukiBridge1 connected
Zitat von: CoolTux am 16 Oktober 2016, 15:56:31Ja.
Wenn ich Dich jezt richtig verstanden habe ist es eine Software Bridge. Korrekt?
Zitat von: CoolTux am 16 Oktober 2016, 15:56:31Ja.
Bridge auf Android sagteat Du. Wenn Du die Bridge App öffnest, ist dann Dein Smartlock dort zu sehen als Nuki Smartlock?
define NukiBridge NUKIBridge 192.168.10.73 abc123 <-- nicht der echte Token
attr NukiBridge room Flur-EG
2016.10.22 15:08:44 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 15:08:44 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 15:08:44 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 15:08:44 4: NUKIBridge (NukiBridge) - Call NUKIBridge_Get
2016.10.22 15:08:44 4: NUKIBridge (NukiBridge) - Bridge ist offline
2016.10.22 15:08:54 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.10.73:8080 timed out
[{"nukiId": 62776481, "name": "AmSti101", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-10-22T12:20:02+00:00"}}]
error while requesting: read from http://192.168.10.73:8080 timed out
telnet 192.168.10.73 8080
Trying 192.168.10.73...
Connected to 192.168.10.73.
Escape character is '^]'.
2016.10.22 16:55:41 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=123abc
2016.10.22 16:55:41 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=123abc
2016.10.22 16:55:41 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 16:55:41 4: NUKIBridge (NukiBridge) - Call NUKIBridge_Get
2016.10.22 16:55:42 4: NUKIBridge (NukiBridge) - Bridge ist offline
2016.10.22 16:55:52 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.10.73:8080 timed out
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Initialize redefined at ./FHEM/73_NUKIBridge.pm line 51.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Read redefined at ./FHEM/73_NUKIBridge.pm line 76.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Define redefined at ./FHEM/73_NUKIBridge.pm line 83.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Undef redefined at ./FHEM/73_NUKIBridge.pm line 127.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Attr redefined at ./FHEM/73_NUKIBridge.pm line 141.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Set redefined at ./FHEM/73_NUKIBridge.pm line 194.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Get redefined at ./FHEM/73_NUKIBridge.pm line 222.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_GetCheckBridgeAlive redefined at ./FHEM/73_NUKIBridge.pm line 237.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Call redefined at ./FHEM/73_NUKIBridge.pm line 255.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_ResponseProcessing redefined at ./FHEM/73_NUKIBridge.pm line 394.
2016.10.22 17:06:32 1: PERL WARNING: Subroutine NUKIBridge_Autocreate redefined at ./FHEM/73_NUKIBridge.pm line 414.
2016.10.22 17:06:41 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:06:41 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 17:06:46 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:06:46 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:06:46 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 17:06:46 4: NUKIBridge (NukiBridge) - Call NUKIBridge_Get
JSON String:
2016.10.22 17:06:46 4: NUKIBridge (NukiBridge) - Bridge ist offline
JSON String:
2016.10.22 17:06:46 4: NUKIBridge (NukiBridge) - error while requesting: http://192.168.10.73:8080/list?token=abc123: empty answer received
JSON String:
2016.10.22 17:06:51 4: NUKIBridge (NukiBridge) - Bridge ist offline
17:06:46 4: NUKIBridge (NukiBridge) - error while requesting: http://192.168.10.73:8080/list?token=
[{"nukiId": 62776481, "name": "AmSti101", "lastKnownState": {"state": 1, "stateName": "locked", "batteryCritical": false, "timestamp": "2016-10-22T15:05:30+00:00"}}]
JSON String:
2016.10.22 17:25:52 4: NUKIBridge (NukiBridge) - Bridge ist offline
2016.10.22 17:26:28 3: Can't connect to socket!
2016.10.22 17:26:35 3: MaxScanner MAX_12e87b Work.1236 Wait at least 180 sec . after last command
2016.10.22 17:26:52 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:26:52 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 17:26:56 3: MaxScanner MAX_12e87b Work.1014 TEMPERATURE received at 2016-10-22 17:26:56, ==> new ns:2016-10-22 17:41:39
2016.10.22 17:27:28 3: Can't connect to socket!
JSON String: [{"nukiId": 62776481, "name": "AmSti101", "lastKnownState": {"state": 1, "stateName": "locked", "batteryCritical": false, "timestamp": "2016-10-22T15:05:30+00:00"}}]
2016.10.22 17:27:52 5: NUKIBridge (NukiBridge) - Bridge ist online
2016.10.22 17:27:52 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:27:52 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 17:28:24 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:28:24 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:28:24 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 17:28:24 4: NUKIBridge (NukiBridge) - Call NUKIBridge_Get
JSON String:
2016.10.22 17:28:24 4: NUKIBridge (NukiBridge) - Bridge ist offline
JSON String:
2016.10.22 17:28:24 4: NUKIBridge (NukiBridge) - error while requesting: http://192.168.10.73:8080/list?token=abc123: empty answer received
2016.10.22 17:28:28 3: Can't connect to socket!
JSON String:
2016.10.22 17:28:52 4: NUKIBridge (NukiBridge) - Bridge ist offline
2016.10.22 17:29:24 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:29:24 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 17:29:28 3: Can't connect to socket!
JSON String: [{"nukiId": 62776481, "name": "AmSti101", "lastKnownState": {"state": 1, "stateName": "locked", "batteryCritical": false, "timestamp": "2016-10-22T15:27:17+00:00"}}]
2016.10.22 17:33:24 5: NUKIBridge (NukiBridge) - Bridge ist online
2016.10.22 17:33:24 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:33:24 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.10.22 17:33:28 3: Can't connect to socket!
2016.10.22 17:33:31 3: MaxScanner MAX_12dba9 Work.1014 TEMPERATURE received at 2016-10-22 17:33:31, ==> new ns:2016-10-22 17:48:14
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_Undef redefined at ./FHEM/73_NUKIBridge.pm line 126.
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_Attr redefined at ./FHEM/73_NUKIBridge.pm line 140.
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_Set redefined at ./FHEM/73_NUKIBridge.pm line 193.
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_Get redefined at ./FHEM/73_NUKIBridge.pm line 221.
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_GetCheckBridgeAlive redefined at ./FHEM/73_NUKIBridge.pm line 236.
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_Call redefined at ./FHEM/73_NUKIBridge.pm line 254.
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_Evaluation redefined at ./FHEM/73_NUKIBridge.pm line 291.
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_ResponseProcessing redefined at ./FHEM/73_NUKIBridge.pm line 391.
2016.10.22 17:33:42 1: PERL WARNING: Subroutine NUKIBridge_Autocreate redefined at ./FHEM/73_NUKIBridge.pm line 411.
2016.10.22 17:34:12 3: NUKIBridge (NukiBridge) - defined with host 192.168.10.73 on port 8080, Token abc123
2016.10.22 17:34:12 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:34:12 4: NUKIBridge (NukiBridge) - Call NUKIBridge_Get
JSON String:
2016.10.22 17:34:12 4: NUKIBridge (NukiBridge) - error while requesting: http://192.168.10.73:8080/list?token=abc123: empty answer received
JSON String:
2016.10.22 17:34:24 4: NUKIBridge (NukiBridge) - Bridge ist offline
2016.10.22 17:34:28 3: Can't connect to socket!
2016.10.22 17:35:28 3: Can't connect to socket!
2016.10.22 17:36:28 3: Can't connect to socket!
2016.10.22 17:36:39 3: NUKIBridge (NukiBridge) - defined with host 192.168.10.73 on port 8080, Token abc123
2016.10.22 17:36:39 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:36:39 4: NUKIBridge (NukiBridge) - Call NUKIBridge_Get
2016.10.22 17:37:28 3: Can't connect to socket!
2016.10.22 17:36:39 3: NUKIBridge (NukiBridge) - defined with host 192.168.10.73 on port 8080, Token abc123
2016.10.22 17:36:39 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/list?token=abc123
2016.10.22 17:36:39 4: NUKIBridge (NukiBridge) - Call NUKIBridge_Get
2016.10.22 17:37:28 3: Can't connect to socket!
JSON String: [{"nukiId": 62776481, "name": "AmSti101", "lastKnownState": {"state": 1, "stateName": "locked", "batteryCritical": false, "timestamp": "2016-10-22T15:27:17+00:00"}}]
2016.10.22 17:49:54 5: NukiBridge: create new device 'NUKIDevice62776481' for address '62776481'
2016.10.22 17:49:54 3: NUKIDevice62776481: I/O device is NukiBridge
2016.10.22 17:49:54 3: NUKIDevice (NUKIDevice62776481) - defined with Code: NukiBridge-62776481
2016.10.22 17:49:54 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/lockState?token=abc123&nukiId=62776481
2016.10.22 17:49:54 2: NukiBridge: autocreated 1 devices
JSON String: {"state": 1, "stateName": "locked", "batteryCritical": false, "success": true}
2016.10.22 17:50:01 3: Can't connect to socket!
2016.10.22 17:50:14 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.10.73:8080/lockState?token=abc123&nukiId=62776481
JSON String: {"state": 1, "stateName": "locked", "batteryCritical": false, "success": true}
http://IP-Bridge:8080/list?token=abc123
Zitat von: Steeeve am 12 Oktober 2016, 12:39:55
Meinst, wäre es noch interessant /log auch ausgeben zu können?Code Auswählenget NukiBridge log
http://192.168.10.73:8080/log?token=abc123
Zitat von: Bjoern2480 am 24 Oktober 2016, 14:54:35
request:
http://IP:8080/list?token=12345
response:
[{"nukiId": 55555555, "name": "myHome", "lastKnownState": {"state": 1, "stateName": "locked", "batteryCritical": false, "timestamp": "2016-10-24T12:51:14+00:00"}}]
Allerdings hängt es auch ab und zu beim Browser. Beim 2. Aufruf/erneuten Laden geht es dann und es erscheint die antwort.
Zitat von: CoolTux am 24 Oktober 2016, 15:06:51
Es sind immer 10s bis zum Timeout. Nach 10s sollte es doch die Bridge geschafft haben zu antworten. Ansonsten blockiert da wohl eher irgendwas.
PERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 338.
2016.10.28 10:28:13 3: stacktrace:
2016.10.28 10:28:13 3: main::__ANON__ called by ./FHEM/74_NUKIDevice.pm (338)
2016.10.28 10:28:13 3: main::NUKIDevice_Parse called by ./FHEM/73_NUKIBridge.pm (386)
2016.10.28 10:28:13 3: main::NUKIBridge_Dispatch called by FHEM/HttpUtils.pm (421)
2016.10.28 10:28:13 3: main::__ANON__ called by fhem.pl (669)
Zitat von: _Marco_ am 29 Oktober 2016, 17:01:32
Hi, ich habe die Module auch im Einsatz und funktionieren sowei ganz gut :)
Ich habe im Log hier das entdecktCode AuswählenPERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 338.
2016.10.28 10:28:13 3: stacktrace:
2016.10.28 10:28:13 3: main::__ANON__ called by ./FHEM/74_NUKIDevice.pm (338)
2016.10.28 10:28:13 3: main::NUKIDevice_Parse called by ./FHEM/73_NUKIBridge.pm (386)
2016.10.28 10:28:13 3: main::NUKIBridge_Dispatch called by FHEM/HttpUtils.pm (421)
2016.10.28 10:28:13 3: main::__ANON__ called by fhem.pl (669)
kann da jemand was mit anfangen?
Das Einzige was mir aufgefallen ist das nach einem Schliessvorgang das Device keinen Status mehr bekommt, aber nach ca. einer Minute gehts wieder.
Gruß Marco
NUKIBridge NUKI_Bridge lastError: read from http://192.168.11.119:8080 timed out
http://192.168.123.74:8080/list?token=##### ergibt
[{"nukiId": ########, "name": "W58 unten", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-11-01T08:28:38+00:00"}}]
2016.11.01 15:34:16 3: NUKIBridge (NukiBridge1) - Param Alive: 1
2016.11.01 15:34:16 3: NUKIBridge (NukiBridge1) - Param Code:
2016.11.01 15:34:16 3: NUKIBridge (NukiBridge1) - Error: read from http://192.168.123.74:8080 timed out
2016.11.01 15:34:16 3: NUKIBridge (NukiBridge1) - JSON:
2016.11.01 15:35:16 3: NUKIBridge (NukiBridge1) - Param Alive: 1
2016.11.01 15:35:16 3: NUKIBridge (NukiBridge1) - Param Code:
2016.11.01 15:35:16 3: NUKIBridge (NukiBridge1) - Error: http://192.168.123.74:8080/list?token=######: empty answer received
2016.11.01 15:35:16 3: NUKIBridge (NukiBridge1) - JSON:
2016.11.01 15:35:16 3: NUKIBridge (NukiBridge1) - Param Alive: 1
2016.11.01 15:35:16 3: NUKIBridge (NukiBridge1) - Param Code:
2016.11.01 15:35:16 3: NUKIBridge (NukiBridge1) - Error: read from http://192.168.123.74:8080 timed out
2016.11.01 15:35:16 3: NUKIBridge (NukiBridge1) - JSON:
Zitat von: TomD am 01 November 2016, 20:24:37
Hallo CoolTux,
ich sehe leider keine angehängte version
Zitat von: _Marco_ am 01 November 2016, 21:07:36
Hi, also ich habe auch die aktellen Versionen jetzt eingespielt nur habe ich gerade ein Problem mit meiner Hardbridge.
Ich hatte bislang nur eine Softbridge mit einem Nuki, jetzt hatte ich mein zweites Nuki und eine Hardbridge bekommen und hatte auch beide Nukis an ihr angemeldet was aber überhaupt nicht richtig läuft, alles dauert ewig bis mal was in der app angezeigt (wenn was angezeigt wird).
Jetzt wollte ich erstmal an jede Bride ein Nuki anmelden, in der Softbridge kann man die Keyturner wieder abmelden aber in der Hardbridge gibts da keinen Menupunkt für, das Problem ist das sich der Keyturner den Ich in der Softbridge anmelde auch funktioniert nur ist er auch noch in der Hardbridge registriert und das kommt sich geade irgendwie in die quere. Frage ist wie kann man die Hardbridge zurücksetzten und wie bekommet man die Firmwareversion raus?
Wen die Probleme gelöst sind kann ich mittesten :)
[{"nukiId": 9454454256, "name": "Wohnungstuer", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-11-01T19:53:47+00:00"}},{"nukiId": 64546051, "name": "Haustuer"}]
Zitat von: _Marco_ am 01 November 2016, 21:27:561x am Tag bzw 1h nach Neustart wird in der Bridge auf updates geprüft und ggf installiert. Probier mal /info ev zeigts dir da sie Version an
Ich habe jetzt gerade mal die Softbridge ausgeschaltet und trotzdem konnte ich mit meinem Handy mit ausgeschaltetem Bluetooth den Keyturner am Handy steuern, über fhem ist der jetzt nicht mehr erreichbar da ich ihn ja über die Softbride eingebunden habe und die Hardbride ist in fhem disabled ::)
Deswegen würde ich die Bridge gerne mal zurück setzen weil ja beide Keyturner scheinbar immer noch über die Bridge laufen, jedenfalls der eine der es ja nicht mehr soll.
UNd wie konnte man denn jetzt die Firmeware der Hardbridge erkennen? und wie wird die eigentlich eingespielt wenn mal eine kommt?
Zitat2016.11.01 22:02:11 3: stacktrace:
2016.11.01 22:02:11 3: main::__ANON__ called by ./FHEM/73_NUKIBridge.pm (332)
2016.11.01 22:02:11 3: main::NUKIBridge_Distribution called by FHEM/HttpUtils.pm (421)
2016.11.01 22:02:11 3: main::__ANON__ called by fhem.pl (669)
2016.11.01 22:02:11 3: NUKIBridge (NUKI_Bridge_Hard) - Param Code:
2016.11.01 22:02:11 3: NUKIBridge (NUKI_Bridge_Hard) - Error: http://192.168.11.119:8080/list?token=123456: empty answer received
2016.11.01 22:02:11 3: NUKIBridge (NUKI_Bridge_Hard) - JSON:
ZitatNUKIBridge (NUKI_Bridge_Hard) - Param Alive: 0
2016.11.01 22:16:57 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 332.
2016.11.01 22:16:57 3: stacktrace:
2016.11.01 22:16:57 3: main::__ANON__ called by ./FHEM/73_NUKIBridge.pm (332)
2016.11.01 22:16:57 3: main::NUKIBridge_Distribution called by FHEM/HttpUtils.pm (421)
2016.11.01 22:16:57 3: main::__ANON__ called by fhem.pl (669)
2016.11.01 22:16:57 3: NUKIBridge (NUKI_Bridge_Hard) - Param Code:
2016.11.01 22:16:57 3: NUKIBridge (NUKI_Bridge_Hard) - Error: http://192.168.11.119:8080/lockState?token=123456&nukiId=78965485: empty answer received
2016.11.01 22:16:57 3: NUKIBridge (NUKI_Bridge_Hard) - JSON:
2016.11.01 22:17:11 3: NUKIBridge (NUKI_Bridge_Hard) - Param Alive: 1
2016.11.01 22:17:11 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 332.
2016.11.01 22:17:11 3: stacktrace:
2016.11.01 22:17:11 3: main::__ANON__ called by ./FHEM/73_NUKIBridge.pm (332)
2016.11.01 22:17:11 3: main::NUKIBridge_Distribution called by FHEM/HttpUtils.pm (89)
2016.11.01 22:17:11 3: main::HttpUtils_Err called by fhem.pl (2863)
2016.11.01 22:17:11 3: main::HandleTimeout called by fhem.pl (604)
2016.11.01 22:17:11 3: NUKIBridge (NUKI_Bridge_Hard) - Param Code:
2016.11.01 22:17:11 3: NUKIBridge (NUKI_Bridge_Hard) - Error: read from http://192.168.11.119:8080 timed out
2016.11.01 22:17:11 3: NUKIBridge (NUKI_Bridge_Hard) - JSON:
2016.11.01 22:17:11 3: SONOS0: Connection accepted from localhost:54082
2016.11.01 22:17:17 3: NUKIBridge (NUKI_Bridge_Hard) - Param Alive: 0
2016.11.01 22:17:17 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 332.
curl http://192.168.11.119:8080/list?token=123456
Zitat von: CoolTux am 02 November 2016, 16:30:16Kann ich gerade nicht testen, bin im Zug. Aber die App ist schneller beim Anzeigen vom Status.
Und und? Klappt denn nun ein statusRequest?
Readings
lastError
http://192.168.123.74:8080/list?token=123456: empty answer received
2016-11-02 20:09:50
state
not connected
2016.11.02 20:04:50 3: NUKIBridge (NukiBridge1) - Param Alive: 1
2016.11.02 20:04:50 3: NUKIBridge (NukiBridge1) - Param Code:
2016.11.02 20:04:50 3: NUKIBridge (NukiBridge1) - Error: read from http://192.168.123.74:8080 timed out
2016.11.02 20:04:50 3: NUKIBridge (NukiBridge1) - JSON:
2016.11.02 20:05:50 3: NUKIBridge (NukiBridge1) - Param Alive: 1
2016.11.02 20:05:50 3: NUKIBridge (NukiBridge1) - Param Code:
2016.11.02 20:05:50 3: NUKIBridge (NukiBridge1) - Error: http://192.168.123.74:8080/list?token=123456: empty answer received
2016.11.02 20:05:50 3: NUKIBridge (NukiBridge1) - JSON:
2016.11.02 20:05:50 3: NUKIBridge (NukiBridge1) - Param Alive: 1
2016.11.02 20:05:50 3: NUKIBridge (NukiBridge1) - Param Code:
2016.11.02 20:05:50 3: NUKIBridge (NukiBridge1) - Error: read from http://192.168.123.74:8080 timed out
2016.11.02 20:05:50 3: NUKIBridge (NukiBridge1) - JSON:
2016.11.02 20:07:50 3: NUKIBridge (NukiBridge1) - Param Alive: 1
2016.11.02 20:07:50 3: NUKIBridge (NukiBridge1) - Param Code:
2016.11.02 20:07:50 3: NUKIBridge (NukiBridge1) - Error: read from http://192.168.123.74:8080 timed out
2016.11.02 20:07:50 3: NUKIBridge (NukiBridge1) - JSON:
2016.11.02 20:07:50 3: NUKIBridge (NukiBridge1) - Param Alive: 1
2016.11.02 20:07:50 3: NUKIBridge (NukiBridge1) - Param Code:
2016.11.02 20:07:50 3: NUKIBridge (NukiBridge1) - Error: http://192.168.123.74:8080/list?token=123456: empty answer received
2016.11.02 20:07:50 3: NUKIBridge (NukiBridge1) - JSON:
pi@raspi3Fhem:~ $ curl http://192.168.123.74:8080/list?token=123456
[{"nukiId": 92145697, "name": "W58 unten", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-11-02T18:10:16+00:00"}}]
pi@raspi3Fhem:~ $
pi@raspi3Fhem:~ $ curl http://192.168.123.74:8080/list?token=123456
[{"nukiId": 92145697, "name": "W58 unten", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-11-02T18:10:16+00:00"}}]
pi@raspi3Fhem:~ $
Zitatcurl http://192.168.11.119:8080/list?token=123456nur
Zitatcurl: (52) Empty reply from serverzurück, Status ist not connected
Zitat[{"nukiId": 88412473, "name": "Wohnungstuer"},{"nukiId": 33527041, "name": "Haustuer", "lastKnownState": {"state": 1, "stateName": "locked", "batteryCritical": false, "timestamp": "2016-11-02T19:44:48+00:00"}}]Wobei nur ein Nuki vorhanden ist, Wohnungstür ist eingeschickt.
Zitat von: TomD am 02 November 2016, 21:16:54Ich glaube Du hast mich da falsch verstanden. curl hat mit dem Modul nichts zu tun. Mich interessiert ob das Modul Daten bekommt.
also kein Unterschied
Zitatcurl: (52) Empty reply from server
pi@raspberrypi:~ $ curl http://192.168.11.119:8080/list?token=123456
curl: (52) Empty reply from server
pi@raspberrypi:~ $ curl http://192.168.11.119:8080/list?token=123456
curl: (52) Empty reply from server
pi@raspberrypi:~ $ curl http://192.168.11.119:8080/list?token=123456
curl: (52) Empty reply from server
pi@raspberrypi:~ $ curl http://192.168.11.119:8080/list?token=123456
curl: (52) Empty reply from server
pi@raspberrypi:~ $ curl http://192.168.11.119:8080/list?token=123456
curl: (52) Empty reply from server
pi@raspberrypi:~ $ curl http://192.168.11.119:8080/list?token=123456
Zitatpi@raspberrypi:~ $ curl http://192.168.11.119:8080/list?token=123456
[{"nukiId": 44412473, "name": "Wohnungstuer"},{"nukiId": 33527041, "name": "Haustuer", "lastKnownState": {"state": 1, "stateName": "locked", "batteryCritical": false, "timestamp": "2016-11-02T19:44:48+00:00"}}]
73_NUKIBridge.pm
my $version = "0.2.1";
my $bridgeAPI = "1.0.2";
74_NUKIDevice.pm
my $version = "0.2.1";
{"timestamp": null, "type": "System-Startup", "version": "1.3.6"},
define nuki01 NUKIbridge 192.168.178.xxx xxxxxx
2016-11-04 14:17:06 NUKIBridge nuki01 statusRequest
2016-11-04 14:17:12 NUKIBridge nuki01 statusRequest
2016-11-04 14:17:12 NUKIBridge nuki01 not connected
2016-11-04 14:17:12 NUKIBridge nuki01 lastError: http://192.168.178.xxx:8080/list?token=xxxxxx: empty answer received
2016-11-04 14:17:17 NUKIBridge nuki01 not connected
2016-11-04 14:17:17 NUKIBridge nuki01 lastError: read from http://192.168.178.xxx:8080 timed out
curl http://192.168.178.xxx:8080/list?token=xxxxxx
[{"nukiId": 123456789, "name": "Tstr23 ", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-11-04T13:10:39+00:00"}}]
lastError
read from http://192.168.178.xxx:8080 timed out 2016-11-04 16:28:15
state Initialized 2016-11-04 16:27:52
Internals:
CFGFN
DEF 192.168.178.xxx 123456
HOST 192.168.178.xxx
INTERVAL 60
NAME nuki01
NR 501
PORT 8080
STATE Initialized
TOKEN 123456
TYPE NUKIBridge
VERSION 0.3.7
Readings:
2016-11-04 16:29:12 bridgeType Hardware
2016-11-04 16:29:12 currentTime 2016-11-04T15:29:12+00:00
2016-11-04 16:29:12 hardwareId 98598929
2016-11-04 16:28:15 lastError read from http://192.168.178.xxx:8080 timed out
2016-11-04 16:29:12 serverConnected true
2016-11-04 16:29:12 serverId 132456789
2016-11-04 16:27:52 state Initialized
2016-11-04 16:29:12 uptime 4466
Attributes:
room NUKI
2016.11.04 16:49:32 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/log?token=123456
2016.11.04 16:49:32 3: NUKIBridge (nuki01) - Kurz vor der Bedingung nach decode_json ARRAY
2016.11.04 16:44:37 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/list?token=123456
2016.11.04 16:44:37 4: NUKIBridge (nuki01) - Call NUKIBridge_Get
2016.11.04 16:44:40 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/info?token=123456
2016.11.04 16:44:40 3: NUKIBridge (nuki01) - Param Alive:
2016.11.04 16:44:40 3: NUKIBridge (nuki01) - Param Code:
2016.11.04 16:44:40 3: NUKIBridge (nuki01) - Error: http://192.168.178.xxx:8080/info?token=123456: empty answer received
2016.11.04 16:44:40 3: NUKIBridge (nuki01) - JSON:
2016.11.04 16:44:40 4: NUKIBridge (nuki01) - error while requesting: http://192.168.178.xxx:8080/info?token=123456: empty answer received
2016.11.04 16:44:47 3: NUKIBridge (nuki01) - Param Alive:
2016.11.04 16:44:47 3: NUKIBridge (nuki01) - Param Code:
2016.11.04 16:44:47 3: NUKIBridge (nuki01) - Error: read from http://192.168.178.xxx:8080 timed out
2016.11.04 16:44:47 3: NUKIBridge (nuki01) - JSON:
2016.11.04 16:44:47 4: NUKIBridge (nuki01) - error while requesting: read from http://192.168.178.xxx:8080 timed out
2016.11.04 16:46:20 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/clearlog?token=123456
2016.11.04 16:46:58 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/fwupdate?token=123456
2016.11.04 16:48:05 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/reboot?token=123456
2016.11.04 16:48:43 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/info?token=123456
2016.11.04 16:48:43 3: NUKIBridge (nuki01) - Param Alive:
2016.11.04 16:48:43 3: NUKIBridge (nuki01) - Param Code: 200
2016.11.04 16:48:43 3: NUKIBridge (nuki01) - Error:
2016.11.04 16:48:43 3: NUKIBridge (nuki01) - JSON: {"bridgeType": 1, "ids": {"hardwareId": 123456789, "serverId": 123456789}, "versions": {"firmwareVersion": "1.3.6", "wifiFirmwareVersion": "1.0.1"}, "uptime": 33, "currentTime": "2016-11-04T15:48:43+00:00", "serverConnected": true, "scanResults": [{"nukiId": 102765321, "name": "Nuki_06201309", "rssi": -79, "paired": true}]}
2016.11.04 16:38:33 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 397.
2016.11.04 16:38:33 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 398.
{"timestamp": "2016-11-04T17:45:14+00:00", "type": "FirmUpdateCheck", "fwType": "wlan"},
{"timestamp": "2016-11-04T17:45:14+00:00", "type": "BLE-Connected", "nukiId": "06201309"},
{"timestamp": "2016-11-04T17:45:14+00:00", "type": "BLE-Connect", "macAddr": "54D272201309"},
{"timestamp": "2016-11-04T17:45:14+00:00", "type": "BLE-Connect", "nukiId": "06201309"},
{"timestamp": "2016-11-04T17:45:15+00:00", "type": "FirmUpdateCheck", "fwType": "main"},
{"timestamp": "2016-11-04T17:45:15+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-04T17:45:15+00:00", "type": "SSE-PushNukisResponse", "error": 0},
{"timestamp": "2016-11-04T17:45:15+00:00", "type": "SSE-PushNukisRequest"},
{"timestamp": "2016-11-04T17:45:15+00:00", "type": "HTTP-FwUpdate"},
2016.11.05 11:46:24 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/list?token=123456
2016.11.05 11:46:24 4: NUKIBridge (nuki01) - Call NUKIBridge_Get
2016.11.05 11:46:27 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/info?token=123456
2016.11.05 11:46:27 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 398.
2016.11.05 11:46:27 3: NUKIBridge (nuki01) - Param Alive:
2016.11.05 11:46:27 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 399.
2016.11.05 11:46:27 3: NUKIBridge (nuki01) - Param Code:
2016.11.05 11:46:27 3: NUKIBridge (nuki01) - Error: http://192.168.178.xxx:8080/info?token=123456: empty answer received
2016.11.05 11:46:27 3: NUKIBridge (nuki01) - JSON:
2016.11.05 11:46:27 4: NUKIBridge (nuki01) - error while requesting: http://192.168.178.xxx:8080/info?token=123456: empty answer received
2016.11.05 11:46:34 3: NUKIBridge (nuki01) - Param Alive:
2016.11.05 11:46:34 3: NUKIBridge (nuki01) - Param Code:
2016.11.05 11:46:34 3: NUKIBridge (nuki01) - Error: read from http://192.168.178.xxx:8080 timed out
2016.11.05 11:46:34 3: NUKIBridge (nuki01) - JSON:
2016.11.05 11:46:34 4: NUKIBridge (nuki01) - error while requesting: read from http://192.168.178.xxx:8080 timed out
2016.11.05 11:49:24 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/clearlog?token=123456
2016.11.05 11:51:44 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/fwupdate?token=123456
{"timestamp": "2016-11-05T10:51:45+00:00", "type": "HTTP-FwUpdate"},
2016.11.05 11:54:49 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/reboot?token=123456
{"timestamp": null, "type": "System-Startup", "version": "1.3.6"},
{"timestamp": "2016-11-05T10:54:52+00:00", "type": "System-Reset"},
2016.11.05 11:56:40 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/info?token=123456
2016.11.05 11:56:40 3: NUKIBridge (nuki01) - Param Alive:
2016.11.05 11:56:40 3: NUKIBridge (nuki01) - Param Code: 200
2016.11.05 11:56:40 3: NUKIBridge (nuki01) - Error:
2016.11.05 11:56:40 3: NUKIBridge (nuki01) - JSON: {"bridgeType": 1, "ids": {"hardwareId": 12345678, "serverId": 123456789}, "versions": {"firmwareVersion": "1.3.6", "wifiFirmwareVersion": "1.0.1"}, "uptime": 106, "currentTime": "2016-11-05T10:56:40+00:00", "serverConnected": true, "scanResults": [{"nukiId": 123456789, "name": "Nuki_12345678", "rssi": -78, "paired": true}]}
{"timestamp": "2016-11-05T10:56:40+00:00", "type": "HTTP-Info"},
2016.11.05 11:59:06 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/log?token=123456
2016.11.05 11:59:06 3: NUKIBridge (nuki01) - Kurz vor der Bedingung nach decode_json ARRAY
Internals:
DEF 192.168.178.xxx 123456
HOST 192.168.178.xxx
INTERVAL 60
NAME nuki01
NR 489
PORT 8080
STATE Initialized
TOKEN 123456
TYPE NUKIBridge
VERSION 0.3.9
Readings:
2016-11-05 11:56:40 bridgeType Hardware
2016-11-05 11:56:40 currentTime 2016-11-05T10:56:40+00:00
2016-11-05 11:56:40 hardwareId 98598929
2016-11-05 11:46:34 lastError read from http://192.168.178.xxx:8080 timed out
2016-11-05 11:56:40 serverConnected true
2016-11-05 11:56:40 serverId 287592143
2016-11-05 11:40:28 state Initialized
2016-11-05 11:56:40 uptime 106
Attributes:
room NUKI
verbose 5
http://192.168.178.xxx:8080/log?token=123456
Resource interpreted as Document but transferred with MIME type application/json: "http://192.168.178.xxx:8080/log?token=123456".
Navigated to http://192.168.178.233:8080/log?token=ge5b7e
favicon.ico:1 GET http://192.168.178.233:8080/favicon.ico 400 (Bad Request)
common.js 5ms
app.js 9ms
2016.11.05 13:45:55 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/list?token=132456
2016.11.05 13:45:55 4: NUKIBridge (nuki01) - Call NUKIBridge_Get
2016.11.05 13:45:58 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/info?token=132456
2016.11.05 13:45:59 3: NUKIBridge (nuki01) - Param Alive:
2016.11.05 13:45:59 3: NUKIBridge (nuki01) - Param Code:
2016.11.05 13:45:59 3: NUKIBridge (nuki01) - Error: http://192.168.178.xxx:8080/info?token=132456: empty answer received
2016.11.05 13:45:59 3: NUKIBridge (nuki01) - JSON:
2016.11.05 13:45:59 4: NUKIBridge (nuki01) - error while requesting: http://192.168.178.xxx:8080/info?token=ge5b7e: empty answer received
2016.11.05 13:46:06 3: NUKIBridge (nuki01) - Param Alive:
2016.11.05 13:46:06 3: NUKIBridge (nuki01) - Param Code:
2016.11.05 13:46:06 3: NUKIBridge (nuki01) - Error: read from http://192.168.178.xxx:8080 timed out
2016.11.05 13:46:06 3: NUKIBridge (nuki01) - JSON:
2016.11.05 13:46:06 4: NUKIBridge (nuki01) - error while requesting: read from http://192.168.178.xxx:8080 timed out
2016.11.05 15:22:14 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/list?token=123456
2016.11.05 15:22:14 4: NUKIBridge (nuki01) - Call NUKIBridge_Get
2016.11.05 15:22:24 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 398.
2016.11.05 15:22:24 3: NUKIBridge (nuki01) - Param Alive:
2016.11.05 15:22:24 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 399.
2016.11.05 15:22:24 3: NUKIBridge (nuki01) - Param Code:
2016.11.05 15:22:24 3: NUKIBridge (nuki01) - Error: read from http://192.168.178.xxx:8080 timed out
2016.11.05 15:22:24 3: NUKIBridge (nuki01) - JSON:
2016.11.05 15:22:24 4: NUKIBridge (nuki01) - error while requesting: read from http://192.168.178.xxx:8080 timed out
define nukiTest HTTPMOD http://192.168.178.xxx:8080/list?token=123456 10
HTTP/1.1 200 OK Connection: Close Content-Type: application/json;charset=utf-8 Transfer-Encoding: chunked 1 [ A6 {"nukiId": 123456789, "name": "Tstr23 ", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-11-05T11:55:14+00:00"}}] 0
Zitat von: CoolTux am 05 November 2016, 15:46:54Klingt irgendwie spannend. Gibts da dann auch ne Auflösung :D
Ok ich habe da eine allerletzte Idee wie das ganze passiert sein kann. Wäre zwar doof aber egal. Lieber erstmal testen ob es das war. Dauert aber . Melde mich heute Abend noch mal.
2016.11.05 20:58:14 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/list?token=123456
2016.11.05 20:58:14 4: NUKIBridge (nuki01) - Call NUKIBridge_Get
2016.11.05 20:58:14 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 396.
2016.11.05 20:58:14 3: NUKIBridge (nuki01) - Param Alive:
2016.11.05 20:58:14 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 397.
2016.11.05 20:58:14 3: NUKIBridge (nuki01) - Param Code:
2016.11.05 20:58:14 3: NUKIBridge (nuki01) - Error: http://192.168.178.xxx:8080/list?token=123456: empty answer received
2016.11.05 20:58:14 3: NUKIBridge (nuki01) - PATH: /list?token=123456
2016.11.05 20:58:14 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 400.
2016.11.05 20:58:14 3: NUKIBridge (nuki01) - httpheader:
2016.11.05 20:58:14 4: NUKIBridge (nuki01) - error while requesting: http://192.168.178.xxx:8080/list?token=123456: empty answer received
2016.11.05 21:21:11 3: NUKIDevice (nuki01) - empty answer received for http://192.168.178.xxx:8080/log?token=123456
2016.11.05 21:21:11 3: NUKIBridge (nuki01) - Kurz vor der Bedingung nach decode_json ARRAY
defmod nuki01 NUKIBridge 192.168.178.xxx 132465
attr nuki01 room NUKI
setstate nuki01 2016-11-06 04:39:18 bridgeType Hardware
setstate nuki01 2016-11-06 04:39:18 currentTime 2016-11-06T03:39:17+00:00
setstate nuki01 2016-11-06 04:39:18 hardwareId 98598929
setstate nuki01 2016-11-06 14:34:33 lastError read from http://192.168.178.xxx:8080 timed out
setstate nuki01 2016-11-06 04:39:18 serverConnected true
setstate nuki01 2016-11-06 04:39:18 serverId 287592143
setstate nuki01 2016-11-06 14:19:37 state Initialized
setstate nuki01 2016-11-06 04:39:18 uptime 60264
defmod nukiHaustuer NUKIDevice 123456789 nuki01
attr nukiHaustuer IODev nuki01
attr nukiHaustuer room NUKI
attr nukiHaustuer verbose 5
setstate nukiHaustuer unlatch
setstate nukiHaustuer 2016-11-06 14:42:21 battery ok
setstate nukiHaustuer 2016-11-06 14:42:21 batteryCritical false
setstate nukiHaustuer 2016-11-06 14:42:21 lockState unlatch
setstate nukiHaustuer 2016-11-06 14:42:21 state unlatch
setstate nukiHaustuer 2016-11-06 14:42:21 success true
2016.11.06 15:07:12 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/lockState?token=123456&nukiId=102765321
2016.11.06 15:07:32 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/lockState?token=123456&nukiId=102765321
2016.11.06 15:07:41 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/lockAction?token=123456&action=2&nukiId=102765321
2016.11.06 15:07:48 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/list?token=123456
2016.11.06 15:07:48 4: NUKIBridge (nuki01) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.11.06 15:07:48 4: NUKIBridge (nuki01) - Bridge ist offline
2016.11.06 15:07:51 4: NUKIBridge (nuki01) - error while requesting: read from http://192.168.178.xxx:8080 timed out
2016.11.06 15:07:52 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/lockState?token=123456&nukiId=102765321
2016.11.06 15:08:12 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/lockState?token=123456&nukiId=102765321
2016.11.06 15:08:32 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.xxx:8080/lockState?token=123456&nukiId=102765321
set nukiHaustier unlatch
Zitat von: Steeeve am 25 Oktober 2016, 21:59:09
Ob es eventuell damit zusammen hängt:
New beta firmware *v1.4.2* available. Further improves the handling of several Smart Locks on the same bridge and fixes a bug in v1.4.1 which could lead to lost commands when a command arrived before the bridge properly disconnected from the Smart Lock.
2016.11.09 13:07:26 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/list?token=123456
2016.11.09 13:07:26 4: NUKIBridge (NukiBridge) - Call NUKIBridge_Get
2016.11.09 13:07:36 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.09 13:07:37 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 397.
2016.11.09 13:07:37 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.09 13:07:37 3: NUKIBridge (NukiBridge) - Error: read from http://192.168.123.250:8080 timed out
2016.11.09 13:07:37 3: NUKIBridge (NukiBridge) - PATH: /list?token=123456
2016.11.09 13:07:37 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 400.
2016.11.09 13:07:37 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.09 13:07:37 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.123.250:8080 timed out
2016.11.09 13:10:23 3: NUKIDevice (NukiBridge) - empty answer received for http://192.168.123.250:8080/log?token=123456
2016.11.09 13:10:23 3: NUKIBridge (NukiBridge) - Kurz vor der Bedingung nach decode_json ARRAY
Zitat von: fred_feuerstein am 09 November 2016, 12:15:36
In der Bridge erhalte ich mit /list nun neben dem neuen Smartlock, noch meine beiden anderen "nicht mehr vorhandenen" Smartlocks. Ist jemandem bekannt, wie ich die aus der Bridge löschen kann? Diese Smartlocks gibts ja nicht mehr.
Internals:
CHANGED
DEF 192.168.178.56 xxxxxx
HOST 192.168.178.56
INTERVAL 60
NAME NBridge1
NR 810
PORT 8080
STATE not connected
TOKEN xxxxxx
TYPE NUKIBridge
VERSION 0.2.1
Readings:
2016-11-04 20:42:44 0_name CobraTuer
2016-11-04 20:42:44 0_nukiId 102844921
2016-11-04 20:42:44 bridgeAPI 1.0.2
2016-11-09 13:12:43 lastError read from http://192.168.178.56:8080 timed out
2016-11-04 20:42:44 smartlockCount 1
2016-11-09 13:12:43 state not connected
Attributes:
group Gateway
room 9.6_System
{"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.3.6", "wifiFirmwareVersion": "1.0.1"}, "uptime": 399653, "currentTime": "2016-11-09T12:16:09+00:00", "serverConnected": true, "scanResults": [{"nukiId": 102844921, "name": "Nuki_062149F9", "rssi": -79, "paired": true}]}
Internals:
CHANGED
DEF 102844921 IODev=NBridge1
INTERVAL 20
IODev NBridge1
NAME NUKIDevice102844921
NR 811
NUKIID 102844921
STATE unlocked
TYPE NUKIDevice
VERSION 0.2.1
Readings:
2016-11-09 13:16:25 battery low
2016-11-09 13:16:25 batteryCritical 0
2016-11-09 13:16:25 lockState unlocked
2016-11-09 13:16:25 state unlocked
2016-11-09 13:16:25 success 1
Helper:
Attributes:
IODev NBridge1
alias CobraTuer
event-on-change-reading .*
icon hm_keymatic
room 1.5_Flur
[{"nukiId": 102844921, "name": "CobraTuer", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-11-09T12:12:12+00:00"}}]
2016.11.09 13:45:49 5: readings set for NUKIDevice102844921
2016.11.09 13:45:49 5: parse status message for NUKIDevice102844921
2016.11.09 13:45:49 4: NUKIBridge (NBridge1) - error while requesting: http://192.168.178.56:8080/lockState?token=xxxxxx&nukiId=102844921: empty answer received
2016.11.09 13:45:49 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.09 13:45:49 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=xxxxxx&nukiId=102844921
2016.11.09 13:45:47 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.09 13:45:47 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.09 13:45:47 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.09 13:45:47 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=xxxxxx&nukiId=102844921
{"state": 3, "stateName": "unlocked", "batteryCritical": false, "success": true}
Zitat von: Cobra am 09 November 2016, 13:23:28In der App wird rechts oben ein (i) abgezeigt wenn es besondere Meldungen gibt, zB Software Update, oder auch leere Batterie.
Habe jetzt jedoch ein kleines Problem. Das SmartLock hat ständig das Reading battery low, obwohl ich schon mehrfach mit neuen Batterien versucht habe. In der Nuki-App selbst finde ich keine Batterieanzeige aber auch keine Warnung dass die Batterien bald leer sind.
Kann es sein dass die ersten Batterien leer waren beim anlegen und er jetzt das Reading nicht mehr aktualisiert?
Zitat von: Cobra am 09 November 2016, 13:49:00
Hey CoolTux,
hier das Log nach dem statusRequest.
Nicht irritieren lassen, hab bei mir das Log umgedreht so dass die aktuellste Meldung immer oben ist :-)Code Auswählen2016.11.09 13:45:49 5: readings set for NUKIDevice102844921
2016.11.09 13:45:49 5: parse status message for NUKIDevice102844921
2016.11.09 13:45:49 4: NUKIBridge (NBridge1) - error while requesting: http://192.168.178.56:8080/lockState?token=xxxxxx&nukiId=102844921: empty answer received
2016.11.09 13:45:49 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.09 13:45:49 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=xxxxxx&nukiId=102844921
2016.11.09 13:45:47 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.09 13:45:47 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.09 13:45:47 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.09 13:45:47 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=xxxxxx&nukiId=102844921
Was komisch ist, wenn ich http://192.168.178.56:8080/lockState?token=xxxxxx&nukiId=102844921 in den Browser eingebe bekomme ichCode Auswählen{"state": 3, "stateName": "unlocked", "batteryCritical": false, "success": true}
Also keine 0 bei batteryCritical sondern false.
NUKIDevice (NUKIDevice102844921) - JSON: {"state": 3, "stateName": "unlocked", "batteryCritical": false, "success": true}
"batteryCritical": false, "success": true
Zitat von: CoolTux am 09 November 2016, 17:37:06
Habe was lustiges entdeckt.Code Auswählen
"batteryCritical": false, "success": true
Und jetzt schaue Dir mal Deine Readings batteryCritical und success an.
Und verrate mir mal was true und false in eigentlich sind aus Informatiker Sicht ;D
Aber wie das kommt kann ich Dir noch nicht sagen. Aber ist lustig
Zitat von: Steeeve am 09 November 2016, 17:49:51
Aber das passt doch, oder?
In dem Fall nicht kritisch, also ok und success:true bekommt man bei erfolgreicher Action, nicht?
2016.11.09 19:44:59 3: NUKIDevice (NUKIDevice102844921) - JSON2: battery 0 und success 1
2016.11.09 19:44:59 3: NUKIDevice (NUKIDevice102844921) - JSON: {"state": 3, "stateName": "unlocked", "batteryCritical": false, "success": true}
2016.11.09 19:44:56 3: NUKIDevice (NUKIDevice102844921) - JSON2: battery 0 und success 1
2016.11.09 19:44:56 3: NUKIDevice (NUKIDevice102844921) - JSON: {"state": 3, "stateName": "unlocked", "batteryCritical": false, "success": true}
Zitat von: fred_feuerstein am 09 November 2016, 13:59:08
hmm, bei mir steht im Device-Modul bei Battery OK und bei batteryCritical steht false.
Also genau wie es sein sollte, denke ich.
Keine Ahnung, warum da bei Dir eine 0 steht. Und battery low.
Zitat von: CoolTux am 09 November 2016, 19:56:05
Kannst du mal bitte schauen welche Perlversion und welche libjson-perl Version Du hast?
2016.11.11 17:31:27 5: parse status message for NUKIDevice102844921
2016.11.11 17:31:27 3: NUKIDevice (NUKIDevice102844921) - JSON2: battery 0 und success 1
2016.11.11 17:31:27 3: NUKIDevice (NUKIDevice102844921) - JSON: {"state": 1, "stateName": "locked", "batteryCritical": false, "success": true}
2016.11.11 17:31:25 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.11 17:31:25 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.11 17:31:25 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.11 17:31:25 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=xxxx&nukiId=102844921
2016.11.11 17:31:09 4: NUKIBridge (NBridge1) - error while requesting: read from http://192.168.178.56:8080 timed out
2016.11.11 17:31:05 4: NUKIBridge (NBridge1) - error while requesting: http://192.168.178.56:8080/lockState?token=xxxx&nukiId=102844921: empty answer received
2016.11.11 17:31:05 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.11 17:31:05 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.11 17:31:05 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.11 17:31:05 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=Fxxxx&nukiId=102844921
2016.11.11 17:30:59 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockAction?token=xxxx&action=2&nukiId=102844921
2016.11.11 17:30:55 4: NUKIBridge (NBridge1) - Bridge ist offline
2016.11.11 17:30:45 4: NUKIBridge (NBridge1) - error while requesting: http://192.168.178.56:8080/lockState?token=xxxx&nukiId=102844921: empty answer received
2016.11.11 17:30:45 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.11 17:30:45 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.11 17:30:45 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.11 17:30:45 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=xxxx&nukiId=102844921
2016.11.11 17:30:44 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.11.11 17:30:44 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=xxxx
2016.11.11 17:30:24 5: readings set for NUKIDevice102844921
2016.11.11 17:30:24 5: parse status message for NUKIDevice102844921
2016.11.11 17:30:24 3: NUKIDevice (NUKIDevice102844921) - JSON2: battery 0 und success 1
2016.11.11 17:30:24 3: NUKIDevice (NUKIDevice102844921) - JSON: {"state": 3, "stateName": "unlocked", "batteryCritical": false, "success": true}
2016.11.11 17:30:22 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.11 17:30:22 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.11 17:30:22 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.11 17:30:22 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=xxxx&nukiId=102844921
2016.11.11 17:30:05 5: parse status message for NUKIDevice102844921
2016.11.11 17:30:05 3: NUKIDevice (NUKIDevice102844921) - JSON2: battery 0 und success 1
2016.11.11 17:30:05 3: NUKIDevice (NUKIDevice102844921) - JSON: {"state": 3, "stateName": "unlocked", "batteryCritical": false, "success": true}
2016.11.11 17:30:02 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.11 17:30:02 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.11 17:30:02 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.11 17:30:02 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=xxxx&nukiId=102844921
2016.11.11 17:29:52 4: NUKIBridge (NBridge1) - Bridge ist offline
2016.11.11 17:29:50 4: NUKIBridge (NBridge1) - error while requesting: http://192.168.178.56:8080/lockAction?token=xxxx&action=2&nukiId=102844921: empty answer received
2016.11.11 17:29:50 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockAction?token=xxxx&action=2&nukiId=102844921
[
{"timestamp": "2016-11-11T17:45:57+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:45:41+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:45:41+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:45:40+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T17:45:39+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T17:45:39+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T17:45:39+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:45:38+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T17:45:38+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:45:38+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:45:38+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:45:28+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:45:18+00:00", "type": "HTTP-List"},
{"timestamp": "2016-11-11T17:45:18+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:44:58+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:44:58+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:44:35+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:44:35+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:44:35+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:44:25+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:44:15+00:00", "type": "HTTP-List"},
{"timestamp": "2016-11-11T17:44:15+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:43:54+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:43:54+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:43:53+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T17:43:53+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T17:43:53+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T17:43:52+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:43:52+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T17:43:52+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:43:52+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:43:52+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:43:35+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:43:35+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:43:34+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T17:43:33+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T17:43:33+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T17:43:33+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:43:32+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T17:43:32+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:43:32+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:43:32+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:43:22+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:43:12+00:00", "type": "HTTP-List"},
{"timestamp": "2016-11-11T17:43:12+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:42:52+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:42:52+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:42:51+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T17:42:50+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T17:42:50+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T17:42:50+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:42:49+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T17:42:49+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:42:49+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:42:49+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:42:33+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:42:33+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:42:31+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T17:42:30+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T17:42:30+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T17:42:30+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:42:29+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T17:42:29+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:42:29+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:42:29+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:42:20+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:42:10+00:00", "type": "HTTP-List"},
{"timestamp": "2016-11-11T17:42:09+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:41:49+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:41:49+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:41:47+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T17:41:47+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T17:41:47+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T17:41:47+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:41:46+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T17:41:46+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:41:46+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:41:46+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T17:41:29+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T17:41:29+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:41:28+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T17:41:27+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T17:41:27+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T17:41:27+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T17:41:26+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"}
]
2016.11.11 19:48:29 4: NUKIBridge (NBridge1) - Bridge ist offline
2016.11.11 19:48:22 5: readings set for NUKIDevice102844921
2016.11.11 19:48:22 5: parse status message for NUKIDevice102844921
2016.11.11 19:48:22 3: NUKIDevice (NUKIDevice102844921) - JSON2: battery 0 und success 1
2016.11.11 19:48:22 3: NUKIDevice (NUKIDevice102844921) - JSON: {"state": 1, "stateName": "locked", "batteryCritical": false, "success": true}
2016.11.11 19:48:19 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.11 19:48:19 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.11 19:48:19 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.11 19:48:19 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=FX0dQQ&nukiId=102844921
2016.11.11 19:48:19 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2016.11.11 19:48:19 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=FX0dQQ
2016.11.11 19:47:59 5: parse status message for NUKIDevice102844921
2016.11.11 19:47:59 3: NUKIDevice (NUKIDevice102844921) - JSON2: battery 0 und success 1
2016.11.11 19:47:59 3: NUKIDevice (NUKIDevice102844921) - JSON: {"state": 1, "stateName": "locked", "batteryCritical": false, "success": true}
2016.11.11 19:47:57 4: NUKIBridge (NBridge1) - error while requesting: http://192.168.178.56:8080/lockAction?token=FX0dQQ&action=1&nukiId=102844921: empty answer received
2016.11.11 19:47:57 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockAction?token=FX0dQQ&action=1&nukiId=102844921
2016.11.11 19:47:56 5: NUKIDevice (NUKIDevice102844921) - Call InternalTimer
2016.11.11 19:47:56 5: NUKIDevice (NUKIDevice102844921) - Call NUKIDevice_GetUpdate
2016.11.11 19:47:56 5: NUKIDevice (NUKIDevice102844921) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2016.11.11 19:47:56 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.56:8080/lockState?token=FX0dQQ&nukiId=102844921
[
{"timestamp": "2016-11-11T18:48:18+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:48:10+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:48:09+00:00", "type": "WLAN-TxDropped", "connection": 0, "bytes": 1509},
{"timestamp": "2016-11-11T18:48:09+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:47:59+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:47:59+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:47:57+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T18:47:56+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T18:47:56+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T18:47:56+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:47:56+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T18:47:56+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:47:56+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:47:56+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:47:39+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:46:55+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:46:54+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T18:46:53+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T18:46:53+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T18:46:53+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:46:53+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T18:46:53+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:46:53+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:46:53+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:46:36+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:46:36+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:46:35+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T18:46:34+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T18:46:34+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T18:46:34+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:46:33+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T18:46:33+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:46:33+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:46:33+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:46:27+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:46:13+00:00", "type": "HTTP-List"},
{"timestamp": "2016-11-11T18:46:13+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:45:52+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:45:52+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:45:51+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T18:45:50+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T18:45:50+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T18:45:50+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:45:50+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T18:45:50+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:45:50+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:45:50+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:45:33+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:45:33+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:45:31+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T18:45:30+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T18:45:30+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T18:45:30+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:45:30+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T18:45:30+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:45:30+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:45:30+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:45:20+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:45:10+00:00", "type": "HTTP-List"},
{"timestamp": "2016-11-11T18:45:10+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:44:52+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:44:52+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:44:51+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T18:44:50+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T18:44:50+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T18:44:50+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:44:50+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T18:44:50+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:44:50+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:44:50+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:44:32+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:44:32+00:00", "type": "BLE-Disconnected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:44:32+00:00", "type": "BLE-ReceivingMsg", "nukiId": "062149F9", "cmdId": "000C"},
{"timestamp": "2016-11-11T18:44:31+00:00", "type": "BLE-SendingMsg", "nukiId": "062149F9", "cmdId": "0001"},
{"timestamp": "2016-11-11T18:44:31+00:00", "type": "BLE-Connect", "handles": [24, 28]},
{"timestamp": "2016-11-11T18:44:31+00:00", "type": "BLE-Connected", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:44:30+00:00", "type": "BLE-Connect", "macAddr": "54D2722149F9"},
{"timestamp": "2016-11-11T18:44:30+00:00", "type": "BLE-Connect", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:44:30+00:00", "type": "HTTP-LockState", "nukiId": "062149F9"},
{"timestamp": "2016-11-11T18:44:30+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:44:21+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-11T18:44:07+00:00", "type": "HTTP-List"},
{"timestamp": "2016-11-11T18:44:07+00:00", "type": "WLAN-SocketConnected", "connection": 0},
{"timestamp": "2016-11-11T18:43:52+00:00", "type": "WLAN-SocketDisconnected", "connection": 0}
]
ZitatDanke für die Info.
Wir haben eine Beta Version der Bridge verfügbar, welche das Problem beheben sollte.
Wenn Sie uns ein Foto der ID der Bridge senden, können wir die Firmware für Sie gerne freischalten.
2016.11.16 17:21:30 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.178.56:8080 timed out
2016.11.16 17:21:30 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.16 17:21:30 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.16 17:21:30 3: NUKIBridge (NukiBridge) - Error: read from http://192.168.178.56:8080 timed out
2016.11.16 17:21:30 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.16 17:21:30 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.16 17:21:25 4: NUKIBridge (NukiBridge) - error while requesting: http://192.168.178.56:8080/list?token=xxxxxx: empty answer received
2016.11.16 17:21:25 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.16 17:21:25 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.16 17:21:25 3: NUKIBridge (NukiBridge) - Error: http://192.168.178.56:8080/list?token=xxxxxx: empty answer received
2016.11.16 17:21:25 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.16 17:21:25 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.16 17:21:25 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=xxxxxx
2016.11.16 17:21:21 3: NUKIBridge (NukiBridge) - Kurz vor der Bedingung nach decode_json ARRAY
2016.11.16 17:21:21 3: NUKIDevice (NukiBridge) - empty answer received for http://192.168.178.56:8080/log?token=xxxxxx
2016.11.16 17:21:00 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=xxxxxx
2016.11.16 17:20:57 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.178.56:8080 timed out
2016.11.16 17:20:57 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.16 17:20:57 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.16 17:20:57 3: NUKIBridge (NukiBridge) - Error: read from http://192.168.178.56:8080 timed out
2016.11.16 17:20:57 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.16 17:20:57 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.16 17:20:27 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=xxxxxx
2016.11.16 17:20:19 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.178.56:8080 timed out
2016.11.16 17:20:19 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.16 17:20:19 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 354.
2016.11.16 17:20:19 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.16 17:20:19 3: NUKIBridge (NukiBridge) - Error: read from http://192.168.178.56:8080 timed out
2016.11.16 17:20:19 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.16 17:20:19 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 351.
2016.11.16 17:20:19 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.16 17:20:19 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 350.
2016.11.16 17:19:48 3: NUKIBridge (NukiBridge) - defined with host 192.168.178.56 on port 8080, Token xxxxxx
Readings
lastError
read from http://192.168.178.56:8080 timed out
2016-11-16 17:22:52
state
Initialized
2016-11-16 17:22:07
Content-Length: 328
Content-Type: application/json;charset=utf-8
Connection: Close
2016.11.16 17:32:01 3: NUKIBridge (NukiBridge) - httpheader: HTTP/1.1 200 OK
2016.11.16 17:32:01 3: NUKIBridge (NukiBridge) - PATH: /info?token=xxxxxx
2016.11.16 17:32:01 3: NUKIBridge (NukiBridge) - Error:
2016.11.16 17:32:01 3: NUKIBridge (NukiBridge) - Param Code: 200
2016.11.16 17:32:01 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.16 17:32:01 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/info?token=xxxxxx
2016.11.16 17:30:23 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.178.56:8080 timed out
2016.11.16 17:30:23 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.16 17:30:23 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.16 17:30:23 3: NUKIBridge (NukiBridge) - Error: read from http://192.168.178.56:8080 timed out
2016.11.16 17:30:23 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.16 17:30:23 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.16 17:29:52 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=xxxxxx
Readings:
2016-11-16 17:32:01 bridgeType Hardware
2016-11-16 17:32:01 currentTime 2016-11-16T16:32:02+00:00
2016-11-16 17:32:01 hardwareId 95991041
2016-11-16 17:35:11 lastError read from http://192.168.178.56:8080 timed out
2016-11-16 17:32:01 serverConnected 1
2016-11-16 17:32:01 serverId 1337010944
2016-11-16 17:22:07 state Initialized
2016-11-16 17:32:01 uptime 38297
define nuki01 NUKIBridge 192.168.178.xxx 123456
attr nuki01 room NUKI
define nukiHaustuer NUKIDevice 123456789 nuki01
attr nukiHaustuer IODev nuki01
attr nukiHaustuer interval 60
attr nukiHaustuer room NUKI
ZitatSoweit funktioniert das Smartlock, außer dass die Befehle nicht immer aufs erste Mal übermittelt werden.
2016.11.18 17:52:15 4: NUKIBridge (NukiBridge) - received http code 503 without any data after requesting
Content-Length: 0
Connection: Close
2016.11.18 17:52:15 3: NUKIBridge (NukiBridge) - httpheader: HTTP/1.1 503 Service Unavailable
2016.11.18 17:52:15 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.18 17:52:15 3: NUKIBridge (NukiBridge) - Error:
2016.11.18 17:52:15 3: NUKIBridge (NukiBridge) - Param Code: 503
2016.11.18 17:52:15 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.18 17:52:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=xxxxxx
2016.11.18 17:51:56 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=xxxxxx
Content-Length: 329
Content-Type: application/json;charset=utf-8
Connection: Close
2016.11.18 17:51:42 3: NUKIBridge (NukiBridge) - httpheader: HTTP/1.1 200 OK
2016.11.18 17:51:42 3: NUKIBridge (NukiBridge) - PATH: /info?token=xxxxxx
2016.11.18 17:51:42 3: NUKIBridge (NukiBridge) - Error:
2016.11.18 17:51:42 3: NUKIBridge (NukiBridge) - Param Code: 200
2016.11.18 17:51:42 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.18 17:51:42 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/info?token=xxxxxx
2016.11.18 17:51:41 3: NUKIBridge (NukiBridge) - Kurz vor der Bedingung nach decode_json ARRAY
2016.11.18 17:51:41 3: NUKIDevice (NukiBridge) - empty answer received for http://192.168.178.56:8080/log?token=xxxxxx
2016.11.18 17:51:25 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.178.56:8080 timed out
2016.11.18 17:51:25 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.18 17:51:25 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.18 17:51:25 3: NUKIBridge (NukiBridge) - Error: read from http://192.168.178.56:8080 timed out
2016.11.18 17:51:25 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.18 17:51:25 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.18 17:50:55 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.56:8080/list?token=xxxxxx
2016.11.18 17:50:31 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.18 17:50:31 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 354.
2016.11.18 17:50:31 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.18 17:50:31 3: NUKIBridge (NukiBridge) - Error: read from http://192.168.178.56:8080 timed out
2016.11.18 17:50:31 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.18 17:50:31 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 351.
2016.11.18 17:50:31 3: NUKIBridge (NukiBridge) - Param Alive:
Content-Length: 0
Connection: Close
2016.11.18 17:50:29 3: NUKIBridge (NukiBridge) - httpheader: HTTP/1.1 503 Service Unavailable
2016.11.18 17:50:29 3: NUKIBridge (NukiBridge) - PATH: /list?token=xxxxxx
2016.11.18 17:50:29 3: NUKIBridge (NukiBridge) - Error:
2016.11.18 17:50:29 3: NUKIBridge (NukiBridge) - Param Code: 503
2016.11.18 17:50:29 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.18 17:50:29 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 350.
2016.11.18 17:50:01 3: NUKIBridge (NukiBridge) - defined with host 192.168.178.56 on port 8080, Token xxxxxx
ZitatSind folgende Einträge gemeint?
{"timestamp": "2016-11-22T16:10:01+00:00", "type": "WLAN-SocketDisconnected", "connection": 0},
{"timestamp": "2016-11-22T16:09:48+00:00", "type": "HTTP-List"},
{"timestamp": "2016-11-22T16:09:48+00:00", "type": "WLAN-SocketConnected", "connection": 0},
Falls ja, diese zeigen nur eine Verbindung eines Clients (z.B. Browser) an.
Im obigen Beispiel eine /list Anfrage und das anschließende Disconnect des Clients.
reload 73_NUKIBridge.pm
Too many arguments for main::NUKIDevice_Parse at ./FHEM/73_NUKIBridge.pm line 387, near "undef) "
Too many arguments for main::NUKIDevice_Parse at ./FHEM/73_NUKIBridge.pm line 388, near "undef) "
2016.11.28 14:57:05 3: NUKIBridge (NukiBridge) - defined with host 192.168.123.250 on port 8080, Token omimn3
2016.11.28 14:58:05 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 350.
2016.11.28 14:58:05 3: NUKIBridge (NukiBridge) - Param Alive:
2016.11.28 14:58:05 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 351.
2016.11.28 14:58:05 3: NUKIBridge (NukiBridge) - Param Code:
2016.11.28 14:58:05 3: NUKIBridge (NukiBridge) - Error: read from http://192.168.123.250:8080 timed out
2016.11.28 14:58:05 3: NUKIBridge (NukiBridge) - PATH: /list?token=omimn3
2016.11.28 14:58:05 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 354.
2016.11.28 14:58:05 3: NUKIBridge (NukiBridge) - httpheader:
2016.11.28 14:58:05 4: NUKIBridge (NukiBridge) - error while requesting: read from http://192.168.123.250:8080 timed out
Zitat von: FhemPiUser am 28 November 2016, 19:52:04
eine frage: kann man den nuki gleichzeitig mit 2 fhem raspberries betreiben, einer zum schalten und einer nur zum status lesen?
ich würde gerne aus sicherheitsgründen den fhem raspi getrennt vom netz betreiben, der den nuki schalten kann, würde aber gerne gleichzeit mit dem fhem raspi, der im netz hängt, den status vom nuki registrieren können, er soll aus sicherheitsgründen den nuki aber nicht auf und zu machen dürfen.
Zitat von: fred_feuerstein am 29 November 2016, 16:23:07
Auch bzgl. der Bluetooth Frage. Aktuell kann FHEM noch nicht per Bluetooth mit dem Nuki kommunizieren, sondern nur per LAN/WLAN. Dafür wird neben dem Smartlock von NUKI auch deren Bridge benötigt. Also die Schnittstelle von NUKI <-> Bluetooth <-> Bridge <-> LAN/WLAN.
Ansonsten verstehe ich Deine Frage noch nicht so genau.
Du hast einen Raspi mit FHEM in deinem Netzwerk. Also ganz normal. Von diesem aus soll nur der Status vom Nuki angezeigt werden?
Würde sich sicher über Zugriffrechte regeln lassen, aber, dieser Raspi benötigt ja ohnehin Zugriff auf die Nuki Bridge.
Oder hast du so eine Art DMZ bei Dir und einen Raspi im internen Netz und einen in der DMZ und der in der DMZ soll dann Nuki schalten können?
Der interne aber nur den Status sehen?
Fragen über Fragen :)
2016.12.05 10:15:30 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/73_NUKIBridge.pm line 368.
malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "AT+CIPCLOSE=3\r\nHTT...") at ./FHEM/74_NUKIDevice.pm line 321.
malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "AT+CIPCLOSE=3\r\nHTT...") at ./FHEM/74_NUKIDevice.pm line 278.
http://<IP der Bridge>:8080/list?token=xxxxxx
http://<IP der Bridge>:8080/info?token=xxxxxx
{"bridgeType": 1, "ids": {"hardwareId": 111111, "serverId": 11111111}, "versions": {"firmwareVersion": "1.4.9", "wifiFirmwareVersion": "1.0.1"}, "uptime": 161754, "currentTime": "2016-12-06T15:28:33+00:00", "serverConnected": true, "scanResults": [{"nukiId": 111111, "name": "Nuki_06201309", "rssi": -79, "paired": true}]}
define Nuki NUKIBridge 192.168.1.13 xxxxxx
http://192.168.1.13:8080/info?token=xxxxxx#
{"bridgeType": 1, "ids": {"hardwareId": xxxxxxxxx, "serverId": xxxxxxxxx}, "versions": {"firmwareVersion": "1.4.9", "wifiFirmwareVersion": "1.0.1"}, "uptime": 37293, "currentTime": "2016-12-08T08:34:23+00:00", "serverConnected": true, "scanResults": [{"nukiId": xxxxxxxxx, "name": "Nuki_XXXXXXXX", "rssi": -71, "paired": true}]}
set Nuki autocreate
2016-12-08 14:20:23.770 NUKIBridge Nuki autocreate
2016-12-08 14:20:24.018 NUKIBridge Nuki lastError: Internal error, 503
2016-12-08 14:20:33.858 NUKIBridge Nuki lastError: read from http://192.168.1.13:8080 timed out
define Tuer NUKIDevice 1234 IODev=NukiBridge
defmod Haustuer NUKIDevice 12345678 IODev=Nuki
attr Haustuer IODev Nuki
attr Haustuer room NUKI
setstate Haustuer unlocked
setstate Haustuer 2016-12-08 15:19:26 battery ok
setstate Haustuer 2016-12-08 15:19:26 batteryCritical false
setstate Haustuer 2016-12-08 15:19:26 lockState unlocked
setstate Haustuer 2016-12-08 15:19:26 state unlocked
setstate Haustuer 2016-12-08 15:19:26 success true
Anlegen der Bridge
2016.12.11 12:39:15 3: NUKIBridge (NUKI_Bridge) - defined with host 192.168.11.119 on port 8080, Token 123456
2016.12.11 12:39:15 3: NUKIDevice (NUKI_Bridge) - create new device 'NUKIDevice101061234' for address '101061234'
2016.12.11 12:39:15 3: NUKIDevice101061234: I/O device is NUKI_Bridge
2016.12.11 12:39:15 3: NUKIDevice (NUKIDevice101061234) - defined with Code: NUKI_Bridge-101061234
2016.12.11 12:39:15 3: NUKIDevice (NUKI_Bridge) - create new device 'NUKIDevice47521234' for address '47521234'
2016.12.11 12:39:15 3: NUKIDevice47521234: I/O device is NUKI_Bridge
2016.12.11 12:39:15 3: NUKIDevice (NUKIDevice47521234) - defined with Code: NUKI_Bridge-47521234
2016.12.11 12:39:15 2: NUKIDevice (NUKI_Bridge) - autocreated 2 devices
Smartlocks haben die 1.3.5 drauf und die Bridge 1.4.10
Info
{"bridgeType": 1, "ids": {"hardwareId": 94513222, "serverId": 1369728111}, "versions": {"firmwareVersion": "1.4.10", "wifiFirmwareVersion": "1.0.1"},
"uptime": 319152, "currentTime": "2016-12-11T12:00:02+00:00", "serverConnected": true, "scanResults":
[{"nukiId": 101061234, "name": "Nuki_06064568", "rssi": -75, "paired": true},
{"nukiId": 47521234, "name": "Nuki_02D54568", "rssi": -71, "paired": true}]}
List
[{"nukiId": 101061234, "name": "Wohnungstuer", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-12-11T10:36:01+00:00"}},
{"nukiId": 47521234, "name": "Haustuer", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-12-11T10:35:53+00:00"}}]
Zitat von: _Marco_ am 11 Dezember 2016, 13:14:23
Hi, habe alles gelöscht und einen reboot gemacht und dann die Bridge neu angelegt, die Smartlocks sind automatisch angelegt worden.
Die Bridge hat den Status connected aber die Smartlocks haben den Status Initialized und ich kann nicht schliessen oder öffnen.Code AuswählenAnlegen der Bridge
2016.12.11 12:39:15 3: NUKIBridge (NUKI_Bridge) - defined with host 192.168.11.119 on port 8080, Token 123456
2016.12.11 12:39:15 3: NUKIDevice (NUKI_Bridge) - create new device 'NUKIDevice101061234' for address '101061234'
2016.12.11 12:39:15 3: NUKIDevice101061234: I/O device is NUKI_Bridge
2016.12.11 12:39:15 3: NUKIDevice (NUKIDevice101061234) - defined with Code: NUKI_Bridge-101061234
2016.12.11 12:39:15 3: NUKIDevice (NUKI_Bridge) - create new device 'NUKIDevice47521234' for address '47521234'
2016.12.11 12:39:15 3: NUKIDevice47521234: I/O device is NUKI_Bridge
2016.12.11 12:39:15 3: NUKIDevice (NUKIDevice47521234) - defined with Code: NUKI_Bridge-47521234
2016.12.11 12:39:15 2: NUKIDevice (NUKI_Bridge) - autocreated 2 devices
Smartlocks haben die 1.3.5 drauf und die Bridge 1.4.10
Info
{"bridgeType": 1, "ids": {"hardwareId": 94513222, "serverId": 1369728111}, "versions": {"firmwareVersion": "1.4.10", "wifiFirmwareVersion": "1.0.1"},
"uptime": 319152, "currentTime": "2016-12-11T12:00:02+00:00", "serverConnected": true, "scanResults":
[{"nukiId": 101061234, "name": "Nuki_06064568", "rssi": -75, "paired": true},
{"nukiId": 47521234, "name": "Nuki_02D54568", "rssi": -71, "paired": true}]}
List
[{"nukiId": 101061234, "name": "Wohnungstuer", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-12-11T10:36:01+00:00"}},
{"nukiId": 47521234, "name": "Haustuer", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-12-11T10:35:53+00:00"}}]
List
[{"nukiId": 101061234, "name": "Wohnungstuer", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-12-11T10:36:01+00:00"}},
{"nukiId": 47521234, "name": "Haustuer", "lastKnownState": {"state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2016-12-11T10:35:53+00:00"}}]
Internals:
CFGFN
DEF 47521234 IODev=NUKI_Bridge
IODev NUKI_Bridge
NAME NUKIDevice47521234
NR 95
NUKIID 47521234
STATE Initialized
TYPE NUKIDevice
VERSION 0.3.30
Helper:
fromAutocreate 1
lockAction unlatch
Attributes:
IODev NUKI_Bridge
alias Haustuer
room NUKI
verbose 5
Internals:
CFGFN
DEF 192.168.11.119 123456
HOST 192.168.11.119
NAME NUKI_Bridge
NR 93
PORT 8080
STATE connected
TOKEN 123456
TYPE NUKIBridge
VERSION 0.3.30
Readings:
2016-12-11 12:39:15 0_name Wohnungstuer
2016-12-11 12:39:15 0_nukiId 101061234
2016-12-11 12:39:15 1_name Haustuer
2016-12-11 12:39:15 1_nukiId 47521234
2016-12-11 12:39:15 bridgeType Hardware
2016-12-11 12:39:15 currentTime 2016-12-11T11:39:15+00:00
2016-12-11 12:39:15 firmwareVersion 1.4.10
2016-12-11 12:39:15 hardwareId 94513222
2016-12-11 12:39:15 serverConnected true
2016-12-11 12:39:15 serverId 1369728111
2016-12-11 12:39:15 smartlockCount 2
2016-12-11 13:57:42 state connected
2016-12-11 12:39:15 uptime 317905
2016-12-11 12:39:15 wifiFirmwareVersion 1.0.1
Helper:
Attributes:
room NUKI
verbose 5
defmod NUKIDevice12345 NUKIDevice 12345 IODev=NukiBridge
attr NUKIDevice12345 IODev NukiBridge
attr NUKIDevice12345 alias CobraTuer
attr NUKIDevice12345 event-on-change-reading .*
attr NUKIDevice12345 room NUKI
attr NUKIDevice12345 verbose 5
attr NUKIDevice12345 webhookFWinstance WEB
attr NUKIDevice12345 webhookHttpHostname 10.6.6.20
setstate NUKIDevice12345 unlocked
setstate NUKIDevice12345 2016-12-12 13:58:05 battery ok
setstate NUKIDevice12345 2016-12-12 13:58:05 batteryCritical false
setstate NUKIDevice12345 2016-12-12 13:58:05 lockState unlocked
setstate NUKIDevice12345 2016-12-12 13:58:05 state unlocked
setstate NUKIDevice12345 2016-12-12 13:58:05 success true
Zitat von: CoolTux am 17 Dezember 2016, 10:20:03
So wie es im Moment scheint konnten alle Probleme mit dem Webhook ausgemerzt werden. Fred testet heute noch mal und wenn das passt bekommt Ihr Sonntag Abend eine neue Develversion in mein Git mit Webhook/Callback Funktion.
Noch kurz zur Erklärung. Das bedeutet das die Bridge bei Änderung des Nuki Smartlocks dessen aktuellen Status an FHEM gibt, ohne das aktiv der Status am Smartlock immer abgefragt werden muß.
Zitat von: Sascha_F am 18 Dezember 2016, 15:31:20
@fred: Bist Du so lieb und stellst mir (oder uns) Dein Bridge.png zur Verfügung?
Zitat von: fred_feuerstein am 18 Dezember 2016, 15:48:27Wie hast du das gemacht, dass das angezeigt wird?
@cooltux: da war nur das Icon vom Smartlock selbst angehängt. Die Bridge noch nicht. Habe es dort ergänzt:
Ich habe es im 2. Beitrag hier im Thread ( klick (https://forum.fhem.de/index.php/topic,55756.msg473610.html#msg473610) ) angehängt.
Dort ist auch das Nuki Icon dabei. Somit ist alles zusammen.
Mein verwendetes Status-Icon (grün / gelb / rot ) ist bei FHEM ja dabei.
Zitat von: fred_feuerstein am 19 Dezember 2016, 15:48:17
Einfach zu den anderen images im fhem ordner kopieren, fhem restart und dann kannst du beim Device das Icon auswählen.
>> gesendet mit LG G4 via Tapatalk <<
attr HomeDoor devStateIcon unlocked:10px-kreis-gruen locked:10px-kreis-rot
attr HomeDoor devStateIcon unlocked:secur_open@green locked:secur_locked@red
Zitat von: fred_feuerstein am 19 Dezember 2016, 15:53:37Perfekt, herzlichen Dank!Code Auswählenattr HomeDoor devStateIcon unlocked:10px-kreis-gruen locked:10px-kreis-rot
oder alternativ:Code Auswählenattr HomeDoor devStateIcon unlocked:secur_open@green locked:secur_locked@red
Halt den Namen von deinem Smartlock ;)
json-batteryCritical:
Internals:
DEF xxx IODev=NukiBridge
IODev NukiBridge
NAME NukiDevice
NR 598
NUKIID xxx
STATE unlocked
TYPE NUKIDevice
VERSION 0.4.0
WEBHOOK_COUNTER 2
WEBHOOK_LAST 2016-12-25 21:15:07
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.188.27:8083/fhem/NUKIDevice-xxx
Readings:
2016-12-25 21:18:11 battery parseError
2016-12-25 21:18:11 batteryCritical 1
2016-12-25 21:14:31 lockState unlocked
2016-12-25 21:14:31 state unlocked
2016-12-25 21:18:11 success 1
Fhem:
infix NUKIDevice
Helper:
Attributes:
IODev NukiBridge
alias Dahoam
devStateIcon unlocked:secur_open@red locked:secur_locked@green
group Nuki
icon nuki_device
room Haus
webCmd lock:unlock
webhookFWinstance WEB
webhookHttpHostname 192.168.188.27
Internals:
DEF Display xxx
HOST Display
NAME NukiBridge
NR 596
PORT 8080
STATE Initialized
TOKEN xxx
TYPE NUKIBridge
VERSION 0.4.0
Readings:
2016-12-25 19:47:58 0_name Dahoam
2016-12-25 19:47:58 0_nukiId xxx
2016-12-25 21:12:05 appVersion 0.2.14
2016-12-25 21:12:05 bridgeType Software
2016-12-25 21:12:05 currentTime 2016-12-25T20:12:04Z
2016-12-25 21:21:25 lastError action is undefined
2016-12-25 21:12:05 serverConnected 1
2016-12-25 21:12:05 serverId xxxx
2016-12-25 19:47:58 smartlockCount 1
2016-12-25 21:11:49 state Initialized
2016-12-25 21:12:05 uptime 5038
Helper:
aliveCount 0
Attributes:
group Nuki
icon nuki_bridge
room Haus
Internals:
DEF 192.168.47.50 xxxx
HOST 192.168.47.50
NAME myNukiBridge
NR 38
PORT 8080
STATE connected
TOKEN xxxx
TYPE NUKIBridge
VERSION 0.4.0
Readings:
2016-12-23 05:02:12 0_name City
2016-12-23 05:02:12 0_nukiId 6060xxxx
2016-12-29 14:36:14 bridgeType Hardware
2016-12-29 14:36:14 currentTime 2016-12-29T13:36:14+00:00
2016-12-29 14:36:14 firmwareVersion 1.4.11
2016-12-29 14:36:14 hardwareId 8190xxxx
2016-12-28 10:35:07 lastError connect to http://192.168.47.50:8080: Das Netzwerk ist nicht erreichbar
2016-12-29 14:36:14 serverConnected true
2016-12-29 14:36:14 serverId 67554xxxx
2016-12-23 05:02:12 smartlockCount 1
2016-12-29 19:08:39 state connected
2016-12-29 14:36:14 uptime 1180053
2016-12-29 14:36:14 wifiFirmwareVersion 1.0.1
Helper:
aliveCount 0
Attributes:
event-on-change-reading .*
event-on-update-reading .*
room NUKI
verbose 5
Internals:
DEF 6060xxxx IODev=myNukiBridge
IODev myNukiBridge
NAME NUKIDevice6060xxxx
NR 39
NUKIID 6060xxxx
STATE Initialized
TYPE NUKIDevice
VERSION 0.4.1
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.47.48:8083/fhem/NUKIDevice-6060xxxx
Readings:
2016-12-28 17:28:07 battery ok
2016-12-28 17:28:07 batteryCritical false
2016-12-28 17:28:07 lockState lock
2016-12-28 17:28:07 state lock
2016-12-28 17:28:07 success true
Fhem:
infix NUKIDevice
Attributes:
IODev myNukiBridge
alias City
event-on-change-reading .*
event-on-update-reading .*
room NUKI
verbose 5
webhookFWinstance WEB
webhookHttpHostname 192.168.47.48
Callback-ID Callback-URL
0 http://192.168.47.48:8083/fhem/NUKIDevice-6060xxxx
curl --data '{"nukiId": 12345, "state": 2,"stateName": "unlocked", "batteryCritical": false}' http://192.168.1.1:8083/fhem/NUKIDevice-12345
malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "AT+CIPCLOSE=3\r\nHTT...") at ./FHEM/74_NUKIDevice.pm line 378.
Zitat von: ulli am 04 Januar 2017, 19:10:54
Ich habe auch die SW Bridge und den selben fehler action is undefined mit dem alten und neuem Modul
Zitat von: samh am 04 Januar 2017, 22:06:29
Hallo,
nun, das schalten funktioniert bei mir gefühlt wie bisher, aber der Status des Schlosses wird nur sporadisch aktualisiert.
Manchmal wird nur die Aktion z.Bsp. "unlock" angezeigt. Ein anderes Mal ändert sich der Status garnicht.
Nach einem StatusRequest passt es dann wieder.
Gruß Sam
Use of uninitialized value $list in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 262.
Zitat von: samh am 06 Januar 2017, 09:37:16
Bei dieser manuellen StatusRequest-Anfrage hat sich der Status nur auf den Zwischenwert "unlock" geändert...
2017.01.06 09:27:30 4: NUKIDevice (NUKI_DeviceZZZZZZZZZ) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.06 09:27:30 4: NUKIDevice (NUKI_DeviceZZZZZZZZZ) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.06 09:27:30 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.06 09:27:30 5: NUKIDevice (NUKI_DeviceZZZZZZZZZ) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2017.01.06 09:27:35 5: NUKIDevice (NUKI_DeviceZZZZZZZZZ) - parse status message for NUKI_DeviceZZZZZZZZZ
2017.01.06 09:27:35 5: NUKIDevice (NUKI_DeviceZZZZZZZZZ) - readings set for NUKI_DeviceZZZZZZZZZ
2017.01.06 09:27:47 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 09:27:47 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 09:27:47 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 09:27:47 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.06 09:28:17 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 09:28:17 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 09:28:17 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 09:28:17 5: NUKIBridge (NBridge1) - Bridge ist online
Response JSON:
2017.01.06 18:22:01 1: PERL WARNING: Use of uninitialized value $list in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 263.
2017.01.06 18:22:11 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYY
2017.01.06 18:22:11 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:22:11 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 18:22:11 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:22:11 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 18:22:11 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.06 18:22:11 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":ZZZZZZZZZ,"name":"HT vorn","lastKnownState":{"nukiId":ZZZZZZZZZ,"state":3,"stateName":"unlocked","batteryCritical":false}}]
2017.01.06 18:22:11 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYY
2017.01.06 18:22:11 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":bbbbbbbb},"versions":{"appVersion":"0.2.14"},"uptime":168877,"currentTime":"2017-01-06T17:22:14Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_AAAAAAAA","rssi":-79,"paired":true}]}
2017.01.06 18:22:15 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.06 18:22:17 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":3,"stateName":"unlocked","success":true}
2017.01.06 18:22:30 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:22:30 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 18:22:30 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:22:30 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 18:22:30 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.06 18:22:51 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:22:51 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 18:22:51 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:22:51 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 18:22:51 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.06 18:22:57 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYY
2017.01.06 18:22:57 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":BBBBBBBBB},"versions":{"appVersion":"0.2.14"},"uptime":168920,"currentTime":"2017-01-06T17:23:00Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_AAAAAAA","rssi":-75,"paired":true}]}
2017.01.06 18:23:09 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockAction?token=YYYYYYYYYY&action=2&nukiId=ZZZZZZZZZ
2017.01.06 18:23:17 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:23:17 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 18:23:17 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:23:17 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 18:23:17 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.06 18:23:20 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'","batteryCritical":false,"success":true}
2017.01.06 18:38:14 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.06 18:38:16 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":1,"stateName":"locked","success":true}
2017.01.06 18:38:30 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:38:30 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 18:38:30 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 18:38:30 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 18:38:30 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.06 18:38:31 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.06 18:38:33 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":1,"stateName":"locked","success":true}
Zitat von: samh am 06 Januar 2017, 19:11:41
Das klingt doch schon mal zuversichtlich. ;)
Wenn ich dazu beitragen kann, lass es mich wissen.
Gute Zeit
Sam
2017.01.06 21:54:27 1: PERL WARNING: Use of uninitialized value $list in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 263.
2017.01.06 21:54:40 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYY
2017.01.06 21:54:40 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:54:40 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 21:54:40 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":ZZZZZZZZZ,"name":"HT vorn","lastKnownState":{"nukiId":ZZZZZZZZZ,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.06 21:54:41 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYY
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response CODE: 400
2017.01.06 21:54:41 4: NUKIBridge (NBridge1) - action is undefined
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":202275232},"versions":{"appVersion":"0.2.14"},"uptime":179117,"currentTime":"2017-01-06T20:54:43Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_CCCCCCC","rssi":-77,"paired":true}]}
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:54:41 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.06 21:54:43 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.06 21:54:43 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.06 21:54:43 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.06 21:54:43 5: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2017.01.06 21:54:46 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":1,"stateName":"locked","success":true}
2017.01.06 21:54:46 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:54:46 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.06 21:54:46 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.06 21:54:46 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.06 21:55:02 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:55:02 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 21:55:02 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:55:03 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 21:55:03 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:55:03 5: NUKIBridge (NBridge1) - Response CODE: 400
2017.01.06 21:55:03 4: NUKIBridge (NBridge1) - action is undefined
2017.01.06 21:55:09 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.06 21:55:09 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.06 21:55:09 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockAction?token=YYYYYYYYYY&action=1&nukiId=ZZZZZZZZZ
2017.01.06 21:55:20 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"success":true}
2017.01.06 21:55:20 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:55:20 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.06 21:55:20 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.06 21:55:20 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.06 21:55:20 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.06 21:55:20 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.06 21:55:20 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.06 21:55:21 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":3,"stateName":"unlocked","success":true}
2017.01.06 21:55:21 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:55:21 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.06 21:55:21 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.06 21:55:21 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.06 21:55:21 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:55:21 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 21:55:21 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:55:22 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 21:55:22 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:55:22 5: NUKIBridge (NBridge1) - Response CODE: 400
2017.01.06 21:55:22 4: NUKIBridge (NBridge1) - action is undefined
2017.01.06 21:55:33 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.06 21:55:33 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.06 21:55:33 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockAction?token=YYYYYYYYYY&action=2&nukiId=ZZZZZZZZZ
2017.01.06 21:55:41 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:55:41 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 21:55:41 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:55:42 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 21:55:42 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:55:42 5: NUKIBridge (NBridge1) - Response CODE: 400
2017.01.06 21:55:42 4: NUKIBridge (NBridge1) - action is undefined
2017.01.06 21:55:44 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'","batteryCritical":false,"success":true}
2017.01.06 21:55:44 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:55:44 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.06 21:56:01 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:56:01 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/alive?token=YYYYYYYYYY
2017.01.06 21:56:01 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.06 21:56:01 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'"}
2017.01.06 21:56:01 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.06 21:56:01 5: NUKIBridge (NBridge1) - Response CODE: 400
2017.01.06 21:56:01 4: NUKIBridge (NBridge1) - action is undefined
Response JSON: {"error":"unknown action: '\/alive'","batteryCritical":false,"success":true}
2017.01.06 21:55:33 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockAction?token=YYYYYYYYYY&action=2&nukiId=ZZZZZZZZZ
2017.01.06 21:55:44 5: NUKIBridge (NBridge1) - Response JSON: {"error":"unknown action: '\/alive'","batteryCritical":false,"success":true}
2017.01.07 08:53:56 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 08:53:56 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":vvvvvvvvvv},"versions":{"appVersion":"0.2.14"},"uptime":192968,"currentTime":"2017-01-07T07:53:59Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_CCCCCCC","rssi":-81,"paired":true}]}
2017.01.07 08:53:56 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.07 08:53:56 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.07 08:53:56 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.07 08:53:59 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.07 08:53:59 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.07 08:53:59 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockAction?token=YYYYYYYYYY&action=2&nukiId=ZZZZZZZZZ
Das"sucess":true soll für das Setzen des Status sorgen ?
2017.01.07 08:54:10 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"success":true}
2017.01.07 08:54:10 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.07 08:54:10 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.07 08:54:10 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.07 08:54:10 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.07 08:54:10 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.07 08:54:10 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.07 08:54:10 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.07 08:54:11 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":1,"stateName":"locked","success":true}
2017.01.07 08:54:11 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.07 08:54:11 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.07 08:54:11 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.07 08:54:11 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.07 08:54:27 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 08:54:27 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYY
2017.01.07 08:54:27 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 08:54:27 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":vvvvvvvvvv},"versions":{"appVersion":"0.2.14"},"uptime":192999,"currentTime":"2017-01-07T07:54:30Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_CCCCCCC","rssi":-77,"paired":true}]}
2017.01.07 08:54:27 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.07 08:54:27 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.07 08:54:27 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.07 08:54:34 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.07 08:54:34 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.07 08:54:34 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockAction?token=YYYYYYYYYY&action=1&nukiId=ZZZZZZZZZ
2017.01.07 08:54:44 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"success":true}
2017.01.07 08:54:44 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.07 08:54:44 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.07 08:54:44 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.07 08:54:44 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.07 08:54:44 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.07 08:54:44 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.07 08:54:44 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.07 08:54:45 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":3,"stateName":"unlocked","success":true}
2017.01.07 08:54:45 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.07 08:54:45 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.07 08:54:45 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.07 08:54:45 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.07 08:54:47 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 08:54:47 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYY
2017.01.07 08:54:47 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 08:54:47 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":vvvvvvvvvv},"versions":{"appVersion":"0.2.14"},"uptime":193019,"currentTime":"2017-01-07T07:54:50Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_CCCCCCC","rssi":-76,"paired":true}]}
2017.01.07 08:54:47 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.07 08:54:47 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.07 08:54:47 5: NUKIBridge (NBridge1) - Bridge ist online
Zitat von: fred_feuerstein am 07 Januar 2017, 19:55:57
Also ich habe nun die 0.4.4. aus dem Master-Branch getestet.
Es schaltet und zeigt den Status an (ist es eigentlich richtig und notwendig, dass ich nach einem solchen Austausch der Version den Callback über das Bridge Modul lösche und über das Device neu erstelle? Mache ich bisher immer)
Was mir aufgefallen ist:
- Die Schaltvorgänge dauern länger, also nach Klick bspw. in der App dauert es länger, bis das Schloss was macht. So, als hätte die Bridge gerade was besseres zu tun.
- Beim Device wird nur noch Lockstate und State aktualisiert. Battery, batteryCritical und Success bekommt kein Update.
- BridgeModul erhält alle Readings in den Abfrageintervallen und nicht nur State Connected.
Weißt Du, wo diese "Internal error, 503" bei last error hin und wieder kommen?
Ich lasse es mal eine Weile laufen mit den Modul Versionen. Dann mal schauen.
LG
fred
2017.01.07 21:10:15 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:10:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:10:15 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:10:15 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1201374, "currentTime": "2017-01-07T20:10:16+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:10:15 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:10:15 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:10:15 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:10:42 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:10:42 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:10:42 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:10:42 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1201401, "currentTime": "2017-01-07T20:10:43+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:10:42 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:10:42 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:10:42 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:11:10 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:11:10 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:11:10 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:11:10 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1201429, "currentTime": "2017-01-07T20:11:11+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:11:10 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:11:10 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:11:10 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:11:39 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:11:39 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:11:39 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:11:39 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1201458, "currentTime": "2017-01-07T20:11:40+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:11:39 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:11:39 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:11:39 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:11:54 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:11:54 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:11:54 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:11:54 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1201473, "currentTime": "2017-01-07T20:11:55+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:11:54 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:11:54 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:11:54 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:11:55 1: WARNING: sleep without additional commands is deprecated and blocks FHEM
2017.01.07 21:11:55 1: WARNING: sleep without additional commands is deprecated and blocks FHEM
2017.01.07 21:11:55 4: NUKIDevice (HomeDoor) - Received webhook for matching NukiId at device HomeDoor
2017.01.07 21:11:55 5: NUKIDevice (HomeDoor) - parse status message for HomeDoor
2017.01.07 21:11:55 5: NUKIDevice (HomeDoor) - readings set for HomeDoor
2017.01.07 21:12:15 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:12:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:12:15 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:12:15 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1201494, "currentTime": "2017-01-07T20:12:16+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:12:15 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:12:15 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:12:15 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:12:43 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:12:43 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:12:43 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:12:44 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1201523, "currentTime": "2017-01-07T20:12:45+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:12:44 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:12:44 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:12:44 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:12:59 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:12:59 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:12:59 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:12:59 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1201538, "currentTime": "2017-01-07T20:13:00+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:12:59 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:12:59 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:12:59 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:48:26 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:48:26 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:48:26 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:48:27 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1203666, "currentTime": "2017-01-07T20:48:28+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:48:27 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:48:27 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:48:27 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:48:51 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:48:51 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:48:51 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:48:52 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1203691, "currentTime": "2017-01-07T20:48:53+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:48:52 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:48:52 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:48:52 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:49:20 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:49:20 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:49:20 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:49:21 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1203720, "currentTime": "2017-01-07T20:49:22+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:49:21 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:49:21 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:49:21 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.07 21:49:39 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:49:39 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.250:8080/info?token=omimn3
2017.01.07 21:49:39 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.07 21:49:39 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 84882841, "serverId": 1245345545}, "versions": {"firmwareVersion": "1.4.11", "wifiFirmwareVersion": "1.0.1"}, "uptime": 1203739, "currentTime": "2017-01-07T20:49:41+00:00", "serverConnected": true, "scanResults": [{"nukiId": 99150361, "name": "Nuki_05E8EA19", "rssi": -79, "paired": true}]}
2017.01.07 21:49:39 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.01.07 21:49:39 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.01.07 21:49:39 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.01.09 18:41:23 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:23 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:24 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:41:24 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:41:24 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:41:24 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92577,"currentTime":"2017-01-09T17:41:29Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:41:24 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:41:24 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:41:24 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:41:30 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:30 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:37 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:37 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:44 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:44 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:41:51 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92591,"currentTime":"2017-01-09T17:41:56Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 18:41:51 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:41:51 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:41:51 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:58 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:58 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:05 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:12 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:12 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:18 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:18 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:42:18 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:18 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92614,"currentTime":"2017-01-09T17:42:23Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-81,"paired":true}]}
2017.01.09 18:42:18 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:42:18 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:42:18 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:42:19 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:19 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:26 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:26 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:33 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92625,"currentTime":"2017-01-09T17:42:38Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 18:42:33 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:42:33 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:42:33 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:42:40 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:40 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:47 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:47 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:49 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:49 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:42:49 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:49 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92641,"currentTime":"2017-01-09T17:42:54Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:42:49 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:42:49 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:42:49 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:42:54 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:54 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:01 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:01 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:06 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:06 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:43:06 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:06 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92645,"currentTime":"2017-01-09T17:43:11Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:43:06 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:43:06 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:43:06 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:43:08 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:08 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:15 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:15 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:22 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:22 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:28 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:28 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:43:28 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:28 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92663,"currentTime":"2017-01-09T17:43:33Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:43:28 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:43:28 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:43:28 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:43:29 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:29 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:36 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:36 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:43 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:43 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:50 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:50 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:55 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:55 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:43:55 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:55 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92675,"currentTime":"2017-01-09T17:44:00Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:43:55 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:43:55 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:43:55 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:43:57 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:57 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:04 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:04 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:11 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:11 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:18 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:18 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:22 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:44:22 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:44:22 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:44:22 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92684,"currentTime":"2017-01-09T17:44:27Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:44:22 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:44:22 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:44:22 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:44:25 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:25 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:32 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:32 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:39 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:39 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:46 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92705,"currentTime":"2017-01-09T17:44:51Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-80,"paired":true}]}
2017.01.09 18:44:46 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:44:46 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:44:46 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:44:53 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:53 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:00 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:00 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:01 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:01 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:45:01 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:01 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92719,"currentTime":"2017-01-09T17:45:06Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-73,"paired":true}]}
2017.01.09 18:45:01 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:45:01 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:45:01 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:45:07 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:07 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:14 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:14 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:21 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92739,"currentTime":"2017-01-09T17:45:26Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:45:21 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:45:21 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:45:21 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:45:28 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:28 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:35 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:35 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:42 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:42 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:49 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92767,"currentTime":"2017-01-09T17:45:54Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:45:49 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:45:49 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:45:49 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:45:56 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:56 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:03 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:03 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:05 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:05 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:46:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:05 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92783,"currentTime":"2017-01-09T17:46:10Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:46:05 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:46:05 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:46:05 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:46:10 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:10 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:17 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:17 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:24 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:24 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:27 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:27 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:46:27 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:27 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92805,"currentTime":"2017-01-09T17:46:32Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:46:27 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:46:27 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:46:27 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:46:31 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:31 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:38 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:38 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:45 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:45 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:52 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:52 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:56 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:56 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:46:56 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:56 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92834,"currentTime":"2017-01-09T17:47:01Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:46:56 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:46:56 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:46:56 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:46:59 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:59 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:06 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:06 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:13 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92851,"currentTime":"2017-01-09T17:47:18Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:47:13 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:47:13 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:47:13 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:47:20 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:20 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:27 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:27 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:31 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:47:31 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:47:31 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:47:31 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92869,"currentTime":"2017-01-09T17:47:36Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:47:31 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:47:31 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:47:31 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:47:34 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:34 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:41 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:41 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:48 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:48 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:55 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:55 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:00 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:00 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:48:00 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:00 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92898,"currentTime":"2017-01-09T17:48:05Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:48:00 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:48:00 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:48:00 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:48:02 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:02 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:09 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:09 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:16 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:16 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:23 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:23 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:25 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:25 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:48:25 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:25 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92923,"currentTime":"2017-01-09T17:48:30Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:48:25 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:48:25 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:48:25 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:48:30 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:30 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:37 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:37 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:40 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:40 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:48:40 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:40 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92938,"currentTime":"2017-01-09T17:48:45Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:48:40 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:48:40 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:48:40 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:48:44 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:44 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:51 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:51 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:58 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:58 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:05 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92963,"currentTime":"2017-01-09T17:49:10Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-80,"paired":true}]}
2017.01.09 18:49:05 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:49:05 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:49:05 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:49:12 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:12 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:19 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:19 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:26 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:26 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:33 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92991,"currentTime":"2017-01-09T17:49:38Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:49:33 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:49:33 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:49:33 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:40 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:40 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:43 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.09 18:49:43 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.09 18:49:43 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.09 18:49:43 5: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2017.01.09 18:49:45 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":3,"stateName":"unlocked","success":true}
2017.01.09 18:49:45 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:49:45 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:49:45 5: NUKIDevice (NUKI_HT_vorn) - Parse with result: {"batteryCritical":false,"state":3,"stateName":"unlocked","success":true}
2017.01.09 18:49:45 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.09 18:49:45 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.09 18:49:47 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:47 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:54 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:54 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:58 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:58 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:49:58 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:58 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":93016,"currentTime":"2017-01-09T17:50:03Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 18:49:58 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:49:58 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:49:58 5: NUKIBridge (NBridge1) - Bridge ist online
sub NUKIDevice_GetUpdate($) {
my ($hash) = @_;
my $name = $hash->{NAME};
#RemoveInternalTimer($hash);
#-- restart timer for updates
RemoveInternalTimer($hash);
InternalTimer(gettimeofday()+ $hash->{INTERVAL}, "NUKIDevice_GetUpdate", $hash,1);
NUKIDevice_ReadFromNUKIBridge($hash, "lockState", undef, $hash->{NUKIID} ) if( !IsDisabled($name) );
Log3 $name, 5, "NUKIDevice ($name) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge" if( !IsDisabled($name) );
return undef;
}
Zitat von: samh am 09 Januar 2017, 18:56:49
Hier mal ein Log von ca. 9 Minuten. Keine Änderung des Status feststllbar. Am Ende dann ein manueller StatusRequest.Code Auswählen
2017.01.09 18:41:23 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:23 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:24 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:41:24 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:41:24 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:41:24 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92577,"currentTime":"2017-01-09T17:41:29Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:41:24 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:41:24 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:41:24 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:41:30 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:30 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:37 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:37 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:44 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:44 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:41:51 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92591,"currentTime":"2017-01-09T17:41:56Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 18:41:51 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:41:51 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:41:51 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:51 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:41:58 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:41:58 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:05 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:12 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:12 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:18 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:18 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:42:18 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:18 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92614,"currentTime":"2017-01-09T17:42:23Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-81,"paired":true}]}
2017.01.09 18:42:18 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:42:18 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:42:18 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:42:19 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:19 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:26 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:26 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:33 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92625,"currentTime":"2017-01-09T17:42:38Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 18:42:33 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:42:33 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:42:33 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:42:40 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:40 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:47 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:47 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:42:49 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:49 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:42:49 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:42:49 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92641,"currentTime":"2017-01-09T17:42:54Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:42:49 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:42:49 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:42:49 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:42:54 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:42:54 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:01 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:01 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:06 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:06 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:43:06 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:06 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92645,"currentTime":"2017-01-09T17:43:11Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:43:06 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:43:06 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:43:06 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:43:08 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:08 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:15 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:15 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:22 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:22 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:28 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:28 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:43:28 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:28 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92663,"currentTime":"2017-01-09T17:43:33Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:43:28 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:43:28 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:43:28 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:43:29 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:29 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:36 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:36 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:43 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:43 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:50 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:50 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:43:55 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:55 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:43:55 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:43:55 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92675,"currentTime":"2017-01-09T17:44:00Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:43:55 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:43:55 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:43:55 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:43:57 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:43:57 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:04 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:04 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:11 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:11 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:18 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:18 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:22 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:44:22 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:44:22 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:44:22 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92684,"currentTime":"2017-01-09T17:44:27Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:44:22 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:44:22 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:44:22 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:44:25 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:25 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:32 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:32 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:39 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:39 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:46 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:44:46 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92705,"currentTime":"2017-01-09T17:44:51Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-80,"paired":true}]}
2017.01.09 18:44:46 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:44:46 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:44:46 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:44:53 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:44:53 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:00 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:00 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:01 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:01 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:45:01 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:01 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92719,"currentTime":"2017-01-09T17:45:06Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-73,"paired":true}]}
2017.01.09 18:45:01 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:45:01 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:45:01 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:45:07 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:07 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:14 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:14 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:21 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:21 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92739,"currentTime":"2017-01-09T17:45:26Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:45:21 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:45:21 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:45:21 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:45:28 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:28 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:35 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:35 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:42 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:42 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:49 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:45:49 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92767,"currentTime":"2017-01-09T17:45:54Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:45:49 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:45:49 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:45:49 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:45:56 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:45:56 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:03 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:03 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:05 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:05 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:46:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:05 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92783,"currentTime":"2017-01-09T17:46:10Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:46:05 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:46:05 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:46:05 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:46:10 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:10 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:17 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:17 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:24 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:24 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:27 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:27 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:46:27 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:27 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92805,"currentTime":"2017-01-09T17:46:32Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:46:27 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:46:27 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:46:27 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:46:31 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:31 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:38 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:38 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:45 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:45 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:52 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:52 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:46:56 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:56 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:46:56 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:46:56 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92834,"currentTime":"2017-01-09T17:47:01Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:46:56 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:46:56 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:46:56 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:46:59 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:46:59 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:06 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:06 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:13 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:13 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92851,"currentTime":"2017-01-09T17:47:18Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:47:13 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:47:13 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:47:13 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:47:20 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:20 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:27 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:27 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:31 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:47:31 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:47:31 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:47:31 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92869,"currentTime":"2017-01-09T17:47:36Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:47:31 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:47:31 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:47:31 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:47:34 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:34 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:41 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:41 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:48 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:48 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:47:55 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:47:55 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:00 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:00 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:48:00 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:00 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92898,"currentTime":"2017-01-09T17:48:05Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-79,"paired":true}]}
2017.01.09 18:48:00 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:48:00 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:48:00 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:48:02 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:02 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:09 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:09 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:16 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:16 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:23 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:23 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:25 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:25 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:48:25 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:25 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92923,"currentTime":"2017-01-09T17:48:30Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 18:48:25 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:48:25 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:48:25 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:48:30 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:30 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:37 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:37 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:40 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:40 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:48:40 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:48:40 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92938,"currentTime":"2017-01-09T17:48:45Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:48:40 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:48:40 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:48:40 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:48:44 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:44 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:51 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:51 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:48:58 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:48:58 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:05 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92963,"currentTime":"2017-01-09T17:49:10Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-80,"paired":true}]}
2017.01.09 18:49:05 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:49:05 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:49:05 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:49:12 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:12 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:19 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:19 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:26 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:26 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:33 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":92991,"currentTime":"2017-01-09T17:49:38Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 18:49:33 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:49:33 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:49:33 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:40 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:40 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:43 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.01.09 18:49:43 4: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.01.09 18:49:43 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/lockState?token=YYYYYYYYYYY&nukiId=ZZZZZZZZZ
2017.01.09 18:49:43 5: NUKIDevice (NUKI_HT_vorn) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2017.01.09 18:49:45 5: NUKIBridge (NBridge1) - Response JSON: {"batteryCritical":false,"state":3,"stateName":"unlocked","success":true}
2017.01.09 18:49:45 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:49:45 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:49:45 5: NUKIDevice (NUKI_HT_vorn) - Parse with result: {"batteryCritical":false,"state":3,"stateName":"unlocked","success":true}
2017.01.09 18:49:45 5: NUKIDevice (NUKI_HT_vorn) - parse status message for NUKI_HT_vorn
2017.01.09 18:49:45 5: NUKIDevice (NUKI_HT_vorn) - readings set for NUKI_HT_vorn
2017.01.09 18:49:47 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:47 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:54 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 18:49:54 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 18:49:58 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:58 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 18:49:58 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 18:49:58 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":AAAAAAAA},"versions":{"appVersion":"0.2.14"},"uptime":93016,"currentTime":"2017-01-09T17:50:03Z","serverConnected":true,"scanResults":[{"nukiId":ZZZZZZZZZ,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 18:49:58 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 18:49:58 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 18:49:58 5: NUKIBridge (NBridge1) - Bridge ist online
Zitat von: samh am 09 Januar 2017, 19:07:57
Hallo Leon,
wäre folgende Vorgehensweise mit Nachteilen behaftet ?Code Auswählen
sub NUKIDevice_GetUpdate($) {
my ($hash) = @_;
my $name = $hash->{NAME};
#RemoveInternalTimer($hash);
#-- restart timer for updates
RemoveInternalTimer($hash);
InternalTimer(gettimeofday()+ $hash->{INTERVAL}, "NUKIDevice_GetUpdate", $hash,1);
NUKIDevice_ReadFromNUKIBridge($hash, "lockState", undef, $hash->{NUKIID} ) if( !IsDisabled($name) );
Log3 $name, 5, "NUKIDevice ($name) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge" if( !IsDisabled($name) );
return undef;
}
Natürlich nur bei Software-Bridge. Das müsste noch abgefragt werden. INTERVAL (30 sec) könnte über ein Attribut oder in der Definition des Device gesetzt werden,
ähnlich NUKIID.
Was meinst Du dazu ?
Gruß Sam
Internals:
CFGFN /opt/fhem/FHEM/nuki.cfg
DEF AAAAAAAAA NBridge1
IODev NBridge1
NAME NUKI_HT_vorn
NR 371
NUKIID AAAAAAAAA
STATE locked
TYPE NUKIDevice
VERSION 0.4.5patch1
WEBHOOK_REGISTER unregistered
Readings:
2017-01-09 19:24:45 battery ok
2017-01-09 19:24:45 batteryCritical false
2017-01-09 19:24:45 lockState locked
2017-01-09 19:24:45 state locked
2017-01-09 19:24:45 success true
Fhem:
infix NUKIDevice
Helper:
Attributes:
IODev NBridge1
alias HT-vorn
devStateIcon locked:secur_locked unlocked:secur_open unlatched:fts_door_open
group Türsensor
icon hm_keymatic
room NUKI,Sicherheit
verbose 0
Internals:
CFGFN /opt/fhem/FHEM/nuki.cfg
DEF 192.168.xxx.xxx ZZZZZZZZZ
HOST 192.168.xxx.xxx
NAME NBridge1
NR 369
PORT 8080
STATE connected
TOKEN AAAAAAAAAAA
TYPE NUKIBridge
VERSION 0.4.5patch1
Readings:
2017-01-09 19:45:25 appVersion 0.2.14
2017-01-09 19:45:25 bridgeType Software
2017-01-09 19:45:25 currentTime 2017-01-09T18:45:30Z
2017-01-09 06:10:05 lastError 192.168.xxx.xxx: Keine Route zum Zielrechner
2017-01-09 19:45:25 serverConnected true
2017-01-09 19:45:25 serverId ccccccccccc
2017-01-09 19:45:25 state connected
2017-01-09 19:45:25 uptime 95258
Helper:
aliveCount 0
checkLockState 0
Attributes:
devStateIcon connected:it_wifi
group Zentralen
icon hue_bridge
room NUKI,Sicherheit,Zentralen
verbose 0
Internals:
CFGFN
DEF 999999999 IODev=NBridge1
IODev NBridge1
NAME NUKIDevice999999999
NR 539
NUKIID 999999999
STATE locked
TYPE NUKIDevice
VERSION 0.4.5patch1
WEBHOOK_REGISTER unregistered
Readings:
2017-01-09 20:16:11 battery ok
2017-01-09 20:16:11 batteryCritical false
2017-01-09 20:16:11 lockState locked
2017-01-09 20:16:11 state locked
2017-01-09 20:15:55 success true
Fhem:
infix NUKIDevice
Helper:
fromAutocreate 1
Attributes:
IODev NBridge1
alias HT vorn
room NUKI
Internals:
CFGFN /opt/fhem/FHEM/nuki.cfg
CHANGED
DEF 192.168.xxx.xxx AAAAAAAAAAA
HOST 192.168.xxx.xxx
NAME NBridge1
NR 369
PORT 8080
STATE connected
TOKEN AAAAAAAAAAA
TYPE NUKIBridge
VERSION 0.4.5patch1
Readings:
2017-01-09 20:15:27 0_name HT vorn
2017-01-09 20:15:27 0_nukiId ccccccccccc
2017-01-09 21:04:47 appVersion 0.2.14
2017-01-09 21:04:47 bridgeType Software
2017-01-09 21:04:47 currentTime 2017-01-09T20:04:52Z
2017-01-09 06:10:05 lastError 192.168.xxx.xxx: Keine Route zum Zielrechner
2017-01-09 21:04:47 serverConnected true
2017-01-09 21:04:47 serverId yyyyyyyyyy
2017-01-09 20:15:27 smartlockCount 1
2017-01-09 21:04:47 state connected
2017-01-09 21:04:47 uptime 98724
Helper:
aliveCount 0
checkLockState 0
Attributes:
devStateIcon connected:it_wifi
group Zentralen
icon hue_bridge
room NUKI,Sicherheit,Zentralen
verbose 0
2017.01.09 21:11:16 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:11:16 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:11:16 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:11:17 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:17 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:17 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:17 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:11:17 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:17 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:11:17 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 21:11:17 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:11:17 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":ZZZZZZZZZ},"versions":{"appVersion":"0.2.14"},"uptime":98978,"currentTime":"2017-01-09T20:11:21Z","serverConnected":true,"scanResults":[{"nukiId":CCCCCCC,"name":"Nuki_ABABABAB","rssi":-75,"paired":true}]}
2017.01.09 21:11:17 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:17 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:17 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 21:11:23 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:11:23 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:11:23 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:11:23 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:23 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:23 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:23 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:11:23 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:30 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:11:30 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:11:30 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:11:30 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:30 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:30 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:30 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:11:30 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:37 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:11:37 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:11:37 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:11:38 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:38 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:38 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:38 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:11:38 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:39 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:11:39 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 21:11:39 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:11:39 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":ZZZZZZZZZ},"versions":{"appVersion":"0.2.14"},"uptime":98996,"currentTime":"2017-01-09T20:11:43Z","serverConnected":true,"scanResults":[{"nukiId":CCCCCCC,"name":"Nuki_ABABABAB","rssi":-75,"paired":true}]}
2017.01.09 21:11:39 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:39 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:39 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 21:11:44 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:11:44 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:11:44 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:11:44 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:44 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:44 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:44 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:11:44 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:51 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:11:51 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:11:51 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:11:51 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:51 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:51 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:51 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:11:51 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:58 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:11:58 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:11:58 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:11:58 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:11:58 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:11:58 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:11:58 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:11:58 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:03 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:12:03 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 21:12:03 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:12:03 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":ZZZZZZZZZ},"versions":{"appVersion":"0.2.14"},"uptime":99010,"currentTime":"2017-01-09T20:12:07Z","serverConnected":true,"scanResults":[{"nukiId":CCCCCCC,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 21:12:03 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:03 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:03 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 21:12:05 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:12:05 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:12:05 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:12:05 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:05 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:05 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:05 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:12:05 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:12 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:12:12 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:12:12 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:12:12 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:12 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:12 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:12 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:12:12 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:19 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:12:19 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:12:19 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:12:20 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:20 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:20 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:20 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:12:20 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:24 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:12:24 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 21:12:24 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:12:24 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":ZZZZZZZZZ},"versions":{"appVersion":"0.2.14"},"uptime":99017,"currentTime":"2017-01-09T20:12:28Z","serverConnected":true,"scanResults":[{"nukiId":CCCCCCC,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 21:12:24 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:24 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:24 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 21:12:26 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:12:26 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:12:26 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:12:27 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:27 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:27 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:27 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:12:27 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:33 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:12:33 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:12:33 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:12:33 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:33 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:33 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:33 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:12:33 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:39 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:12:39 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 21:12:39 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:12:39 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":ZZZZZZZZZ},"versions":{"appVersion":"0.2.14"},"uptime":99020,"currentTime":"2017-01-09T20:12:43Z","serverConnected":true,"scanResults":[{"nukiId":CCCCCCC,"name":"Nuki_ABABABAB","rssi":-78,"paired":true}]}
2017.01.09 21:12:39 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:39 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:39 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 21:12:40 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:12:40 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:12:40 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:12:40 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:40 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:40 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:40 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:12:40 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:47 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:12:47 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:12:47 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:12:47 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:47 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:47 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:47 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:12:47 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:54 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:12:54 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:12:54 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:12:54 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:12:54 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:12:54 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:12:54 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:12:54 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:13:01 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:13:01 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:13:01 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:13:02 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:13:02 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:13:02 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:13:02 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:13:02 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:13:04 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:13:04 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 21:13:04 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:13:04 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":ZZZZZZZZZ},"versions":{"appVersion":"0.2.14"},"uptime":99037,"currentTime":"2017-01-09T20:13:09Z","serverConnected":true,"scanResults":[{"nukiId":CCCCCCC,"name":"Nuki_ABABABAB","rssi":-77,"paired":true}]}
2017.01.09 21:13:04 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:13:04 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:13:04 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 21:13:08 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:13:08 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:13:08 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:13:09 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:13:09 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:13:09 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:13:09 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:13:09 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":1,"stateName":"locked","batteryCritical":false}}]
2017.01.09 21:13:15 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:13:15 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:13:15 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:13:15 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":3,"stateName":"unlocked","batteryCritical":false}}]
2017.01.09 21:13:15 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:13:15 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:13:15 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:13:15 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":3,"stateName":"unlocked","batteryCritical":false}}]
2017.01.09 21:13:22 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:13:22 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:13:22 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:13:23 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":3,"stateName":"unlocked","batteryCritical":false}}]
2017.01.09 21:13:23 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:13:23 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:13:23 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:13:23 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":3,"stateName":"unlocked","batteryCritical":false}}]
2017.01.09 21:13:23 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:13:23 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/info?token=YYYYYYYYYYY
2017.01.09 21:13:23 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.09 21:13:23 5: NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":ZZZZZZZZZ},"versions":{"appVersion":"0.2.14"},"uptime":99048,"currentTime":"2017-01-09T20:13:27Z","serverConnected":true,"scanResults":[{"nukiId":CCCCCCC,"name":"Nuki_ABABABAB","rssi":-76,"paired":true}]}
2017.01.09 21:13:23 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:13:23 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:13:23 5: NUKIBridge (NBridge1) - Bridge ist online
2017.01.09 21:13:29 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:13:29 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:13:29 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:13:29 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":3,"stateName":"unlocked","batteryCritical":false}}]
2017.01.09 21:13:29 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:13:29 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:13:29 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:13:29 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":3,"stateName":"unlocked","batteryCritical":false}}]
2017.01.09 21:13:36 4: NUKIBridge (NBridge1) - NUKIBridge_LockStateTimer
2017.01.09 21:13:36 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.XXX.XXX:8080/list?token=YYYYYYYYYYY
2017.01.09 21:13:36 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_LockStateTimer
2017.01.09 21:13:36 5: NUKIBridge (NBridge1) - Response JSON: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":3,"stateName":"unlocked","batteryCritical":false}}]
2017.01.09 21:13:36 5: NUKIBridge (NBridge1) - Response ERROR:
2017.01.09 21:13:36 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.01.09 21:13:36 4: NUKIDevice (NUKIDeviceCCCCCCC) - Received LockState for matching NukiID CCCCCCC at device NUKIDeviceCCCCCCC
2017.01.09 21:13:36 5: NUKIBridge (NBridge1) - Run NUKIBridge_LockStateResponse with Path:list and JSON-Data: [{"nukiId":CCCCCCC,"name":"HT vorn","lastKnownState":{"nukiId":CCCCCCC,"state":3,"stateName":"unlocked","batteryCritical":false}}]
Zitat
Kompatibilität zu HTTP-API 1.3 wurde vor Weihnachten mit der v0.2.14 released. Also ja, Callbacks gehen auch mit der Softwarebridge.
Internals:
DEF 77399938 IODev=NBridge1
IODev NBridge1
NAME NUKI_HT_vorn
NR 524
NUKIID 77399938
STATE unlocked
TYPE NUKIDevice
VERSION 0.4.5patch2
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8085
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.268.100:8085/fhem/NUKIDevice-77399938
Readings:
2017-01-10 18:06:01 battery ok
2017-01-10 18:06:01 batteryCritical false
2017-01-10 18:06:01 lockState unlocked
2017-01-10 18:06:01 state unlocked
2017-01-10 18:06:01 success true
Fhem:
infix NUKIDevice
Helper:
Attributes:
IODev NBridge1
alias HT vorn
devStateIcon locked:secur_locked unlocked:secur_open unlatched:hue_room_other
icon hm_keymatic
room NUKI
verbose 0
webhookFWinstance NUKI
webhookHttpHostname 192.168.268.100
Messages collected while initializing FHEM:
configfile: webhookFWinstance can only use with hardware bridge
webhookHttpHostname can only use with hardware bridge
Zitat von: CaptainCarrot am 13 Januar 2017, 09:29:31
Servus,
ich lese hier schon ziemlich seit Beginn mit und habe ein Smartlock mit HW-Bridge im Einsatz, bisher hab ich nicht geschrieben, weil ihr mit dem Problemlösen schneller wart als ich mit der Integration meines NUKIs in FHEM ;-). Finde ich total super, das Feedback wollte ich auch mal geben!
Bei der Webhook-Funktion war ich jetzt allerdings wohl auch bei der Implementierung mal einer der ersten, daher noch ein kleines Feedback dazu:
1. Es wäre praktisch, wenn man den PORT noch als attr setzen könnte, wenn man die Standard-Instanzen per Passwort gesichert hat muss man sonst basteln. Ich hatte das TabletWEB-Interface noch nicht gesichert, also läuft es jetzt darüber, würde das aber lieber über einen anderen Port auf mein "normales" intern ungesichertes Webinterface laufen lassen. Ist bei Neueinrichtungen kein Problem, aber bei bestehenden Systemen.
2. Ich musste ebenfalls Bridge und Smartlock nochmal löschen und neu anlegen, um die Webhooks zum funktionieren zu bringen, obwohl eigentlich alle attr und readings richtig aussahen. Scheinbar war aber der Webhook nicht erreichbar, das gab dann auf der Bridge den Error 503 und das Smartlock-Device hat den Webhook auch immer wieder neu in die Bridge eingetragen, der Stand da ständig 3 mal drin. Also vielleicht als Hinweis an alle, die ebenfalls ein schon etwas länger bestehendes NUKI-Schloss mit Webhooks versorgen wollen: Erst Locks und Bridge nochmal komplett neu anlegen.
Ansonsten: Weiter so, tolle Arbeit!
Viele Grüße
Joachim
list BRIDGEDEVICENAME
Zitat
HTTP 503 Returned if the given Smart Lock is offline
Zitat
Das ändern des Webhook Ports hatte ich in früheren Versionen drin. Da man aber nun bequem alle vorhandenen FHEM WEB Instanzen auswählen kann ergibt sich der Port ja automatisch. Man kann ja nur den Port nehmen den die Webinstanz anbietet und den lese ich automatisch aus.
Wenn ich mir Punkt 1 bei Dir so durchlese, gehe ich davon aus das Du etwas im Modulcode angepasst hast um einen anderen Port aus zu wählen. Daraus ergibt sich aber ein Problem. Beim define eines jeden Smartlock Devices wird eine Art Marker gesetzt, Anhand dieses Markers wird erkannt ob das Device Berechtigt ist ein Webhookaufruf an zu nehmen. Hier wird dann wohl auch Dein 503 her gekommen sein.
Um zusammen zu fassen. Sobald ich eine FHEM Webinstanz ausgesucht habe (es werden alle vorhandenen aufgelistet) steht automatisch der Port fest, und dieser wird dann beim anlegen des webhooks ausgelesen.
Zitat von: CoolTux am 15 Januar 2017, 06:58:45
Welche Modulversion setzt Du aktuell ein?
Zitat
Kannst Du bitte ein list von der Webinstanz machen welche Du nehmen möchtest?
Internals:
CONNECTS 79
DEF 8086 global
FD 190
NAME IntraWEB
NR 460
NTFY_ORDER 50-IntraWEB
PORT 8086
STATE Initialized
TYPE FHEMWEB
Attributes:
Zitat
Welche werden denn angezeigt? Alle anderen ausser die die Du nehmen möchtest?
{ join( ",", devspec2array('TYPE=FHEMWEB:FILTER=TEMPORARY!=1') ) }
Zitat von: CoolTux am 15 Januar 2017, 10:31:08
Kannst Du das bitte mal bei Dir eingeben in der FHEM CommandlineCode Auswählen
{ join( ",", devspec2array('TYPE=FHEMWEB:FILTER=TEMPORARY!=1') ) }
IntraWEB,WEB,WEBphone,WEBtablet
Zitat von: Sascha_F am 16 Januar 2017, 23:25:50
Keine Eile ;)
Bin gespannt, was Dir noch an Readings eingefallen ist!
Hmm, bekommt man vll raus, wer einen Schließvorgang ausgelöst hat? Ich bin gespannt! :)
Zitat
Danke für das Feedback.
Diese Funktionen sind leider nicht verfügbar.
Wir nehmen das Feedback dazu gerne an, können aber keine Umsetzung garantieren.
Schöne Grüße,
Zitat von: CaptainCarrot am 15 Januar 2017, 12:44:38
Das liefert alle Instanzen zurück:Code AuswählenIntraWEB,WEB,WEBphone,WEBtablet
Zitat von: Stephan1965 am 23 Januar 2017, 19:13:00
Hallo,
ich habe ein paar Fragen:
- In der Nuki App kann man die Betätigung des Knopfes am Smartlock deaktivieren. Ist dies auch von FHEM aus möglich? Dann könnte man z. B. im Party-Modus diesen deaktivieren (gemeinsam mit den anderen Party-Einstellungen im zugehörigen DOIF wie Rollos, Licht etc.), damit die neugierigen Gäste nicht immer auf den Knopf drücken (bzw. Erfolg haben mit der Betätigung und dann kriegen sie die Tür nicht mehr auf).
- Wenn ich auf den Knopf am Smartlock drücke, schließt das Schloß. Ich hätte gerne, dass beim erneuten Drücken (also wenn das Schloß zugesperrt ist) das Schloß wieder geöffnet wird. Ist das über FHEM realisierbar? (Oder geht das über die Nuki-App und ich habe es noch nicht gefunden?). Sprich: Kann die Betätigung des Knopfes in FHEM ausgelesen werden?
Viele Grüße
Stephan
Zitat von: Stephan1965 am 23 Januar 2017, 19:13:00
- In der Nuki App kann man die Betätigung des Knopfes am Smartlock deaktivieren. Ist dies auch von FHEM aus möglich? Dann könnte man z. B. im Party-Modus diesen deaktivieren (gemeinsam mit den anderen Party-Einstellungen im zugehörigen DOIF wie Rollos, Licht etc.), damit die neugierigen Gäste nicht immer auf den Knopf drücken (bzw. Erfolg haben mit der Betätigung und dann kriegen sie die Tür nicht mehr auf).
- Wenn ich auf den Knopf am Smartlock drücke, schließt das Schloß. Ich hätte gerne, dass beim erneuten Drücken (also wenn das Schloß zugesperrt ist) das Schloß wieder geöffnet wird. Ist das über FHEM realisierbar? (Oder geht das über die Nuki-App und ich habe es noch nicht gefunden?). Sprich: Kann die Betätigung des Knopfes in FHEM ausgelesen werden?
Zitat von: markukug am 23 Januar 2017, 20:57:41
Irgendwie schaffe ich es nicht den Status des Smartlock automatisch aktualisiert zu bekommen.
Leider habe ich auch die Webhook Funktion (ich habe die Webhook IP auf den FHEM Server gesetzt) noch nicht so richtig verstanden.
Vielleicht kann hier jemand versuchen eine Erklärung zu geben.
Danke
LG
Markus
DEF 192.168.178.233 abcdef
HOST 192.168.178.233
NAME nuki01
NR 532
PORT 8080
STATE connected
TOKEN abcdef
TYPE NUKIBridge
VERSION 0.4.7
0_name Tstr23 2017-01-21 14:44:10
0_nukiId 102765321 2017-01-21 14:44:10
bridgeType Hardware 2017-01-24 07:32:54
currentTime 2017-01-24T06:32:55+00:00 2017-01-24 07:32:54
firmwareVersion 1.4.20 2017-01-24 07:32:54
hardwareId 98598929 2017-01-24 07:32:54
lastError 192.168.178.233: No route to host 2017-01-23 06:13:22
serverConnected true 2017-01-24 07:32:54
serverId 287592143 2017-01-24 07:32:54
smartlockCount 1 2017-01-21 14:44:10
state connected 2017-01-24 07:32:54
uptime 59397 2017-01-24 07:32:54
wifiFirmwareVersion 1.0.1 2017-01-24 07:32:54
DEF 111111111 IODev=nuki01
IODev nuki01
NAME nukiHaustuer
NR 533
NUKIID 1111111111
STATE locked
TYPE NUKIDevice
VERSION 0.4.7
WEBHOOK_COUNTER 0
WEBHOOK_PORT
WEBHOOK_REGISTER incomplete_attributes
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL
battery ok 2017-01-23 20:53:40
batteryCritical false 2017-01-23 20:53:40
lockState locked 2017-01-23 20:53:40
name Nuki_22222222 2017-01-24 07:29:41
paired true 2017-01-24 07:29:41
rssi -79 2017-01-24 07:29:41
state locked 2017-01-23 20:53:40
success true 2017-01-23 20:53:40
IODev nuki01 deleteattr
alias Tstr23 deleteattr
room NUKI deleteattr
webhookHttpHostname 192.168.178.10 deleteattr
WEBHOOK_REGISTER incomplete_attributes
Callback-ID Callback-URL
0 http://192.168.178.233:8083/fhem/NUKIDevice-102765321
1 http://192.168.178.10:8083/fhem/NUKIDevice-102765321
2 http://192.168.178.10:8083/fhem/NUKIDevice-102765321
Zitat von: markukug am 24 Januar 2017, 08:54:44
Das Ganze sieht jetzt wie folgt aus:Code Auswählen
Callback-ID Callback-URL
0 http://192.168.178.233:8083/fhem/NUKIDevice-102765321
1 http://192.168.178.10:8083/fhem/NUKIDevice-102765321
2 http://192.168.178.10:8083/fhem/NUKIDevice-102765321
Kann man diese Callbacks irgendwie bereinigen? Die .10 ist mein FHEM-Server. .233 ist die Nuki-Bridge, welche ich in den Anfängen mal fälschlich eingetragen habe.
lg
Markus
Callback-ID Callback-URL
0 http://192.168.178.10:8083/fhem/NUKIDevice-102765321
set nukiHaustuer statusRequest
wir der Status aktualisiert. Läuft irgendwie noch nicht so rund.lastError 192.168.178.233: No route to host 2017-01-24 10:59:13
2017.01.24 11:17:15 5: NUKIDevice (nukiHaustuer) - Parse with result: {"name":"Nuki_06201309","rssi":-77,"paired":true}
2017.01.24 11:17:15 5: NUKIDevice (nukiHaustuer) - parse status message for nukiHaustuer
2017.01.24 11:17:15 5: NUKIDevice (nukiHaustuer) - readings set for nukiHaustuer
2017.01.24 11:17:41 5: NUKIDevice (nukiHaustuer) - Parse with result: {"rssi":-77,"name":"Nuki_06201309","paired":true}
2017.01.24 11:17:41 5: NUKIDevice (nukiHaustuer) - parse status message for nukiHaustuer
2017.01.24 11:17:41 5: NUKIDevice (nukiHaustuer) - readings set for nukiHaustuer
2017.01.24 11:18:04 5: NUKIDevice (nukiHaustuer) - Parse with result: {"rssi":-77,"name":"Nuki_06201309","paired":true}
2017.01.24 11:18:04 5: NUKIDevice (nukiHaustuer) - parse status message for nukiHaustuer
2017.01.24 11:18:04 5: NUKIDevice (nukiHaustuer) - readings set for nukiHaustuer
2017.01.24 11:18:21 5: NUKIDevice (nukiHaustuer) - Parse with result: {"rssi":-79,"name":"Nuki_06201309","paired":true}
2017.01.24 11:18:21 5: NUKIDevice (nukiHaustuer) - parse status message for nukiHaustuer
2017.01.24 11:18:21 5: NUKIDevice (nukiHaustuer) - readings set for nukiHaustuer
2017.01.24 11:18:30 1: PERL WARNING: Use of uninitialized value in hash element at ./FHEM/72_FRITZBOX.pm line 1419.
2017.01.24 11:18:30 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/72_FRITZBOX.pm line 1424.
2017.01.24 11:18:30 1: PERL WARNING: Use of uninitialized value in hash element at ./FHEM/72_FRITZBOX.pm line 1460.
2017.01.24 11:18:30 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/72_FRITZBOX.pm line 1460.
2017.01.24 11:18:30 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/72_FRITZBOX.pm line 1453.
2017.01.24 11:18:44 5: NUKIDevice (nukiHaustuer) - Parse with result: {"name":"Nuki_06201309","rssi":-79,"paired":true}
2017.01.24 11:18:44 5: NUKIDevice (nukiHaustuer) - parse status message for nukiHaustuer
2017.01.24 11:18:44 5: NUKIDevice (nukiHaustuer) - readings set for nukiHaustuer
2017.01.24 11:19:12 4: NUKIBridge (nuki01) - NUKIBridge_GetCheckBridgeAlive
2017.01.24 11:19:12 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.233:8080/info?token=ge5b7e
2017.01.24 11:19:12 4: NUKIBridge (nuki01) - run NUKIBridge_Call
2017.01.24 11:19:12 4: NUKIBridge (nuki01) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.24 11:19:12 5: NUKIBridge (nuki01) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 98598929, "serverId": 287592143}, "versions": {"firmwareVersion": "1.4.20", "wifiFirmwareVersion": "1.0.1"}, "uptime": 72975, "currentTime": "2017-01-24T10:19:13+00:00", "serverConnected": true, "scanResults": [{"nukiId": 102765321, "name": "Nuki_06201309", "rssi": -77, "paired": true}]}
2017.01.24 11:19:12 5: NUKIBridge (nuki01) - Response ERROR:
2017.01.24 11:19:12 5: NUKIBridge (nuki01) - Response CODE: 200
2017.01.24 11:19:12 5: NUKIBridge (nuki01) - Bridge ist online
2017.01.24 11:19:12 4: NUKIDevice (nukiHaustuer) - Received scanResults for matching NukiID 102765321 at device nukiHaustuer
2017.01.24 11:19:12 5: NUKIDevice (nukiHaustuer) - Parse with result: {"rssi":-77,"name":"Nuki_06201309","paired":true}
2017.01.24 11:19:12 5: NUKIDevice (nukiHaustuer) - parse status message for nukiHaustuer
2017.01.24 11:19:12 5: NUKIDevice (nukiHaustuer) - readings set for nukiHaustuer
2017.01.24 11:19:37 4: NUKIBridge (nuki01) - NUKIBridge_GetCheckBridgeAlive
2017.01.24 11:19:37 4: NUKIBridge (nuki01) - Send HTTP POST with URL http://192.168.178.233:8080/info?token=ge5b7e
2017.01.24 11:19:37 4: NUKIBridge (nuki01) - run NUKIBridge_Call
2017.01.24 11:19:37 4: NUKIBridge (nuki01) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.01.24 11:19:37 5: NUKIBridge (nuki01) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 98598929, "serverId": 287592143}, "versions": {"firmwareVersion": "1.4.20", "wifiFirmwareVersion": "1.0.1"}, "uptime": 73000, "currentTime": "2017-01-24T10:19:38+00:00", "serverConnected": true, "scanResults": [{"nukiId": 102765321, "name": "Nuki_06201309", "rssi": -79, "paired": true}]}
2017.01.24 11:19:37 5: NUKIBridge (nuki01) - Response ERROR:
2017.01.24 11:19:37 5: NUKIBridge (nuki01) - Response CODE: 200
2017.01.24 11:19:37 5: NUKIBridge (nuki01) - Bridge ist online
2017.01.24 11:19:37 4: NUKIDevice (nukiHaustuer) - Received scanResults for matching NukiID 102765321 at device nukiHaustuer
2017.01.24 11:19:37 5: NUKIDevice (nukiHaustuer) - Parse with result: {"paired":true,"rssi":-79,"name":"Nuki_06201309"}
2017.01.24 11:19:37 5: NUKIDevice (nukiHaustuer) - parse status message for nukiHaustuer
2017.01.24 11:19:37 5: NUKIDevice (nukiHaustuer) - readings set for nukiHaustuer
Zitat von: Stephan1965 am 23 Januar 2017, 19:13:00Nach dem heutigen Nuki Software-Update des Smartlocks funktioniert es wieder.
- Wenn ich auf den Knopf am Smartlock drücke, schließt das Schloß. Ich hätte gerne, dass beim erneuten Drücken (also wenn das Schloß zugesperrt ist) das Schloß wieder geöffnet wird.
Zitat von: danillo am 26 Januar 2017, 15:08:12
ok, das erklärt's dann. Aber in der App kann ich das Protokoll auch über die Bridge aus der Ferne abrufen.
Wenn du die Doku anpasst, da hätte ich dann noch etwas. mit dem Lesen dieses Thread hab ich es ja jetzt hinbekommen, dass der Status automatisch aktualisiert wird. Aber in der Doku hatte ich das nicht gefunden. ich denke, dass das Feature jeder nutzen will. Daher sollte es in der Doku bei der Einrichtung gleich dabei stehen.
Zitat von: CoolTux am 25 Januar 2017, 19:44:47
wie sowas FHEM Konform arbeiten soll, werde ich in baldiger Zukunft das Nuki Modul ebenfalls FHEM Konform umbauen.
ZitatPERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 215, <$fh> line 53.
Zitat3: NUKIDevice (Nukibridge) - NukiId '########' already defined as 'NUKIDevice########'
Zitat von: CoolTux am 02 Februar 2017, 20:07:57
Und wer oder was hat Dir gesagt das der Code für die cfg ist? Im. Normalfall sind Codebeispiele hier für die DEF des Devices.
Mach bitte mal ein list vom Device.
list Devicename
Internals:
DEF 112944569 IODev=NBridge1
IODev NBridge1
NAME NUKIDevice112944569
NR 53
NUKIID 112944569
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.0
WEBHOOK_REGISTER unregistered
Readings:
2017-02-02 20:12:36 battery ok
2017-02-02 20:12:36 batteryCritical false
2017-02-02 20:12:36 lockState unlocked
2017-02-02 20:13:34 name Nuki_06BB65B9
2017-02-02 20:13:34 paired true
2017-02-02 20:13:34 rssi -85
2017-02-02 20:12:36 state unlocked
2017-02-02 20:12:36 success true
Fhem:
infix NUKIDevice
Helper:
Attributes:
IODev NBridge1
alias Nuki Zuhause
genericDeviceType lock
homebridgeMapping LockCurrentState=lockState,values=/^lock/:SECURED;/^unlock:UNSECUREDLockTargetState=state,values=/^lock/:SECURED;/^unlock:UNSECURED,cmds=SECURED:lock;UNSECURED:unlock
room Homekit,NUKI
define WEBhook FHEMWEB 8088 global
attr WEBhook hiddenroom input,detail,save,Unsorted,Everything,CUL_HM,FS20,Commandref,style,Edit files,Select style,Logfile,Floorplans,Remotedoc,FileLogs,Apartment,Bathroom,Bedroom,Kitchen,Living,Residents,System,Weather,Event monitor,NEW
attr WEBhook room hidden
attr WEBhook webname webhook
define allowedWEBhook allowed
attr allowedWEBhook allowedCommands ,
attr allowedWEBhook allowedDevices ,
attr allowedWEBhook validFor WEBhook
Zitat von: Morpheus_1977 am 02 Februar 2017, 20:26:43Kann mir hier den noch jemand weiter helfen??? Wäre toll :)
OK, danke schonmal für deine Hilfe!
Warum auch immer ist Nuki nun doch verfügbar. Nur hab ich folgendes Problem:
Siri Name: Haustür
Sag ich Siri nun: Haustür abschließen, sagt Siri mir->Haustür ist abgeschlossen, aber es erfolt keine Aktion bei Nuki obwohl sie unlocked ist.
Das gleiche passiert auch anders herum, Siri bzw Fhem scheinen keine Aktion an Nuki zu senden!?!?
Zitat von: CoolTux am 08 Februar 2017, 16:03:18
Irgendwelche Logfiles?
2017.02.08 16:05:33 4: NUKIDevice (NUKIDevice112944569) - Received scanResults for matching NukiID 112944569 at device NUKIDevice112944569
2017.02.08 16:05:33 5: NUKIDevice (NUKIDevice112944569) - Parse with result: {"paired":true,"name":"Nuki_06BB65B9","rssi":-77}
2017.02.08 16:05:33 5: NUKIDevice (NUKIDevice112944569) - parse status message for NUKIDevice112944569
2017.02.08 16:05:33 5: NUKIDevice (NUKIDevice112944569) - readings set for NUKIDevice112944569
2017.02.08 16:05:33 5: Starting notify loop for NUKIDevice112944569, 3 event(s), first is name: Nuki_06BB65B9
2017.02.08 16:05:33 5: End notify loop for NUKIDevice112944569
Zitat
2017.02.08 16:09:21 4 : NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.02.08 16:09:21 4 : HttpUtils url=http://192.168.2.42:8080/info?token=xxx
2017.02.08 16:09:21 4 : NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.2.42:8080/info?token=xxxx
2017.02.08 16:09:21 4 : NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.02.08 16:09:21 4 : NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.02.08 16:09:21 4 : http://192.168.2.42:8080/info?token=xxxx: HTTP response code 200
2017.02.08 16:09:21 4 : HttpUtils http://192.168.2.42:8080/info?token=xxxx: Got data, length: 241
2017.02.08 16:09:21 5 : NUKIBridge (NBridge1) - Response JSON: {"bridgeType":2,"ids":{"serverId":915081946},"versions":{"appVersion":"0.2.14"},"uptime":805473,"currentTime":"2017-02-08T15:09:16Z","serverConnected":true,"scanResults":[{"nukiId":112944569,"name":"Nuki_06BB65B9","rssi":-77,"paired":true}]}
2017.02.08 16:09:21 5 : NUKIBridge (NBridge1) - Response ERROR:
2017.02.08 16:09:21 5 : NUKIBridge (NBridge1) - Response CODE: 200
2017.02.08 16:09:21 5 : NUKIBridge (NBridge1) - Bridge ist online
2017.02.08 16:09:21 5 : Starting notify loop for NBridge1, 1 event(s), first is connected
2017.02.08 16:09:21 5 : createNotifyHash
2017-02-08 16:09:21 NUKIBridge NBridge1 connected
2017.02.08 16:09:21 5 : End notify loop for NBridge1
2017.02.08 16:09:21 5 : Starting notify loop for NBridge1, 6 event(s), first is appVersion: 0.2.14
2017-02-08 16:09:21 NUKIBridge NBridge1 appVersion: 0.2.14
2017-02-08 16:09:21 NUKIBridge NBridge1 bridgeType: Software
2017-02-08 16:09:21 NUKIBridge NBridge1 serverId: 915081946
2017-02-08 16:09:21 NUKIBridge NBridge1 uptime: 805473
2017-02-08 16:09:21 NUKIBridge NBridge1 currentTime: 2017-02-08T15:09:16Z
2017-02-08 16:09:21 NUKIBridge NBridge1 serverConnected: true
2017.02.08 16:09:21 5 : End notify loop for NBridge1
2017.02.08 16:09:21 4 : NUKIDevice (NUKIDevice112944569) - Received scanResults for matching NukiID 112944569 at device NUKIDevice112944569
2017.02.08 16:09:21 5 : NUKIDevice (NUKIDevice112944569) - Parse with result: {"rssi":-77,"paired":true,"name":"Nuki_06BB65B9"}
2017.02.08 16:09:21 5 : NUKIDevice (NUKIDevice112944569) - parse status message for NUKIDevice112944569
2017.02.08 16:09:21 5 : NUKIDevice (NUKIDevice112944569) - readings set for NUKIDevice112944569
2017.02.08 16:09:21 5 : Starting notify loop for NUKIDevice112944569, 3 event(s), first is name: Nuki_06BB65B9
2017-02-08 16:09:21 NUKIDevice NUKIDevice112944569 name: Nuki_06BB65B9
2017-02-08 16:09:21 NUKIDevice NUKIDevice112944569 rssi: -77
2017-02-08 16:09:21 NUKIDevice NUKIDevice112944569 paired: true
2017.02.08 16:09:21 5 : End notify loop for NUKIDevice112944569
Zitat von: CoolTux am 08 Februar 2017, 16:13:52Also aus der Console?
Das ist Standardkram. Dachte mehr an Log von Homebride/Siri
Feb 08 15:54:01 raspberrypi homebridge[474]: 2017-02-08 15:54:01 caching: NUKIDevice112944569-lockState: unlocked
Feb 08 15:54:01 raspberrypi homebridge[474]: [2/8/2017, 3:54:01 PM] [FHEM] NUKIDevice112944569-lockState value unlocked not handled in values
Feb 08 15:54:01 raspberrypi homebridge[474]: 2017-02-08 15:54:01 caching: NUKIDevice112944569-state: unlocked
Zitat von: Morpheus_1977 am 08 Februar 2017, 16:17:27
Also aus der Console?
Ich glaub das könnte interessant seinCode Auswählen
Feb 08 15:54:01 raspberrypi homebridge[474]: 2017-02-08 15:54:01 caching: NUKIDevice112944569-lockState: unlocked
Feb 08 15:54:01 raspberrypi homebridge[474]: [2/8/2017, 3:54:01 PM] [FHEM] NUKIDevice112944569-lockState value unlocked not handled in values
Feb 08 15:54:01 raspberrypi homebridge[474]: 2017-02-08 15:54:01 caching: NUKIDevice112944569-state: unlocked
2017.02.10 09:51:06 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 215, <$fh> line 231
2017.02.10 09:56:53 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 215, <$fh> line 232
2017.02.10 10:08:33 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 459.
2017.02.10 10:08:33 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 465.
2017.02.10 12:44:27 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/37_plex.pm line 4075.
2017.02.10 12:44:27 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/37_plex.pm line 4145.
Zitat von: CoolTux am 10 Februar 2017, 13:32:13
Nein hast nichts falsch gemacht. Das werde ich demnächst mal abfabgen. Geht denn sonst alles soweit?
ZitatIch hoffe das ich die richtigen Daten gesetzt habe? Ohne zu wissen was sie bewirken denke ich sieht das ganz gut aus ;) Oder?
Internals:
DEF 112944569 IODev=NBridge1
IODev NBridge1
NAME NUKIDevice112944569
NR 90
NUKIID 112944569
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.0
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.2.45:8083/fhem/NUKIDevice-112944569
Readings:
2017-02-10 13:06:06 battery ok
2017-02-10 13:06:06 batteryCritical false
2017-02-10 13:06:06 lockState unlocked
2017-02-10 17:36:32 name Nuki_06BB65B9
2017-02-10 17:36:32 paired true
2017-02-10 17:36:32 rssi -88
2017-02-10 13:06:06 state unlocked
2017-02-10 13:06:06 success true
Fhem:
infix NUKIDevice
Helper:
Attributes:
IODev NBridge1
alias Nuki Zuhause
genericDeviceType lock
room Homekit,NUKI
webhookFWinstance WEB
webhookHttpHostname 192.168.2.45
Zitat von: Weisswurstverkäufer am 11 Februar 2017, 11:14:03
Hallo,
ich hätte einen Vorschlag bezüglich der SET-Befehle. Und zwar fände ich es gut, wenn man nicht direkt "set nukidevice {unlock,lock,...,statusRequest}, sondern die "lockActions" zweistufig machen würde. Also "set nukidevice lockAction lock".
Hintergrund: wenn man manuell über FHEMWEB einen statusRequest senden will hat man so ein gewisses Risiko sich leicht zu verklicken und die Tür versehentlich zu öffnen. Möglicherweise kommen ja auch noch andere API Aufrufe die keine lockAction sind dazu, dann wäre eine klare Trennung sowieso noch sinnvoller.
Meinungen dazu?
Gruß
Zitat von: CoolTux am 11 Februar 2017, 12:34:23ich bin auch eher für pro, damit man es nicht ausversehen tätigt. Wenn ich bei mir unlatch mache, geht die Tür auch automatisch 1-2cm auf, sodass ein Verriegeln nicht möglich ist, bzw es sinnfrei ist.
Gibt es Seitens der Anderen Meinungen dazu? Pro oder Contro Argumente?
Zitat von: Andy89 am 12 Februar 2017, 00:53:41Darf ich draus schließen das du Nuki über Siri nutzt? Falls ja, wie sieht den dein Mapping aus? Bei mir funktioniert eben genau das leider nicht....
ich bin auch eher für pro, damit man es nicht ausversehen tätigt. Wenn ich bei mir unlatch mache, geht die Tür auch automatisch 1-2cm auf, sodass ein Verriegeln nicht möglich ist, bzw es sinnfrei ist.
Aber auf der andere Seite mache ich über Fhemweb fast gar nichs mehr ::)
Zitat von: Morpheus_1977 am 12 Februar 2017, 08:47:19nicht direkt. Ich hab zwar ein Mapping irgendwo her, aber ich nutz das eigentlich auch nicht. Aber Homekit beschwert sich immer wenn die Tür nicht abgeschlossen ist oder wenn sie geöffnet wird.
Darf ich draus schließen das du Nuki über Siri nutzt? Falls ja, wie sieht den dein Mapping aus? Bei mir funktioniert eben genau das leider nicht....
Gruß
Morpheus
Gesendet von iPhone mit Tapatalk
LockCurrentState=lockState,values=/^lock/:SECURED;/^unlock/:UNSECURED LockTargetState=state,values=/^lock/:SECURED;/^unlock/:UNSECURED,cmds=SECURED:lock;UNSECURED:unlatch
LockCurrentState=lockState,values=locked:1;unlocked:0;lock:1;unlock:0 LockTargetState=lockState,values=locked:1;unlocked:0,cmds=1:lock;0:unlock,cmd=
state
lock
2017-02-12 20:26:20
state
locked
2017-02-12 20:26:49
Internals:
CFGFN
DEF 65459745 IODev=NUKI
IODev NUKI
NAME NUKIDevice65459745
NR 263
NUKIID 65459745
STATE locked
TYPE NUKIDevice
VERSION 0.6.0
WEBHOOK_REGISTER unregistered
Readings:
2017-02-12 20:26:49 battery ok
2017-02-12 20:26:49 batteryCritical false
2017-02-12 20:26:49 lockState locked
2017-02-12 20:28:53 name Nuki_03E6D621
2017-02-12 20:28:53 paired true
2017-02-12 20:28:53 rssi -74
2017-02-12 20:26:49 state locked
2017-02-12 20:26:49 success true
Fhem:
infix NUKIDevice
Helper:
fromAutocreate 1
Attributes:
IODev NUKI
alias Eingang
genericDeviceType lock
homebridgeMapping LockCurrentState=lockState,values=locked:1;unlocked:0;lock:1;unlock:0 LockTargetState=lockState,values=locked:1;unlocked:0,cmds=1:lock;0:unlock,cmd=
room Homekit,NUKI
Internals:
BRIDGEAPI 1.5
CFGFN
DEF 192.168.0.168 xxxxxx
HOST 192.168.0.168
NAME NUKI
NR 258
PORT 8080
STATE connected
TOKEN xxxxxx
TYPE NUKIBridge
VERSION 0.6.0
Readings:
2017-02-12 20:19:01 0_name Eingang
2017-02-12 20:19:01 0_nukiId 65459745
2017-02-12 20:29:54 bridgeType Hardware
2017-02-12 20:29:54 currentTime 2017-02-12T19:29:56+00:00
2017-02-12 20:29:54 firmwareVersion 1.4.20
2017-02-12 20:29:54 hardwareId 82649465
2017-02-12 20:29:54 serverConnected true
2017-02-12 20:29:54 serverId 263279036
2017-02-12 20:19:01 smartlockCount 1
2017-02-12 20:29:54 state connected
2017-02-12 20:29:54 uptime 1726181
2017-02-12 20:29:54 wifiFirmwareVersion 1.0.1
Helper:
aliveCount 0
Attributes:
room NUKI
2017-02-12 20:33:46 NUKIBridge NUKI connected
2017-02-12 20:33:46 NUKIBridge NUKI firmwareVersion: 1.4.20
2017-02-12 20:33:46 NUKIBridge NUKI wifiFirmwareVersion: 1.0.1
2017-02-12 20:33:46 NUKIBridge NUKI bridgeType: Hardware
2017-02-12 20:33:46 NUKIBridge NUKI hardwareId: 82649465
2017-02-12 20:33:46 NUKIBridge NUKI serverId: 263279036
2017-02-12 20:33:46 NUKIBridge NUKI uptime: 1726413
2017-02-12 20:33:46 NUKIBridge NUKI currentTime: 2017-02-12T19:33:48+00:00
2017-02-12 20:33:46 NUKIBridge NUKI serverConnected: true
2017-02-12 20:33:46 NUKIDevice NUKIDevice65459745 name: Nuki_03E6D621
2017-02-12 20:33:46 NUKIDevice NUKIDevice65459745 rssi: -76
2017-02-12 20:33:46 NUKIDevice NUKIDevice65459745 paired: true
2017-02-12 20:33:15 NUKIDevice NUKIDevice65459745 statusRequest
2017-02-12 20:33:16 NUKIDevice NUKIDevice65459745 batteryCritical: false
2017-02-12 20:33:16 NUKIDevice NUKIDevice65459745 lockState: unlocked
2017-02-12 20:33:16 NUKIDevice NUKIDevice65459745 unlocked
2017-02-12 20:33:16 NUKIDevice NUKIDevice65459745 battery: ok
2017-02-12 20:33:16 NUKIDevice NUKIDevice65459745 success: true
Zitat von: muehlberger am 12 Februar 2017, 20:37:26
Hallo zusammen,
ich nutze NUKI & HomeKit mittlerweile auch ganz gerne, allerdings ohne meine SIRI.
Das führt mich schon zur ersten Frage - der LockState scheint manchmal mit Lock, manchmal mit Locked ausgegeben werden. Ist das so Absicht?
Soweit ich mich erinnere, hat beides (lock/locked und Status-Aktualisierung) schon mal geklappt. Hatte die Bridge und das Lock auch schon in FHEM gelöscht und wieder neu eingetragen - leider ohne Erfolg.
Hat jemand eine Idee oder Lösung? Wäre toll!
fg, muehlberger
Zitat von: muehlberger am 12 Februar 2017, 21:05:33
Ok - Danke für die Erklärung! Ist ja eh nicht tragisch, hatte mich nur gewundert .
Hast du eventuell auch noch einen tip für die status Aktualisierung?
Gesendet von iPhone mit Tapatalk
Zitat von: Morpheus_1977 am 12 Februar 2017, 08:47:19
Darf ich draus schließen das du Nuki über Siri nutzt? Falls ja, wie sieht den dein Mapping aus? Bei mir funktioniert eben genau das leider nicht....
Gruß
Morpheus
Gesendet von iPhone mit Tapatalk
Zitat von: CoolTux am 12 April 2017, 15:55:54"sudo apt-get install libjson-perl" gemacht, war schon auf dem aktuellsten Stand...
Hallo,
Das sollte eigentlich soweit korrekt sein. Eventuell hast du die jsonlib nicht installiert?
2017.04.12 18:05:17 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.04.12 18:05:17 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.2.112:8080/info?token=xxxx
2017.04.12 18:05:17 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.04.12 18:05:17 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.04.12 18:05:17 5: NUKIBridge (NBridge1) - Response JSON:
2017.04.12 18:05:17 5: NUKIBridge (NBridge1) - Response ERROR: 192.168.2.112: Connection refused
2017.04.12 18:05:17 5: NUKIBridge (NBridge1) - Response CODE:
2017.04.12 18:05:17 5: NUKIBridge (NBridge1) - Bridge ist offline
2017.04.12 18:05:17 4: NUKIBridge (NBridge1) - error while requesting: 192.168.2.112: Connection refused
Ping wird ausgeführt für 192.168.2.112 mit 32 Bytes Daten:
Antwort von 192.168.2.112: Bytes=32 Zeit=4ms TTL=128
Antwort von 192.168.2.112: Bytes=32 Zeit=1ms TTL=128
Antwort von 192.168.2.112: Bytes=32 Zeit=1ms TTL=128
Antwort von 192.168.2.112: Bytes=32 Zeit=1ms TTL=128
Ping-Statistik für 192.168.2.112:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 1ms, Maximum = 4ms, Mittelwert = 1ms
pi@raspberrypi ~ $ sudo ping 192.168.2.112
PING 192.168.2.112 (192.168.2.112) 56(84) bytes of data.
64 bytes from 192.168.2.112: icmp_req=1 ttl=128 time=2.17 ms
64 bytes from 192.168.2.112: icmp_req=2 ttl=128 time=1.59 ms
64 bytes from 192.168.2.112: icmp_req=3 ttl=128 time=1.41 ms
64 bytes from 192.168.2.112: icmp_req=4 ttl=128 time=1.60 ms
64 bytes from 192.168.2.112: icmp_req=5 ttl=128 time=1.82 ms
64 bytes from 192.168.2.112: icmp_req=6 ttl=128 time=1.64 ms
^C
--- 192.168.2.112 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 1.419/1.711/2.173/0.238 ms
ZitatTo add a Nuki bridge to your installation, you need to enable developer mode on your bridge and define a port and an access token. This can be achieved using the Android app. Please note that the API token should be 6-20 characters long, even though the app allows you to set a longer one.
Zitat von: CoolTux am 12 April 2017, 19:31:09
aber den developer mode hast du aktiviert, oder? Da sollte dann ja alles im untermenü drin stehen. Ich kenne leider die hardware bridge nicht. Eventuell kann ein User mal bitte helfen
Zitat von: daniel2311 am 18 April 2017, 16:33:02
Ich denke, das ist die Schwierigkeit in der Hardware-Bridge. Man kommt da meines Erachtens wirklich nur dran, wenn man die Hardware-Bridge in der App hinzufügt. Vllt. mache ich da mal ein paar Screenshots von, wenn ich Zeit habe. Das hat mich auch echt Zeit gekostet und ist der selbe Effekt, wie hier beschrieben bzgl. connections refused.
Zitat von: mahowi am 27 April 2017, 08:47:28
Falls noch jemand ein Nuki sucht, für Prime Mitglieder gibt es heute bei Amazon das Nuki Schloß mit der Bridge für €224,25.
Zitat von: FhemPiUser am 30 April 2017, 13:12:53
laut https://nuki.io/de/api/ (https://nuki.io/de/api/) gibt es auch eine bluetooth api. wäre es damit nicht machbar ein entsprechendes fhem modul zu dchreiben, was über einen bluetooth usb stick im raspberry und bluez das nuki direkt, also ohne bridge, zu steuern? hat sich das mal jemand angeschaut?
Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 375.
Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 375.
Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 375.
Zitat von: ulli am 06 Mai 2017, 11:24:52
Hallo,
Ich bekomme aktuell das log mit folgender Meldung zu gemüllt.Code Auswählen
Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 375.
Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 375.
Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 375.
PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 375.
NUKIBridge (NBridge1) - defined with host 192.168.178.48 on port 8080, Token xxxxxx
2017.05.14 09:50:50 3: NUKIDevice (NUKIDevice140073833) - I/O device is NBridge1
2017.05.14 09:50:50 3: NUKIDevice (NUKIDevice140073833) - defined with Code: NBridge1-140073833
2017.05.14 09:50:50 2: NUKIDevice (NUKIDevice140073833) - Registering NUKIDevice for webhook URI /NUKIDevice ...
[color=red]2017.05.14 09:50:50 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 215, <$fh> line 316.[/color]
2017.05.14 09:50:50 3: NUKIDevice (NUKIDevice140073833) - URL ist: http://192.168.178.48:8083/fhem/NUKIDevice-140073833
Internals:
DEF 140073833 IODev=NBridge1
IODev NBridge1
NAME NUKIDevice140073833
NR 1042
NUKIID 140073833
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.0
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8088
WEBHOOK_REGISTER sent
WEBHOOK_URI /webhook/NUKIDevice
WEBHOOK_URL http://192.168.178.37:8088/webhook/NUKIDevice-140073833
Readings:
2017-05-14 10:13:19 battery ok
2017-05-14 10:13:19 batteryCritical 0
2017-05-14 10:13:19 lockState unlocked
2017-05-14 14:15:55 name Nuki_08595B69
2017-05-14 14:15:55 paired 1
2017-05-14 14:15:55 rssi -79
2017-05-14 10:13:19 state unlocked
2017-05-14 10:20:12 success 1
Fhem:
infix NUKIDevice
Helper:
Attributes:
IODev NBridge1
alarmDevice Sensor
alarmSettings alarm5,alarm6,|NUKIDevice140073833:lock|Verriegelung Wohnung|on
alias NUKI_L1
fp_Home 150,490,2,
icon 1_nuki
room Hall,NUKI
webCmd lock:unlock:unlatch
webhookFWinstance WEBhook
webhookHttpHostname 192.168.178.37
Internals:
BRIDGEAPI 1.5
DEF 192.168.178.48 xxxxxx
HOST 192.168.178.48
NAME NBridge1
NR 1041
PORT 8080
STATE connected
TOKEN xxxxxx
TYPE NUKIBridge
VERSION 0.6.1
Readings:
2017-05-13 11:09:55 0_name Home
2017-05-13 11:09:55 0_nukiId 140073833
2017-05-14 14:18:23 bridgeType Hardware
2017-05-14 14:18:23 currentTime 2017-05-14T12:18:23+00:00
2017-05-14 14:18:23 firmwareVersion 1.5.2
2017-05-14 14:18:23 hardwareId 110157993
2017-05-14 14:18:23 serverConnected 1
2017-05-14 14:18:23 serverId 951376988
2017-05-13 11:09:55 smartlockCount 1
2017-05-14 14:18:23 state connected
2017-05-14 14:18:23 uptime 97999
2017-05-14 14:18:23 wifiFirmwareVersion 1.0.1
Helper:
aliveCount 0
Attributes:
icon 1_nuki_bridge
room NUKI
Zitat von: Newbee am 14 Mai 2017, 14:22:24
Anbei die Infos für die Beiden.
List Device:Code AuswählenInternals:
DEF 140073833 IODev=NBridge1
IODev NBridge1
NAME NUKIDevice140073833
NR 1042
NUKIID 140073833
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.0
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8088
WEBHOOK_REGISTER sent
WEBHOOK_URI /webhook/NUKIDevice
WEBHOOK_URL http://192.168.178.37:8088/webhook/NUKIDevice-140073833
Readings:
2017-05-14 10:13:19 battery ok
2017-05-14 10:13:19 batteryCritical 0
2017-05-14 10:13:19 lockState unlocked
2017-05-14 14:15:55 name Nuki_08595B69
2017-05-14 14:15:55 paired 1
2017-05-14 14:15:55 rssi -79
2017-05-14 10:13:19 state unlocked
2017-05-14 10:20:12 success 1
Fhem:
infix NUKIDevice
Helper:
Attributes:
IODev NBridge1
alarmDevice Sensor
alarmSettings alarm5,alarm6,|NUKIDevice140073833:lock|Verriegelung Wohnung|on
alias NUKI_L1
fp_Home 150,490,2,
icon 1_nuki
room Hall,NUKI
webCmd lock:unlock:unlatch
webhookFWinstance WEBhook
webhookHttpHostname 192.168.178.37
List BridgeCode AuswählenInternals:
BRIDGEAPI 1.5
DEF 192.168.178.48 xxxxxx
HOST 192.168.178.48
NAME NBridge1
NR 1041
PORT 8080
STATE connected
TOKEN xxxxxx
TYPE NUKIBridge
VERSION 0.6.1
Readings:
2017-05-13 11:09:55 0_name Home
2017-05-13 11:09:55 0_nukiId 140073833
2017-05-14 14:18:23 bridgeType Hardware
2017-05-14 14:18:23 currentTime 2017-05-14T12:18:23+00:00
2017-05-14 14:18:23 firmwareVersion 1.5.2
2017-05-14 14:18:23 hardwareId 110157993
2017-05-14 14:18:23 serverConnected 1
2017-05-14 14:18:23 serverId 951376988
2017-05-13 11:09:55 smartlockCount 1
2017-05-14 14:18:23 state connected
2017-05-14 14:18:23 uptime 97999
2017-05-14 14:18:23 wifiFirmwareVersion 1.0.1
Helper:
aliveCount 0
Attributes:
icon 1_nuki_bridge
room NUKI
Danke vorab
Zitat von: Skjall am 14 Mai 2017, 14:49:36
Ich hätte mal ne frage zum Gesamtsystem: Wenn ich die Nuki-Bridge verwende, benötigt die dann im Betrieb eine Verbindung zum Internet?
Sprich: Werden für das Auf- und Zuschließen Cloud-Dienst verwendet?
LG Jan
Zitat von: CoolTux am 14 Mai 2017, 14:53:15
Ok das passt soweit. Kannst Du bei der. Kannst Du bitte einmal ein get callbackList machen und die Ausgabe hier zeigen.
Callback-ID Callback-URL
0 http://192.168.178.48:8083/fhem/NUKIDevice-140073833
1 http://192.168.178.37:8083/fhem/NUKIDevice-140073833
2 http://192.168.178.37:8088/webhook/NUKIDevice-140073833
Zitat von: Newbee am 14 Mai 2017, 16:22:00
Hier der callback Inhalt:Code AuswählenCallback-ID Callback-URL
0 http://192.168.178.48:8083/fhem/NUKIDevice-140073833
1 http://192.168.178.37:8083/fhem/NUKIDevice-140073833
2 http://192.168.178.37:8088/webhook/NUKIDevice-140073833
2017.05.15 09:03:46 5: NUKIDevice (NUKIDevice140403361) - readings set for NUKIDevice140403361
2017.05.15 09:03:57 4: NUKIDevice (NUKIDevice140403361) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.05.15 09:03:57 4: NUKIDevice (NUKIDevice140403361) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.05.15 09:04:02 5: NUKIDevice (NUKIDevice140403361) - Parse with result: {"success": true, "batteryCritical": false}
2017.05.15 09:04:02 5: NUKIDevice (NUKIDevice140403361) - parse status message for NUKIDevice140403361
2017.05.15 09:04:02 5: NUKIDevice (NUKIDevice140403361) - lockAction readings set for NUKIDevice140403361
Readings:
2017-05-12 09:10:31 battery ok
2017-05-12 09:10:31 batteryCritical 0
2017-05-12 09:10:31 lockState unlocked
2017-05-15 09:07:33 name Nuki_085E62A1
2017-05-15 09:07:33 paired 1
2017-05-15 09:07:33 rssi -79
2017-05-12 09:10:31 state unlocked
2017-05-15 09:04:02 success 1
Zitat von: oli82 am 15 Mai 2017, 09:55:03
Verwende die " 0.6.1" als Bridgemodul.
Das schloss braucht ja ein paar Sekunden, bis es den Status neu setzt. Der kommt zwar in der App, aber nicht in Fhem an.
Muss mir aber trotzdem die CallbackURL mal anschauen, wie diese zu setzen ist.
Aber wenn wir gerade bei der Bridge sind: der Name des Schloss wird nicht in den Readings aktualisiert, wenn man ihn nachträglich ändert und Sonderzeichen äöüß werden nicht unterstützt ;)
Zitat von: oli82 am 15 Mai 2017, 09:55:03
Verwende die " 0.6.1" als Bridgemodul.
Das schloss braucht ja ein paar Sekunden, bis es den Status neu setzt. Der kommt zwar in der App, aber nicht in Fhem an.
Muss mir aber trotzdem die CallbackURL mal anschauen, wie diese zu setzen ist.
Aber wenn wir gerade bei der Bridge sind: der Name des Schloss wird nicht in den Readings aktualisiert, wenn man ihn nachträglich ändert und Sonderzeichen äöüß werden nicht unterstützt ;)
Zitat von: CoolTux am 15 Mai 2017, 10:48:37
Was ich noch vergessen habe. Die erste Readingaktualisierung sollte erfolgen sobald der Motor aufgehört hat zu drehen.
2017.05.15 09:03:57 4: NUKIDevice (NUKIDevice140403361) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.05.15 09:04:02 5: NUKIDevice (NUKIDevice140403361) - Parse with result: {"success": true, "batteryCritical": false}
2017-05-15 09:04:02 success 1
Zitat von: oli82 am 15 Mai 2017, 12:48:24
YES! Läuft. Danke für´s schnelle Umsetzen. Ach, hier liegt immer noch ein Nest Protect ;)
Zitat von: CoolTux am 14 Mai 2017, 16:24:42
Bisschen viel des guten. Am besten einmal alle 3 Einträge löschen. Dann ein Attribut für den Webhook anklicken und ohne es zu löschen neu setzen. Am Ende sollte nur ein Eintrag drin stehen pro Smartlock.
[quote]Internals:
BRIDGEAPI 1.5
DEF 192.168.178.51 cXXXXX
HOST 192.168.178.51
NAME NBridge1
NR 388
PORT 8080
STATE connected
TOKEN cXXXXX
TYPE NUKIBridge
VERSION 0.6.1
Readings:
2017-06-05 08:54:47 0_name Haus
2017-06-05 08:54:47 0_nukiId 1487XXXXX
2017-06-05 09:09:43 appVersion 1.3.0
2017-06-05 09:09:43 bridgeType Software
2017-06-05 09:09:43 currentTime 2017-06-05T07:09:43Z
2017-06-05 09:09:43 serverConnected true
2017-06-05 09:09:43 serverId 2155XXXXX
2017-06-05 08:54:47 smartlockCount 1
2017-06-05 09:09:43 state connected
2017-06-05 09:09:43 uptime 10385
Helper:
aliveCount 0
Attributes:
room NUKI
[code]
Internals:
CFGFN DEF 1487XXXXX
IODev=NBridge1
IODev [url=http://192.168.178.84:8083/fhem?detail=NBridge1]NBridge1[/url]
NAME [url=http://192.168.178.84:8083/fhem?detail=NUKIDevice1487XXXXX]NUKIDevice1487XXXXX[/url]
NR 395
NUKIID 1487XXXXX
STATE unknown
TYPE NUKIDevice
VERSION 0.6.1
WEBHOOK_REGISTER unregistered Readings:
2017-06-05 08:56:30 battery ok
2017-06-05 08:56:30 batteryCritical false
2017-06-05 08:56:30 lockState unknown
2017-06-05 09:14:18 name Nuki_08DXXXXX
2017-06-05 09:14:18 paired true
2017-06-05 09:14:18 rssi -71
2017-06-05 08:56:30 state unknown
2017-06-05 08:58:42 success false
Fhem:
infix NUKIDevice
Helper:
fromAutocreate 1
Attributes:
IODev [url=http://192.168.178.84:8083/fhem?detail=NBridge1]NBridge1[/url]
alias Haus
room NUKI
Internals:
CFGFN
DEF 1487XXXXX IODev=NBridge1
IODev NBridge1
NAME NUKIDevice1487XXXXX
NR 396
NUKIID 1487XXXXX
STATE unknown
TYPE NUKIDevice
VERSION 0.6.1
WEBHOOK_REGISTER unregistered
Readings:
2017-06-05 14:19:37 battery ok
2017-06-05 14:19:37 batteryCritical false
2017-06-05 14:21:15 lockState unknown
2017-06-05 14:21:47 name Nuki_08DXXXXX
2017-06-05 14:21:47 paired true
2017-06-05 14:21:47 rssi -68
2017-06-05 14:21:15 state unknown
2017-06-05 14:21:15 success false
Fhem:
infix NUKIDevice
Helper:
fromAutocreate 1
Attributes:
IODev NBridge1
alias Haus
room NUKI
battery
ok
2017-06-05 16:30:25
batteryCritical
false
2017-06-05 16:30:25
lockState
unknown
2017-06-05 16:30:25
name
Nuki_08DD6979
2017-06-05 16:30:22
paired
true
2017-06-05 16:30:22
rssi
-73
2017-06-05 16:30:22
state
unknown
2017-06-05 16:30:25
success
false
2017-06-05 16:30:25
Zitat von: andy6090 am 05 Juni 2017, 16:31:20
Ne leider immer noch nicht, keine reaktionCode Auswählen
battery
ok
2017-06-05 16:30:25
batteryCritical
false
2017-06-05 16:30:25
lockState
unknown
2017-06-05 16:30:25
name
Nuki_08DD6979
2017-06-05 16:30:22
paired
true
2017-06-05 16:30:22
rssi
-73
2017-06-05 16:30:22
state
unknown
2017-06-05 16:30:25
success
false
2017-06-05 16:30:25
2017.06.06 00:09:53 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.06.06 00:09:53 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.51:8080/info?token=cXXXXX
2017.06.06 00:09:53 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.06.06 00:09:53 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.06.06 00:09:54 4: NUKIDevice (NUKIDevice1487XXXXX) - Received scanResults for matching NukiID 1487XXXXX at device NUKIDevice1487XXXXX
2017.06.06 00:10:20 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.06.06 00:10:20 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.51:8080/info?token=cXXXXX
2017.06.06 00:10:20 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.06.06 00:10:20 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.06.06 00:10:20 4: NUKIDevice (NUKIDevice1487XXXXX) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.06.06 00:10:20 4: NUKIDevice (NUKIDevice1487XXXXX) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.06.06 00:10:20 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.51:8080/lockAction?token=cXXXXX&action=1&nukiId=1487XXXXX
2017.06.06 00:10:21 4: NUKIDevice (NUKIDevice1487XXXXX) - Received scanResults for matching NukiID 1487XXXXX at device NUKIDevice1487XXXXX
2017.06.06 00:10:49 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.06.06 00:10:49 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.51:8080/info?token=cXXXXX
2017.06.06 00:10:49 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.06.06 00:10:49 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.06.06 00:10:49 4: NUKIDevice (NUKIDevice1487XXXXX) - Received scanResults for matching NukiID 1487XXXXX at device NUKIDevice1487XXXXX
Zitat2017.07.01 10:22:12 3: NUKIBridge (Door_Bridge) - invalid json detected: HTTP 503 Unavailable
2017.07.01 10:24:30 1: Perfmon: possible freeze starting at 10:24:29, delay is 1.207
Error: Connection refused
Error: Connection refused
Error: Connection refused
2017.07.01 19:20:39 4: NUKIBridge (Door_Bridge) - NUKIBridge_GetCheckBridgeAlive
2017.07.01 19:20:39 4: NUKIBridge (Door_Bridge) - Send HTTP POST with URL http://192.168.0.19:8080/info?token=XXXXXX
2017.07.01 19:20:39 4: NUKIBridge (Door_Bridge) - run NUKIBridge_Call
2017.07.01 19:20:39 4: NUKIBridge (Door_Bridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.07.01 19:20:39 5: NUKIBridge (Door_Bridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": XXX, "serverId": XXXXXX}, "versions": {"firmwareVersion": "1.5.2", "wifiFirmwareVersion": "1.0.1"}, "uptime": 204257, "currentTime": "2017-07-01T17:20:39+00:00", "serverConnected": true, "scanResults": [{"nukiId": XXX XXX XXX, "name": "Nuki_08C569F1", "rssi": -79, "paired": true}]}
2017.07.01 19:20:39 5: NUKIBridge (Door_Bridge) - Response ERROR:
2017.07.01 19:20:39 5: NUKIBridge (Door_Bridge) - Response CODE: 200
2017.07.01 19:20:39 5: NUKIBridge (Door_Bridge) - Bridge ist online
2017.07.01 19:20:39 4: NUKIDevice (Nuki_Key_01) - Received scanResults for matching NukiID XXX XXX XXX at device Nuki_Key_01
Error: Connection refused
Error: Connection refused
Error: Connection refused
ZitatPERL WARNING: Use of uninitialized value in string eq at ./FHEM/74_NUKIDevice.pm line 215, <$fh> line 3562.Kann man das beheben?
2017.09.22 14:58:00 1: stacktrace:
2017.09.22 14:58:00 1: main::__ANON__ called by ./FHEM/74_NUKIDevice.pm (215)
2017.09.22 14:58:00 1: main::NUKIDevice_Attr called by fhem.pl (3448)
2017.09.22 14:58:00 1: main::CallFn called by fhem.pl (2785)
2017.09.22 14:58:00 1: main::CommandAttr called by fhem.pl (1174)
2017.09.22 14:58:00 1: main::AnalyzeCommand called by fhem.pl (1027)
2017.09.22 14:58:00 1: main::AnalyzeCommandChain called by fhem.pl (1309)
2017.09.22 14:58:00 1: main::CommandInclude called by fhem.pl (537)
Invalid value for attribute blablu: needs to be different from the defined name/address of your Smartlock, we need to know how Smartlock can connect back to FHEM here!
Zitatdefine NUKIWEB FHEMWEB 8282 global
attr NUKIWEB hiddenroom Tablet-UI,Außenbereich,DG,Dummy,EG_Arbeitszimmer,EG_Esszimmer,EG_Flur,EG_Kueche,EG_Technikraum, EG_Terrasse,EG_WC,EG_Wohnzimmer,Fritz-Box,HUE,Heizung,Kalender,Kamera,NUC,NUKI,OG_Abstellraum,OG_Bad,OG_Felixzimmer,OG_Flur,OG_Lenizimmer,OG_Schlafzimmer,Residents,Sonos,Wetter,Zentral,Everything,Logfile,Commandref,Remote doc,Edit files,Select style,Event monitor,Restart,Update
attr NUKIWEB room hidden
attr NUKIWEB webname webhook
define allowedNUKIWEB allowed
attr allowedNUKIWEB allowedCommands set
attr allowedNUKIWEB allowedDevices Home
attr allowedNUKIWEB validFor NUKIWEB
ZitatFHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
Zitat2017.10.13 10:43:08 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
2017.10.13 10:45:13 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
2017.10.13 10:45:36 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
Internals:
DEF 111966073 IODev=NukiBridge
IODev NukiBridge
NAME NUKIDevice111966073
NR 793
NUKIID 111966073
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.1
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8282
WEBHOOK_REGISTER sent
WEBHOOK_URI /webhook/NUKIDevice
WEBHOOK_URL http://192.168.0.23:8282/webhook/NUKIDevice-111966073
READINGS:
2017-10-13 11:27:52 battery ok
2017-10-13 11:27:52 batteryCritical 0
2017-10-13 11:27:52 lockState unlocked
2017-10-13 11:29:08 name Nuki_06AC7779
2017-10-13 11:29:08 paired 1
2017-10-13 11:29:08 rssi -78
2017-10-13 11:27:52 state unlocked
2017-10-13 11:27:52 success 1
fhem:
infix NUKIDevice
helper:
Attributes:
IODev NukiBridge
alias Home
room NUKI
webhookFWinstance NUKIWEB
webhookHttpHostname 192.168.0.23
Internals:
CSRFTOKEN csrf_232796455891768
DEF 8282 global
FD 10
NAME NUKIWEB
NR 21
NTFY_ORDER 50-NUKIWEB
PORT 8282
STATE Initialized
TYPE FHEMWEB
Attributes:
hiddenroom Tablet-UI,Außenbereich,DG,Dummy,EG_Arbeitszimmer,EG_Esszimmer,EG_Flur,EG_Kueche,EG_Technikraum, EG_Terrasse,EG_WC,EG_Wohnzimmer,Fritz-Box,HUE,Heizung,Kalender,Kamera,NUC,NUKI,OG_Abstellraum,OG_Bad,OG_Felixzimmer,OG_Flur,OG_Lenizimmer,OG_Schlafzimmer,Residents,Sonos,Wetter,Zentral,Everything,Logfile,Commandref,Remote doc,Edit files,Select style,Event monitor,Restart,Update
room hidden
webname webhook
2017.10.13 10:43:08 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
2017.10.13 10:45:13 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
2017.10.13 10:45:36 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
Zitat von: marvin78 am 04 November 2017, 14:41:04Also ich habe 2 fobs im Einsatz und die funktionieren gut. Einer davon aber erst, als ich eine neue andere Batterie eingesetzt habe.
Die Fobs sind Müll. Sie funktionieren mit Glück hin und wieder mal. Mein Tipp: Finger weg.
ZitatNiedrigpreis-Geräte (zB Elephone Q) oder ungeeignete Geräte wie zB Android TV Boxen oder Android TV Sticks haben oft nicht ausreichend dimensionierte Antennen sowie unvollständige Bluetooth-Implementierungen und können dadurch keine Bluetooth-Verbindung zum Smart Lock aufbauen.
Zitat von: CoolTux am 14 Januar 2017, 14:53:21
Bitte einmal einspielen und schauen was passiert. Es müsste wenn wieder 503 kommt diesmal im Error Reading der Bridge "Smartlock offline" stehen und im state des jeweiligen Smartlock ebenfalls "Smartlock offline"
-------------------> normaler "Alive Check"
2017.11.06 16:18:48 4: NUKIBridge (NB1) - NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:18:48 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=xxxxx
2017.11.06 16:18:48 4: NUKIBridge (NB1) - run NUKIBridge_Call
2017.11.06 16:18:48 4: NUKIBridge (NB1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:18:48 5: NUKIBridge (NB1) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 112896353, "serverId": 600025564}, "versions": {"firmwareVersion": "1.8.0", "wifiFirmwareVersion": "1.1.0"}, "uptime": 362291, "currentTime": "2017-11-06T15:18:48+00:00", "serverConnected": false, "scanResults": [{"nukiId": yyyyyy, "name": "Nuki_zzzzz", "rssi": -79, "paired": true}]}
2017.11.06 16:18:48 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:18:48 5: NUKIBridge (NB1) - Response CODE: 200
2017.11.06 16:18:48 5: NUKIBridge (NB1) - Bridge ist online
2017.11.06 16:18:48 4: NUKIDevice (NUKILock1) - Received scanResults for matching NukiID yyyyyy at device NUKILock1
2017.11.06 16:18:48 5: NUKIDevice (NUKILock1) - Parse with result: {"rssi":-79,"paired":true,"name":"Nuki_zzzzz"}
2017.11.06 16:18:48 5: NUKIDevice (NUKILock1) - parse status message for NUKILock1
2017.11.06 16:18:48 5: NUKIDevice (NUKILock1) - readings set for NUKILock1
-------------------> Befehl "unlatch" an NukiLock
2017.11.06 16:19:05 4: NUKIDevice (NUKILock1) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.11.06 16:19:05 4: NUKIDevice (NUKILock1) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.06 16:19:05 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/lockAction?token=xxxxx&action=3&nukiId=yyyyyy
-------------------> Fast gleichzeitig der "Alive Check"
2017.11.06 16:19:09 4: NUKIBridge (NB1) - NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:19:09 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=xxxxx
2017.11.06 16:19:09 4: NUKIBridge (NB1) - run NUKIBridge_Call
2017.11.06 16:19:09 4: NUKIBridge (NB1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
-------------------> Antwort "nicht verfügbar" (auf den Alive Check, da schon mit unlatch beschäftigt)
2017.11.06 16:19:10 5: NUKIBridge (NB1) - Response JSON: HTTP 503 Unavailable
2017.11.06 16:19:10 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:19:10 5: NUKIBridge (NB1) - Response CODE: 503
2017.11.06 16:19:10 3: NUKIBridge (NB1) - invalid json detected: HTTP 503 Unavailable
-------------------> Antwort auf "unlatch"
2017.11.06 16:19:19 5: NUKIBridge (NB1) - Response JSON: {"success": true, "batteryCritical": false}
2017.11.06 16:19:19 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:19:19 5: NUKIBridge (NB1) - Response CODE: 200
2017.11.06 16:19:19 5: NUKIDevice (NUKILock1) - Parse with result: {"success": true, "batteryCritical": false}
2017.11.06 16:19:19 5: NUKIDevice (NUKILock1) - parse status message for NUKILock1
2017.11.06 16:19:19 5: NUKIDevice (NUKILock1) - lockAction readings set for NUKILock1
2017.11.06 16:19:24 4: NUKIDevice (NUKILock1) - Received webhook for matching NukiId at device NUKILock1
2017.11.06 16:19:24 5: NUKIDevice (NUKILock1) - Parse with result: {"nukiId": yyyyyy, "state": 3, "stateName": "unlocked", "batteryCritical": false}
2017.11.06 16:19:24 5: NUKIDevice (NUKILock1) - parse status message for NUKILock1
2017.11.06 16:19:24 5: NUKIDevice (NUKILock1) - readings set for NUKILock1
-------------------> Befehl "lock" an NukiLock
2017.11.06 16:19:27 4: NUKIDevice (NUKILock1) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.11.06 16:19:27 4: NUKIDevice (NUKILock1) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.06 16:19:27 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/lockAction?token=xxxxx&action=2&nukiId=yyyyyy
-------------------> Antwort "nicht verfügbar" (auf den lock-Befehl, da noch beschäftigt)
2017.11.06 16:19:27 5: NUKIBridge (NB1) - Response JSON: HTTP 503 Unavailable
2017.11.06 16:19:27 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:19:27 5: NUKIBridge (NB1) - Response CODE: 503
2017.11.06 16:19:27 5: NUKIDevice (NUKILock1) - Parse with result: HTTP 503 Unavailable
2017.11.06 16:19:27 3: NUKIDevice (NUKILock1) - invalid json detected: HTTP 503 Unavailable
-------------------> normaler "Alive Check"
2017.11.06 16:19:35 4: NUKIBridge (NB1) - NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:19:35 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=xxxxx
2017.11.06 16:19:35 4: NUKIBridge (NB1) - run NUKIBridge_Call
2017.11.06 16:19:35 4: NUKIBridge (NB1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
-------------------> Antwort "nicht verfügbar" (auf den Alive Check, da noch beschäftigt)
2017.11.06 16:19:35 5: NUKIBridge (NB1) - Response JSON: HTTP 503 Unavailable
2017.11.06 16:19:35 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:19:35 5: NUKIBridge (NB1) - Response CODE: 503
2017.11.06 16:19:35 3: NUKIBridge (NB1) - invalid json detected: HTTP 503 Unavailable
-------------------> normaler "Alive Check"
2017.11.06 16:19:52 4: NUKIBridge (NB1) - NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:19:52 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=xxxxx
2017.11.06 16:19:52 4: NUKIBridge (NB1) - run NUKIBridge_Call
2017.11.06 16:19:52 4: NUKIBridge (NB1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:19:52 5: NUKIBridge (NB1) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 112896353, "serverId": 600025564}, "versions": {"firmwareVersion": "1.8.0", "wifiFirmwareVersion": "1.1.0"}, "uptime": 362355, "currentTime": "2017-11-06T15:19:52+00:00", "serverConnected": false, "scanResults": [{"nukiId": yyyyyy, "name": "Nuki_zzzzz", "rssi": -79, "paired": true}]}
2017.11.06 16:19:52 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:19:52 5: NUKIBridge (NB1) - Response CODE: 200
2017.11.06 16:19:52 5: NUKIBridge (NB1) - Bridge ist online
2017.11.06 16:19:52 4: NUKIDevice (NUKILock1) - Received scanResults for matching NukiID yyyyyy at device NUKILock1
2017.11.06 16:19:52 5: NUKIDevice (NUKILock1) - Parse with result: {"name":"Nuki_zzzzz","rssi":-79,"paired":true}
2017.11.06 16:19:52 5: NUKIDevice (NUKILock1) - parse status message for NUKILock1
2017.11.06 16:19:52 5: NUKIDevice (NUKILock1) - lockAction readings set for NUKILock1
-------------------> normaler "Alive Check"
2017.11.06 16:20:17 4: NUKIBridge (NB1) - NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:20:17 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=xxxxx
2017.11.06 16:20:17 4: NUKIBridge (NB1) - run NUKIBridge_Call
2017.11.06 16:20:17 4: NUKIBridge (NB1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:20:17 5: NUKIBridge (NB1) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 112896353, "serverId": 600025564}, "versions": {"firmwareVersion": "1.8.0", "wifiFirmwareVersion": "1.1.0"}, "uptime": 362380, "currentTime": "2017-11-06T15:20:17+00:00", "serverConnected": false, "scanResults": [{"nukiId": yyyyyy, "name": "Nuki_zzzzz", "rssi": -79, "paired": true}]}
2017.11.06 16:20:17 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:20:17 5: NUKIBridge (NB1) - Response CODE: 200
2017.11.06 16:20:17 5: NUKIBridge (NB1) - Bridge ist online
2017.11.06 16:20:17 4: NUKIDevice (NUKILock1) - Received scanResults for matching NukiID yyyyyy at device NUKILock1
2017.11.06 16:20:17 5: NUKIDevice (NUKILock1) - Parse with result: {"name":"Nuki_zzzzz","paired":true,"rssi":-79}
2017.11.06 16:20:17 5: NUKIDevice (NUKILock1) - parse status message for NUKILock1
2017.11.06 16:20:17 5: NUKIDevice (NUKILock1) - readings set for NUKILock1
-------------------> Befehl "lock" an NukiLock
2017.11.06 16:21:42 4: NUKIDevice (NUKILock1) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.11.06 16:21:42 4: NUKIDevice (NUKILock1) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.06 16:21:42 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/lockAction?token=xxxxx&action=2&nukiId=yyyyyy
2017.11.06 16:21:55 5: NUKIBridge (NB1) - Response JSON: {"success": true, "batteryCritical": false}
2017.11.06 16:21:55 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:21:55 5: NUKIBridge (NB1) - Response CODE: 200
2017.11.06 16:21:55 5: NUKIDevice (NUKILock1) - Parse with result: {"success": true, "batteryCritical": false}
2017.11.06 16:21:55 5: NUKIDevice (NUKILock1) - parse status message for NUKILock1
2017.11.06 16:21:55 5: NUKIDevice (NUKILock1) - lockAction readings set for NUKILock1
2017.11.06 16:22:02 4: NUKIDevice (NUKILock1) - Received webhook for matching NukiId at device NUKILock1
2017.11.06 16:22:02 5: NUKIDevice (NUKILock1) - Parse with result: {"nukiId": yyyyyy, "state": 1, "stateName": "locked", "batteryCritical": false}
2017.11.06 16:22:02 5: NUKIDevice (NUKILock1) - parse status message for NUKILock1
2017.11.06 16:22:02 5: NUKIDevice (NUKILock1) - readings set for NUKILock1
-------------------> normaler "Alive Check"
2017.11.06 16:22:07 4: NUKIBridge (NB1) - NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:22:07 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=xxxxx
2017.11.06 16:22:07 4: NUKIBridge (NB1) - run NUKIBridge_Call
2017.11.06 16:22:07 4: NUKIBridge (NB1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
-------------------> Antwort "nicht verfügbar" (auf den Alive Check, da noch beschäftigt)
2017.11.06 16:22:07 5: NUKIBridge (NB1) - Response JSON: HTTP 503 Unavailable
2017.11.06 16:22:07 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:22:07 5: NUKIBridge (NB1) - Response CODE: 503
2017.11.06 16:22:07 3: NUKIBridge (NB1) - invalid json detected: HTTP 503 Unavailable
-------------------> normaler "Alive Check"
2017.11.06 16:22:28 4: NUKIBridge (NB1) - NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:22:28 4: NUKIBridge (NB1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=xxxxx
2017.11.06 16:22:28 4: NUKIBridge (NB1) - run NUKIBridge_Call
2017.11.06 16:22:28 4: NUKIBridge (NB1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.06 16:22:29 5: NUKIBridge (NB1) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 112896353, "serverId": 600025564}, "versions": {"firmwareVersion": "1.8.0", "wifiFirmwareVersion": "1.1.0"}, "uptime": 362511, "currentTime": "2017-11-06T15:22:28+00:00", "serverConnected": false, "scanResults": [{"nukiId": yyyyyy, "name": "Nuki_zzzzz", "rssi": -79, "paired": true}]}
2017.11.06 16:22:29 5: NUKIBridge (NB1) - Response ERROR:
2017.11.06 16:22:29 5: NUKIBridge (NB1) - Response CODE: 200
2017.11.06 16:22:29 5: NUKIBridge (NB1) - Bridge ist online
2017.11.06 16:22:29 4: NUKIDevice (NUKILock1) - Received scanResults for matching NukiID yyyyyy at device NUKILock1
2017.11.06 16:22:29 5: NUKIDevice (NUKILock1) - Parse with result: {"name":"Nuki_zzzzz","paired":true,"rssi":-79}
2017.11.06 16:22:29 5: NUKIDevice (NUKILock1) - parse status message for NUKILock1
2017.11.06 16:22:29 5: NUKIDevice (NUKILock1) - readings set for NUKILock1
2017.11.09 18:36:06 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 18:36:06 5: NUKIBridge (NBridge1) - Response CODE: 200
CFGFN
DEF
99247689 IODev=NBridge1
IODev
NBridge1
NAME
NUKIDevice99247689
NR
1349
NUKIID
99247689
STATE
locked
TYPE
NUKIDevice
VERSION
0.6.1
WEBHOOK_COUNTER
0
WEBHOOK_PORT
8083
WEBHOOK_REGISTER
sent
WEBHOOK_URI
/fhem/NUKIDevice
WEBHOOK_URL
http://192.168.178.32:8083/fhem/NUKIDevice-99247689
Readings
battery
ok
2017-11-09 18:36:22
batteryCritical
false
2017-11-09 18:36:22
lockState
locked
2017-11-09 18:36:22
name
Nuki_05EA6649
2017-11-09 18:39:02
paired
true
2017-11-09 18:39:02
rssi
-73
2017-11-09 18:39:02
state
locked
2017-11-09 18:36:22
success
true
2017-11-09 18:36:22
NUKIDevice99247689
Attributes
IODev
NBridge1
deleteattr
alias
P2
deleteattr
room
NUKI
deleteattr
webhookFWinstance
WEB
deleteattr
webhookHttpHostname
192.168.178.32:8083
deleteattr
Probably associated with
NBridge1
connected
NUKIBridge
Internals:
CFGFN
DEF 99247689 IODev=NBridge1
IODev NBridge1
NAME NUKIDevice99247689
NR 1349
NUKIID 99247689
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.1
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.178.32:8083/fhem/NUKIDevice-99247689
READINGS:
2017-11-09 19:11:25 battery ok
2017-11-09 19:11:25 batteryCritical false
2017-11-09 19:11:25 lockState unlocked
2017-11-09 19:19:03 name Nuki_05EA6649
2017-11-09 19:19:03 paired true
2017-11-09 19:19:03 rssi -72
2017-11-09 19:11:25 state unlocked
2017-11-09 19:11:25 success true
fhem:
infix NUKIDevice
helper:
fromAutocreate 1
Attributes:
IODev NBridge1
alias P2
room NUKI
verbose 0
webhookFWinstance WEB
webhookHttpHostname 192.168.178.32
2017.11.09 20:15:07 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:15:07 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:15:07 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:15:07 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:15:07 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:15:14Z","uptime":5521,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-81,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:15:07 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:15:07 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:15:07 5: NUKIBridge (NBridge1) - Bridge ist online
2017.11.09 20:15:07 4: NUKIDevice (NUKIDevice99247689) - Received scanResults for matching NukiID 99247689 at device NUKIDevice99247689
2017.11.09 20:15:07 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"name":"Nuki_05EA6649","paired":true,"rssi":-81}
2017.11.09 20:15:07 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:15:07 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:15:28 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:15:28 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:15:28 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:15:28 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:15:28 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:15:35Z","uptime":5542,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-78,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:15:28 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:15:28 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:15:28 5: NUKIBridge (NBridge1) - Bridge ist online
2017.11.09 20:15:28 4: NUKIDevice (NUKIDevice99247689) - Received scanResults for matching NukiID 99247689 at device NUKIDevice99247689
2017.11.09 20:15:28 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"rssi":-78,"paired":true,"name":"Nuki_05EA6649"}
2017.11.09 20:15:28 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:15:28 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:15:56 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:15:56 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:15:56 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:15:56 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:15:56 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:16:03Z","uptime":5570,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-78,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:15:56 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:15:56 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:15:56 5: NUKIBridge (NBridge1) - Bridge ist online
2017.11.09 20:15:56 4: NUKIDevice (NUKIDevice99247689) - Received scanResults for matching NukiID 99247689 at device NUKIDevice99247689
2017.11.09 20:15:56 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"rssi":-78,"paired":true,"name":"Nuki_05EA6649"}
2017.11.09 20:15:56 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:15:56 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:16:17 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:16:17 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:16:17 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:16:17 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:16:17 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:16:24Z","uptime":5591,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-71,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:16:17 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:16:17 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:16:17 5: NUKIBridge (NBridge1) - Bridge ist online
2017.11.09 20:16:17 4: NUKIDevice (NUKIDevice99247689) - Received scanResults for matching NukiID 99247689 at device NUKIDevice99247689
2017.11.09 20:16:17 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"paired":true,"rssi":-71,"name":"Nuki_05EA6649"}
2017.11.09 20:16:17 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:16:17 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:16:38 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:16:38 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:16:38 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:16:38 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:16:38 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:16:45Z","uptime":5612,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-68,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:16:38 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:16:38 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:16:38 5: NUKIBridge (NBridge1) - Bridge ist online
2017.11.09 20:16:38 4: NUKIDevice (NUKIDevice99247689) - Received scanResults for matching NukiID 99247689 at device NUKIDevice99247689
2017.11.09 20:16:38 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"paired":true,"rssi":-68,"name":"Nuki_05EA6649"}
2017.11.09 20:16:38 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:16:38 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:16:47 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.11.09 20:16:47 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.09 20:16:47 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/lockState?token=rqknc6&nukiId=99247689
2017.11.09 20:16:47 5: NUKIDevice (NUKIDevice99247689) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2017.11.09 20:16:48 5: NUKIBridge (NBridge1) - Response JSON: {"state":1,"success":true,"stateName":"locked","batteryCritical":false}
2017.11.09 20:16:48 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:16:48 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:16:48 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"state":1,"success":true,"stateName":"locked","batteryCritical":false}
2017.11.09 20:16:48 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:16:48 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:16:57 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:16:57 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:16:57 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:16:57 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:16:57 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:17:04Z","uptime":5631,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-79,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:16:57 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:16:57 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:16:57 5: NUKIBridge (NBridge1) - Bridge ist online
2017.11.09 20:16:57 4: NUKIDevice (NUKIDevice99247689) - Received scanResults for matching NukiID 99247689 at device NUKIDevice99247689
2017.11.09 20:16:57 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"paired":true,"rssi":-79,"name":"Nuki_05EA6649"}
2017.11.09 20:16:57 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:16:57 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:16:57 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.11.09 20:16:57 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.09 20:16:57 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/lockAction?token=rqknc6&action=1&nukiId=99247689
2017.11.09 20:17:07 5: NUKIBridge (NBridge1) - Response JSON: {"success":true,"batteryCritical":false}
2017.11.09 20:17:07 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:17:07 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:17:07 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"success":true,"batteryCritical":false}
2017.11.09 20:17:07 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:17:07 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.11.09 20:17:07 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.09 20:17:07 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/lockState?token=rqknc6&nukiId=99247689
2017.11.09 20:17:07 5: NUKIDevice (NUKIDevice99247689) - lockAction readings set for NUKIDevice99247689
2017.11.09 20:17:08 5: NUKIBridge (NBridge1) - Response JSON: {"state":3,"success":true,"stateName":"unlocked","batteryCritical":false}
2017.11.09 20:17:08 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:17:08 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:17:08 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"state":3,"success":true,"stateName":"unlocked","batteryCritical":false}
2017.11.09 20:17:08 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:17:08 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:17:18 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:17:18 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:17:18 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:17:18 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:17:18 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:17:25Z","uptime":5652,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-86,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:17:18 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:17:18 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:17:18 5: NUKIBridge (NBridge1) - Bridge ist online
2017.11.09 20:17:18 4: NUKIDevice (NUKIDevice99247689) - Received scanResults for matching NukiID 99247689 at device NUKIDevice99247689
2017.11.09 20:17:18 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"paired":true,"rssi":-86,"name":"Nuki_05EA6649"}
2017.11.09 20:17:18 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:17:18 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:17:37 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:17:37 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:17:37 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:17:37 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:17:37 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:17:44Z","uptime":5671,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-72,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:17:37 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:17:37 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:17:37 5: NUKIBridge (NBridge1) - Bridge ist online
2017.11.09 20:17:37 4: NUKIDevice (NUKIDevice99247689) - Received scanResults for matching NukiID 99247689 at device NUKIDevice99247689
2017.11.09 20:17:37 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"name":"Nuki_05EA6649","paired":true,"rssi":-72}
2017.11.09 20:17:37 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 20:17:37 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 20:17:55 4: NUKIBridge (NBridge1) - NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:17:55 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/info?token=rqknc6
2017.11.09 20:17:55 4: NUKIBridge (NBridge1) - run NUKIBridge_Call
2017.11.09 20:17:55 4: NUKIBridge (NBridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.11.09 20:17:55 5: NUKIBridge (NBridge1) - Response JSON: {"currentTime":"2017-11-09T19:18:02Z","uptime":5689,"scanResults":[{"paired":true,"nukiId":99247689,"rssi":-73,"name":"Nuki_05EA6649"},{"paired":false,"nukiId":105423241,"rssi":-98,"name":"Nuki_0648A189"}],"versions":{"appVersion":"1.3.3"},"bridgeType":2,"ids":{"serverId":1355477230},"serverConnected":true}
2017.11.09 20:17:55 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:17:55 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:17:55 5: NUKIBridge (NBridge1) - Bridge ist online
battery
ok
2017-11-09 20:17:08
batteryCritical
false
2017-11-09 20:17:08
lockState
unlocked
2017-11-09 20:17:08
name
Nuki_05EA6649
2017-11-09 20:21:16
paired
true
2017-11-09 20:21:16
rssi
-68
2017-11-09 20:21:16
state
unlocked
2017-11-09 20:17:08
success
true
2017-11-09 20:17:08
2017.11.09 20:16:57 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.09 20:16:57 4: NUKIBridge (NBridge1) - Send HTTP POST with URL http://192.168.178.21:8080/lockAction?token=rqknc6&action=1&nukiId=99247689
2017.11.09 20:17:07 5: NUKIBridge (NBridge1) - Response ERROR:
2017.11.09 20:17:07 5: NUKIBridge (NBridge1) - Response CODE: 200
2017.11.09 20:17:07 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"success":true,"batteryCritical":false}
2017.11.09 22:31:48 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.11.09 22:31:48 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.09 22:31:48 5: NUKIDevice (NUKIDevice99247689) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2017.11.09 22:31:50 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"state":3,"success":true,"stateName":"unlocked","batteryCritical":false}
2017.11.09 22:31:50 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 22:31:50 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 22:32:04 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"rssi":-73,"paired":true,"name":"Nuki_05EA6649"}
2017.11.09 22:32:04 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 22:32:04 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 22:32:30 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"name":"Nuki_05EA6649","paired":true,"rssi":-72}
2017.11.09 22:32:30 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 22:32:30 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 22:32:50 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"name":"Nuki_05EA6649","paired":true,"rssi":-73}
2017.11.09 22:32:50 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 22:32:50 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 22:33:09 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2017.11.09 22:33:09 4: NUKIDevice (NUKIDevice99247689) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2017.11.09 22:33:09 5: NUKIDevice (NUKIDevice99247689) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2017.11.09 22:33:11 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"state":1,"success":true,"stateName":"locked","batteryCritical":false}
2017.11.09 22:33:11 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 22:33:11 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
2017.11.09 22:33:15 5: NUKIDevice (NUKIDevice99247689) - Parse with result: {"rssi":-71,"paired":true,"name":"Nuki_05EA6649"}
2017.11.09 22:33:15 5: NUKIDevice (NUKIDevice99247689) - parse status message for NUKIDevice99247689
2017.11.09 22:33:15 5: NUKIDevice (NUKIDevice99247689) - readings set for NUKIDevice99247689
READINGS:
2017-11-17 16:17:34 battery ok
2017-11-17 16:17:34 batteryCritical false
2017-11-17 16:17:34 lockState unlocked
2017-11-17 16:17:45 name Nuki_05EA6649
2017-11-17 16:17:45 paired true
2017-11-17 16:17:45 rssi -74
2017-11-17 16:17:34 state unlocked
2017-11-17 16:17:34 success true
Internals:
CHANGED
DEF 99247689 IODev=NBridge1
IODev NBridge1
NAME NUKIDevice99247689
NR 60
NUKIID 99247689
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.1
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.178.32:8083/fhem/NUKIDevice-99247689
READINGS:
2017-11-20 17:56:07 battery ok
2017-11-20 17:56:07 batteryCritical false
2017-11-20 17:56:07 lockState unlocked
2017-11-20 18:00:38 name Nuki_05EA6649
2017-11-20 18:00:38 paired true
2017-11-20 18:00:38 rssi -89
2017-11-20 17:56:07 state unlocked
2017-11-20 17:58:27 success true
fhem:
infix NUKIDevice
helper:
Attributes:
IODev NBridge1
alias P2
event-on-change-reading state, battery, batteryCritical, lockstate
room NUKI
verbose 0
webhookFWinstance WEB
webhookHttpHostname 192.168.178.32
Zitat von: CoolTux am 20 November 2017, 18:18:11
Hat damit nichts zu tun.
Mein Devicename ist WgtTuer und im Webhook steht auch NUKIDevice-12345
battery ok 2017-11-20 19:06:40
batteryCritical false 2017-11-20 19:06:40
lockState locked 2017-11-20 19:05:38
name Nuki_05EA6649 2017-11-20 19:08:54
paired true 2017-11-20 19:08:54
rssi -75 2017-11-20 19:08:54
state locked 2017-11-20 19:05:38
success true 2017-11-20 19:06:40
Zitat von: olaf am 20 November 2017, 15:54:26
@danillo: bei mir klappt das mit dem Callback einwandfrei. Wie ich sehe, hast Du eine Software-Bridge. Ich habe eine Hardware-Bridge. Kann das daran liegen? Ich kenn die SW-Bridge nicht. Kann man da sehen, ob die "locked"-Meldung des Schlosses ankommt? Die 3 readings rssi, paired und name, die immer aktualisiert werden, resultieren nur aus einer zyklischen "Alive"-Abfrage des NUKI_Bridge Moduls. Diese ist nur vorgesehen, um zu sehen, ob die Bridge noch "connected" ist.
@CoolTux: Auf Github habe ich einen PR für meine Änderungen eingestellt. Kannst ja mal schauen.
Der Fehler 503 schlägt nun nicht mehr als json-error durch.
Weiterhin habe ich alle Anfragen an die Bridge/Schloss nun serialisiert und, wenn es eine Fehlermedung zurückgibt (503-unavailable, leere Antwort, http-timeout) wiederhole ich die Befehle solange, bis sie vom Schloss umgesetzt wurden. Damit vermeide ich, dass wichtige Befehle wie "lock" im Falle eines Fehlers einfach unter den Tisch fallen.
Eine Sache habe ich noch nicht im Griff, s. Anhang.
Kann man irgendwie zwischen Statusmeldungen des Schlosses aufgrund manueller Betätigung und Antworten auf fhem-Anfragen unterscheiden?
Zitat von: CoolTux am 21 November 2017, 12:30:49
Ich habe Deinen Patch gestern ins master übernommen und werde es die Tage testen. Laden hat schon mal geklappt ;D
Grüße
Zitat von: olaf am 21 November 2017, 19:42:41
Das mit dem notify ist die Grundidee. Wenn der state von "processing" auf "connected" zurückgeht, ist die Bridge wieder aufnahmebereit und per notify löse ich den nächsten Befehl aus, der sich auf dem Stack angesammelt hat.
Das mit dem save bekomme ich nicht. Ich denke das liegt daran, dass ich in der cfg "attr global autosave 0" gesetzt habe. Ich mag es nicht, wenn immerzu in meiner cfg rumgeschrieben wird.
Aber ein guter Hinweis und vielleicht nicht für jeden Anwendungsfall geeignet. Ich denke mir mal was anderes aus.
Für weitere Hinweise bin ich dankbar ....
Zitat von: olaf am 22 November 2017, 17:36:48
Hallo Leon,
ganz meine Meinung. Lass mich dann auch Deine Lösung wissen. Ich bin neugierig.
2017.11.29 16:29:12 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
Zitat von: CoolTux am 29 November 2017, 17:04:59Danke. Hab die neue Version drauf. Teste es nun mal ein paar Tage. :)
Das sollte damit zu tun haben.
Einfach das Zip runterladen und die Module von Hand installieren, so wie damals :)
Zitat von: CoolTux am 05 Dezember 2017, 06:35:17Also meine 503 Meldungen sind bisher weg. Auch verzögerte oder nicht gemeldete Statusänderungen hatte ich nicht mehr.
Guten Morgen,
Kann mir schon jemand was zu der neuen Version mit dem Patch von Olaf sagen.
Bin leider selbst erst heute dazu gekommen die Version bei mir mal ein zu spielen. Aber je mehr Tester um so besser.
Grüße
Leon
Zitat von: Mikka am 05 Dezember 2017, 00:01:02
Mir sind noch ein paar weitere Fragen eingefallen:
1- Wenn man die Tür von außen mit dem normalen Schlüssel öffnet, bekommt der NUKI diesen Status mit?
2- Lässt sich die Nuki Bridge durch z. B. eine Softwarebridge + FHEM und einen BT-Adapter-Stick ersetzen? Hat jemand dies bereits umgesetzt?
3- Lässt sich der Button am Smart Lock ausschalten?
4- Kriegen kleine Kinder den Nuki mal eben so von der Tür abgezogen (hier meine ich den Nuki-Smart-Lock an sich, nicht die Montageplatte)?
5- Die Montageplatte A hat zwei zusätzliche Löcher (links und rechts neben dem Türzylinder), sind dies für Schrauben? Wäre jemand so nett und könnte den Abstand zwischen den Löchern (mittig) messen?
Gute Nacht
Mikka
Zitat von: CoolTux am 05 Dezember 2017, 07:50:05Guter Plan. Und natürlich auch von mir ein Danke an dich und Oli.
Habe gerade selber noch ein bisschen was am Code geändert. Hauptsächlich im Bereich NUKIDevice. Ich würde sagen wir lassen das noch ein zwei Wochen so laufen und wenn nichts weiter ist würde ich es dann einchecken.
Ein dickes Danke geht an Oli für seine super tolle Arbeit.
Grüße
Zitat von: CoolTux am 05 Dezember 2017, 15:05:21Kann ich das prüfen ob das bei mir auch so ist? Im Webif sieht alles gut aus denke ich.
Aus irgendeinem Grund werden bei mir die BridgeCallStacks nicht abgearbeitet. Habe da nun hunderte Arrays drin stehen.
Ausserdem stehen stacktrace Auszüge im Log. Muss da noch mal schauen was da los ist.
2017.12.05 16:16:10 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2017.12.05 16:16:10 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.123.216:8080/info?token=omimn3
2017.12.05 16:16:10 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2017.12.05 16:16:10 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2017.12.05 16:16:10 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 848811841, "serverId": 1245341545}, "versions": {"firmwareVersion": "1.8.0", "wifiFirmwareVersion": "1.1.0"}, "uptime": 3692416, "currentTime": "2017-12-05T15:16:11+00:00", "serverConnected": true, "scanResults": [{"nukiId": 12345, "name": "Nuki_12345", "rssi": -79, "paired": true}]}
2017.12.05 16:16:10 5: NUKIBridge (NukiBridge) - Response ERROR:
2017.12.05 16:16:10 5: NUKIBridge (NukiBridge) - Response CODE: 200
2017.12.05 16:16:10 5: NUKIBridge (NukiBridge) - Request info!=lockAction. Not deleting from CallStack. Stacksize 7137
2017.12.05 16:16:10 5: NUKIBridge (NukiBridge) - Bridge ist online
2017.12.05 16:16:10 4: NUKIDevice (HomeDoor) - Received scanResults for matching NukiID 12345 at device HomeDoor
BridgeCallStack:
ARRAY(0x4e90458)
ARRAY(0x4f73628)
ARRAY(0x4af82d0)
ARRAY(0x5057e30)
ARRAY(0x4f4b128)
ARRAY(0x412b090)
ARRAY(0x4c631a0)
ARRAY(0x52ad8c0)
ARRAY(0x5051818)
ARRAY(0x423b370)
ARRAY(0x4162c10)
ARRAY(0x4af8f90)
ARRAY(0x45204b8)
ARRAY(0x512a290)
ARRAY(0x4d3f5f0) ............
Zitat von: fred_feuerstein am 05 Dezember 2017, 07:53:03
Zu1: ja.
Zu2: es gibt nur eine softwarebridge in Form einer App für bspw. ein älteres Handy, welches dann die Aufgabe der bridge übernimmt. Das haben ein paar Leute so im Einsatz, aber von der Stabilität her ist die Hardware bridge eher zu empfehlen. Eine BT Anbindung an fhem gibt es denke ich noch nicht.
Zu3: man kann die Funktion Sperren etc. für den Knopf ausschalten. Bzw. auch das pairen für neue Geräte über den Knopf. Also ja.
Zu4: mit Gewalt kriegt man alles ab. Aber das nuki ist schon fest. Bei mir mit der geklebten Variante B. Die Variante mit den Schrauben funktioniert nur, wenn der schließzylinder etwas weiter aus der Tür ragt. Kannst dir dazu am besten die Anleitung auf der nuki Homepage anschauen.
Zu 5: kann man damit festschrauben. Falls du es direkt mit der Tür verschrauben willst. Abstand kann ich nicht messen, da die Platte nicht griffbereit. Normalerweise wird die platte A aber nur mit 3 imbus Schrauben am zylinder festgeklemmt. platte b wird mit 3m klebepad geklebt.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Zitat von: CoolTux am 05 Dezember 2017, 18:53:03
In den Array sollte jeweils eine Befehlskette drin sein welche eigentlich abgearbeitet werden soll. Aber irgendwas funktioniert da noch nicht. Habe auch aktuell wenig Zeit um intensiv zu schauen. Entweder gab es Probleme in Olaf seinen Code oder ich habe was falsch übernommen oder vergessen.
Zitat von: gero112233 am 08 Dezember 2017, 12:36:20Steht aber auch in der Montageanleitung wenn ich mich nicht irre
So ein Zylinder ist für Nuki praktisch ungeeignet. Beim Kauf vom Zylinder muss also aufgepasst werden!
Beste Grüße,
Gero
[code]2017.12.15 11:35:03 1: main::readingsBeginUpdate called by ./FHEM/73_NUKIBridge.pm (462)
2017.12.15 11:35:03 1: main::NUKIBridge_Distribution called by FHEM/HttpUtils.pm (808)
2017.12.15 11:35:03 1: main::HttpUtils_NonblockingGet called by ./FHEM/73_NUKIBridge.pm (433)
2017.12.15 11:35:03 1: main::NUKIBridge_Call called by ./FHEM/73_NUKIBridge.pm (263)
2017.12.15 11:35:03 1: main::NUKIBridge_Set called by ./FHEM/73_NUKIBridge.pm (232)
2017.12.15 11:35:03 1: main::NUKIBridge_Notify called by fhem.pl (3448)
2017.12.15 11:35:03 1: main::CallFn called by fhem.pl (3368)
2017.12.15 11:35:03 1: main::DoTrigger called by fhem.pl (4342)
2017.12.15 11:35:03 1: main::readingsEndUpdate called by ./FHEM/73_NUKIBridge.pm (593)
2017.12.15 11:35:03 1: main::NUKIBridge_ResponseProcessing called by ./FHEM/73_NUKIBridge.pm (549)
2017.12.15 11:35:03 1: main::NUKIBridge_Distribution called by FHEM/HttpUtils.pm (544)
2017.12.15 11:35:03 1: main::__ANON__ called by fhem.pl (689)
2017.12.15 11:35:03 1: readingsUpdate(,lastError,http://:8080?token=xxx: malformed or unsupported URL) missed to call readingsBeginUpdate first.
2017.12.15 11:35:03 1: stacktrace:
2017.12.15 11:35:03 1: main::readingsBulkUpdate called by ./FHEM/73_NUKIBridge.pm (472)
2017.12.15 11:35:03 1: main::NUKIBridge_Distribution called by FHEM/HttpUtils.pm (808)
2017.12.15 11:35:03 1: main::HttpUtils_NonblockingGet called by ./FHEM/73_NUKIBridge.pm (433)
2017.12.15 11:35:03 1: main::NUKIBridge_Call called by ./FHEM/73_NUKIBridge.pm (263)
2017.12.15 11:35:03 1: main::NUKIBridge_Set called by ./FHEM/73_NUKIBridge.pm (232)
2017.12.15 11:35:03 1: main::NUKIBridge_Notify called by fhem.pl (3448)
2017.12.15 11:35:03 1: main::CallFn called by fhem.pl (3368)
2017.12.15 11:35:03 1: main::DoTrigger called by fhem.pl (4342)
2017.12.15 11:35:03 1: main::readingsEndUpdate called by ./FHEM/73_NUKIBridge.pm (593)
[/code]Zitat von: SeppiDeluxe am 26 Januar 2018, 15:46:48
Aber ich nehme dann deinen Ansatz mit der sekundaren FI und nagel die halt zu.
Danke dir
Zitat von: Sascha_F am 16 November 2017, 01:33:10
Hallo zusammen!
Ich mal wieder ;)
Ich glaube, ich brauche eine Eingebung...
Vorweg - ich bekomme nach wie vor immer wieder Log-Einträge (jetzt nicht x-fach, aber mehrmals am Tag). Um es etwas übersichtlicher zu halten, habe ich die Ziffern hinter Device nachfolgend immer entfernt:
NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
NUKIDevice (NUKIDevice) - invalid json detected: HTTP 503 Unavailable
Mein ganz anders Problem habe ich aber gerade mit Nuki (Device) in Verbindung mit einem DOIF. Der Plan sieht vor, dass die Beleuchtung im Windfang angeschaltet wird, sobald das Schloss aufgeschlossen wurde. Das DOIF sieht so aus:
([NUKIDevice:state] eq "unlocked" and [?{sunset("REAL",1800,"16:00","23:00")}-{sunrise("REAL",0,"05:45","06:00")}]) (set HM_377AFE start)
'start' => eventMap auf on-for-timer
'?' => war ein Versuch, damit bei Eintreten der 'sunset'-Bedingung nicht aufgrund dieser Bedingung ausgelöst wird
Das Problem ist, dass die Beleuchtung auch eingeschaltet wird, wenn um 22:30 h aus einem DOIF das Abschließen ausgelöst wird. Im NukiDevice habe ich es auch mit "event-on-change state" probiert, aber das hat auch nicht geholfen. Eigentlich dachte ich, dass sich der state (oder auch lockState) nur aufgrund des webhook ändern - und dieser nur ausgelöst wird, wenn auch tatsächlich etwas am NukiDevice 'passiert' ist...
Also ich dachte:
Ausgangslage
state/lockState = 'unlocked' [ändert sich auch nicht, also kein event-on-change state/lockState; DOIF sollte daher bei Erfüllen der 'sunset'-Bedingung nicht auslösen - passiert aber. Das '?' scheint nicht als "nicht auslösende Bedingung" zu funktionieren]
später (wenn 'sunset'-Bedingung bereits erfüllt)
22:30 h: Anderes DOIF cmd setzt 'set NukiDevice lock' [jetzt wechseln state/lockState auf 'locked'; event-on-change state triggert, aber DOIF-Bedingung dürfte nicht erfüllt sein, da nicht 'unlocked' - passiert aber]
Ich war mir erst nicht sicher, ob DOIF-Problem oder NUKI, aber meine anderen DOIFs laufen einwandfrei, sodass ich es mir nur mit dem webhook oder wie auch immer erklären kann...
Danke euch und viele Grüße
Sascha
NUKIBridge (NBridge) - invalid json detected: HTTP 401 Unauthorized
2018.02.26 08:04:46 3: Forbidden device wz_avr for WEBhook_192.168.42.95_30216
2018.02.26 23:09:27 3: NUKIDevice (NukiBridge) - invalid json detected for http://192.168.x.xxx:8080/callback/list?token=0bc2xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: HTTP 403 Forbidden
Can't use string ("NUKIDevice (NukiBridge) - invali"...) as a HASH ref while "strict refs" in use at ./FHEM/73_NUKIBridge.pm line 683.
http://192.168.x.xxx:8080/info?token=0bc2xxxxxxxxxxxxx
oder statt info auch log oder list. Diese Abfragen führen bei mir zu einem 403- forbidden Fehler. Stimmt also etwas an meinem API-Key nicht?defmod NUKIDevice89706097 NUKIDevice 89706097 IODev=NBridge
attr NUKIDevice89706097 IODev NBridge
attr NUKIDevice89706097 alias XYZ
attr NUKIDevice89706097 devStateIcon unlock:fts_door_open lock:fts_door
attr NUKIDevice89706097 eventMap lock:zu unlock:auf
attr NUKIDevice89706097 icon fts_door_open
attr NUKIDevice89706097 room Eingang,FAVORITEN,NUKI
attr NUKIDevice89706097 webCmd auf:zu
Zitat von: MAC66666 am 27 Februar 2018, 08:15:59
Ich habe derweil auch ein Problem, ich bekomme statt einem Tür auf oder Tür zu Icon nur noch "initialized" angezeigt:Code Auswählendefmod NUKIDevice89706097 NUKIDevice 89706097 IODev=NBridge
attr NUKIDevice89706097 IODev NBridge
attr NUKIDevice89706097 alias XYZ
attr NUKIDevice89706097 devStateIcon unlock:fts_door_open lock:fts_door
attr NUKIDevice89706097 eventMap lock:zu unlock:auf
attr NUKIDevice89706097 icon fts_door_open
attr NUKIDevice89706097 room Eingang,FAVORITEN,NUKI
attr NUKIDevice89706097 webCmd auf:zu
Zitat von: MAC66666 am 27 Februar 2018, 11:41:27
OK, DHCP hat eine andere Adresse zugewiesen. Habe jetzt meinem Router mal klargemacht, dass das so nicht geht ;)
Schade dass man der Bridge selbst keine feste IP zuweisen kann...
Zitat von: CoolTux am 27 Februar 2018, 11:46:43
Sagen wir mal so, Du kannst keine statische festlegen aber Du kannst Deinem DHCP Server sagen er soll eine feste Zuordnung zur entsprechenden MAC machen.
Denke mal das es das ist was Du nun gemacht hast.
Zitat von: CoolTux am 27 Februar 2018, 11:56:49
Es wird morgen Früh ein keines Update geben. Darin wird lediglich decode_json() Errors abgefangen das diese nicht mehr zu einem Crash führen.
2018.02.27 18:07:47 3: NUKIBridge (NBridge) - invalid json detected: HTTP 503 Unavailable
Zitat von: MAC66666 am 27 Februar 2018, 21:50:40
Jup... Kann halt nicht jeder Router, deshalb meinte ich, dass es schade ist, dass man keine feste IP in der Bridge anlegen kann...
Meinst Du das?Code Auswählen2018.02.27 18:07:47 3: NUKIBridge (NBridge) - invalid json detected: HTTP 503 Unavailable
Zitat von: MAC66666 am 27 Februar 2018, 11:41:27
OK, DHCP hat eine andere Adresse zugewiesen. Habe jetzt meinem Router mal klargemacht, dass das so nicht geht ;)
Schade dass man der Bridge selbst keine feste IP zuweisen kann...
Zitat von: MAC66666 am 27 Februar 2018, 22:27:54
Ach und nochwas: Ich lese hier was von Callback usw. aber auch nach intensiver Suche ist mir nicht klar, was das sein soll und warum ich die zwei webhook* attr eintragen soll.
invalid json detected: HTTP 503 Unavailable
Zitat von: CoolTux am 13 Oktober 2017, 13:10:46
Kann beim besten willen nicht finden warum dasCode Auswählen
2017.10.13 10:43:08 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
2017.10.13 10:45:13 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
2017.10.13 10:45:36 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (peer: 192.168.0.22)
Vom Modul kommen sollte.
Sorry
Internals:
DEF 11199XXXX IODev=Nuki
IODev Nuki
NAME NUKIDevice11199XXXX
NR 211
NUKIID 11199XXXX
STATE unlock
TYPE NUKIDevice
VERSION 0.6.2
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.2.250:8083/fhem/NUKIDevice-11199XXXX
READINGS:
2018-06-06 00:26:26 battery ok
2018-06-06 00:26:26 batteryCritical 0
2018-06-06 00:26:26 batteryState ok
2018-06-06 18:33:36 lockState unlock
2018-06-06 22:45:54 name Nuki_06ACXXXX
2018-06-06 22:45:54 paired 1
2018-06-06 22:45:54 rssi -70
2018-06-06 18:33:36 state unlock
2018-06-06 18:33:36 success 1
fhem:
infix NUKIDevice
helper:
Attributes:
IODev Nuki
alias Haustüre
genericDeviceType lock
homebridgeMapping LockCurrentState=lockState,values=locked:1;unlocked:0;lock:1;unlock:0 LockTargetState=lockState,values=locked:1;unlocked:0;lock:1;unlock:0,cmds=1:lock;0:unlock,cmd=
StatusLowBattery=battery,values=ok:BATTERY_LEVEL_NORMAL;low:BATTERY_LEVEL_LOW
CurrentDoorState=lockState,values=/^unlock/:OPEN;/^unlocked/:OPEN;/^lock/:CLOSED;/^locked/:CLOSED
CurrentLockMechanismState=lockState,values=locked:SECURED;unlock=UNSECURED;lock:SECURED;unlock=UNSECURED
room Flur,HomeKit
webhookFWinstance WEB
webhookHttpHostname 192.168.2.250
Internals:
BRIDGEAPI 1.5
DEF 192.168.2.206 1BbXXXX
HOST 192.168.2.206
NAME Nuki
NR 210
PORT 8080
STATE connected
TOKEN 1BbXXXX
TYPE NUKIBridge
VERSION 0.6.2
READINGS:
2018-06-04 20:11:55 0_name Haust�re
2018-06-04 20:11:55 0_nukiId 11199XXXX
2018-06-06 22:49:21 bridgeType Hardware
2018-06-06 22:49:21 currentTime 2018-06-06T20:49:21+00:00
2018-06-06 22:49:21 firmwareVersion 1.10.1
2018-06-06 22:49:21 hardwareId 20218XXXX
2018-06-06 22:49:21 serverConnected 1
2018-06-06 22:49:21 serverId 1827XXXX
2018-06-04 20:11:55 smartlockCount 1
2018-06-06 22:49:21 state connected
2018-06-06 22:49:21 uptime 1387805
2018-06-06 22:49:21 wifiFirmwareVersion 1.1.0
helper:
aliveCount 0
Attributes:
icon 1_nuki_bridge
room HWR
Zitat von: robspr am 06 Juni 2018, 21:20:22
Ich weiß nicht ob ihr immer noch dieses Problem habt da es schon recht lange her ist, bei mir habe ich aber eine Lösung bzw. auch die Ursache gefunden:
In der Nuki Bridge kann man ja bis zu 3 callbacks einrichten, leider waren da immer noch die alten (falschen) drinnen, die bei der Ersteinrichtung erstellt wurden, die auf den FHEMWEB gezeigt haben, der für SSL mit passwort konfiguriert ist.
Manuelles Löschen aller callbacks via "http://192.168.1.50:8080/callback/remove?id=0&token=123456" und neu zuweisen via FHEM hat geholfen.
Edit: die Befehle zum Entfernen der Callbacks gibt es ja auch schon in der Bridge Oberfläche, hätte ich vorher schauen sollen :(
Zitat von: MobiusOne am 06 Juni 2018, 22:56:18
Ich habe das Problem das ich eine Statusänderung von Nuki (manuelles drücken des Knopfes) nicht in FHEM aktualisiert wird. Meiner Meinung nach, habe ich Nuki so konfiguriert, wie hier im Thread beschrieben wurde. Ich habe den Webhook konfiguriert. FHEM hat bei mir die IP-Adresse 192.168.2.250. Die Readings name, paired und rssi werden alle X Sekunden aktualisiert.
Auszug vom Schloss:Code AuswählenInternals:
DEF 11199XXXX IODev=Nuki
IODev Nuki
NAME NUKIDevice11199XXXX
NR 211
NUKIID 11199XXXX
STATE unlock
TYPE NUKIDevice
VERSION 0.6.2
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.2.250:8083/fhem/NUKIDevice-11199XXXX
READINGS:
2018-06-06 00:26:26 battery ok
2018-06-06 00:26:26 batteryCritical 0
2018-06-06 00:26:26 batteryState ok
2018-06-06 18:33:36 lockState unlock
2018-06-06 22:45:54 name Nuki_06ACXXXX
2018-06-06 22:45:54 paired 1
2018-06-06 22:45:54 rssi -70
2018-06-06 18:33:36 state unlock
2018-06-06 18:33:36 success 1
fhem:
infix NUKIDevice
helper:
Attributes:
IODev Nuki
alias Haustüre
genericDeviceType lock
homebridgeMapping LockCurrentState=lockState,values=locked:1;unlocked:0;lock:1;unlock:0 LockTargetState=lockState,values=locked:1;unlocked:0;lock:1;unlock:0,cmds=1:lock;0:unlock,cmd=
StatusLowBattery=battery,values=ok:BATTERY_LEVEL_NORMAL;low:BATTERY_LEVEL_LOW
CurrentDoorState=lockState,values=/^unlock/:OPEN;/^unlocked/:OPEN;/^lock/:CLOSED;/^locked/:CLOSED
CurrentLockMechanismState=lockState,values=locked:SECURED;unlock=UNSECURED;lock:SECURED;unlock=UNSECURED
room Flur,HomeKit
webhookFWinstance WEB
webhookHttpHostname 192.168.2.250
und von der Bridge:Code AuswählenInternals:
BRIDGEAPI 1.5
DEF 192.168.2.206 1BbXXXX
HOST 192.168.2.206
NAME Nuki
NR 210
PORT 8080
STATE connected
TOKEN 1BbXXXX
TYPE NUKIBridge
VERSION 0.6.2
READINGS:
2018-06-04 20:11:55 0_name Haust�re
2018-06-04 20:11:55 0_nukiId 11199XXXX
2018-06-06 22:49:21 bridgeType Hardware
2018-06-06 22:49:21 currentTime 2018-06-06T20:49:21+00:00
2018-06-06 22:49:21 firmwareVersion 1.10.1
2018-06-06 22:49:21 hardwareId 20218XXXX
2018-06-06 22:49:21 serverConnected 1
2018-06-06 22:49:21 serverId 1827XXXX
2018-06-04 20:11:55 smartlockCount 1
2018-06-06 22:49:21 state connected
2018-06-06 22:49:21 uptime 1387805
2018-06-06 22:49:21 wifiFirmwareVersion 1.1.0
helper:
aliveCount 0
Attributes:
icon 1_nuki_bridge
room HWR
Seht jemand den Fehler den ich hier mache?
Vielen dank.
Zitat von: CoolTux am 07 Juni 2018, 08:10:35
Ist Dein WEB eventuell mit HTTPS oder Passwort gesichert?
define allowed_WEB allowed
attr allowed_WEB basicAuth bWFyXXXXXXXXXXXX==
attr allowed_WEB validFor WEB
0 http://192.168.2.250:8083/fhem/NUKIDevice-11199XXXX
Zitat von: MobiusOne am 07 Juni 2018, 10:34:45
Hallo CoolTux,
mein FHEM ist standard über HTTP erreichbar.
Mit Password würde mir nur mein Anmelde Kennwort an FHEM einfallen, meinst du dies? Soll ich das entfernen?Code Auswählendefine allowed_WEB allowed
attr allowed_WEB basicAuth bWFyXXXXXXXXXXXX==
attr allowed_WEB validFor WEB
Ansonsten sieht so das Callback auf Nuki aus:Code Auswählen0 http://192.168.2.250:8083/fhem/NUKIDevice-11199XXXX
Zitat von: MobiusOne am 07 Juni 2018, 14:47:39
Top, funktioniert jetzt :D
Danke!
Zitat von: CoolTux am 07 Juni 2018, 14:50:56
Eigentlich müsste Dein FHEM Log von nicht gelungenden Anmeldungen überschwemmt sein :)
NUKIBridge (Nuki) - invalid json detected: HTTP 503 Unavailable
Zitat von: CoolTux am 07 Juni 2018, 14:59:24
Nein das meine ich nicht. Ich meinte vom allowed Device für Web.
Internals:
BRIDGEAPI 1.5
DEF 192.168.100.120 123456
HOST 192.168.100.120
NAME NUKI_Bridge
NR 250
PORT 8080
STATE connected
TOKEN 123456
TYPE NUKIBridge
VERSION 0.6.2
READINGS:
2018-06-23 07:53:35 0_name Haust�r
2018-06-23 07:53:35 0_nukiId 30255XXXX
2018-06-23 08:20:58 bridgeType Hardware
2018-06-23 08:20:58 currentTime 2018-06-23T06:20:58+00:00
2018-06-23 08:20:58 firmwareVersion 1.10.1
2018-06-23 08:20:58 hardwareId 28468XXXX
2018-06-23 08:20:58 serverConnected 1
2018-06-23 08:20:58 serverId 13398XXXX
2018-06-23 07:53:35 smartlockCount 1
2018-06-23 08:20:58 state connected
2018-06-23 08:20:58 uptime 4413
2018-06-23 08:20:58 wifiFirmwareVersion 1.1.0
helper:
aliveCount 0
Attributes:
room NUKI
Internals:
DEF 3025XXXX IODev=NUKI_Bridge
IODev NUKI_Bridge
NAME NUKIDevice3025XXXX
NR 251
NUKIID 3025XXXX
STATE unlock
TYPE NUKIDevice
VERSION 0.6.2
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8088
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.100.109:8088/fhem/NUKIDevice-30255XXXX
READINGS:
2018-06-23 08:04:06 battery ok
2018-06-23 08:04:06 batteryCritical 0
2018-06-23 08:04:06 batteryState ok
2018-06-23 08:06:02 lockState unlock
2018-06-23 08:22:40 name Nuki_1208XXXX
2018-06-23 08:22:40 paired 1
2018-06-23 08:22:40 rssi -68
2018-06-23 08:06:02 state unlock
2018-06-23 08:06:02 success 1
fhem:
infix NUKIDevice
helper:
Attributes:
IODev NUKI_Bridge
alias Haust�r
room NUKI
webhookFWinstance WEBApi
webhookHttpHostname 192.168.100.109
Internals:
CONNECTS 3
DEF 8088 global
FD 19
NAME WEBApi
NR 142
NTFY_ORDER 50-WEBApi
PORT 8088
STATE Initialized
TYPE FHEMWEB
Attributes:
allowfrom ^192\.168\.100\.([1-9]|[1-9][0-9]|1([0-9][0-9])|2([0-4][0-9]|5[0-4]))$|127.0.0.1|192.168.100.120
csrfToken none
stylesheetPrefix dark
Callback-ID Callback-URL
0 http://192.168.100.109:8088/fhem/NUKIDevice-3025XXXX
2018.06.23 11:54:59 5: NUKIDevice (NUKIDevice3025XXXX) - Parse with result: {"paired":true,"name":"Nuki_1208XXXX","rssi":-67}
2018.06.23 11:54:59 5: NUKIDevice (NUKIDevice3025XXXX) - parse status message for NUKIDevice3025XXXX
2018.06.23 11:54:59 5: NUKIDevice (NUKIDevice3025XXXX) - readings set for NUKIDevice3025XXXX
2018.06.23 11:55:39 5: NUKIDevice (NUKIDevice3025XXXX) - Parse with result: {"name":"Nuki_1208XXXX","rssi":-64,"paired":true}
2018.06.23 11:55:39 5: NUKIDevice (NUKIDevice3025XXXX) - parse status message for NUKIDevice3025XXXX
2018.06.23 11:55:39 5: NUKIDevice (NUKIDevice3025XXXX) - readings set for NUKIDevice3025XXXX
2018.06.23 11:56:04 3: NUKIBridge (NUKI_Bridge) - invalid json detected: HTTP 503 Unavailable
2018.06.23 11:56:30 5: NUKIDevice (NUKIDevice3025XXXX) - Parse with result: {"paired":true,"name":"Nuki_1208XXXX","rssi":-68}
2018.06.23 11:56:30 5: NUKIDevice (NUKIDevice3025XXXX) - parse status message for NUKIDevice3025XXXX
2018.06.23 11:56:30 5: NUKIDevice (NUKIDevice3025XXXX) - readings set for NUKIDevice3025XXXX
2018.06.23 11:56:58 5: NUKIDevice (NUKIDevice3025XXXX) - Parse with result: {"paired":true,"rssi":-64,"name":"Nuki_1208XXXX"}
2018.06.23 11:56:58 5: NUKIDevice (NUKIDevice3025XXXX) - parse status message for NUKIDevice3025XXXX
2018.06.23 11:56:58 5: NUKIDevice (NUKIDevice3025XXXX) - readings set for NUKIDevice3025XXXX
2018.06.23 11:57:16 5: NUKIDevice (NUKIDevice3025XXXX) - Parse with result: {"name":"Nuki_1208XXXX","rssi":-64,"paired":true}
2018.06.23 11:57:16 5: NUKIDevice (NUKIDevice3025XXXX) - parse status message for NUKIDevice3025XXXX
2018.06.23 11:57:16 5: NUKIDevice (NUKIDevice3025XXXX) - readings set for NUKIDevice3025XXXX
2018.06.23 11:57:37 4: NUKIDevice (NUKIDevice3025XXXX) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2018.06.23 11:57:37 4: NUKIDevice (NUKIDevice3025XXXX) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2018.06.23 11:57:37 5: NUKIDevice (NUKIDevice3025XXXX) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2018.06.23 11:57:39 5: NUKIDevice (NUKIDevice3025XXXX) - Parse with result: {"state": 3, "stateName": "unlocked", "batteryCritical": false, "success": true}
2018.06.23 11:57:39 5: NUKIDevice (NUKIDevice3025XXXX) - parse status message for NUKIDevice3025XXXX
2018.06.23 11:57:39 5: NUKIDevice (NUKIDevice3025XXXX) - readings set for NUKIDevice3025XXXX
2018.06.23 11:57:39 5: NUKIDevice (NUKIDevice3025XXXX) - Parse with result: {"name":"Nuki_1208XXXX","rssi":-68,"paired":true}
2018.06.23 11:57:39 5: NUKIDevice (NUKIDevice3025XXXX) - parse status message for NUKIDevice3025XXXX
2018.06.23 11:57:39 5: NUKIDevice (NUKIDevice3025XXXX) - readings set for NUKIDevice3025XXXX
timestamp: 2018-06-23T11:22:00+00:00 type: HTTP-Log
timestamp: 2018-06-23T11:22:00+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-06-23T11:21:54+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-06-23T11:21:52+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-06-23T11:21:52+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:52+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:52+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:21:52+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 188
timestamp: 2018-06-23T11:21:52+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00000103
timestamp: 2018-06-23T11:21:52+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 256
timestamp: 2018-06-23T11:21:52+00:00 type: BLE-ReceivingSSE bytes: 106 auth: 00000103
timestamp: 2018-06-23T11:21:51+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-06-23T11:21:49+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-06-23T11:21:49+00:00 type: BLE-SendingSSE bytes: 96 auth: 00000103
timestamp: 2018-06-23T11:21:49+00:00 type: BLE-Connect handles: ARRAY(0x701ab20)
timestamp: 2018-06-23T11:21:49+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:49+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:21:49+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:49+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 96
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:21:48+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 228
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00000103
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-SendingSSE bytes: 56 auth: 00000103
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-Connect handles: ARRAY(0x6ffceb8)
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:21:48+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:48+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 56
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:21:47+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 208
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-ReceivingSSE bytes: 72 auth: 00000103
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-SendingSSE bytes: 56 auth: 00000103
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-Connect handles: ARRAY(0x701afd0)
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:47+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 56
timestamp: 2018-06-23T11:21:47+00:00 type: SSE-KeyturnerEventResp nukiId: 12088ED1
timestamp: 2018-06-23T11:21:47+00:00 type: HTTP-PostStart
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:47+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:46+00:00 type: SSE-KeyturnerEventReq nukiId: 12088ED1
timestamp: 2018-06-23T11:21:46+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000C
timestamp: 2018-06-23T11:21:46+00:00 type: BLE-SendingMsg nukiId: 12088ED1 cmdId: 0001
timestamp: 2018-06-23T11:21:46+00:00 type: BLE-Connect handles: ARRAY(0x7022370)
timestamp: 2018-06-23T11:21:46+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:45+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:21:45+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:45+00:00 type: BLE-StatusUpdate nukiId: 12088ED1
timestamp: 2018-06-23T11:21:45+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:45+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:45+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:21:45+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 189
timestamp: 2018-06-23T11:21:45+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00000101
timestamp: 2018-06-23T11:21:45+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 209
timestamp: 2018-06-23T11:21:45+00:00 type: BLE-ReceivingSSE bytes: 72 auth: 00000101
timestamp: 2018-06-23T11:21:40+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 209
timestamp: 2018-06-23T11:21:40+00:00 type: BLE-ReceivingSSE bytes: 72 auth: 00000101
timestamp: 2018-06-23T11:21:40+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 189
timestamp: 2018-06-23T11:21:40+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00000101
timestamp: 2018-06-23T11:21:40+00:00 type: BLE-SendingSSE bytes: 92 auth: 00000101
timestamp: 2018-06-23T11:21:40+00:00 type: BLE-Connect handles: ARRAY(0x704b5d8)
timestamp: 2018-06-23T11:21:40+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:40+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:21:40+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:40+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 92
timestamp: 2018-06-23T11:21:40+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-06-23T11:21:39+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:39+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:39+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:21:39+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 229
timestamp: 2018-06-23T11:21:39+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00000101
timestamp: 2018-06-23T11:21:39+00:00 type: BLE-SendingSSE bytes: 56 auth: 00000101
timestamp: 2018-06-23T11:21:39+00:00 type: BLE-Connect handles: ARRAY(0x701c310)
timestamp: 2018-06-23T11:21:39+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:38+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:21:38+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:37+00:00 type: BLE-Retry nukiId: 12088ED1 count: 1
timestamp: 2018-06-23T11:21:37+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:37+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:37+00:00 type: BLE-SendingSSE bytes: 56 auth: 00000101
timestamp: 2018-06-23T11:21:37+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:21:37+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-06-23T11:21:37+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 188
timestamp: 2018-06-23T11:21:37+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00000103
timestamp: 2018-06-23T11:21:37+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-06-23T11:21:36+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 56
timestamp: 2018-06-23T11:21:35+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-06-23T11:21:35+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 256
timestamp: 2018-06-23T11:21:35+00:00 type: BLE-ReceivingSSE bytes: 106 auth: 00000103
timestamp: 2018-06-23T11:21:34+00:00 type: BLE-SendingSSE bytes: 96 auth: 00000103
timestamp: 2018-06-23T11:21:34+00:00 type: BLE-Connect handles: ARRAY(0x6dcd678)
timestamp: 2018-06-23T11:21:34+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:21:34+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:21:34+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:21:34+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 96
timestamp: 2018-06-23T11:25:31+00:00 type: HTTP-Log
timestamp: 2018-06-23T11:25:31+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-06-23T11:25:24+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-06-23T11:25:23+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:23+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:23+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:25:23+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-06-23T11:25:23+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 188
timestamp: 2018-06-23T11:25:23+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00000103
timestamp: 2018-06-23T11:25:23+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-06-23T11:25:22+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-06-23T11:25:20+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 256
timestamp: 2018-06-23T11:25:20+00:00 type: BLE-ReceivingSSE bytes: 106 auth: 00000103
timestamp: 2018-06-23T11:25:20+00:00 type: BLE-SendingSSE bytes: 96 auth: 00000103
timestamp: 2018-06-23T11:25:20+00:00 type: BLE-Connect handles: ARRAY(0x6ffdee8)
timestamp: 2018-06-23T11:25:20+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:20+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:25:20+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:20+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 96
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:25:19+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 228
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00000103
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-SendingSSE bytes: 56 auth: 00000103
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-Connect handles: ARRAY(0x701c790)
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:25:19+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:19+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 56
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:25:18+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 208
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-ReceivingSSE bytes: 72 auth: 00000103
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-SendingSSE bytes: 56 auth: 00000103
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-Connect handles: ARRAY(0x701c2e0)
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:25:18+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:18+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 56
timestamp: 2018-06-23T11:25:18+00:00 type: SSE-KeyturnerEventResp nukiId: 12088ED1
timestamp: 2018-06-23T11:25:17+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-06-23T11:25:13+00:00 type: HTTP-PostStart
timestamp: 2018-06-23T11:25:13+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:13+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:13+00:00 type: SSE-KeyturnerEventReq nukiId: 12088ED1
timestamp: 2018-06-23T11:25:13+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000C
timestamp: 2018-06-23T11:25:12+00:00 type: BLE-SendingMsg nukiId: 12088ED1 cmdId: 0001
timestamp: 2018-06-23T11:25:12+00:00 type: BLE-Connect handles: ARRAY(0x6ebdf68)
timestamp: 2018-06-23T11:25:12+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:12+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:25:12+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:12+00:00 type: BLE-StatusUpdate nukiId: 12088ED1
timestamp: 2018-06-23T11:25:12+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:25:06+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:25:05+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:25:04+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000C
timestamp: 2018-06-23T11:25:01+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000C
timestamp: 2018-06-23T11:24:57+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000C
timestamp: 2018-06-23T11:24:56+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:24:56+00:00 type: BLE-SendingMsg nukiId: 12088ED1 cmdId: 000D
timestamp: 2018-06-23T11:24:56+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 0004
timestamp: 2018-06-23T11:24:55+00:00 type: BLE-SendingMsg nukiId: 12088ED1 cmdId: 0001
timestamp: 2018-06-23T11:24:55+00:00 type: BLE-Connect handles: ARRAY(0x706cde8)
timestamp: 2018-06-23T11:24:55+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:24:55+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:24:55+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:24:55+00:00 type: HTTP-LockAction nukiId: 12088ED1
timestamp: 2018-06-23T11:24:55+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-06-23T11:24:44+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-06-23T11:24:44+00:00 type: HTTP-Info
timestamp: 2018-06-23T11:24:44+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-06-23T11:24:37+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:24:36+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 188
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00000103
timestamp: 2018-06-23T11:24:36+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 256
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-ReceivingSSE bytes: 106 auth: 00000103
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-SendingSSE bytes: 96 auth: 00000103
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-Connect handles: ARRAY(0x7076fb8)
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:24:36+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:24:36+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 96
timestamp: 2018-06-23T11:24:35+00:00 type: BLE-Disconnected nukiId: 12088ED1
timestamp: 2018-06-23T11:24:35+00:00 type: BLE-Disconnect nukiId: 12088ED1
timestamp: 2018-06-23T11:24:35+00:00 type: BLE-ReceivingMsg nukiId: 12088ED1 cmdId: 000E
timestamp: 2018-06-23T11:24:35+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-06-23T11:24:32+00:00 type: SSE-KeyturnerResponse nukiId: 12088ED1 bytes: 228
timestamp: 2018-06-23T11:24:32+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00000103
timestamp: 2018-06-23T11:24:32+00:00 type: BLE-SendingSSE bytes: 56 auth: 00000103
timestamp: 2018-06-23T11:24:32+00:00 type: BLE-Connect handles: ARRAY(0x7077438)
timestamp: 2018-06-23T11:24:32+00:00 type: BLE-Connected nukiId: 12088ED1
timestamp: 2018-06-23T11:24:32+00:00 type: BLE-Connect macAddr: 54D272088ED1
timestamp: 2018-06-23T11:24:32+00:00 type: BLE-Connect nukiId: 12088ED1
timestamp: 2018-06-23T11:24:32+00:00 type: SSE-KeyturnerRequest nukiId: 12088ED1 bytes: 56
timestamp: 2018-06-23T11:24:31+00:00 type: BLE-Disconnected nukiId: 12088ED1
2018.06.23 13:27:35 3: NUKIBridge (NUKI_Bridge) - invalid json detected: HTTP 503 Unavailable
2018.06.23 13:28:45 3: NUKIBridge (NUKI_Bridge) - invalid json detected: HTTP 503 Unavailable
bridgeType Hardware 2018-07-25 22:36:15
currentTime 2018-07-25T20:36:14+00:00 2018-07-25 22:36:15
firmwareVersion 1.10.1 2018-07-25 22:36:15
hardwareId 114621249 2018-07-25 22:36:15
lastError http://192.168.0.19:8080/info?token=XXX: empty answer received 2018-07-25 22:21:50
serverConnected 1 2018-07-25 22:36:15
serverId XXXX 2018-07-25 22:36:15
state connected 2018-07-25 22:36:14
uptime 7457 2018-07-25 22:36:15
wifiFirmwareVersion 1.1.0 2018-07-25 22:36:15
Zitat von: RitterSport am 25 Juli 2018, 22:40:02
Hallo,
ich habe schon einiges gesucht aber nicht das richtige gefunden.
Nuki lief bei mir mind. ein Jahr lang problemlos.
Seit ein paar Wochen habe ich das Problem das der Staus des NukiDevice in Fhem nach einer gewissen Zeit nicht aktualisiert wird.
Habe das Device auch neu angelegt, dann läuft es einige Zeit.
Irgendwann stimmt der Status nicht mehr, und das Nicht-Ändern passt mit dem Eintrag Webhook last zusammen. Manchmal funktioniert es dann von alleine wieder.
In der Zwischenzeit bekomme ich in der Bridge manchmal den Fehler : empty answer receivedCode Auswählen
bridgeType Hardware 2018-07-25 22:36:15
currentTime 2018-07-25T20:36:14+00:00 2018-07-25 22:36:15
firmwareVersion 1.10.1 2018-07-25 22:36:15
hardwareId 114621249 2018-07-25 22:36:15
lastError http://192.168.0.19:8080/info?token=XXX: empty answer received 2018-07-25 22:21:50
serverConnected 1 2018-07-25 22:36:15
serverId XXXX 2018-07-25 22:36:15
state connected 2018-07-25 22:36:14
uptime 7457 2018-07-25 22:36:15
wifiFirmwareVersion 1.1.0 2018-07-25 22:36:15
Laut App habe ich zu den Zeiten jeweils eine Verbindung über den Server zur Bridge
Eine Idee wo ich ansetzen kann?
Zitat von: RitterSport am 31 Juli 2018, 10:37:25
Leider noch kein Log aus der Bridge vorhanden, weil ich irgendwann mal Verbose 0 gesetzt hatte.
Sobald ich ein Log habe, poste ich ihn.
Bei dem Bild unten erkennt man, das ab dem Vorabend die Aktualisierung per Webhook nicht erfolgte.
timestamp: 2018-07-31T11:21:22+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:21:21+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:21:21+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:21:04+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:21:04+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:21:04+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:20:38+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:20:38+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:20:38+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:20:09+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:20:09+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:20:09+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:19:50+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:19:50+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:19:50+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:19:21+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:19:21+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:19:21+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:19:07+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:19:06+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:19:06+00:00 type: WLAN-SocketConnected connection: 0
Zitat von: RitterSport am 31 Juli 2018, 13:31:09
Da muss ich dumm fragen:
Du meinst den Log den ich auslesen kann über fhem?
Siehe Beispiel unten?Code Auswählentimestamp: 2018-07-31T11:21:22+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:21:21+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:21:21+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:21:04+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:21:04+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:21:04+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:20:38+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:20:38+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:20:38+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:20:09+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:20:09+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:20:09+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:19:50+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:19:50+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:19:50+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:19:21+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:19:21+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:19:21+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T11:19:07+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T11:19:06+00:00 type: HTTP-Info
timestamp: 2018-07-31T11:19:06+00:00 type: WLAN-SocketConnected connection: 0
In dem Log sind nur die letzten 20 Minuten und dann auch noch jeweils -2 Std.
Zitat von: RitterSport am 31 Juli 2018, 15:00:58
Danke schonmal. Sobald es wieder Auftritt werde ich den passenden Log posten.
Ich habe 2 WebInstanzen, 8083 zum "Arbeiten" und 8086 "Wandtablett" als Anzeige.
Kann er damit durcheinander kommen?
timestamp: 2018-07-31T19:36:27+00:00 type: HTTP-Log
timestamp: 2018-07-31T19:36:27+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:36:19+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:36:19+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:36:19+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:36:17+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:36:17+00:00 type: BLE-ConnectTimeout nukiId: XXXXXXX
timestamp: 2018-07-31T19:36:11+00:00 type: BLE-Connect macAddr: XXXXXXX
timestamp: 2018-07-31T19:36:11+00:00 type: BLE-Connect nukiId: XXXXXXX
timestamp: 2018-07-31T19:36:11+00:00 type: HTTP-LockState nukiId: XXXXXXX
timestamp: 2018-07-31T19:36:11+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:36:10+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:36:10+00:00 type: BLE-ConnectTimeout nukiId: XXXXXXX
timestamp: 2018-07-31T19:36:04+00:00 type: BLE-Connect macAddr: XXXXXXX
timestamp: 2018-07-31T19:36:04+00:00 type: BLE-Connect nukiId: XXXXXXX
timestamp: 2018-07-31T19:36:04+00:00 type: HTTP-LockAction nukiId: XXXXXXX
timestamp: 2018-07-31T19:36:04+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:35:58+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:35:58+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:35:58+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:35:41+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:35:41+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:35:41+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:35:24+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:35:24+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:35:23+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:35:02+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:35:01+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:35:01+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:34:32+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:34:32+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:34:32+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:34:05+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:34:05+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:34:05+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:33:46+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:33:46+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:33:46+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:33:21+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:33:21+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:33:21+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:33:00+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:33:00+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:33:00+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:32:45+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:32:45+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:32:45+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:32:18+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:32:18+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:32:18+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:32:12+00:00 type: BLE-Disconnected nukiId: XXXXXXX
timestamp: 2018-07-31T19:32:06+00:00 type: BLE-Disconnect nukiId: XXXXXXX
timestamp: 2018-07-31T19:32:06+00:00 type: BLE-CheckTime nukiId: XXXXXXX
timestamp: 2018-07-31T19:32:06+00:00 type: BLE-ReceivingMsg nukiId: XXXXXXX cmdId: 0015
timestamp: 2018-07-31T19:32:05+00:00 type: BLE-SendingMsg nukiId: XXXXXXX cmdId: 0014
timestamp: 2018-07-31T19:32:05+00:00 type: BLE-ReceivingMsg nukiId: XXXXXXX cmdId: 0004
timestamp: 2018-07-31T19:32:04+00:00 type: BLE-SendingMsg nukiId: XXXXXXX cmdId: 0001
timestamp: 2018-07-31T19:32:04+00:00 type: BLE-Connect handles: ARRAY(0x7447738)
timestamp: 2018-07-31T19:32:04+00:00 type: BLE-Connected nukiId: XXXXXXX
timestamp: 2018-07-31T19:32:04+00:00 type: FirmUpdateCheck fwType: wlan
timestamp: 2018-07-31T19:32:04+00:00 type: BLE-Connect macAddr: XXXXXXX
timestamp: 2018-07-31T19:32:04+00:00 type: BLE-Connect nukiId: XXXXXXX
timestamp: 2018-07-31T19:32:04+00:00 type: FirmUpdateCheck fwType: main
timestamp: 2018-07-31T19:32:04+00:00 type: SSE-PushNukisResponse error: 0
timestamp: 2018-07-31T19:32:04+00:00 type: SSE-PushNukisRequest count: 1
timestamp: 2018-07-31T19:32:01+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:32:01+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:32:01+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:31:45+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:31:45+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:31:45+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:31:22+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:31:22+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:31:22+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:30:55+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:30:55+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:30:55+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:30:26+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:30:26+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:30:26+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:30:12+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:30:11+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:30:09+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:29:40+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:29:40+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:29:40+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:29:25+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:29:25+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:29:25+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:28:59+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:28:59+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:28:59+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:28:34+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:28:34+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:28:34+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:28:12+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:28:12+00:00 type: HTTP-Info
timestamp: 2018-07-31T19:28:12+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-07-31T19:27:53+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-07-31T19:27:53+00:00 type: HTTP-Info
Zitat von: Xguide am 29 September 2018, 12:03:49
Hallo zusammen,
danke für das tolle Modul.
Könnte jemand mal das Wiki/Commandref zur Einrichtung um einen Verweis zur Einrichtung des Webhooks erweitern?
Eigentlich eine einfache und verständliche Sache, habe aber etwas länger im Dunkeln getappt, warum ich den Status nicht aktualisiert bekomme.
Danke und viele Grüße,
Marcel
attr Haustuer webhookFWinstance WEB (Name der FHEMWEB Instanz)
attr Haustuer webhookHttpHostname 192.168.0.1 (IP/FQDN vom FHEM Server)
0 http://192.168.0.1:8083/fhem/NUKIDevice-123456789
attr Haustuer webhookFWinstance WEB (Name of the FHEMWEB instance)
attr Haustuer webhookHttpHostname 192.168.0.1 (IP/FQDN of the FHEM server)
0 http://192.168.0.1:8083/fhem/NUKIDevice-123456789
Zitat von: CoolTux am 29 September 2018, 12:11:43
Schick mir doch gerne Deine Vorstellung, dann baue ich sie in die Commandref und im Wiki ein.
Danke Dir
Grüße
ZitatDu bist stolzer Besitzer der ersten Generation und möchtest von den neuen Features profitieren?
Dann solltest du dir unser Austausch-Programm genauer anschauen. Mit diesem Programm tauscht du deine alte Version des Nuki Smart Locks gegen die neue Version und profitierst von einer gesteigerten Geschwindigkeit, HomeKit-Unterstützung, ZigBee und dem nagelneuen Türsensor. Weitere Details folgen zum Verkaufsstart im November.
Zitat von: markukug am 16 Oktober 2018, 14:07:33
Ein paypal € 10er von mir ist Dir sicher.
Zitat von: CoolTux am 16 Oktober 2018, 14:22:02
Ist jetzt nur das Smartlock neu oder auch die Bridge? Weiß as einer.
Zitat von: Cobra am 16 Oktober 2018, 14:12:04
Da bin ich natürlich auch wieder dabei ;-)
Zitat von: CoolTux am 16 Oktober 2018, 14:22:02
Ist jetzt nur das Smartlock neu oder auch die Bridge? Weiß as einer.
Zitat von: Cobra am 06 November 2018, 13:22:28
Du rechnest da etwas falsch.
Du brauchst ja nur das Schloss und das kostet 229€. Wenn du das alte Schloss zurück gibst bekommst du 100€ Gutschrift. Also kostet es dich nur 129€ ;-)
Die Bridge brauchst du ja nicht zurückschicken, die ist identisch und kann weiter verwendet werden.
Zitat von: Cobra am 06 November 2018, 13:53:22
Das hat mich auch verwundert, daher habe ich bei Nuki angerufen.
Die Dame meinte das würde nur Sinn machen wenn zB. die alte Bridge defekt ist.
Stand heute ist es die gleiche Bridge die du/ich jetzt auch haben.
ZitatCobra 40 Euro
markukug 40 Euro
fred_feuerstein 25 EUR
Zitat von: fred_feuerstein am 06 November 2018, 13:58:48
Also 105 EUR. ;)
Musst demnach nicht mehr viel drauflegen :)
Zitat von: Starbug am 06 November 2018, 14:01:14
Wenn das neue Nuki 2.0 nun Bluetooth 5.0 spricht, dann wäre es aber sinnvoll, wenn die Bridge dies auch könnte.
ZitatFrage:
- If i buy Nuki 2.0, do I still need the bridge or is a HomePod enough to open/lock doors via Internet?
- How is the distance of the new BT 5 with nuki 2.0? I have a door sensor from Koogeek next to my nuki and it works flawlessly with my homepod. Does this mean it will work flawlessly with nuki 2.0 in terms of distance?
- How is the speed compared between Nuki2.0 + Homekit and Nuki 1.0 + Bridge? Any compare values?
Antwort:
This aren't real developer questions and they will be covered in the faq too, so i'm keeping the answers short:
- HomePod (or IPad, AppleTV) will do the job.
- Apple devices don't support BT5 long range mode yet. BLE reach will still be ~30% better than with SL 1.0. Should work when the door sensor works too.
- HomeKit is fast, very fast. Mechanics didn't change. So no speed gain in the actual lock process though.
Callback-ID Callback-URL
0 http://192.168.178.5:8085/fhem/NUKIDevice-347794437
Internals:
CFGFN
DEF 347794437 IODev=NukiBridge
IODev NukiBridge
NAME NUKIDevice347794437
NR 6348
NUKIID 347794437
STATE lock
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 12:02:17 battery ok
2018-11-13 12:02:17 batteryCritical 0
2018-11-13 12:02:17 batteryState ok
2018-11-13 12:33:52 lockState lock
2018-11-13 12:34:49 name Nuki_14BAEC05
2018-11-13 12:34:49 paired 1
2018-11-13 12:34:49 rssi -74
2018-11-13 12:33:52 state lock
2018-11-13 12:33:52 success 1
helper:
fromAutocreate 1
Attributes:
IODev NukiBridge
alias CobraDoor
devStateIcon unlocked:secur_open@green locked:secur_locked@red
icon 1_nuki
room NUKI
webCmd lock:unlock:unlatch
webhookFWinstance WEBtablet
webhookHttpHostname 192.168.178.5
NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.13 13:11:07 5: NUKIDevice (NUKIDevice347794437) - readings set for NUKIDevice347794437
2018.11.13 13:11:07 5: NUKIDevice (NUKIDevice347794437) - parse status message for NUKIDevice347794437
2018.11.13 13:11:07 5: NUKIDevice (NUKIDevice347794437) - Parse with result: {"rssi":-75,"paired":true,"name":"Nuki_14BAEC05"}
2018.11.13 13:10:47 5: NUKIDevice (NUKIDevice347794437) - lockAction readings set for NUKIDevice347794437
2018.11.13 13:10:47 5: NUKIDevice (NUKIDevice347794437) - parse status message for NUKIDevice347794437
2018.11.13 13:10:47 5: NUKIDevice (NUKIDevice347794437) - Parse with result: {"success": true, "batteryCritical": false}
2018.11.13 13:10:43 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.13 13:10:38 4: NUKIDevice (NUKIDevice347794437) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2018.11.13 13:10:38 4: NUKIDevice (NUKIDevice347794437) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
timestamp: 2018-11-13T12:45:58+00:00 type: HTTP-Log
timestamp: 2018-11-13T12:45:58+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:45:37+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:45:37+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:45:37+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:45:31+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:45:31+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-13T12:45:31+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-13T12:45:30+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-13T12:45:30+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000C
timestamp: 2018-11-13T12:45:24+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000C
timestamp: 2018-11-13T12:45:23+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-13T12:45:23+00:00 type: BLE-SendingMsg nukiId: 14BAEC05 cmdId: 000D
timestamp: 2018-11-13T12:45:23+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 0004
timestamp: 2018-11-13T12:45:23+00:00 type: BLE-SendingMsg nukiId: 14BAEC05 cmdId: 0001
timestamp: 2018-11-13T12:45:23+00:00 type: BLE-Connect handles: ARRAY(0x7209360)
timestamp: 2018-11-13T12:45:23+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-13T12:45:22+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-13T12:45:22+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-13T12:45:22+00:00 type: HTTP-LockAction nukiId: 14BAEC05
timestamp: 2018-11-13T12:45:22+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:45:14+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:45:13+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:45:13+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:44:55+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:44:54+00:00 type: HTTP-Log
timestamp: 2018-11-13T12:44:54+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:44:43+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:44:43+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:44:43+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:44:34+00:00 type: SSE-PushNukisResponse error: 0
timestamp: 2018-11-13T12:44:34+00:00 type: SSE-PushNukisRequest count: 1
timestamp: 2018-11-13T12:44:34+00:00 type: SSE-Connected serverNum: 9 serverCert: 1
timestamp: 2018-11-13T12:44:34+00:00 type: SSE-Connect serverNum: 9 serverCert: 1
timestamp: 2018-11-13T12:44:24+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:44:23+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:44:21+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:44:18+00:00 type: SSE-Disconnected serverNum: 8 pingTo: 8
timestamp: 2018-11-13T12:43:59+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:43:59+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:43:58+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:43:58+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:43:55+00:00 type: HTTP-Log
timestamp: 2018-11-13T12:43:55+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:43:39+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:43:37+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:43:37+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:43:17+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:43:17+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:43:17+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:43:02+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:42:59+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:42:59+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:42:58+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:42:54+00:00 type: HTTP-Log
timestamp: 2018-11-13T12:42:54+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:42:46+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:42:41+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:42:40+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:42:38+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:42:32+00:00 type: HTTP-Log
timestamp: 2018-11-13T12:42:32+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:42:22+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:42:19+00:00 type: HTTP-Log
timestamp: 2018-11-13T12:42:19+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:42:02+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:42:02+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:42:02+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:41:37+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:41:37+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:41:37+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:41:14+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-13T12:41:14+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-13T12:41:11+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-13T12:41:11+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-13T12:41:11+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDD
timestamp: 2018-11-13T12:41:10+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDD
timestamp: 2018-11-13T12:41:10+00:00 type: BLE-Connect handles: ARRAY(0x6faff78)
timestamp: 2018-11-13T12:41:10+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:41:10+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-13T12:41:10+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:41:10+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:41:10+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-13T12:41:10+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-13T12:41:10+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-13T12:40:54+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:40:52+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:40:52+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:40:33+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:40:33+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:40:33+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:40:14+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:40:14+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:40:14+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:39:44+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:39:44+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:39:44+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-13T12:39:26+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-13T12:39:24+00:00 type: HTTP-Info
timestamp: 2018-11-13T12:39:22+00:00 type: WLAN-SocketConnected connection: 0
Zitathttps://developer.nuki.io/t/no-webhook-state-after-lockaction-nuki-2-0/482
Happens to me as well. No Callback (after an lockAction-Call) for the new LOCKED-State. I looked in the Bridge-Log and there is no HTTP-POST-Entry for the Callback :frowning:
For an Unlock-Action-Call I get an Callback with the new UNLOCKED-State. There is an HTTP-POST-Entry in the Bridge-Logs.
Grüße.
niklas
Zitat
Hi!
Wir konnten die Callback-Probleme jetzt teilweise reproduzieren.
Werden uns das noch näher anschauen und uns dann "offiziell" zurückmelden.
lg,
Stephan
Zitat von: Steffen am 14 November 2018, 05:47:09
Hallo!
Seit heute scheint mein ca.5Jahre altes KeyMatic durch zu sein und auf der suche nach ein neues bin ich nun auf Nuki gestoßen.
Ich wollte vielleicht hier mal fragen ob jemand von euch den vergleich durch persönliche erfahrungen machen kann zwischen Nuki und KeyMatic?
Wenn ich mir dann auch das neue Nuki holen sollte, ob dann es vielleicht auch mit "zigbee2mqtt" gehen würde um mir die Bridge zu Sparen?!
Mfg Steffen
timestamp: 2018-11-14T08:22:32+00:00 type: HTTP-Log
timestamp: 2018-11-14T08:22:32+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:22:09+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T08:22:08+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T08:22:05+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:22:05+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:22:04+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:22:04+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:21:55+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:21:55+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:21:54+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:52+00:00 type: WLAN-SocketConnected connection: 3
timestamp: 2018-11-14T08:21:51+00:00 type: HTTP-PostStart
timestamp: 2018-11-14T08:21:51+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:51+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:50+00:00 type: SSE-KeyturnerEventReq nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:50+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000C
timestamp: 2018-11-14T08:21:50+00:00 type: BLE-SendingMsg nukiId: 14BAEC05 cmdId: 0001
timestamp: 2018-11-14T08:21:50+00:00 type: BLE-Connect handles: ARRAY(0x6393b60)
timestamp: 2018-11-14T08:21:50+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:49+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T08:21:49+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:49+00:00 type: BLE-Retry nukiId: 14BAEC05 count: 1
timestamp: 2018-11-14T08:21:49+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:49+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:48+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T08:21:48+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:48+00:00 type: BLE-StatusUpdate nukiId: 14BAEC05
timestamp: 2018-11-14T08:21:39+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:21:39+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:21:39+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:21:14+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:21:14+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:21:14+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:20:47+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:20:46+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:20:46+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:20:25+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:20:25+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:20:25+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:20:04+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:20:04+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:20:04+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:19:42+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:19:42+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:19:42+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:19:23+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:19:16+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:19:16+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:18:53+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:18:53+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:18:53+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:18:38+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:18:38+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:18:38+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:18:11+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:18:11+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:18:11+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:17:53+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:17:53+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:17:53+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:17:38+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:17:38+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:17:36+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:17:16+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:17:16+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:17:16+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:16:53+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:16:51+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:16:51+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:16:30+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:16:30+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:16:30+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:16:04+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:16:04+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:16:03+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:15:45+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:15:45+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:15:45+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:15:25+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:15:25+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:15:25+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:15:05+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:15:05+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:15:05+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:14:36+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:14:36+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:14:36+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:14:08+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:14:08+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:14:08+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:13:50+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:13:50+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:13:50+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:13:27+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:13:27+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:13:27+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T08:13:02+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T08:13:01+00:00 type: HTTP-Info
timestamp: 2018-11-14T08:13:01+00:00 type: WLAN-SocketConnected connection: 0
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
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
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.
timestamp: 2018-11-14T09:44:08+00:00 type: HTTP-PostFailed urlId: 0
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.
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": []}
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
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
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.
Callback-ID Callback-URL
0 http://192.168.178.5:8085/fhem/NUKIDevice-347794437
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
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
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 13:46:28 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_CGI redefined at ./FHEM/74_NUKIDevice.pm line 502.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_WriteReadings redefined at ./FHEM/74_NUKIDevice.pm line 433.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Parse redefined at ./FHEM/74_NUKIDevice.pm line 373.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_ReadFromNUKIBridge redefined at ./FHEM/74_NUKIDevice.pm line 337.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_GetUpdate redefined at ./FHEM/74_NUKIDevice.pm line 324.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Set redefined at ./FHEM/74_NUKIDevice.pm line 279.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_removeExtension redefined at ./FHEM/74_NUKIDevice.pm line 268.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_addExtension redefined at ./FHEM/74_NUKIDevice.pm line 251.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Attr redefined at ./FHEM/74_NUKIDevice.pm line 181.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Undef redefined at ./FHEM/74_NUKIDevice.pm line 159.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Define redefined at ./FHEM/74_NUKIDevice.pm line 84.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Initialize redefined at ./FHEM/74_NUKIDevice.pm line 59.
018.11.14 13:52:04 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 13:52:04 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 13:52:04 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 13:52:04 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 10546, "currentTime": "2018-11-14T12:52:03+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 13:52:04 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 13:52:04 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 13:52:04 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 13:52:04 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 13:51:40 5: NUKIDevice (NUKIDevice347794437) - readings set for NUKIDevice347794437
2018.11.14 13:51:40 5: NUKIDevice (NUKIDevice347794437) - parse status message for NUKIDevice347794437
2018.11.14 13:51:40 5: NUKIDevice (NUKIDevice347794437) - Parse with result: {"rssi":-75,"paired":true,"name":"Nuki_14BAEC05"}
2018.11.14 13:51:40 4: NUKIDevice (NUKIDevice347794437) - Received scanResults for matching NukiID 347794437 at device NUKIDevice347794437
2018.11.14 13:51:40 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 13:51:40 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 13:51:40 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 13:51:40 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 10522, "currentTime": "2018-11-14T12:51:39+00:00", "serverConnected": true, "scanResults": [{"nukiId": 347794437, "name": "Nuki_14BAEC05", "rssi": -75, "paired": true}]}
2018.11.14 13:51:40 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 13:51:40 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 13:51:40 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 13:51:40 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 13:51:34 4: Connection closed for WEBtablet_192.168.178.23_28609: EOF
2018.11.14 13:51:21 4: WEBtablet: /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 3, "stateName": "unlocked", "batteryCritical": false} / RL:8041 / text/html; charset=UTF-8 / /
2018.11.14 13:51:21 4: WEBtablet_192.168.178.23_28609 POST /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 3, "stateName": "unlocked", "batteryCritical": false}; BUFLEN:0
2018.11.14 13:51:19 4: Connection accepted from WEBtablet_192.168.178.23_28609
2018.11.14 13:51:15 5: NUKIDevice (NUKIDevice347794437) - readings set for NUKIDevice347794437
2018.11.14 13:51:15 5: NUKIDevice (NUKIDevice347794437) - parse status message for NUKIDevice347794437
2018.11.14 13:51:15 5: NUKIDevice (NUKIDevice347794437) - Parse with result: {"paired":true,"rssi":-76,"name":"Nuki_14BAEC05"}
2018.11.14 13:51:15 4: NUKIDevice (NUKIDevice347794437) - Received scanResults for matching NukiID 347794437 at device NUKIDevice347794437
2018.11.14 13:51:15 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 13:51:15 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 13:51:15 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 13:51:15 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 10497, "currentTime": "2018-11-14T12:51:14+00:00", "serverConnected": true, "scanResults": [{"nukiId": 347794437, "name": "Nuki_14BAEC05", "rssi": -76, "paired": true}]}
2018.11.14 13:51:15 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 13:51:15 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 13:51:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 13:51:15 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 13:50:48 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 13:50:48 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 13:50:48 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 13:50:48 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 10470, "currentTime": "2018-11-14T12:50:47+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 13:50:48 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 13:50:48 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 13:50:48 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 13:50:48 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 13:50:30 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.14 13:46:28 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_CGI redefined at ./FHEM/74_NUKIDevice.pm line 502.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_WriteReadings redefined at ./FHEM/74_NUKIDevice.pm line 433.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Parse redefined at ./FHEM/74_NUKIDevice.pm line 373.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_ReadFromNUKIBridge redefined at ./FHEM/74_NUKIDevice.pm line 337.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_GetUpdate redefined at ./FHEM/74_NUKIDevice.pm line 324.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Set redefined at ./FHEM/74_NUKIDevice.pm line 279.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_removeExtension redefined at ./FHEM/74_NUKIDevice.pm line 268.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_addExtension redefined at ./FHEM/74_NUKIDevice.pm line 251.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Attr redefined at ./FHEM/74_NUKIDevice.pm line 181.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Undef redefined at ./FHEM/74_NUKIDevice.pm line 159.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Define redefined at ./FHEM/74_NUKIDevice.pm line 84.
2018.11.14 13:45:18 1: PERL WARNING: Subroutine NUKIDevice_Initialize redefined at ./FHEM/74_NUKIDevice.pm line 59.
Zitat von: CoolTux am 14 November 2018, 14:09:39
Da ist rein gar nichts vom webhook zu sehen, obwohl die entsprechende FHEMWEB Instanz aufgerufen wurde.
Zitat von: Cobra am 14 November 2018, 14:15:38Kannst Du gerne machen, aber ich sehe da nicht das die Funktion im Modul aufgerufen wird, obwohl der webhook ja angesprochen wird und die URL aufgerufen.
Soll ich nochmal nen weiteren LOG-Auszug schicken?
2018.11.14 15:12:35 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 15:12:35 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 15:12:35 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 15:12:35 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 15377, "currentTime": "2018-11-14T14:12:34+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 15:12:35 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 15:12:35 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 15:12:35 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 15:12:35 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 15:12:25 4: Connection closed for WEBtablet_192.168.178.23_12886: EOF
2018.11.14 15:12:13 4: WEBtablet: /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 3, "stateName": "unlocked", "batteryCritical": false} / RL:8041 / text/html; charset=UTF-8 / /
2018.11.14 15:12:13 4: WEBtablet_192.168.178.23_12886 POST /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 3, "stateName": "unlocked", "batteryCritical": false}; BUFLEN:0
2018.11.14 15:12:10 4: Connection accepted from WEBtablet_192.168.178.23_12886
2018.11.14 15:12:08 5: NUKIDevice (NUKIDevice347794437) - readings set for NUKIDevice347794437
2018.11.14 15:12:08 5: NUKIDevice (NUKIDevice347794437) - parse status message for NUKIDevice347794437
2018.11.14 15:12:08 5: NUKIDevice (NUKIDevice347794437) - Parse with result: {"name":"Nuki_14BAEC05","paired":true,"rssi":-71}
2018.11.14 15:12:07 4: NUKIDevice (NUKIDevice347794437) - Received scanResults for matching NukiID 347794437 at device NUKIDevice347794437
2018.11.14 15:12:07 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 15:12:07 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 15:12:07 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 15:12:07 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 15349, "currentTime": "2018-11-14T14:12:06+00:00", "serverConnected": true, "scanResults": [{"nukiId": 347794437, "name": "Nuki_14BAEC05", "rssi": -71, "paired": true}]}
2018.11.14 15:12:07 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 15:12:07 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 15:12:07 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 15:12:07 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 15:11:54 4: Connection closed for WEBtablet_192.168.178.23_9057: EOF
2018.11.14 15:11:41 4: WEBtablet: /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 1, "stateName": "locked", "batteryCritical": false} / RL:8041 / text/html; charset=UTF-8 / /
2018.11.14 15:11:41 4: WEBtablet_192.168.178.23_9057 POST /fhem/NUKIDevice-347794437&{"nukiId": 347794437, "state": 1, "stateName": "locked", "batteryCritical": false}; BUFLEN:0
2018.11.14 15:11:40 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2018.11.14 15:11:40 5: NUKIBridge (NukiBridge) - Response CODE: 503
2018.11.14 15:11:40 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 15:11:40 5: NUKIBridge (NukiBridge) - Response JSON: HTTP 503 Unavailable
2018.11.14 15:11:40 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 15:11:40 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 15:11:40 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 15:11:40 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2018.11.14 15:11:39 4: Connection accepted from WEBtablet_192.168.178.23_9057
2018.11.14 15:11:16 5: NUKIBridge (NukiBridge) - Bridge ist online
2018.11.14 15:11:16 5: NUKIBridge (NukiBridge) - Response CODE: 200
2018.11.14 15:11:16 5: NUKIBridge (NukiBridge) - Response ERROR:
2018.11.14 15:11:16 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 95991041, "serverId": 1337010944}, "versions": {"firmwareVersion": "1.11.3", "wifiFirmwareVersion": "1.2.0"}, "uptime": 15298, "currentTime": "2018-11-14T14:11:15+00:00", "serverConnected": true, "scanResults": []}
2018.11.14 15:11:16 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.14 15:11:16 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2018.11.14 15:11:16 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.23:8080/info?token=XXXXXX
2018.11.14 15:11:16 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
timestamp: 2018-11-14T14:14:37+00:00 type: HTTP-Log
timestamp: 2018-11-14T14:14:37+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:14:13+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T14:14:13+00:00 type: HTTP-Info
timestamp: 2018-11-14T14:14:13+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:13:54+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T14:13:52+00:00 type: HTTP-Info
timestamp: 2018-11-14T14:13:52+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:13:29+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T14:13:29+00:00 type: HTTP-Info
timestamp: 2018-11-14T14:13:29+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:13:14+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T14:13:14+00:00 type: HTTP-Info
timestamp: 2018-11-14T14:13:14+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:12:56+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T14:12:56+00:00 type: HTTP-Info
timestamp: 2018-11-14T14:12:55+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:12:34+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T14:12:34+00:00 type: HTTP-Info
timestamp: 2018-11-14T14:12:34+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:12:26+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T14:12:25+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T14:12:19+00:00 type: HTTP-PostTimeout
timestamp: 2018-11-14T14:12:13+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:13+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:11+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:10+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T14:12:10+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T14:12:10+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDF
timestamp: 2018-11-14T14:12:10+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T14:12:10+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T14:12:10+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 96
timestamp: 2018-11-14T14:12:10+00:00 type: BLE-SendingSSE bytes: 96 auth: 00345CDF
timestamp: 2018-11-14T14:12:09+00:00 type: WLAN-SocketConnected connection: 3
timestamp: 2018-11-14T14:12:09+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T14:12:09+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T14:12:09+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDF
timestamp: 2018-11-14T14:12:09+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T14:12:09+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T14:12:08+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T14:12:08+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T14:12:08+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDF
timestamp: 2018-11-14T14:12:08+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDF
timestamp: 2018-11-14T14:12:08+00:00 type: BLE-Connect handles: ARRAY(0x6fb0638)
timestamp: 2018-11-14T14:12:08+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:07+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T14:12:07+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:07+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T14:12:07+00:00 type: SSE-KeyturnerEventResp nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:07+00:00 type: HTTP-PostStart
timestamp: 2018-11-14T14:12:07+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:07+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:07+00:00 type: SSE-KeyturnerEventReq nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:07+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000C
timestamp: 2018-11-14T14:12:07+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T14:12:06+00:00 type: HTTP-Info
timestamp: 2018-11-14T14:12:06+00:00 type: BLE-SendingMsg nukiId: 14BAEC05 cmdId: 0001
timestamp: 2018-11-14T14:12:06+00:00 type: BLE-Connect handles: ARRAY(0x6008c20)
timestamp: 2018-11-14T14:12:06+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:06+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:12:06+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T14:12:06+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:06+00:00 type: BLE-StatusUpdate nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:06+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:06+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T14:12:03+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T14:12:03+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T14:12:03+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDD
timestamp: 2018-11-14T14:12:03+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T14:12:03+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDD
timestamp: 2018-11-14T14:11:57+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 212
timestamp: 2018-11-14T14:11:57+00:00 type: BLE-ReceivingSSE bytes: 73 auth: 00345CDD
timestamp: 2018-11-14T14:11:57+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T14:11:57+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDD
timestamp: 2018-11-14T14:11:57+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 92
timestamp: 2018-11-14T14:11:57+00:00 type: BLE-SendingSSE bytes: 92 auth: 00345CDD
timestamp: 2018-11-14T14:11:56+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T14:11:56+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 228
timestamp: 2018-11-14T14:11:56+00:00 type: BLE-ReceivingSSE bytes: 86 auth: 00345CDD
timestamp: 2018-11-14T14:11:56+00:00 type: BLE-SendingSSE bytes: 56 auth: 00345CDD
timestamp: 2018-11-14T14:11:56+00:00 type: BLE-Connect handles: ARRAY(0x5fe1578)
timestamp: 2018-11-14T14:11:56+00:00 type: BLE-Connected nukiId: 14BAEC05
timestamp: 2018-11-14T14:11:55+00:00 type: HTTP-PostFailed urlId: 0
timestamp: 2018-11-14T14:11:54+00:00 type: WLAN-SocketDisconnected connection: 3
timestamp: 2018-11-14T14:11:50+00:00 type: BLE-Connect macAddr: 54D272BAEC05
timestamp: 2018-11-14T14:11:50+00:00 type: BLE-Connect nukiId: 14BAEC05
timestamp: 2018-11-14T14:11:50+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 56
timestamp: 2018-11-14T14:11:43+00:00 type: BLE-Disconnected nukiId: 14BAEC05
timestamp: 2018-11-14T14:11:43+00:00 type: BLE-Disconnect nukiId: 14BAEC05
timestamp: 2018-11-14T14:11:40+00:00 type: HTTP-Post urlId: 0 nukiId: 14BAEC05
timestamp: 2018-11-14T14:11:40+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
timestamp: 2018-11-14T14:11:40+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 188
timestamp: 2018-11-14T14:11:40+00:00 type: BLE-ReceivingSSE bytes: 55 auth: 00345CDF
timestamp: 2018-11-14T14:11:40+00:00 type: SSE-KeyturnerResponse nukiId: 14BAEC05 bytes: 256
timestamp: 2018-11-14T14:11:40+00:00 type: BLE-ReceivingSSE bytes: 107 auth: 00345CDF
timestamp: 2018-11-14T14:11:39+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2018-11-14T14:11:39+00:00 type: SSE-KeyturnerRequest nukiId: 14BAEC05 bytes: 96
timestamp: 2018-11-14T14:11:39+00:00 type: BLE-SendingSSE bytes: 96 auth: 00345CDF
timestamp: 2018-11-14T14:11:39+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2018-11-14T14:11:39+00:00 type: BLE-ReceivingMsg nukiId: 14BAEC05 cmdId: 000E
Zitat von: Cobra am 15 November 2018, 10:38:24
Kein Problem, es ist ja nur der Status der aktuell nicht stimmt, damit kann ich noch ein paar Tage leben.
Gib einfach Bescheid wenn du nochmal Daten von mir benötigst.
Internals:
CONNECTS 203
CSRFTOKEN csrf_xxxxxxxxxxxxx
DEF 8085 global
FD 8
NAME WEBtablet
NR 12
NTFY_ORDER 50-WEBtablet
PORT 8085
STATE Initialized
TYPE FHEMWEB
READINGS:
2018-11-12 08:38:47 state Initialized
Attributes:
editConfig 1
hiddenroom AlarmRoom
room 9.6_System
stylesheetPrefix dark
verbose 3
Zitat von: marvin78 am 15 November 2018, 10:43:35
Ich habe heute mein 2. Nuki bekommen (diesmal ein 2.0). Das alte wandert an die Garagentür. Wenn ich dazu komme (kann dauern), werde ich berichten, wie gut es läuft.
Zitat von: Cobra am 15 November 2018, 10:47:14
Hier mal das List von der Web-Instanz:Code AuswählenInternals:
CONNECTS 203
CSRFTOKEN csrf_xxxxxxxxxxxxx
DEF 8085 global
FD 8
NAME WEBtablet
NR 12
NTFY_ORDER 50-WEBtablet
PORT 8085
STATE Initialized
TYPE FHEMWEB
READINGS:
2018-11-12 08:38:47 state Initialized
Attributes:
editConfig 1
hiddenroom AlarmRoom
room 9.6_System
stylesheetPrefix dark
verbose 3
Ein Allowed-Device dafür gibt es nicht, die Instanz habe ich seit der Installation damals nicht groß verändert.
Zitat von: marvin78 am 15 November 2018, 10:49:50
Bekommst du, aber ich hoffe ernsthaft (für dich und alle), dass jemand schneller ist, als ich, denn bei mir kann es wirklich noch dauern, wenn nicht zufällig Zeit frei wird ;)
Zitat von: CoolTux am 15 November 2018, 10:50:32
Ich Ahne eventuell was. Wann hast Du das letzte mal wirklich für Dich in der Erinnerung einen korrekten Schaltstatus über den webhook bekommen?
Zum testen meiner Vermutung würde ich Dich bitten das Attribut hiddenroom zu entfernen, speichern. Neustart machen und dann noch mal testen.
Grüße
Zitat von: CoolTux am 15 November 2018, 11:07:47
Und seit diesem Update gehe ich davon aus hat es nicht mehr funktioniert.
Grund ist eine Änderung bei der hiddenroom Geschichte. URLs welche Geräte im hiddenroom aufrufen werden geblockt. Aber eigentlich hätte da eine Nachricht kommen müssen.
Zu Testzwecken kannst das Gerät ja wieder ohne neustart in den hiddenroom setzen.
Zitat von: fred_feuerstein am 17 November 2018, 15:04:08
Neustart hatte ich gemacht.
Ach das mit den Zwischenschritten kann natürlich sein, wenn die vom Modul kommen... Hab ja eben die ganze Zeit extern verschlossen mit app und bridge um den callback zu testen. Das scheint zu funktionieren.
Normalerweise bediene ich das Schloss ausschließlich über fhem. Gerade probiert. Über fhem bedient kommen die Zwischenschritte. Aber dann kein Endstatus mehr. Fhem bleibt also bei unlock oder Lock stehen und erhält nicht mehr locked oder unlocked.
Zitat
Happens to me as well. No Callback (after an lockAction-Call) for the new LOCKED-State. I looked in the Bridge-Log and there is no HTTP-POST-Entry for the Callback
Zitat
We could track down the problem and hope to fix it with the next FW-update.
Zitat von: fred_feuerstein am 17 November 2018, 14:42:06
Allerdings kam bisher der callback wohl früher, denn ich hatte oft als callback bereits die Zwischenstufe: beim zuschliessen kam also bereits: "lock" als callback und dann nach ein paar sekunden kam "locked".
Umgekehrt kam bereits: "unlock" und dann später "unlocked".
Also diese Zwischenschritte habe ich nicht mehr gesehen. Das gibt es scheinbar nicht mehr.
Wie ist das bei Dir Cobra?
Zitat von: fred_feuerstein am 17 November 2018, 15:54:11
ok dann bin ich beruhigt. Dann geht es also im Moment so, wie es der Firmware-Stand vom neuen Nuki im Moment zulässt.
Internals:
BRIDGEAPI 1.6
DEF 192.168.x.x xxxxx
HOST 192.168.x.x
NAME nukibridge1
NR 237
PORT 8080
STATE connected
TOKEN xxxxx
TYPE NUKIBridge
VERSION 0.6.3
READINGS:
2018-11-21 15:28:38 bridgeType Hardware
2018-11-21 15:26:17 currentTime 2018-11-21T14:26:17+00:00
2018-11-21 15:28:38 firmwareVersion 1.10.0
2018-11-21 15:28:38 hardwareId 274043297
2018-11-21 15:27:59 lastError 192.168.x.x: Connection refused
2018-11-21 15:28:38 serverConnected false
2018-11-21 15:28:38 serverId 542905088
2018-11-21 15:28:38 state connected
2018-11-21 15:28:38 uptime 22
2018-11-21 15:28:38 wifiFirmwareVersion 1.1.0
helper:
aliveCount 0
Attributes:
room NUKI
2018.11.21 15:34:09 4: NUKIBridge (nukibridge1) - NUKIBridge_GetCheckBridgeAlive
2018.11.21 15:34:09 4: NUKIBridge (nukibridge1) - Send HTTP POST with URL http://192.168.x.x:8080/info?token=xxxx
2018.11.21 15:34:09 4: NUKIBridge (nukibridge1) - run NUKIBridge_Call
2018.11.21 15:34:09 4: NUKIBridge (nukibridge1) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2018.11.21 15:34:10 5: NUKIBridge (nukibridge1) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 274043297, "serverId": 542905088}, "versions": {"firmwareVersion": "1.10.0", "wifiFirmwareVersion": "1.1.0"}, "uptime": 354, "currentTime": "2018-11-21T14:34:10+00:00", "serverConnected": true, "scanResults": [{"nukiId": 63125473, "name": "Nuki_03C337E1", "rssi": -65, "paired": true}]}
2018.11.21 15:34:10 5: NUKIBridge (nukibridge1) - Response ERROR:
2018.11.21 15:34:10 5: NUKIBridge (nukibridge1) - Response CODE: 200
2018.11.21 15:34:10 5: NUKIBridge (nukibridge1) - Bridge ist online
Zitat von: toemk am 21 November 2018, 15:54:46
Ja, Aufruf im Browser geht und die Bridge ist "connected".
Idee: Muss autocreate global im fhem aktiviert sein?
Zitat von: marvin78 am 23 Dezember 2018, 16:53:49
Schaltzustand ganz sicher. Das Protokoll müsstest du erst nach FHEM bekommen. Aber im Grunde kannst du ja per Log selbst eines erstellen.
Zitat von: marvin78 am 23 Dezember 2018, 19:50:50
Falsches Forum.
Zitat von: Cobra am 28 Dezember 2018, 10:21:10
Und was ist jetzt deine Frage bzw. wo funktioniert dein Notify/DOIF/etc denn nicht?
Zitat von: CoolTux am 28 Dezember 2018, 10:22:44
Cobra bitte sei so lieb. Nicht hier. Sowas gehört nicht hier rein.
Der User möge die Frage in das passende Forum stellen und da können wir dann gerne antworten.
LG
Zitat von: Cobra am 28 Dezember 2018, 10:24:01Falls wir uns nicht mehr lesen. Dir und Deiner Familie einen guten Rutsch ins neue Jahr.
Bereits gelöscht ;-)
Zitat von: obelix221 am 02 Januar 2019, 09:41:03
Hi CoolTux,
danke für die schnelle Antwort.
Siehst Du grundsätzlich Chancen mit einem Log-File-Parser auf das Log in der App zu gehen, und dann den jeweiligen Eintrag an FHEM zu schicken?
Wenn ja, wo und wie würdest Du da ansetzen/ vorgehen?
Falls der Weg erfolgsversprechend ist und mir meine Skills ausreichend erscheinen, würde ich mich ggf. auf den Weg machen.
VG
Obelix
2019.01.15 21:33:48 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2019.01.15 21:33:48 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.1.45:8080/info?token=XXXXXX
2019.01.15 21:33:48 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2019.01.15 21:33:48 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2019.01.15 21:33:48 5: NUKIBridge (NukiBridge) - Response JSON: HTTP 503 Unavailable
2019.01.15 21:33:48 5: NUKIBridge (NukiBridge) - Response ERROR:
2019.01.15 21:33:48 5: NUKIBridge (NukiBridge) - Response CODE: 503
2019.01.15 21:33:48 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
Zitat von: torte am 18 Januar 2019, 21:30:12
Guten Abend,
hab da auch mal so eine frage.
Werden eigentlich zur Zeit die Stati richtig übertragen oder nicht.
Ich bekomme im FHEM nur locked oder unlocked angezeigt.
Im Eventmonitor sehe ich nie den unlatch und weiß jetzt nicht ob das normal ist oder bei mir was falsch läuft.
Webhook hab ich eingerichtet. WEBInstanz ohne https und ohne user Passwort.
Grüße
Torte
2019.02.12 18:33:35 3: NUKIDevice (Connector_NUKIBridge) - empty answer received for http://10.2.12.61:8080/reboot?token=xxxxxx
2019.02.12 18:34:06 3: NUKIDevice (Connector_NUKIBridge) - invalid json detected for http://10.2.12.61:8080/callback/list?token=xxxxxx: HTTP 503 Unavailable
Can't use string ("NUKIDevice (Connector_NUKIBridge"...) as a HASH ref while "strict refs" in use at ./FHEM/73_NUKIBridge.pm line 687.
ZitatHi, ich muss mal kurz nachfragen da ich unsicher bin: Unterscheidet sich die v2-Bridge von der v1? API sollte doch identisch sein --> also wenn sich etwas an der API tut, sollten doch alle Bridges damit umgehen können oder erhalten die v1 nicht die Firmwareupdates? Oder habe ich es nur komplett falsch interpretiert und die v2 haben noch nicht die korrekte Firmware bei Auslieferung gehabt??
Hatte auch bereits überlegt, das Upgrade-Programm zu nehmen, aber konnte auch nach Rückfrage mit Nuki.io keinen Vorteil der v2-Bridge feststellen (und die Preisdifferenz von "nur" Schloss zu "Schloss und Bridge" ist ja nicht ganz ohne). Hat jemand schon das neue Schloss? Wie sieht es denn mit der Entfernung zwischen Schloss und Magnet aus? Bei wie viel cm ist Schluss mit der Erkennung?
Zitat von: pc1246 am 18 Februar 2019, 13:43:31
Danke Loredo
Warum will Nuki, dann die Bridge tauschen? Wobei ich ja eigentlich ganz froh waere, da die schon zweimal 1,1m im freien Fall hinter sich hat, und natuerlich auf den Stecker gefallen ist. Ein drittes Mal verhindere ich durch Umplatzierung, da sonst kaputt.
Gruss Christoph
Zitat
timestamp: 2019-02-25T18:07:59+00:00 type: HTTP-Log
timestamp: 2019-02-25T18:07:59+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:07:48+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:07:48+00:00 type: HTTP-Info
timestamp: 2019-02-25T18:07:48+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:07:31+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:07:31+00:00 type: HTTP-Info
timestamp: 2019-02-25T18:07:31+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:07:07+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:07:07+00:00 type: HTTP-Info
timestamp: 2019-02-25T18:07:07+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:06:42+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:06:42+00:00 type: HTTP-Info
timestamp: 2019-02-25T18:06:42+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:06:14+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:06:14+00:00 type: HTTP-Info
timestamp: 2019-02-25T18:06:14+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:05:58+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:05:55+00:00 type: HTTP-Info
timestamp: 2019-02-25T18:05:54+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:05:47+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:05:46+00:00 type: HTTP-Log
timestamp: 2019-02-25T18:05:46+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:05:40+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:05:40+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:05:26+00:00 type: WLAN-SocketDisconnected connection: 0
timestamp: 2019-02-25T18:05:26+00:00 type: HTTP-Info
timestamp: 2019-02-25T18:05:26+00:00 type: WLAN-SocketConnected connection: 0
timestamp: 2019-02-25T18:05:01+00:00 type: WLAN-SocketDisconnected connection: 0
Internals:
BRIDGEAPI 1.6
DEF 192.168.178.144 ********
FUUID 5c88da6f-f33f-7f1e-8a8f-6a7467ced9d3736f
HOST 192.168.178.144
NAME NukiBridge
NR 715
PORT 8080
STATE connected
TOKEN ********
TYPE NUKIBridge
VERSION 0.6.3
.attraggr:
.attrminint:
READINGS:
2019-03-13 12:46:27 bridgeType Hardware
2019-03-13 12:46:27 currentTime 2019-03-13T11:45:54+00:00
2019-03-13 12:46:27 firmwareVersion 2.1.37
2019-03-13 12:46:27 hardwareId 386659482
2019-03-13 12:14:16 lastError connect to http://192.168.178.144:8080 timed out
2019-03-13 12:46:27 serverConnected 1
2019-03-13 12:46:27 serverId 1111302243
2019-03-13 12:46:27 state connected
2019-03-13 12:46:27 uptime 1731
2019-03-13 12:46:27 wifiFirmwareVersion 2.0.0
helper:
aliveCount 0
Attributes:
room NUKI
verbose 2
Internals:
DEF 1 NukiBridge
FUUID 5c88e7ec-f33f-7f1e-9765-758662b02604de4f
IODev NukiBridge
NAME NukiLock
NR 716
NUKIID 1
STATE Initialized
TYPE NUKIDevice
VERSION 0.6.3
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.178.71:8083/fhem/NUKIDevice-1
READINGS:
2019-03-13 12:22:52 success 1
fhem:
infix NUKIDevice
helper:
lockAction lock
Attributes:
IODev NukiBridge
room NUKI
webhookFWinstance WEB
webhookHttpHostname 192.168.178.71
2019.03.13 12:40:19 3: NUKIDevice (NukiLock) - invalid json detected: HTTP 404 Not Found
2019.03.13 12:48:36 3: NUKIDevice (NukiLock) - invalid json detected: HTTP 404 Not Found
2019.03.13 12:48:47 4: NUKIDevice (NukiLock) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2019.03.13 12:48:47 4: NUKIDevice (NukiLock) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2019.03.13 12:48:47 5: NUKIDevice (NukiLock) - Parse with result: HTTP 404 Not Found
2019.03.13 12:48:47 3: NUKIDevice (NukiLock) - invalid json detected: HTTP 404 Not Found
2019.03.13 12:48:50 4: NUKIDevice (NukiLock) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2019.03.13 12:48:50 4: NUKIDevice (NukiLock) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2019.03.13 12:48:50 5: NUKIDevice (NukiLock) - NUKIDevice_GetUpdate Call NUKIDevice_ReadFromNUKIBridge
2019.03.13 12:48:51 5: NUKIDevice (NukiLock) - Parse with result: HTTP 404 Not Found
2019.03.13 12:48:51 3: NUKIDevice (NukiLock) - invalid json detected: HTTP 404 Not Found
2019.03.13 12:49:20 4: NUKIDevice (NukiLock) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2019.03.13 12:49:20 4: NUKIDevice (NukiLock) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2019.03.13 12:49:20 5: NUKIDevice (NukiLock) - Parse with result: HTTP 404 Not Found
2019.03.13 12:49:20 3: NUKIDevice (NukiLock) - invalid json detected: HTTP 404 Not Found
webhookHttpHostname 192.168.178.64
WEBHOOK_URL http://192.168.178.64:8083/fhem/NUKIDevice-204483353
http://192.168.178.64:8087/fhem/NUKIDevice-204483353
allowedHttpMethods
habe ich schon durchprobiert...
Zitat von: Jostar am 21 März 2019, 09:42:28
Ja, das hatte ich gemacht. Da kommt die URL, siehe oben oder hier der Screenshot:
userReadings firmware { ReadingsVal($name, "appVersion", "") }
2019.03.29 09:15:56 1: readingsUpdate(nuki,firmware,1.4.6) missed to call readingsBeginUpdate first.
2019.03.29 09:15:56 1: stacktrace:
2019.03.29 09:15:56 1: main::readingsBulkUpdate called by fhem.pl (4670)
2019.03.29 09:15:56 1: main::readingsEndUpdate called by ./FHEM/73_NUKIBridge.pm (458)
2019.03.29 09:15:56 1: main::NUKIBridge_Distribution called by FHEM/HttpUtils.pm (606)
2019.03.29 09:15:56 1: main::__ANON__ called by fhem.pl (741)
2019.03.29 09:16:20 1: readingsUpdate(nuki,firmware,1.4.6) missed to call readingsBeginUpdate first.
userReadings firmware:appVersion:.* { ReadingsVal($name, "appVersion", "") }
Zitat von: CoolTux am 29 März 2019, 10:12:38Danke, das hilft. Das Reading wird aktualisiert und es gibt keine Fehler dazu mehr im Log! :)
Versuche mal bitteCode AuswählenuserReadings firmware:appVersion:.* { ReadingsVal($name, "appVersion", "") }
define NBridge NUKIBridge 192.168.178.120 13ee4454a61229edee99d3f2fc9cf303e10e61367736f54de33a8869f3a065449f04f5ad05eafb26
Zitat von: CoolTux am 21 April 2019, 22:51:06
In der Bridge APP kannst Du den Developer Modus aktivieren und bekommst dann da einen API Key.
Zitat von: thgorjup am 10 Mai 2019, 09:55:33
Hallo Leute,
mein NUKI 2.0 läuft wunderbar und fast problemlos. In seltenen Fällen verliert die Hardware Bridge die Verbindung aber damit kann ich leben. Ich würde nun gerne weitere Informationen aus der Bridge auslesen um sie zu verarbeiten.
1. Benutzername (wer hat die Tür auf/zu geschlossen)
2. Zustand der Haustüre (Tür geschlossen/geöffnet) Die 2.0 hat ja einen zusätzlichen Türsensor
Damit lässt sich z.B. eine Anwesenheitserkennung realisieren oder die Alarmanlage deaktivieren.
Ebenso kann man eine Warnung absetzen, wenn die Tür nur angelehnt ist.
Ist es irgendwie möglich diese Infos noch als Readings aus der Bridge zu holen?
Danke und Gruß
Thomas
Zitat
The HTTP API of the Bridge is now available for all current public firmware versions. (1.12.6/2.2.9)
Zitat
The door state is currently only part of the Web API. It's a feature very broadly requested for our Bridge API, but I'm sorry I can't give you an ETA on that yet.
define NukiUeberwachung DOIF ([NukiBridge] ne "connected") (set pushmsg msg 'fhem' 'NukiBridge nicht erreichbar. Steckdose wird geschaltet!';; set it_socket_5 off-for-timer 5)\
DOELSE
attr NukiUeberwachung cmdpause 1200
attr NukiUeberwachung wait 300
Zitat von: thgorjup am 01 Juni 2019, 17:24:22
@jsChris: Und kann man diese Web API irgendwie ansprechen und in das Modul integrieren?
Was mit aufgefallen ist, dass die Bridge mehrmals täglich auf "not connected" wechselt. Dann ist Nuki nicht mehr ansprechbar.
Ich habe das momentan über eine Funksteckdose gelöst, welche dann schaltet wenn die Bridge 300 Sek. kein "connected" meldet. Aber weiß jemand woran das liegt?
2019.06.02 16:21:24 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 16:31:38 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 17:19:38 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 17:20:23 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 17:42:48 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 17:43:04 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 17:48:21 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
Zitat von: CoolTux am 02 Juni 2019, 18:43:45
Chris was Du hast sind inkorrekte Daten welche die Bridge meldet.
2019.06.02 20:50:46 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2019.06.02 20:50:46 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.2.124:8080/info?token=aaaaaa
2019.06.02 20:50:46 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2019.06.02 20:50:46 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2019.06.02 20:50:46 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 33333, "serverId": 222222}, "versions": {"firmwareVersion": "2.2.9", "wifiFirmwareVersion": "2.0.0"}, "uptime": 40797, "currentTime": "2019-06-02T18:50:47+00:00", "wlanConnected": true, "serverConnected": true, "scanResults": [{"deviceType": 0, "nukiId": 333333, "name": "Nuki_111111", "rssi": -53, "paired": true}]}
2019.06.02 20:50:46 5: NUKIBridge (NukiBridge) - Response ERROR:
2019.06.02 20:50:46 5: NUKIBridge (NukiBridge) - Response CODE: 200
2019.06.02 20:50:46 5: NUKIBridge (NukiBridge) - Bridge ist online
2019.06.02 20:50:46 4: NUKIDevice (NUKIDevice33333) - Received scanResults for matching NukiID 333333 at device NUKIDevice33333
Zitat
Das hat aber mit verbose 5 nichts zu tun. Irgendwann kommt auch wieder ein 503
Zitat
Mal allgemein: Wie gut funktioniert denn das Nuki-System bei euch?
Wenn ich beim Versandhändler in den Rezensionen die (immer gleichen) vielfältigen Probleme durchlese, bekomme ich den Eindruck eines eher nicht funktionierenden Systems. Und so etwas soll man seiner Haustüre anschrauben? :o
Zitat von: RappaSan am 03 Juni 2019, 07:03:08Moin
Mal allgemein: Wie gut funktioniert denn das Nuki-System bei euch?
Wenn ich beim Versandhändler in den Rezensionen die (immer gleichen) vielfältigen Probleme durchlese, bekomme ich den Eindruck eines eher nicht funktionierenden Systems. Und so etwas soll man seiner Haustüre anschrauben? :o
Zitat von: CoolTux am 02 Juni 2019, 18:43:45
thgorjup hat Probleme mit der Verbindungsstabilität zur Bridge (Hardware oder Software)?
2019.06.02 01:07:50 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 10:21:36 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 10:21:52 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 10:22:14 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 10:38:03 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 13:12:12 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 13:12:26 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 15:28:56 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 15:51:26 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 19:36:41 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 19:52:07 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 20:19:33 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 405 Method not allowed
2019.06.02 20:34:29 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 20:37:06 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.02 23:00:23 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 08:10:55 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 08:13:00 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 08:13:15 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 08:15:47 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 08:28:27 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 15:01:47 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 15:03:15 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 17:41:17 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 17:46:20 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 17:46:35 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 17:46:59 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 18:17:12 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 18:18:30 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 18:34:28 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 18:53:18 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 19:07:58 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 20:00:43 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 20:01:05 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.03 21:15:45 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 08:09:14 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 08:38:02 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 17:42:41 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 17:43:10 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 17:44:17 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 17:58:25 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 18:07:30 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 18:07:45 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 18:08:12 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 19:13:57 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 19:35:49 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 19:56:28 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 20:56:08 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.04 23:00:29 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 07:46:23 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 07:46:40 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 07:47:29 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 08:03:29 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 08:10:21 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 09:22:50 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 09:38:01 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 11:52:21 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 11:52:58 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 11:53:18 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 12:07:16 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 12:54:57 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 12:55:16 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 13:08:38 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 17:38:31 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 17:53:24 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 18:50:05 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 18:50:33 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 19:11:24 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 21:01:07 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 21:01:25 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 21:01:41 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 21:09:43 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.06.05 21:19:44 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
Zitat von: CoolTux am 05 Juni 2019, 21:57:45
Kannst Du eventuell zusätzlich auf einem anderen Weg noch verifizieren das die Bridge in der Tat nicht erreichbar war?
sqlite> select * from history where DEVICE like 'Nuki%' and VALUE like '%not%' order by TIMESTAMP;
2019-06-05 22:07:21|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-06 19:50:21|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-06 23:01:05|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 06:13:01|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 17:32:03|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 17:33:28|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 17:34:40|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 17:35:51|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 17:37:09|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 21:34:23|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 21:38:08|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 21:39:40|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 21:40:53|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 21:42:28|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
2019-06-07 21:44:06|NukiBridge|NUKIBRIDGE|state: not connected|state|not connected|
root@pi2:/var/log/fhem# cat pingtest_nuki.log|grep DOWN
Donnerstag 06.06.2019 20:04:31 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 08:47:48 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:30:13 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:30:46 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:31:04 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:31:22 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:31:40 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:31:58 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:32:17 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:32:34 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:32:51 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:33:09 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:33:27 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:33:43 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:34:01 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:34:19 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:34:37 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:34:55 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:35:13 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:35:31 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:35:49 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:36:06 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:36:24 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:36:42 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:37:00 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 17:59:06 --- (10.4.70.159) IST DOWN
Freitag 07.06.2019 21:43:15 --- (10.4.70.159) IST DOWN
define WEBhabridge FHEMWEB 8088 global
setuuid WEBhabridge xxxxxxx
attr WEBhabridge allowfrom "hier ist die IP der Bridge eingetragen"
attr WEBhabridge csrfToken none
attr VR_NUKI_Haustuere webhookFWinstance WEBhabridge
attr VR_NUKI_Haustuere webhookHttpHostname "IP vom FHEM"
wget http://192.168.0.9:8088/fhem/NUKIDevice-405930229
--2019-07-23 10:45:01-- http://192.168.0.9:8088/fhem/NUKIDevice-XXXXXXXXX
Connecting to 192.168.0.9:8088... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.
--2019-07-23 10:45:02-- (try: 2) http://192.168.0.9:8088/fhem/NUKIDevice-XXXXXXXXX
Connecting to 192.168.0.9:8088... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.
....
Zitat von: CoolTux am 23 Juli 2019, 13:56:55
Hallo,
Ich bin im Urlaub. Daher nur kurz. Devicename ist nicht wichtig. Wichtig ist die ID und das die Callback URL passt.
Entferne mal das allowFrom und teste das bitte.
Tun on the Samsung Note 4
Go to home screen and select the app icon
Then select on the settings icon
Browse for the Application Manager
Display All Tabs by swiping either right or left
Select on Bluetooth
Select to stop it forcefully.
Now clear the cache
Select clear the Bluetooth data
Select Ok
Finally restart the Samsung Note 4
https://www.techjunkie.com/how-to-fix-samsung-note-4-bluetooth-problems/
Zitat von: RappaSan am 15 August 2019, 09:54:02
Hallo Leon,
ich hab dies schon bei den Anfängerfragen geschrieben, aber da wird ja nicht so häufig mitgelesen...
Mir ist noch aufgefallen, daß es inkonsistenzen beim status gibt.
Je nachdem man mit FHEM oder per app den Status ändert, wird im NUKIdevice lock/locked oder unlock/unlocked angezeigt.
Ist das von dir so gewollt?
Internals:
BRIDGEAPI 1.6
CFGFN ./FHEM/Nuki.cfg
DEF 192.168.0.29 k40u54
FUUID 5d55311e-f33f-d006-786b-ee2573d8731f22dc
HOST 192.168.0.29
NAME NukiBridge
NR 121
PORT 8080
STATE connected
TOKEN k40u54
TYPE NUKIBridge
VERSION 0.6.3
READINGS:
2019-08-15 13:14:03 bridgeType Hardware
2019-08-15 13:14:03 currentTime 2019-08-15T11:14:03+00:00
2019-08-15 13:14:03 firmwareVersion 2.2.12
2019-08-15 13:14:03 hardwareId 362094074
2019-08-15 12:55:10 lastError 192.168.0.29: Verbindungsaufbau abgelehnt (111)
2019-08-15 13:14:03 serverConnected 1
2019-08-15 13:14:03 serverId 453749113
2019-08-15 13:14:03 state connected
2019-08-15 13:14:03 uptime 1083
2019-08-15 13:14:03 wifiFirmwareVersion 2.0.0
helper:
aliveCount 0
Attributes:
room NUKI,Status
Internals:
CFGFN ./FHEM/Nuki.cfg
CHANGED
DEF 364729365 IODev=NukiBridge
FUUID 5d55311e-f33f-d006-c601-d291b6a5df3a353e
IODev NukiBridge
NAME NUKIDevice364729365
NR 123
NUKIID 364729365
STATE unlock
TYPE NUKIDevice
VERSION 0.6.3
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8086
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://FHEM.fritz.box:8086/fhem/NUKIDevice-364729365
READINGS:
2019-08-15 13:10:22 battery ok
2019-08-15 13:10:22 batteryCritical 0
2019-08-15 13:10:22 batteryState ok
2019-08-15 13:10:42 lockState unlock
2019-08-15 13:15:23 name Nuki_15BD5415
2019-08-15 13:15:23 paired 1
2019-08-15 13:15:23 rssi -64
2019-08-15 13:10:42 state unlock
2019-08-15 13:10:42 success 1
fhem:
infix NUKIDevice
helper:
Attributes:
IODev NukiBridge
alias Haustuer
devStateIcon lock.*:fts_door@green unlo.*:fts_door@orange unla.*:fts_door_open@red
event-on-change-reading state,lockState,batt.*
room NUKI,Status
webhookFWinstance WEBNuki
webhookHttpHostname FHEM.fritz.box
Internals:
CONNECTS 1
DEF 8086 global
FD 9
FUUID 5d4a60ab-f33f-d006-bb98-55527682b3a3b4d5
NAME WEBNuki
NR 18
NTFY_ORDER 50-WEBNuki
PORT 8086
STATE Initialized
TYPE FHEMWEB
READINGS:
2019-08-15 12:41:23 state Initialized
Attributes:
csrfToken none
Zitat von: RappaSan am 16 August 2019, 07:10:30
Mein WebHooK:Code AuswählenInternals:
CONNECTS 1
DEF 8086 global
FD 9
FUUID 5d4a60ab-f33f-d006-bb98-55527682b3a3b4d5
NAME WEBNuki
NR 18
NTFY_ORDER 50-WEBNuki
PORT 8086
STATE Initialized
TYPE FHEMWEB
READINGS:
2019-08-15 12:41:23 state Initialized
Attributes:
csrfToken none
Tür wurde gerade durch Tastendruck aufgesperrt, aber auch nach 3 Minuten noch keine Statusänderung.
Zitat von: RappaSan am 20 August 2019, 08:20:45
Irgend etwas stimmt noch nicht mit dem webhhok/der callbackList-Funktion.
Es kommt häufiger vor, daß das gesamte FHEM neu startet, wenn ich ein "get callbackList" absetze.
Ich bin aber noch nicht dahinter gekommen, wie man diesen Zustand zielsicher provoziert.
2019.08.20 08:34:37 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.08.20 08:35:11 3: NUKIDevice (NukiBridge) - empty answer received for http://192.168.0.29:8080/reboot?token=123456
2019.08.20 08:35:59 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.08.20 08:36:07 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.08.20 08:36:16 3: NUKIDevice (NukiBridge) - invalid json detected for http://192.168.0.29:8080/callback/list?token=123456: HTTP 503 Unavailable
Can't use string ("NUKIDevice (NukiBridge) - invali"...) as a HASH ref while "strict refs" in use at ./FHEM/73_NUKIBridge.pm line 687.
Zitat von: RappaSan am 20 August 2019, 08:41:13
Hat gerade wieder ein Reboot FHEM nach dem get gegeben, und ich hab etwas im Log:Code Auswählen2019.08.20 08:34:37 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.08.20 08:35:11 3: NUKIDevice (NukiBridge) - empty answer received for http://192.168.0.29:8080/reboot?token=123456
2019.08.20 08:35:59 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.08.20 08:36:07 3: NUKIBridge (NukiBridge) - invalid json detected: HTTP 503 Unavailable
2019.08.20 08:36:16 3: NUKIDevice (NukiBridge) - invalid json detected for http://192.168.0.29:8080/callback/list?token=123456: HTTP 503 Unavailable
Can't use string ("NUKIDevice (NukiBridge) - invali"...) as a HASH ref while "strict refs" in use at ./FHEM/73_NUKIBridge.pm line 687.
Da haste mit dem Hash wohl nicht so falsch gelegen.
Zitat von: Loredo am 06 September 2019, 17:22:40
Hab ich schon zu Hause liegen, werde berichten.
Zitat von: Loredo am 06 September 2019, 17:38:23
Beta, kam aber 1 Tag vorm Urlaub.
Komme erst nächstes Wochenende dazu leider.
Alte Bridge hab ich.
Internals:
DEF 45956XXXX IODev=Connector_NUKIBridge
FUUID 5d8b74e0-f33f-6138-f061-7dd08c699805XXXX
IODev Connector_NUKIBridge
NAME 21000.Opener.1
NR 1628
NUKIID 45956XXXX
STATE Initialized
TYPE NUKIDevice
VERSION 0.6.4
WEBHOOK_REGISTER unregistered
READINGS:
2019-09-28 13:29:41 name Nuki_Opener_1B6XXXXA
2019-09-28 13:29:41 paired 1
2019-09-28 13:29:41 rssi -75
helper:
Attributes:
IODev Connector_NUKIBridge
icon 1_nuki_bridge
room 1.21301_Entré
2019.09.29 11:04:51 5: NUKIBridge (Connector_NUKIBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 11908xxxx, "serverId": 10626xxxx}, "versions": {"firmwareVersion": "1.13.1", "wifiFirmwareVersion": "1.2.0"}, "uptime": 317002, "currentTime": "2019-09-29T09:04:50+00:00", "serverConnected": true, "scanResults": [{"deviceType": 2, "nukiId": 45956xxxx, "name": "Nuki_Opener_1B6xxxxA", "rssi": -73, "paired": true}, {"deviceType": 0, "nukiId": 36309xxxx, "name": "Nuki_15A4xxxx", "rssi": -79, "paired": true}]}
2019.09.29 11:04:51 4: NUKIDevice (21000.Opener.1) - Received scanResults for matching NukiID 459563082 at device 21000.Opener.1
2019.09.29 11:04:51 5: NUKIDevice (21000.Opener.1) - Parse with result: {"rssi":-73,"name":"Nuki_Opener_1B64604A","paired":true}
2019.09.29 11:04:51 5: NUKIDevice (21000.Opener.1) - parse status message for 21000.Opener.1
2019.09.29 11:04:51 5: NUKIDevice (21000.Opener.1) - readings set for 21000.Opener.1
2019.09.29 11:07:14 4: NUKIDevice (21000.Opener.1) - NUKIDevice_ReadFromNUKIBridge check Bridge connected
2019.09.29 11:07:14 4: NUKIDevice (21000.Opener.1) - NUKIDevice_ReadFromNUKIBridge Bridge is connected call IOWrite
2019.09.29 11:07:15 5: NUKIDevice (21000.Opener.1) - Parse with result: HTTP 404 Not Found
2019.09.29 11:07:15 3: NUKIDevice (21000.Opener.1) - invalid json detected: HTTP 404 Not Found
Zitat von: Claus1985 am 02 Oktober 2019, 15:01:28
Hat Passwort Schutz. Wie kann ich das mit eingeben?
{
"bridgeType":1,
"ids":{
"hardwareId":XXXXXXXXX,
"serverId":XXXXXXXXX
},
"versions":{
"firmwareVersion":"1.13.1",
"wifiFirmwareVersion":"1.2.0"
},
"uptime":4204,
"currentTime":"2019-10-05T18:20:14+00:00",
"serverConnected":true,
"scanResults":[
{
"deviceType":2,
"nukiId":XXXXXXXXX,
"name":"Nuki_Opener_XXXXXXXXX",
"rssi":-72,
"paired":true
},
{
"deviceType":0,
"nukiId":XXXXXXXXX,
"name":"Nuki_XXXXXXXXX",
"rssi":-69,
"paired":true
}
]
}
[
{
"deviceType":0,
"nukiId":XXXXXXXXX,
"name":"Wohnung",
"firmwareVersion":"2.5.4",
"lastKnownState":{
"mode":2,
"state":3,
"stateName":"unlocked",
"batteryCritical":false,
"timestamp":"2019-10-05T17:10:39+00:00"
}
},
{
"deviceType":2,
"nukiId":XXXXXXXXX,
"name":"Haus",
"firmwareVersion":"1.1.10",
"lastKnownState":{
"mode":2,
"state":1,
"stateName":"online",
"batteryCritical":false,
"timestamp":"2019-10-05T17:10:44+00:00"
}
}
]
{
"success":true,
"batteryCritical":false
}
{
"mode":2,
"state":1,
"stateName":"online",
"batteryCritical":false,
"success":true
}
Internals:
BRIDGEAPI 1.6
DEF 192.168.178.92 xxxxxx
FUUID 5d8b89bd-f33f-d232-fe0a-e774b888ef0e3448
HOST 192.168.178.92
NAME NukiBridge
NR 486
PORT 8080
STATE not connected
TOKEN xxxxxx
TYPE NUKIBridge
VERSION 0.6.4
READINGS:
2019-09-25 17:37:33 0_name Wohnung
2019-09-25 17:37:33 0_nukiId xxxxxxx
2019-10-06 09:40:13 bridgeType Hardware
2019-10-06 04:34:19 currentTime 2019-10-06T02:34:19+00:00
2019-10-06 09:40:13 firmwareVersion 2.2.13
2019-10-06 09:40:13 hardwareId xxxxxx
2019-10-06 09:44:07 lastError connect to http://192.168.178.92:8080 timed out
2019-10-06 09:40:13 serverConnected true
2019-10-06 09:40:13 serverId xxxxxx
2019-09-25 17:37:33 smartlockCount 1
2019-10-06 09:44:07 state not connected
2019-10-06 09:40:13 uptime 15
2019-10-06 09:40:13 wifiFirmwareVersion 2.0.0
Internals:
DEF 441770669 IODev=NukiBridge
FUUID 5d8b89bd-f33f-d232-a7e6-0a54ad334bcde350
IODev NukiBridge
NAME NUKIDevice441770669
NR 487
NUKIID 441770669
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.4
WEBHOOK_COUNTER 12
WEBHOOK_LAST 2019-10-07 15:28:51
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.178.12:8083/fhem/NUKIDevice-441770669
READINGS:
2019-10-07 15:28:51 battery ok
2019-10-07 15:28:51 batteryCritical false
2019-10-07 15:28:51 batteryState ok
2019-10-07 15:28:51 lockState unlocked
2019-10-07 05:56:27 name Nuki_1A54E2AD
2019-10-07 05:56:27 paired true
2019-10-07 05:56:27 rssi -49
2019-10-07 15:28:51 state unlocked
2019-10-07 05:57:13 success true
2019.10.07 18:53:15 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2019.10.07 18:53:15 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.92:8080/info?token=xxxxxx
2019.10.07 18:53:15 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2019.10.07 18:53:15 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2019.10.07 18:53:22 5: NUKIBridge (NukiBridge) - Response JSON:
2019.10.07 18:53:22 5: NUKIBridge (NukiBridge) - Response ERROR: connect to http://192.168.178.92:8080 timed out
2019.10.07 18:53:22 5: NUKIBridge (NukiBridge) - Bridge ist offline
2019.10.07 19:10:43 5: NUKIBridge (NukiBridge) - Response ERROR:
2019.10.07 19:10:43 5: NUKIBridge (NukiBridge) - Response CODE: 200
2019.10.07 19:10:43 5: NUKIBridge (NukiBridge) - Bridge ist online
2019.10.07 19:10:43 4: NUKIDevice (NUKIDevice441770669) - Received scanResults for matching NukiID 441770669 at device NUKIDevice441770669
2019.10.07 19:10:58 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2019.10.07 19:10:58 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.92:8080/info?token=xxxxxx
2019.10.07 19:10:58 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2019.10.07 19:10:58 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2019.10.07 19:10:58 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": xxxxxxxx, "serverId": xxxxxxxx}, "versions": {"firmwareVersion": "2.2.13", "wifiFirmwareVersion": "2.0.0"}, "uptime": 158, "currentTime": "2019-10-07T17:10:59+00:00", "wlanConnected": true, "serverConnected": true, "scanResults": [{"deviceType": 0, "nukiId": 441770669, "name": "Nuki_1A54E2AD", "rssi": -59, "paired": true}]}
2019.10.07 19:10:58 5: NUKIBridge (NukiBridge) - Response ERROR:
2019.10.07 19:10:58 5: NUKIBridge (NukiBridge) - Response CODE: 200
2019.10.07 19:10:58 5: NUKIBridge (NukiBridge) - Bridge ist online
2019.10.07 19:10:58 4: NUKIDevice (NUKIDevice441770669) - Received scanResults for matching NukiID 441770669 at device NUKIDevice441770669
Internals:
BRIDGEAPI 1.6
CFGFN
DEF 192.168.1.104 xxxx
FUUID 5dc1cd66-f33f-2ed4-8d9d-87ec304f26630cc2
HOST 192.168.1.104
NAME NBridge
NR 1072
PORT 8080
STATE connected
TOKEN xxxx
TYPE NUKIBridge
VERSION 0.6.4
READINGS:
2019-11-05 20:55:56 bridgeType Hardware
2019-11-05 20:55:56 currentTime 2019-11-05T19:55:56+00:00
2019-11-05 20:55:56 firmwareVersion 2.2.13
2019-11-05 20:55:56 hardwareId xxxx
2019-11-05 20:55:56 serverConnected 1
2019-11-05 20:55:56 serverId xxxx
2019-11-05 20:55:56 state connected
2019-11-05 20:55:56 uptime 7915
2019-11-05 20:55:56 wifiFirmwareVersion 2.0.0
helper:
aliveCount 0
Attributes:
room Sicherheit
Verbindung via Bluetooth: Sehr gut
Verbindung via Bridge: Sehr gut
curl http://192.168.1.104:8080/list?token=TOKEN
2019.11.06 10:23:21.892 3: 2019.11.06 10:54:29.906 4: NUKIBridge (NBridge) - Send HTTP POST with URL http://192.168.1.104:8080/list?token=rjbvjo
2019.11.06 10:54:30.170 5: NUKIBridge (NBridge) - Response JSON: [{"deviceType": 0, "nukiId": 440953477, "name": "Josef-Tuschl 5", "lastKnownState": {"mode": 2, "state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2019-11-06T09:29:28+00:00"}}]
2019.11.06 10:54:30.170 5: NUKIBridge (NBridge) - Response ERROR:
2019.11.06 10:54:30.170 5: NUKIBridge (NBridge) - Response CODE: 200
2019.11.06 10:54:30.173 4: NUKIBridge (NBridge) - Send HTTP POST with URL http://192.168.1.104:8080/info?token=rjbvjo
und:
[code]2019.11.06 10:54:44.908 4: NUKIBridge (NBridge) - NUKIBridge_GetCheckBridgeAlive
2019.11.06 10:54:44.909 4: NUKIBridge (NBridge) - Send HTTP POST with URL http://192.168.1.104:8080/info?token=rjbvjo
2019.11.06 10:54:44.909 4: NUKIBridge (NBridge) - run NUKIBridge_Call
2019.11.06 10:54:44.909 4: NUKIBridge (NBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2019.11.06 10:54:45.034 5: NUKIBridge (NBridge) - Response JSON: HTTP 503 Unavailable
2019.11.06 10:54:45.034 5: NUKIBridge (NBridge) - Response ERROR:
2019.11.06 10:54:45.034 5: NUKIBridge (NBridge) - Response CODE: 503
2019.11.06 10:54:45.034 3: NUKIBridge (NBridge) - invalid json detected: HTTP 503 Unavailable
2019.11.06 10:55:00.181 5: NUKIBridge (NBridge) - Response JSON:
2019.11.06 10:55:00.181 5: NUKIBridge (NBridge) - Response ERROR: read from http://192.168.1.104:8080 timed out
2019.11.06 10:55:00.181 5: NUKIBridge (NBridge) - Bridge ist offline
2019.11.06 10:55:00.181 4: NUKIBridge (NBridge) - error while requesting: read from http://192.168.1.104:8080 timed out
2019.11.06 10:55:10.913 4: NUKIBridge (NBridge) - NUKIBridge_GetCheckBridgeAlive
2019.11.06 10:55:10.915 4: NUKIBridge (NBridge) - Send HTTP POST with URL http://192.168.1.104:8080/info?token=rjbvjo
2019.11.06 10:55:10.915 4: NUKIBridge (NBridge) - run NUKIBridge_Call
2019.11.06 10:55:10.915 4: NUKIBridge (NBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2019.11.06 10:55:11.026 5: NUKIBridge (NBridge) - Response JSON: HTTP 503 Unavailable
2019.11.06 10:55:11.027 5: NUKIBridge (NBridge) - Response ERROR:
2019.11.06 10:55:11.027 5: NUKIBridge (NBridge) - Response CODE: 503
2019.11.06 10:55:11.027 3: NUKIBridge (NBridge) - invalid json detected: HTTP 503 Unavailable
2019.11.06 10:23:21.892 3: 2019.11.06 10:54:29.906 4: NUKIBridge (NBridge) - Send HTTP POST with URL http://192.168.1.104:8080/list?token=rjbvjo
2019.11.06 10:54:30.170 5: NUKIBridge (NBridge) - Response JSON: [{"deviceType": 0, "nukiId": 440953477, "name": "Josef-Tuschl 5", "lastKnownState": {"mode": 2, "state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2019-11-06T09:29:28+00:00"}}]
2019.11.06 10:54:30.170 5: NUKIBridge (NBridge) - Response ERROR:
2019.11.06 10:54:30.170 5: NUKIBridge (NBridge) - Response CODE: 200
CFGFN
DEF 476030020 IODev=nuki_bridge
FUUID 5dd1701e-f33f-0759-c4b2-1643840f8bf88235
IODev nuki_bridge
NAME nuki_haustuer
NR 1757
NUKIID 476030020
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.4
WEBHOOK_COUNTER 6
WEBHOOK_LAST 2019-11-18 05:39:37
WEBHOOK_PORT 9081
WEBHOOK_REGISTER sent
WEBHOOK_URI /WEBNUKI/NUKIDevice
WEBHOOK_URL http://fhem.ah.home:9081/WEBNUKI/NUKIDevice-476030020
Helper:
DBLOG:
battery:
logdb:
TIME 1574051977.21216
VALUE ok
batteryCritical:
logdb:
TIME 1574051977.21216
VALUE 0
batteryState:
logdb:
TIME 1574051977.21216
VALUE ok
lockState:
logdb:
TIME 1574051977.21216
VALUE unlocked
name:
logdb:
TIME 1574073036.14708
VALUE Nuki_1C5FA444
paired:
logdb:
TIME 1574073036.14708
VALUE 1
rssi:
logdb:
TIME 1574073036.14708
VALUE -54
state:
logdb:
TIME 1574051977.21216
VALUE unlocked
success:
logdb:
TIME 1574007686.21882
VALUE 1
READINGS:
2019-11-18 05:39:37 battery ok
2019-11-18 05:39:37 batteryCritical 0
2019-11-18 05:39:37 batteryState ok
2019-11-18 05:39:37 lockState unlocked
2019-11-18 11:30:36 name Nuki_1C5FA444
2019-11-18 11:30:36 paired 1
2019-11-18 11:30:36 rssi -54
2019-11-18 05:39:37 state unlocked
2019-11-17 17:21:26 success 1
fhem:
infix NUKIDevice
helper:
fromAutocreate 1
Attributes:
DbLogExclude .*
DbLogInclude .*
IODev nuki_bridge
alias Haustür
devStateIcon open:fts_door_right_open@red locked:fts_door_right@green unlocked:fts_door_right@yellow
group Sicherheit
icon nuki_lock
room ControlCenter,Erdgeschoss
webhookFWinstance WEBNUKI
webhookHttpHostname fhem.ah.home
WEBHOOK_COUNTER 6
WEBHOOK_LAST 2019-11-18 05:39:37
Zitat von: OdfFhem am 18 November 2019, 12:31:08
@eddy242
Ich habe Deine Angaben mal mit meinen verglichen und das Muster ist identisch - also auch NUKIDevice mit "-".
Was ich noch nicht ganz verstehe: bei Dir wird der WEBHOOK doch erfolgreich genutzt:Code Auswählen
WEBHOOK_COUNTER 6
WEBHOOK_LAST 2019-11-18 05:39:37
Hast Recht. Danke Dir fürs genau schauen. In der Tat wird der Webhook laut Counter und Timestamp sowie laut reading state verwendet.
Was genau funktioniert denn nicht?
Zitat von: eddy242 am 18 November 2019, 12:41:52
Nun meine Errwatungshaltung war, dass das FHEM Smartlock-Device einen Statusupdate bekommt (reading lockState), egal auf welche Weise das Schloss betätigt wurde (HomeKit, App, Schlüssel, FHEM). Das passiert jedoch nicht, auch nach einer längeren Wartezeit bleibt der Zustand unverändert. Das Absetzen eines getStatusRequests hilft, dann wird der aktuelle Status gesetzt.
2019.11.11 02:53:07 3: NUKIBridge (<FHEM-NAME>) - invalid json detected: HTTP 503 Unavailable
2019.11.11 08:44:07 3: NUKIDevice (<FHEM-NAME>) - invalid json detected: HTTP 503 Unavailable
Internals:
CFGFN
DEF 476030020 IODev=nuki_bridge
FUUID 5dd1701e-f33f-0759-c4b2-1643840f8bf88235
IODev nuki_bridge
NAME nuki_haustuer
NR 1757
NUKIID 476030020
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.4
WEBHOOK_COUNTER 6
WEBHOOK_LAST 2019-11-18 14:02:18
WEBHOOK_PORT 9081
WEBHOOK_REGISTER sent
WEBHOOK_URI /WEBNUKI/NUKIDevice
WEBHOOK_URL http://192.168.178.20:9081/WEBNUKI/NUKIDevice-476030020
Helper:
DBLOG:
battery:
logdb:
TIME 1574082138.61199
VALUE ok
batteryCritical:
logdb:
TIME 1574082138.61199
VALUE 0
batteryState:
logdb:
TIME 1574082138.61199
VALUE ok
lockState:
logdb:
TIME 1574082138.61199
VALUE unlocked
name:
logdb:
TIME 1574082328.52834
VALUE Nuki_1C5FA444
paired:
logdb:
TIME 1574082328.52834
VALUE 1
rssi:
logdb:
TIME 1574082328.52834
VALUE -51
state:
logdb:
TIME 1574082138.61199
VALUE unlocked
success:
logdb:
TIME 1574075800.51071
VALUE 1
READINGS:
2019-11-18 14:02:18 battery ok
2019-11-18 14:02:18 batteryCritical 0
2019-11-18 14:02:18 batteryState ok
2019-11-18 14:02:18 lockState unlocked
2019-11-18 14:05:28 name Nuki_1C5FA444
2019-11-18 14:05:28 paired 1
2019-11-18 14:05:28 rssi -51
2019-11-18 14:02:18 state unlocked
2019-11-18 12:16:40 success 1
fhem:
infix NUKIDevice
helper:
fromAutocreate 1
Attributes:
DbLogExclude .*
DbLogInclude .*
IODev nuki_bridge
alias Haustür
devStateIcon open:fts_door_right_open@red locked:fts_door_right@green unlocked:fts_door_right@yellow
group Sicherheit
icon nuki_lock
room ControlCenter,Erdgeschoss
webhookFWinstance WEBNUKI
webhookHttpHostname 192.168.178.20
2019.11.18 14:09:08 4: NUKIDevice (nuki_haustuer) - Received webhook for matching NukiId at device nuki_haustuer
2019.11.18 14:10:49 4: NUKIDevice (nuki_haustuer) - Received webhook for matching NukiId at device nuki_haustuer
2019.11.18 14:24:43 4: NUKIDevice (nuki_haustuer) - Received webhook for matching NukiId at device nuki_haustuer
Internals:
CFGFN
DEF 476030020 IODev=nuki_bridge
FUUID 5dd1701e-f33f-0759-c4b2-1643840f8bf88235
IODev nuki_bridge
NAME nuki_haustuer
NR 1757
NUKIID 476030020
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.4
WEBHOOK_COUNTER 8
WEBHOOK_LAST 2019-11-18 14:10:49
WEBHOOK_PORT 9081
WEBHOOK_REGISTER sent
WEBHOOK_URI /WEBNUKI/NUKIDevice
WEBHOOK_URL http://192.168.178.20:9081/WEBNUKI/NUKIDevice-476030020
Helper:
DBLOG:
battery:
logdb:
TIME 1574082649.56157
VALUE ok
batteryCritical:
logdb:
TIME 1574082649.56157
VALUE 0
batteryState:
logdb:
TIME 1574082649.56157
VALUE ok
lockState:
logdb:
TIME 1574082649.56157
VALUE unlocked
name:
logdb:
TIME 1574082718.91023
VALUE Nuki_1C5FA444
paired:
logdb:
TIME 1574082718.91023
VALUE 1
rssi:
logdb:
TIME 1574082718.91023
VALUE -51
state:
logdb:
TIME 1574082649.56157
VALUE unlocked
success:
logdb:
TIME 1574075800.51071
VALUE 1
READINGS:
2019-11-18 14:10:49 battery ok
2019-11-18 14:10:49 batteryCritical 0
2019-11-18 14:10:49 batteryState ok
2019-11-18 14:10:49 lockState unlocked
2019-11-18 14:11:58 name Nuki_1C5FA444
2019-11-18 14:11:58 paired 1
2019-11-18 14:11:58 rssi -51
2019-11-18 14:10:49 state unlocked
2019-11-18 12:16:40 success 1
fhem:
infix NUKIDevice
helper:
fromAutocreate 1
Attributes:
DbLogExclude .*
DbLogInclude .*
IODev nuki_bridge
alias Haustür
devStateIcon open:fts_door_right_open@red locked:fts_door_right@green unlocked:fts_door_right@yellow
group Sicherheit
icon nuki_lock
room ControlCenter,Erdgeschoss
verbose 4
webhookFWinstance WEBNUKI
webhookHttpHostname 192.168.178.20
get nuki_bridge logFile
macht gar nichts (sollte da ein Popup kommen?)
Internals:
BRIDGEAPI 1.6
DEF nukibridge.ah.home XXXXX
FUUID 5dd03016-f33f-0759-18dd-a93f3a06b7460d18
HOST nukibridge.ah.home
NAME nuki_bridge
NR 468
PORT 8080
STATE connected
TOKEN EOUpkh
TYPE NUKIBridge
VERSION 0.6.4
READINGS:
2019-11-17 17:06:54 0_name Haust�r
2019-11-17 17:06:54 0_nukiId 476030020
2019-11-18 14:57:08 bridgeType Hardware
2019-11-18 14:57:08 currentTime 2019-11-18T13:57:13+00:00
2019-11-18 14:57:08 firmwareVersion 2.2.13
2019-11-18 14:57:08 hardwareId 444324306
2019-11-17 17:36:25 lastError read from http://nukibridge.ah.home:8080 timed out
2019-11-18 14:57:08 serverConnected 1
2019-11-18 14:57:08 serverId 801476865
2019-11-17 17:06:54 smartlockCount 1
2019-11-18 14:57:08 state connected
2019-11-18 14:57:08 uptime 1721
2019-11-18 14:57:08 wifiFirmwareVersion 2.0.0
helper:
aliveCount 0
Attributes:
DbLogExclude .*
devStateIcon connected:nuki_bridge@green .*:nuki_bridge@red
group ServerConnections,Sicherheit
icon nuki_bridge
room Server
Zitat von: eddy242 am 18 November 2019, 15:01:08
Ist eine größere FHEM Installation wo schon einiges los ist, die meisten Devices, die viele (nutzlose) Events generieren, sind mit event-min-interval etc runtergedämpft. Fhem läuft containerized auf leistungstarker HW, durchschnittlich ist die CPU bei >20 Containern eher bei 20%, im Peak mal 60%, aber fernab von Vollauslastung. Das Heimnetz ist eigentlich auch ganz gut geölt und zeigt keine Probleme. WLAN Access points sind von Unifi, die NUKI Bridge hat guten Empfang. Sonst läuft FHEM auch rund, keine Unregelmäßigkeiten. Ich lege jetzt mal ein DOIF an das alle 20min pollt aber das ist ja nicht Sinn der Sache.
Was mir noch auffiel, kann es an der Bridge liegen. Der letzte von mir bewusst ausgelöste Neustart war gesten Nachmittag, jetzt ist die Uptime 1721, d.h. vorhin beim experimentieren muss sich das Ding rebootet haben, obwohl ich nichts dergleichen veranlasst habe. Kann das die Spur sein?Code Auswählenget nuki_bridge logFile
macht gar nichts (sollte da ein Popup kommen?)Code Auswählen
Internals:
BRIDGEAPI 1.6
DEF nukibridge.ah.home XXXXX
FUUID 5dd03016-f33f-0759-18dd-a93f3a06b7460d18
HOST nukibridge.ah.home
NAME nuki_bridge
NR 468
PORT 8080
STATE connected
TOKEN EOUpkh
TYPE NUKIBridge
VERSION 0.6.4
READINGS:
2019-11-17 17:06:54 0_name Haust�r
2019-11-17 17:06:54 0_nukiId 476030020
2019-11-18 14:57:08 bridgeType Hardware
2019-11-18 14:57:08 currentTime 2019-11-18T13:57:13+00:00
2019-11-18 14:57:08 firmwareVersion 2.2.13
2019-11-18 14:57:08 hardwareId 444324306
2019-11-17 17:36:25 lastError read from http://nukibridge.ah.home:8080 timed out
2019-11-18 14:57:08 serverConnected 1
2019-11-18 14:57:08 serverId 801476865
2019-11-17 17:06:54 smartlockCount 1
2019-11-18 14:57:08 state connected
2019-11-18 14:57:08 uptime 1721
2019-11-18 14:57:08 wifiFirmwareVersion 2.0.0
helper:
aliveCount 0
Attributes:
DbLogExclude .*
devStateIcon connected:nuki_bridge@green .*:nuki_bridge@red
group ServerConnections,Sicherheit
icon nuki_bridge
room Server
Callback-ID Callback-URL
0 http://192.168.1.10:8083/fhem/NUKIDevice-440953477
1 http://192.168.1.10:8084:8083/fhem/NUKIDevice-440953477
Internals:
DEF 440953477 IODev=NBridge
FUUID 5dd81b25-f33f-2ed4-933a-cd8057e4d1bb2415
FVERSION 74_NUKIDevice.pm:v0.6.4-s20027/2019-08-20
IODev NBridge
NAME NUKIDevice440953477
NR 1053
NUKIID 440953477
STATE unlocked
TYPE NUKIDevice
VERSION 0.6.4
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8084
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.1.10:8084/fhem/NUKIDevice-440953477
READINGS:
2019-11-22 18:30:15 battery ok
2019-11-22 18:30:15 batteryCritical 0
2019-11-22 18:30:15 batteryState ok
2019-11-22 18:30:15 lockState unlocked
2019-11-23 13:14:12 name Nuki_1A486A85
2019-11-23 13:14:12 paired 1
2019-11-23 13:14:12 rssi -58
2019-11-22 18:30:15 state unlocked
2019-11-22 18:30:15 success 1
fhem:
infix NUKIDevice
helper:
Attributes:
IODev NBridge
alias Josef-Tuschl 5
devStateIcon unlocked:nuki_lock@orange open:nuki_lock@red locked:nuki_lock@green
icon nuki_lock
room Haus,Sicherheit
verbose 5
webhookFWinstance WEBNUKI
webhookHttpHostname 192.168.1.10
Internals:
BRIDGEAPI 1.6
CHANGED
DEF 192.168.1.104 xxxx
FUUID 5dc1cd66-f33f-2ed4-8d9d-87ec304f26630cc2
FVERSION 73_NUKIBridge.pm:v0.6.4-s20027/2019-08-20
HOST 192.168.1.104
NAME NBridge
NR 1045
PORT 8080
STATE connected
TOKEN xxx
TYPE NUKIBridge
VERSION 0.6.4
READINGS:
2019-11-22 18:30:13 0_name Josef-Tuschl 5
2019-11-22 18:30:13 0_nukiId 440953477
2019-11-23 13:14:39 bridgeType Hardware
2019-11-23 13:14:39 currentTime 2019-11-23T12:14:39+00:00
2019-11-23 13:14:39 firmwareVersion 2.3.0
2019-11-23 13:14:39 hardwareId 409057010
2019-11-23 11:45:45 lastError read from http://192.168.1.104:8080 timed out
2019-11-23 13:14:39 serverConnected 1
2019-11-23 13:14:39 serverId 963197504
2019-11-22 18:30:13 smartlockCount 1
2019-11-23 13:14:39 state connected
2019-11-23 13:14:39 uptime 5390
2019-11-23 13:14:39 wifiFirmwareVersion 2.0.0
helper:
aliveCount 0
Attributes:
devStateIcon connected:nuki_bridge@green disconnected:nuki_bridge@red
event-on-change-reading state
icon nuki_bridge
room Sicherheit
verbose 5
0 http://192.168.1.10:8083/fhem/NUKIDevice-440953477
1 http://192.168.1.10:8084:8083/fhem/NUKIDevice-440953477
2 http://192.168.1.10:8084/fhem/NUKIDevice-440953477
Zitat von: CoolTux am 29 November 2019, 11:41:59
Mach mal bitte ein list von der Bridge und dem Nuki Schloß
Zitat von: casi am 29 November 2019, 11:57:17
Sorry, wie mache ich das genau? :-[
einfach den Programmcode, wie er in der fhem.cfg steht ..?
oder einen Befehl in der Kommandozeile ausführen?
Internals:
BRIDGEAPI 1.6
DEF 192.168.178.150 abcdef
FUUID 12345678-abcd-dcba-4321-123456789123456789
HOST 192.168.178.150
NAME NukiBridge
NR 70
PORT 8080
STATE connected
TOKEN abcdef
TYPE NUKIBridge
VERSION 0.6.4
READINGS:
2019-11-29 12:35:18 bridgeType Hardware
2019-11-29 12:35:18 currentTime 2019-11-29T11:35:18+00:00
2019-11-29 12:35:18 firmwareVersion 2.4.8
2019-11-29 12:35:18 hardwareId 441180000
2019-11-29 12:35:18 serverConnected 1
2019-11-29 12:35:18 serverId 2299079111
2019-11-29 12:35:18 state connected
2019-11-29 12:35:18 uptime 573708
2019-11-29 12:35:18 wifiFirmwareVersion 2.1.4
helper:
aliveCount 0
Attributes:
icon nuki_bridge
room NUKI
Internals:
DEF 543210005 IODev=NukiBridge
FUUID 12345678-abcd-dcba-4321-123456789123456789
IODev NukiBridge
NAME NUKIDevice543210005
NR 72
NUKIID 543210005
STATE locked
TYPE NUKIDevice
VERSION 0.6.4
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8086
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIDevice
WEBHOOK_URL http://192.168.178.147:8086/fhem/NUKIDevice-543210005
READINGS:
2019-11-29 04:01:43 battery ok
2019-11-29 04:01:43 batteryCritical 0
2019-11-29 04:01:43 batteryState ok
2019-11-29 04:01:43 lockState locked
2019-11-29 12:43:33 name Nuki_1ABG345F
2019-11-29 12:43:33 paired 1
2019-11-29 12:43:33 rssi -59
2019-11-29 04:01:43 state locked
2019-11-29 04:01:43 success 1
fhem:
infix NUKIDevice
helper:
Attributes:
IODev NukiBridge
alias Nuki
devStateIcon open:fts_door_right_open@red locked:fts_door_right@green unlocked:fts_door_right@yellow
icon nuki_lock
room NUKI
webhookFWinstance WEBnuki
webhookHttpHostname 192.168.178.147
Zitat von: CoolTux am 29 November 2019, 13:17:29
Sieht soweit ok aus. Und wenn Du bei der Bridge nun get callBacklist ausführst kommt eine Fehlermeldung?
Zitat von: CoolTux am 29 November 2019, 13:17:29
Mach mal bitte bei der Bridge das Attribut verbose auf 5 setzen und dann ein get callBacklist und schaue ins Log was dazu steht.
2019.11.29 13:46:44 5: NUKIBridge (NukiBridge) - Response JSON: [{"deviceType": 0, "nukiId": 543210005, "name": "Nuki", "firmwareVersion": "2.6.4", "lastKnownState": {"mode": 2, "state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2019-11-29T12:45:16+00:00"}}, {"deviceType": 2, "nukiId": 543210078, "name": "Opener", "firmwareVersion": "1.2.7", "lastKnownState": {"mode": 2, "state": 1, "stateName": "online", "batteryCritical": false, "timestamp": "2019-11-29T10:28:53+00:00"}}]
2019.11.29 13:46:44 5: NUKIBridge (NukiBridge) - Response ERROR:
2019.11.29 13:46:44 5: NUKIBridge (NukiBridge) - Response CODE: 200
2019.11.29 13:46:44 3: NUKIDevice (NukiBridge) - NukiId '543210005' already defined as 'NUKIDevice543210005'
2019.11.29 13:46:44 3: NUKIDevice (NukiBridge) - NukiId '543210078' already defined as 'NUKIDevice543210078'
2019.11.29 13:46:44 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.150:8080/info?token=abcdef
2019.11.29 13:58:10 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.150:8080/info?token=abcdef
2019.11.29 13:58:10 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2019.11.29 13:58:10 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2019.11.29 13:58:10 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 441180000, "serverId": 2299079111}, "versions": {"firmwareVersion": "2.4.8", "wifiFirmwareVersion": "2.1.4"}, "uptime": 578675, "currentTime": "2019-11-29T12:58:08+00:00", "wlanConnected": true, "serverConnected": true, "scanResults": [{"deviceType": 2, "nukiId": 543210078, "name": "Nuki_Opener_1CAAFFFF", "rssi": -73, "paired": true}, {"deviceType": 0, "nukiId": 543210005, "name": "Nuki_1AF3FFFF", "rssi": -55, "paired": true}]}
2019.11.29 13:58:10 5: NUKIBridge (NukiBridge) - Response ERROR:
2019.11.29 13:58:10 5: NUKIBridge (NukiBridge) - Response CODE: 200
2019.11.29 13:58:10 5: NUKIBridge (NukiBridge) - Bridge ist online
2019.11.29 13:58:10 4: NUKIDevice (NUKIDevice543210078) - Received scanResults for matching NukiID 543210078 at device NUKIDevice543210078
2019.11.29 13:58:10 4: NUKIDevice (NUKIDevice543210005) - Received scanResults for matching NukiID 543210005 at device NUKIDevice543210005
2019.11.29 13:58:18 5: NUKIBridge (NukiBridge) - Data: {"callbacks": []}
2019.11.29 13:58:18 4: NUKIBridge (NukiBridge) - Blocking HTTP Query finished
2019.11.29 13:58:18 4: NUKIBridge (NukiBridge) - Callback data is collected and processed
Zitat von: CoolTux am 29 November 2019, 14:25:58
Hat er Recht. Es sind keine Daten zum Callback vorhanden. Kannst du bitte eines der Weebhook Attribute noch mal setzen und dann im Log noch mal schauen.
0 http://192.168.178.147:8086/fhem/NUKIDevice-543210005
1 http://192.168.178.147:8086/fhem/NUKIDevice-543210005
2019.11.29 14:49:49 5: NUKIBridge (NukiBridge) - Data: {"callbacks": [{"id": 0, "url": "http://192.168.178.147:8086/fhem/NUKIDevice-543210005"},{"id": 1, "url": "http://192.168.178.147:8086/fhem/NUKIDevice-543210005"}]}
2019.11.29 14:49:49 4: NUKIBridge (NukiBridge) - Blocking HTTP Query finished
2019.11.29 14:49:49 4: NUKIBridge (NukiBridge) - Callback data is collected and processed
2019.11.29 14:49:49 4: NUKIBridge (NukiBridge) - created Table with log file
2019.11.29 14:49:50 4: NUKIBridge (NukiBridge) - NUKIBridge_GetCheckBridgeAlive
2019.11.29 14:49:50 4: NUKIBridge (NukiBridge) - Send HTTP POST with URL http://192.168.178.150:8080/info?token=abcdef
2019.11.29 14:49:50 4: NUKIBridge (NukiBridge) - run NUKIBridge_Call
2019.11.29 14:49:50 4: NUKIBridge (NukiBridge) - Call InternalTimer for NUKIBridge_GetCheckBridgeAlive
2019.11.29 14:49:50 5: NUKIBridge (NukiBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 441180000, "serverId": 2299079111}, "versions": {"firmwareVersion": "2.4.8", "wifiFirmwareVersion": "2.1.4"}, "uptime": 581771, "currentTime": "2019-11-29T13:49:48+00:00", "wlanConnected": true, "serverConnected": true, "scanResults": [{"deviceType": 2, "nukiId": 543210078, "name": "Nuki_Opener_1CAAFFFF", "rssi": -73, "paired": true}, {"deviceType": 0, "nukiId": 543210005, "name": "Nuki_1AF3FFFF", "rssi": -55, "paired": true}]}
2019.11.29 14:49:50 5: NUKIBridge (NukiBridge) - Response ERROR:
2019.11.29 14:49:50 5: NUKIBridge (NukiBridge) - Response CODE: 200
2019.11.29 14:49:50 5: NUKIBridge (NukiBridge) - Bridge ist online
2019.11.29 14:49:50 4: NUKIDevice (NUKIDevice543210078) - Received scanResults for matching NukiID 543210078 at device NUKIDevice543210078
2019.11.29 14:49:50 4: NUKIDevice (NUKIDevice543210005) - Received scanResults for matching NukiID 543210005 at device NUKIDevice543210005
Zitat von: CoolTux am 29 November 2019, 15:12:45
Und wieder so ein typischer Fall warum ich sowas nicht mag wenn Leute die Konfig von Hand editieren. Aber egal.
Zitat von: CoolTux am 29 November 2019, 15:12:45
Absichern kannst mit einem allowed Device. Da kannst den Zugriff auf eine einzige IP beschränken zum Beispiel.
/callback
The following endpoints provide methods to register up to 3 http (no https) url callbacks, which will be triggered once the lock state of one of the known Smart Locks changes.
The new lock state will be sent to the callback url by executing a POST request and posting a JSON list in the following format:
{"nukiId": 11, "deviceType": 0, "mode": 2, "state": 1, "stateName": "locked", "batteryCritical": false}
battery | ok | 2019-12-14 05:59:42 |
batteryCritical | 0 | 2019-12-14 05:59:42 |
batteryState | ok | 2019-12-14 05:59:42 |
Zitat von: CoolTux am 16 Dezember 2019, 12:40:43auch bei mir hat das nicht geklappt.
Verstehe ich das richtig das einCode Auswählenset NUKIBRIDGE fwUpdate
nicht geklappt hat?
Zitat von: Andy89 am 16 Dezember 2019, 16:26:58
auch bei mir hat das nicht geklappt.
Ich habe dann auch das Fhem Bridge Device disabled und den manuellen http fwupdate Befehl gestartet. In der Nacht wurde dann das Update ausgeführt..
Davor habt wohl fhem das Update verhindet, indem es Befehle/Anfragen an die Bridge gesendet hat. Irgendwo im Nuki Forum hab ich gelesen, dass man auch keine info Anfrage an die Bridge senden soll, wenn man den fwupdate Befehl absetzt. Nur deswegen bin ich darauf gekommen, dass ich es in Fhem deaktiviere.
Beste Grüße
Andy
Zitat von: Thyraz am 18 Dezember 2019, 11:34:14done
Ich kann nur jeden ermutigen hier:
https://developer.nuki.io/t/nuki-bridge-api-bell-ring-of-nuki-opener-as-trigger-for-callbacks/2557/8
- einen Vote für den Featurerequest abzugeben
- ein Post in dem Thread zu hinterlassen, dass eine SmartHome Implementierung des Openers damit ziemlich nutzlos ist und dies schnellstens nachgerüstet werden sollte.
2019.12.23 10:35:24 1: reload: Error:Modul 73_NUKIBridge deactivated:
Excessively long <> operator at ./FHEM/73_NUKIBridge.pm line 21, <$fh> line 79.
2019.12.23 10:35:24 0: Excessively long <> operator at ./FHEM/73_NUKIBridge.pm line 21, <$fh> line 79.
2019.12.23 10:35:24 1: reload: Error:Modul 74_NUKIDevice deactivated:
Excessively long <> operator at ./FHEM/74_NUKIDevice.pm line 21, <$fh> line 30.
2019.12.23 10:35:24 0: Excessively long <> operator at ./FHEM/74_NUKIDevice.pm line 21, <$fh> line 30.
2019.12.23 10:35:24 1: reload: Error:Modul 74_NUKIDevice deactivated:
Excessively long <> operator at ./FHEM/74_NUKIDevice.pm line 21, <$fh> line 48.
2019.12.23 10:35:24 0: Excessively long <> operator at ./FHEM/74_NUKIDevice.pm line 21, <$fh> line 48.
2019.12.23 10:35:33 1: configfile: Cannot load module NUKIBridge
Zitat von: Thyraz am 21 Dezember 2019, 22:13:45
So, wer will kann hier mal eine erste Version mit Support für den Opener runterladen und testen:
https://github.com/Thyraz/NUKI/tree/Opener
Die Attribute für den Webhook müssen nach Einspielen und FHEM Restart dann nochmal im Bridge Device angelegt werden,
da der Webhook dann nicht mehr pro Device läuft, sondern das Bridge Modul die einkommenden Events an die einzelnen Nuki Devices verteilt.
Da der Opener bei dem meisten ja sicher schon per Bridge Autocreate als nicht funktionelles Device angelegt wurde,
dieses nochmal löschen und dann nochmal den autocreate set Befehl in der Bridge ausführen.
Danach sollte der Opener neu angelegt werden und mit entsprechenden Readings und den passenden Set-Befehlen ausgestattet werden.
Sofern es bei euch zu keinen Problemen kommt, erstell ich für Cooltux einen Pull-Request auf Github.
P.S. da meine Erfahrung mit FHEM Entwicklungs-Internas noch nicht sooo ausgeprägt sind, empfiehlt sich evtl. ein Backup vor dem Test. ;)
Zitat von: CoolTux am 09 Januar 2020, 17:26:43
Ich bin mit den ersten Umbauten soweit durch und würde mich über Tester sehr freuen
https://github.com/fhem/NUKI/archive/devel.zip
Files einspielen und dann FHEM neustarten. Danach warten bis das rote Fragezeichen oben bei "save config" erscheint. Dann auf "save config" drücken und noch mal neustarten bitte. Danach muß im Bridge Device noch der Webhook eingerichtet werden.
Ich bilde mir ein das ich das mit dem 501 nun besser in den Griff bekommen habe. Habe beim testen raus gefunden das der 501 immer nach einer Lock Aktion gekommen ist.
Grüße
Internals:
CFGFN
DEF 333550209 0
DEVICETYPE 0
FUUID 5e17818d-f33f-810c-8ba0-d4a8ac5d0d61d11d
IODev NUKI
LASTInputDev NUKI
MSGCNT 40
NAME Home
NR 22
NUKIID 333550209
NUKI_MSGCNT 40
NUKI_TIME 2020-01-09 20:56:00
STATE unlocked
TYPE NUKIDevice
VERSION 0.7.11
READINGS:
2020-01-09 20:40:07 batteryCritical 0
2020-01-09 20:40:07 batteryState ok
2020-01-09 20:40:07 lockState unlocked
2020-01-09 20:56:00 name Nuki_13E19281
2020-01-09 20:56:00 paired 1
2020-01-09 20:56:00 rssi -79
2020-01-09 20:40:07 state unlocked
2020-01-09 20:40:07 success 1
helper:
Attributes:
IODev NUKI
model smartlock
room NUKI
Unknown argument getDeviceList, choose one of info getDeviceList callbackRemove clearLog fwUpdate reboot factoryReset
Zitat von: enno am 09 Januar 2020, 21:30:08
Moin CoolTux,
wenn ich in der Nuki Bridge auf set NUKI getDeviceList klicke bekomme ich eine Fehlermeldung:Code AuswählenUnknown argument getDeviceList, choose one of info getDeviceList callbackRemove clearLog fwUpdate reboot factoryReset
....
@Obelix ich trage mich dort gerade ein.
Gruss
Enno
Zitat von: CoolTux am 09 Januar 2020, 19:52:30
Komisch. Eigentlich hätte er das übernehmen sollen und nicht ein neues Device anlegen. Aber cool das alles soweit rennt.
Kannst Du mir ein list vom NUKIDevice geben?
Internals:
CFGFN
DEF 460817874 2
DEVICETYPE 2
FUUID xxxxxxxx
IODev NBridge1
LASTInputDev NBridge1
MSGCNT 392
NAME Nuki_Opener_1B7785D2
NBridge1_MSGCNT 392
NBridge1_TIME 2020-01-09 21:52:10
NR 1088
NUKIID 460817874
STATE online
TYPE NUKIDevice
VERSION 0.7.11
READINGS:
2020-01-09 19:39:59 batteryCritical 0
2020-01-09 19:39:59 batteryState ok
2020-01-09 19:39:59 lockState online
2020-01-09 21:52:10 name Nuki_Opener_1B7785D2
2020-01-09 21:52:10 paired 1
2020-01-09 21:52:10 rssi -76
2020-01-09 19:39:59 state online
2020-01-09 19:39:49 success 1
helper:
Attributes:
IODev NBridge1
alias Intercom
icon 1_nuki_bridge
model opener
room Hall,NUKI
Zitat von: CoolTux am 09 Januar 2020, 17:26:43
Ich bin mit den ersten Umbauten soweit durch und würde mich über Tester sehr freuen
https://github.com/fhem/NUKI/archive/devel.zip
Files einspielen und dann FHEM neustarten. Danach warten bis das rote Fragezeichen oben bei "save config" erscheint. Dann auf "save config" drücken und noch mal neustarten bitte. Danach muß im Bridge Device noch der Webhook eingerichtet werden.
Ich bilde mir ein das ich das mit dem 501 nun besser in den Griff bekommen habe. Habe beim testen raus gefunden das der 501 immer nach einer Lock Aktion gekommen ist.
Grüße
Zitat von: enno am 09 Januar 2020, 20:59:28
Wenn ich jetzt noch in FHEM erkennen könnte, wer die Tür geöffnet hat, dann hätte ich alles was ich brauche. Aber das gibt die API wohl nicht her.
Gruss
Enno
Zitat von: enno am 09 Januar 2020, 21:30:08
Moin CoolTux,
wenn ich in der Nuki Bridge auf set NUKI getDeviceList klicke bekomme ich eine Fehlermeldung:Code AuswählenUnknown argument getDeviceList, choose one of info getDeviceList callbackRemove clearLog fwUpdate reboot factoryReset
....
@Obelix ich trage mich dort gerade ein.
Gruss
Enno
deletereading NAME .*
Unknown argument getDeviceList, choose one of info getDeviceList callbackRemove clearLog fwUpdate reboot factoryReset
NAME NUKIDevice355928989
NBridge1_MSGCNT 25
NBridge1_TIME 2020-01-10 13:09:24
NR 994
NUKIID 355928989
STATE unlocked
TYPE NUKIDevice
VERSION 0.7.27
READINGS:
2020-01-10 13:01:28 batteryState ok
2020-01-10 13:09:24 deviceType smartlock
2020-01-10 13:01:22 firmwareVersion 2.6.4
2020-01-10 13:01:28 mode door mode
2020-01-10 13:09:24 name Nuki_15370B9D
2020-01-10 13:09:24 nukiId 355928989
2020-01-10 13:09:24 paired true
2020-01-10 13:09:24 rssi -79
2020-01-10 13:01:28 state unlocked
2020-01-10 13:01:28 stateName unlocked
2020-01-10 13:01:28 success 1
NAME Nuki_Opener_1B7785D2
NBridge1_MSGCNT 21
NBridge1_TIME 2020-01-10 13:08:27
NR 1070
NUKIID 460817874
STATE online
TYPE NUKIDevice
VERSION 0.7.27
READINGS:
2020-01-10 13:01:22 batteryState ok
2020-01-10 13:08:27 deviceType opener
2020-01-10 13:01:22 firmwareVersion 1.3.1
2020-01-10 13:01:22 mode door mode
2020-01-10 13:08:27 name Nuki_Opener_1B7785D2
2020-01-10 13:08:27 nukiId 460817874
2020-01-10 13:08:27 paired true
2020-01-10 13:08:27 rssi -75
2020-01-10 13:01:22 state online
2020-01-10 13:01:22 stateName online
Zitat von: CoolTux am 10 Januar 2020, 13:24:57
Dann hast du nur NUKIDevice aktualisiert aber nicht NUKIBridge.
Welche Version hat Dein NUKIBridge Device?
TYPE NUKIBridge
VERSION 0.7.22
WEBHOOK_COUNTER 1
WEBHOOK_LAST 2020-01-10 13:19:11
Zitat von: CoolTux am 10 Januar 2020, 14:06:44
Wie sind die neuen Readings im NUKIDevice Device?
Internals:
DEF 123456789 2
DEVICETYPE 2
FUUID 5e1865a0-f33f-398d-3e5d-b5ce3ae7952ed03f
IODev NBridge1
LASTInputDev NBridge1
MSGCNT 363
NAME Nuki_Opener_1CC12345
NBridge1_MSGCNT 363
NBridge1_TIME 2020-01-10 17:24:30
NR 334
NUKIID 123456789
STATE online
TYPE NUKIDevice
VERSION 0.7.27
.attraggr:
.attrminint:
READINGS:
2020-01-10 17:22:01 batteryState ok
2020-01-10 17:24:30 deviceType opener
2020-01-10 17:22:01 mode door mode
2020-01-10 17:24:30 name Nuki_Opener_1CC12345
2020-01-10 17:24:30 nukiId 123456789
2020-01-10 17:24:30 paired true
2020-01-10 17:24:30 rssi -42
2020-01-10 17:22:01 state online
2020-01-10 17:22:01 stateName online
2020-01-10 14:02:59 success 1
helper:
Attributes:
IODev NBridge1
icon 1_nuki_bridge
model opener
room NUKI
Messages collected while initializing FHEM:
configfile: Invalid value for attribute webhookFWinstance: FHEMWEB instance apiWEB not existing
Zitat von: Kuehnhackel am 09 Januar 2020, 22:01:28
Moin, ich würde auch gerne testen. Könntest mal kurz "Files einspielen" erklären falls meine Idee/Überlegung falsch ist?
Einfach die Files per FileZilla in das Verzeichnis /fhem/ kopieren und überschreiben? Rechte eventuell anpassen und dann besagter "Neustart"?
Ralf
Zitat von: danillo am 10 Januar 2020, 17:57:44
Ich hab nochmal eine Frage zum Callback.
Ich habe eine eigene Webinstanz geschaffen, welche nur von der IP der Bridge erreichbar ist.
Ich kann nur beim Attribut webhookFWinstance meine Instanz nicht auswählen. Was aber geht ist, dass ich das Attribut per attr manuell setze. Jetzt funktioniert auch alles. Nur das Attribut webhookFWinstance kann ich nicht sehen unter Attributes.
Beim Systemstart erscheint:Code AuswählenMessages collected while initializing FHEM:
configfile: Invalid value for attribute webhookFWinstance: FHEMWEB instance apiWEB not existing
Zitat von: danillo am 10 Januar 2020, 17:57:44
Ich hab nochmal eine Frage zum Callback.
Ich habe eine eigene Webinstanz geschaffen, welche nur von der IP der Bridge erreichbar ist.
Ich kann nur beim Attribut webhookFWinstance meine Instanz nicht auswählen. Was aber geht ist, dass ich das Attribut per attr manuell setze. Jetzt funktioniert auch alles. Nur das Attribut webhookFWinstance kann ich nicht sehen unter Attributes.
Beim Systemstart erscheint:Code AuswählenMessages collected while initializing FHEM:
configfile: Invalid value for attribute webhookFWinstance: FHEMWEB instance apiWEB not existing
Zitat von: Kuehnhackel am 10 Januar 2020, 18:01:25
Warum antwortet mir keiner?
Zitat von: danillo am 10 Januar 2020, 17:57:44
Ich hab nochmal eine Frage zum Callback.
Ich habe eine eigene Webinstanz geschaffen, welche nur von der IP der Bridge erreichbar ist.
Ich kann nur beim Attribut webhookFWinstance meine Instanz nicht auswählen. Was aber geht ist, dass ich das Attribut per attr manuell setze. Jetzt funktioniert auch alles. Nur das Attribut webhookFWinstance kann ich nicht sehen unter Attributes.
Beim Systemstart erscheint:Code AuswählenMessages collected while initializing FHEM:
configfile: Invalid value for attribute webhookFWinstance: FHEMWEB instance apiWEB not existing
Zitat von: enno am 10 Januar 2020, 19:02:42
Ich mache das über FHEM. Erstmal die Dateien von CoolTux ohne Steuerzeichen (RAW und kein Windowseditor mit Zeilenumbruch!) kopieren. Dann in FHEM Oberfläche "Edit Files" anklicken. Irgend eine Text anklicken. (z.B. "rss.layout") dann dort den Text reinkopieren. Wichtig unter "Save as" den Namen der Datei (z.B. "74_NUKIDevice.pm") eintragen.
Das mit beiden Dateien machen: Dann "Shutdown Reload"...
Auf diese Weise gibt es auch keine Probleme mit irgendwelchen Rechten.
Gruss
Enno
Zitat von: Kuehnhackel am 10 Januar 2020, 21:23:11
Achja, jetzt fehlt noch das Firmwareupdate. Geht das jetzt über FHEM, oder wie muss ich das anstoßen?
2020.01.11 09:41:50 3: NUKIDevice (NBridge1) - empty answer received for http://192.168.0.2:8080/fwupdate?token=blabla
Internals:
BRIDGEAPI 1.9
DEF 192.168.0.2 blabla
FUUID 5e1834b4-f33f-398d-b739-c59854d2546dc12f
HOST 192.168.0.2
NAME NBridge1
NR 332
PORT 8080
STATE connected
TOKEN blabla
TYPE NUKIBridge
VERSION 0.7.22
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.0.2
WEBHOOK_URL http://192.168.0.219:8083/fhem/NUKIBridge-192.168.0.2
.attraggr:
.attrminint:
.clientArray:
NUKIDevice
READINGS:
2020-01-11 10:24:19 bridgeType Hardware
2020-01-11 10:24:19 currentTime 2020-01-11T09:24:20+00:00
2020-01-11 10:24:19 firmwareVersion 2.3.0
2020-01-11 10:24:19 hardwareId 123456789
2020-01-10 22:38:17 lastError read from http://192.168.0.2:8080 timed out
2020-01-11 10:24:19 serverConnected 1
2020-01-11 10:24:19 serverId 87654321
2020-01-11 10:24:19 state connected
2020-01-11 10:24:19 uptime 1267
2020-01-11 10:24:19 wifiFirmwareVersion 2.0.0
fhem:
infix NUKIBridge
helper:
aliveCount 0
iowrite 0
Attributes:
icon nuki_bridge
room NUKI
webhookFWinstance WEB
webhookHttpHostname 192.168.0.219
Zitat von: Kuehnhackel am 10 Januar 2020, 21:23:11
Achja, jetzt fehlt noch das Firmwareupdate. Geht das jetzt über FHEM, oder wie muss ich das anstoßen?
http://192.168.1.50:8080/fwupdate?token=123456
oder in FHEM anstoßen. Über Browser die entsprechende IP deiner Bridge vor 8080 eingeben, sowie dein individuellen Token.Zitat von: CoolTux am 10 Januar 2020, 19:50:28Jetzt muss ich ganz doof fragen. Hier: https://github.com/fhem/ herunterladen?
Ich habe das Problem gefixt. Bitte die neuen Files aus dem Git laden und testen.
Zitat von: danillo am 11 Januar 2020, 11:27:24
Jetzt muss ich ganz doof fragen. Hier: https://github.com/fhem/ herunterladen?
Zitat von: OdfFhem am 11 Januar 2020, 10:58:58
@BM030
Laut Deinem list hat die Bridge die Firmware-Version 2.3.0.
Diese Firmware-Version hat meine Bridge automatisch im Nov. 2019 eingespielt. Der Sprung auf die Folgeversion 2.4.x ist lt. Hersteller ein großer Schritt, der nicht gestört werden darf; ein aktives NUKIBridge-Device ist dabei mehr als hinderlich. Evtl. hilfreich könnte folgender Link sein: https://forum.fhem.de/index.php/topic,55756.msg1002362.html#msg1002362 (https://forum.fhem.de/index.php/topic,55756.msg1002362.html#msg1002362)
Aktuell hat meine Bridge seit Mitte Dezember Firmware-Version 2.4.21 - wurde wieder automatisch eingespielt.
Zitat von: CoolTux am 11 Januar 2020, 11:29:43hm, vielleicht stell ich mich da auch zu doof an. Ich hab die Datei nach opt/fhem/FHEM geladen und dann mit chown noch fhem zugewiesen. Wenn ich dann neu starte kommt
JA genau.
https://github.com/fhem/NUKI
Messages collected while initializing FHEM:
configfile: Cannot load module NUKIDevice
Please define NUKIDevice99247689 5e18a50e-f33f-8009-f3db-ca952425a9fd2e8e first
Zitat von: danillo am 11 Januar 2020, 14:28:39
hm, vielleicht stell ich mich da auch zu doof an. Ich hab die Datei nach opt/fhem/FHEM geladen und dann mit chown noch fhem zugewiesen. Wenn ich dann neu starte kommtCode AuswählenMessages collected while initializing FHEM:
configfile: Cannot load module NUKIDevice
Please define NUKIDevice99247689 5e18a50e-f33f-8009-f3db-ca952425a9fd2e8e first
Zitat von: danillo am 11 Januar 2020, 14:28:39
hm, vielleicht stell ich mich da auch zu doof an. Ich hab die Datei nach opt/fhem/FHEM geladen und dann mit chown noch fhem zugewiesen. Wenn ich dann neu starte kommtCode AuswählenMessages collected while initializing FHEM:
configfile: Cannot load module NUKIDevice
Please define NUKIDevice99247689 5e18a50e-f33f-8009-f3db-ca952425a9fd2e8e first
wget https://github.com/fhem/NUKI/raw/devel/73_NUKIBridge.pm
wget https://github.com/fhem/NUKI/raw/devel/74_NUKIDevice.pm
Zitat von: fred_feuerstein am 11 Januar 2020, 15:25:49
Gerade gesehen, es gibt eine neue bridge api Doku v1.10 vom 07.01.2020.
Changelog:
● Introduced Simple lock actions for all usecases where the logic should be handled
by the device itself.
● Made wording for Nuki devices more general.
Hast du das schon gesehen? In deinem git ist noch die 1.09 hinterlegt.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Zitat von: fred_feuerstein am 11 Januar 2020, 15:49:35
Welche bridge hast du? V1 oder v2?
Bei meiner V1 ist die Firmware 1.13.1
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Zitat von: moskito am 11 Januar 2020, 19:00:24
Mir ist eben noch was aufgefallen:
Ein "set <devicename> callbackRemove" meldet immer "Success Callback id=0 removed"
Eine Auswahl wie früher wird nicht mehr angezeigt.
Version 0.7.22
Gruß
Danny
set <devicename> callbackRemove" <id>
Zitat von: fred_feuerstein am 11 Januar 2020, 15:25:49
Gerade gesehen, es gibt eine neue bridge api Doku v1.10 vom 07.01.2020.
Changelog:
● Introduced Simple lock actions for all usecases where the logic should be handled
by the device itself.
● Made wording for Nuki devices more general.
Hast du das schon gesehen? In deinem git ist noch die 1.09 hinterlegt.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Zitat von: fred_feuerstein am 13 Januar 2020, 07:27:09
Ich hatte einen link auch zu dem nuki dev forum. Den findet man aktuell noch über Google. Allerdings läuft er nun ins Leere und findet keine Datei mehr. ( Suche nach nuki bridge api 1.10)
Hatte das dok aber noch auf dem Handy und habs mal in die Dropbox gelegt.
https://www.dropbox.com/s/smjaln5by123ore/20200107NukiBridgeAPI1_10.pdf?dl=1
Könnte sein, dass nuki diese api vorerst wieder zurückgezogen hat? Keine Ahnung.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Zitat von: slor am 13 Januar 2020, 16:11:09siehe hier weiter oben « Antwort #1418 am: 09 Januar 2020, 22:03:25 » und dann hier bei Nuki voten ;)
Am besten natürlich eine Info, welcher Code gerade die Tür geöffnet hat, oder welches Handy via app. Geht das?
Zitat von: ViRaZ am 14 Januar 2020, 21:01:27
Habe dir die Dateien hochgeladen.
Vielen Dank für deine Hilfe!
Send HTTP POST with URL http://10.6.34.52:8080/list?token=7crtn1
2020.01.14 21:14:33.456 4: NUKIBridge (myNukiBridge) - Response JSON: [{"deviceType": 0, "nukiId": 140395513, "name": "WgTuer", "firmwareVersion": "1.8.1", "lastKnownState": {"mode": 2, "state": 3, "stateName": "unlocked", "batteryCritical": false, "timestamp": "2020-01-14T20:13:22+00:00"}}]
Zitat von: danillo am 15 Januar 2020, 20:26:01
Hallo zusammen,
die Fehlermeldungen sind bei mir jetzt weg. Ich hatte ja das Attribut webhookFWinstance von Hand gesetzt. Nach dem Update hat sie Fhem ständig aufgehängt. Ich musste alle Nukigeräte in der fhem.cfg von Hand entfernen. Dann hab ich sie nochmal angelegt. Funktioniert jetzt soweit. Aber das Attribut webhookFWinstance gibt's jetzt gar nicht mehr in der Auswahl. Ebenso wie webhookHttpHostname. Kann ich die noch setzen? Ich würde ja gerne wieder eine andere Webinstanz verwenden für den Callback.
Zitat von: Wscheff am 15 Januar 2020, 22:01:11
Hi zusammen.
Kann es sein, dass beim set callbackRemove der Parameter ID fehlt. Oder wo kann man das angeben?
Hatte nämlich Mist eingetragen und konnte das nur von Hand wieder aus der Bridge entfernen.
Zitat von: CoolTux am 15 Januar 2020, 22:10:04
Derfehlt in der Tat. Das hat was mit der nächsten Ausbaustufe zu tun. Du kannst ihn aber von Hand löschen in dem Du set NUKIBRIDGE callbackRemove id in der FHEM Kommandozeile ein gibst.
Zitat von: Wscheff am 15 Januar 2020, 22:20:17
Danke für die schnelle Rückmeldung. Ich hatte es mir natürlich nicht so einfach gemacht, und erstmal in der Bridge API gekramt und das via Browser erledigt.
*** Danke für das tolle Modul, freue mich auf die Nächste Ausbaustufe
PERL WARNING: Use of uninitialized value $v in pattern match (m//) at ./FHEM/74_NUKIDevice.pm line 580.
Zitat von: CoolTux am 15 Januar 2020, 21:01:50Das hab ich jetzt erledigt. Auch die anderen CallBack-Einträge habe ich gelöscht. Geht aber leider nicht :-(
Diese Attribute werden jetzt im Bridge Device gesetzt.
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8088
WEBHOOK_REGISTER sent
WEBHOOK_URI /webhook/NUKIBridge-192.168.178.64
WEBHOOK_URL http://192.168.178.32:8088/webhook/NUKIBridge-192.168.178.64
webhookFWinstance apiWEB
webhookHttpHostname 192.168.178.32
Zitat von: CoolTux am 16 Januar 2020, 07:54:20
Ich gehe davon aus das es der selbe webhook ist der beim alten Modul funktioniert hat? Zeig mal bitte das Ergebnis eines get callbackList. Gerne auch als Screen
Callback-ID Callback-URL
2 http://192.168.178.32:8088/webhook/NUKIDevice-99247689
Zitat von: CoolTux am 16 Januar 2020, 08:48:57
Nein das passt schon soweit. Aber Du kannst den mal komplett löschen.
In der FHEM Kommandozeile
set NUKIBRIDGEDEVICENAME callbackRemove 2
eingeben und dann noch mal ein get calbackList und wenn da nichts kommt dann einfach kurz auf webhookFWinstance klicken und dann auf das attr wenn dort webhookFWinstance dahinter steht.
Danach noch mal das get und dann müsste da etwas kommen.
Zitat von: CoolTux am 16 Januar 2020, 08:48:57
Nein das passt schon soweit. Aber Du kannst den mal komplett löschen.
In der FHEM Kommandozeile
set NUKIBRIDGEDEVICENAME callbackRemove 2
eingeben und dann noch mal ein get calbackList und wenn da nichts kommt dann einfach kurz auf webhookFWinstance klicken und dann auf das attr wenn dort webhookFWinstance dahinter steht.
Danach noch mal das get und dann müsste da etwas kommen.
Zitat von: CoolTux am 16 Januar 2020, 07:16:41
Welche Version verwendest Du?
Zitat von: CoolTux am 16 Januar 2020, 23:59:09
Startest Du FHEM zufällig täglich neu? Ist die Uhrzeit eine Zeit wo das Schloss geschalten wird?
Zitat von: PatrickR am 18 Januar 2020, 02:33:43
Guten Abend/Morgen zusammen!
Habe gerade den Callback eingerichtet, was ein ganzes Stück Arbeit war. Wie kann ich ihn testen bzw. einen Aufruf erzwingen?
Patrick
Zitat von: Kuehnhackel am 18 Januar 2020, 20:05:46Callback eingerichtet und ohne Passwort für Bridge erreichbar?
Erst wenn ich einen set StatusRequest im Nuki ausführe ändern sich die states
autocreate: define Terrasse NUKIDevice 123456789
2020.01.19 13:18:19 1: define Terrasse NUKIDevice 123456789 : too few parameters: define <name> NUKIDevice <nukiId> <deviceType>
2020.01.19 13:18:19 1: ERROR: too few parameters: define <name> NUKIDevice <nukiId> <deviceType>
define Terrasse NUKIDevice 123456789 smartlock
2020.01.18 14:00:05 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/74_NUKIDevice.pm line 414.
2020.01.18 14:00:05 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/74_NUKIDevice.pm line 417.
Undefined subroutine &FHEM::NUKIDevice::CommandDefMod called at ./FHEM/74_NUKIDevice.pm line 489, <FH> line 27869.
Zitat von: kkoeniger am 20 Januar 2020, 10:02:10
War bei mir genau so wie bei @Sascha_F. Die letzten Zeilen im Log waren:Code Auswählen2020.01.18 14:00:05 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/74_NUKIDevice.pm line 414.
2020.01.18 14:00:05 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/74_NUKIDevice.pm line 417.
Undefined subroutine &FHEM::NUKIDevice::CommandDefMod called at ./FHEM/74_NUKIDevice.pm line 489, <FH> line 27869.
Zitat von: PatrickR am 18 Januar 2020, 22:52:57
Callback eingerichtet und ohne Passwort für Bridge erreichbar?
Von unterwegs gesendet.
Zitat von: fabtie am 21 Januar 2020, 22:44:01
Ja, korrekt. Schalten im Device über set lock/unlock funktioniert.
Dann ändert sich sogar auch der state, allerdings nicht in locked oder unlocked sondern in lock oder unlock.
Internals:
BRIDGEAPI 1.9
CFGFN
DEF 'BridgeIP' abc123
FUUID 5e27630e-f33f-3d64-6f0f-9d75ea687aa7a461
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 'BridgeIP'
NAME NBridge1
NOTIFYDEV global,NBridge1
NR 184
NTFY_ORDER 50-NBridge1
PORT 8080
STATE connected
TOKEN abc123
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-'BridgeIP'
WEBHOOK_URL http://'FhemIP':8083/fhem/NUKIBridge-'BridgeIP'
READINGS:
2020-01-22 08:04:40 bridgeType Hardware
2020-01-22 08:04:40 currentTime 2020-01-22T07:04:40+00:00
2020-01-22 08:04:40 firmwareVersion 1.13.1
2020-01-22 08:04:40 hardwareId 324204985
2020-01-22 08:04:40 serverConnected 1
2020-01-22 08:04:40 serverId 2028750935
2020-01-22 08:04:40 state connected
2020-01-22 08:04:40 uptime 40999
2020-01-22 08:04:40 wifiFirmwareVersion 1.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
room NUKI
webhookFWinstance WEB
webhookHttpHostname 'FhemIP'
Zitat von: CoolTux am 25 Januar 2020, 17:30:22
Jepp gibt es nicht mehr.
lockState - aktueller Schließstatus uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.
# grep lockState *
74_NUKIDevice.pm:my %lockStates = (
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID},
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID} )
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID},
74_NUKIDevice.pm: ( $v =~ m/^[0-9]$/ ? $lockStates{$v}{ $hash->{DEVICETYPE} } : $v ) )
74_NUKIDevice.pm: <li>lockState - current lock status uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.</li>
74_NUKIDevice.pm: <li>lockState - aktueller Schließstatus uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.</li>
Zitat von: choenig am 26 Januar 2020, 10:02:41
Laut meiner commandref existiert das noch ;)Code Auswählen
lockState - aktueller Schließstatus uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.
... und nicht nur da ...Code Auswählen
# grep lockState *
74_NUKIDevice.pm:my %lockStates = (
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID},
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID} )
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID},
74_NUKIDevice.pm: ( $v =~ m/^[0-9]$/ ? $lockStates{$v}{ $hash->{DEVICETYPE} } : $v ) )
74_NUKIDevice.pm: <li>lockState - current lock status uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.</li>
74_NUKIDevice.pm: <li>lockState - aktueller Schließstatus uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.</li>
ABER:
Habe ich die Ankündigung irgendwo überlesen, dass das entfernt wurde?
LG
Christian
Zitat von: Claus1985 am 26 Januar 2020, 18:56:57
Hi CoolTux,
danke für das geniale Modul!
Habe seit dem Update (vorhin FHEM vollständig geupdated) eine Fehlermeldung bzgl.
der Webhooks:
NUKIDevicexxx unknown attribute webhookFWinstance. Type
NUKIDevicexxx unknown attribute webhookHttpHostname. Type
Gibt es eine Möglichkeit das zu fixen ohne Schloss und Bridge zu entfernen und neu
einzufügen?
Danke und Gruß,
Claus
Zitat von: Claus1985 am 26 Januar 2020, 19:18:39
Muss ich Lockstate noch gegen State tauschen damit der Status nach wie vor übertragen werden kann?
Zitat von: Claus1985 am 26 Januar 2020, 19:26:16
Bisher reiche ich den Lockstate per Notify und 99_myUtils an Loxone weiter,
da ich letztlich damit steuere. Kann ich das nach wie vor mit Lockstate?
Zitat von: Claus1985 am 26 Januar 2020, 20:12:31
Hm, das funktioniert nicht richtig. Wenn ich über die App oder direkt am Schloss ab- oder aufschließe,
überträgt der state das nicht / nicht richtig. Kannst Du den Lockstate wieder mit einbauen?
Zitat von: Claus1985 am 26 Januar 2020, 20:22:19
Den Webhook hab ich wie folgt in der cfg:
attr NBridge webhookHttpHostname 192.168.138.32
attr NBridge webhookFWinstance NWEB
quasi so wie es vorher auch am Schloss war nur mit anderem
Device Name.
Muss ich da etwas ändern?
Zitat von: choenig am 26 Januar 2020, 10:02:41
Laut meiner commandref existiert das noch ;)Code Auswählen
lockState - aktueller Schließstatus uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.
... und nicht nur da ...Code Auswählen
# grep lockState *
74_NUKIDevice.pm:my %lockStates = (
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID},
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID} )
74_NUKIDevice.pm: IOWrite( $hash, 'lockState', undef, $hash->{NUKIID},
74_NUKIDevice.pm: ( $v =~ m/^[0-9]$/ ? $lockStates{$v}{ $hash->{DEVICETYPE} } : $v ) )
74_NUKIDevice.pm: <li>lockState - current lock status uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.</li>
74_NUKIDevice.pm: <li>lockState - aktueller Schließstatus uncalibrated, locked, unlocked, unlocked (lock 'n' go), unlatched, locking, unlocking, unlatching, motor blocked, undefined.</li>
ABER:
Habe ich die Ankündigung irgendwo überlesen, dass das entfernt wurde?
LG
Christian
Internals:
CONNECTS 7
CSRFTOKEN csrf_104465736907610
DEF 8004 global
FD 15
FUUID 5e225bae-f33f-5676-242c-de3559ba1bab0b46
NAME WWW_NUKI_CALLBACK
NR 400
NTFY_ORDER 50-WWW_NUKI_CALLBACK
PORT 8004
STATE Initialized
TYPE FHEMWEB
READINGS:
2020-01-26 20:49:31 state Initialized
helper:
bm:
FW_Get:
cnt 1
dmx -1000
dtot 0
dtotcnt 0
mTS 28.01. 18:20:47
max 2.09808349609375e-05
tot 2.09808349609375e-05
mAr:
HASH(0x557f81bfc268)
WWW_NUKI_CALLBACK
?
FW_Notify:
cnt 168074
dmx -1000
dtot 0
dtotcnt 0
mTS 28.01. 00:10:29
max 0.000266075134277344
tot 0.365667104721069
mAr:
HASH(0x557f81bfc268)
HASH(0x557f80479f38)
FW_Read:
cnt 7
dmx -1000
dtot 0
dtotcnt 0
mTS 27.01. 07:49:41
max 0.000763893127441406
tot 0.00425314903259277
mAr:
HASH(0x557f81bfc268)
FW_Set:
cnt 3
dmx -1000
dtot 0
dtotcnt 0
mTS 28.01. 18:20:47
max 4.38690185546875e-05
tot 7.58171081542969e-05
mAr:
HASH(0x557f81bfc268)
WWW_NUKI_CALLBACK
?
Attributes:
DockerHealthCheck 0
allowfrom ^192\.168\.150\.72$
room System->Net
userattr DockerHealthCheck
2020.01.26 02:48:03.431 3: NUKIBridge (NUKIBridge) - defined with host nuki-bridge-flur.prdom on port 8080, Token TOKEN
2020.01.26 02:48:03.431 2: NUKIBridge (NUKIBridge) - Registering NUKIBridge for webhook URI /NUKIBridge-nuki-bridge-flur.prdom ...
2020.01.26 02:48:03.433 3: Invalid value for attribute webhookFWinstance: FHEMWEB instance WWW_NUKI_CALLBACK not existing
2020.01.26 02:48:03.494 3: NUKIDevice (XX.XX.Haustuerschloss) - I/O device is NUKIBridge
2020.01.26 02:48:03.494 3: NUKIDevice (XX.XX.Haustuerschloss) - defined with NukiId: XXXX
2020.01.26 02:48:03.495 3: NUKIDevice (XX.XX.Haustuerschloss) - change model
2020.01.26 02:48:03.496 3: NUKIDevice (XX.XX.Haustuerschloss) - change model
2020.01.26 02:48:03.518 3: WWW_NUKI_CALLBACK: port 8004 opened
2020.01.26 02:48:04.193 1: configfile: Invalid value for attribute webhookFWinstance: FHEMWEB instance WWW_NUKI_CALLBACK not existing
2020.01.26 02:48:04.561 2: NUKIDevice (XX.XX.Haustuerschloss) - GetUpdate Call IOWrite
2020.01.26 20:41:08.936 1: UPD FHEM/74_NUKIDevice.pm
2020.01.26 20:41:10.205 1: - bugfix: 74_NUKIDevice: fix FHEM Crash
2020.01.26 20:41:10.205 1: Undefined subroutine &FHEM::NUKIDevice::CommandDefMod
2020.01.26 20:49:31.567 3: NUKIBridge (NUKIBridge) - defined with host nuki-bridge-flur.prdom on port 8080, Token TOKEN
2020.01.26 20:49:31.567 2: NUKIBridge (NUKIBridge) - Registering NUKIBridge for webhook URI /NUKIBridge-nuki-bridge-flur.prdom ...
2020.01.26 20:49:31.603 3: NUKIDevice (XX.XX.Haustuerschloss) - I/O device is NUKIBridge
2020.01.26 20:49:31.603 3: NUKIDevice (XX.XX.Haustuerschloss) - defined with NukiId: XXXX
2020.01.26 20:49:31.603 3: NUKIDevice (XX.XX.Haustuerschloss) - change model
2020.01.26 20:49:31.605 3: NUKIDevice (XX.XX.Haustuerschloss) - change model
2020.01.26 20:49:31.626 3: WWW_NUKI_CALLBACK: port 8004 opened
2020.01.26 20:49:32.702 2: NUKIDevice (XX.XX.Haustuerschloss) - GetUpdate Call IOWrite
Zitat von: PatrickR am 28 Januar 2020, 18:25:02
Guten Abend!
Ich habe aktuell ein merkwürdiges Problem. Ich habe 4 FHEMWEB-Instanzen, wovon eine für NUKI vorgesehen ist. Wenn ich das Attribut WebhookFWInstance setzen möchte, werden im Dropdown nur die drei ersten Instanzen angeboten. Manuell kann ich es über attr setzen, was allerdings nur bis zum nächsten Neustart hält.
Hier ein List des FHEMWEB-Devices:Code Auswählen
Internals:
CONNECTS 7
CSRFTOKEN csrf_104465736907610
DEF 8004 global
FD 15
FUUID 5e225bae-f33f-5676-242c-de3559ba1bab0b46
NAME WWW_NUKI_CALLBACK
NR 400
NTFY_ORDER 50-WWW_NUKI_CALLBACK
PORT 8004
STATE Initialized
TYPE FHEMWEB
READINGS:
2020-01-26 20:49:31 state Initialized
helper:
bm:
FW_Get:
cnt 1
dmx -1000
dtot 0
dtotcnt 0
mTS 28.01. 18:20:47
max 2.09808349609375e-05
tot 2.09808349609375e-05
mAr:
HASH(0x557f81bfc268)
WWW_NUKI_CALLBACK
?
FW_Notify:
cnt 168074
dmx -1000
dtot 0
dtotcnt 0
mTS 28.01. 00:10:29
max 0.000266075134277344
tot 0.365667104721069
mAr:
HASH(0x557f81bfc268)
HASH(0x557f80479f38)
FW_Read:
cnt 7
dmx -1000
dtot 0
dtotcnt 0
mTS 27.01. 07:49:41
max 0.000763893127441406
tot 0.00425314903259277
mAr:
HASH(0x557f81bfc268)
FW_Set:
cnt 3
dmx -1000
dtot 0
dtotcnt 0
mTS 28.01. 18:20:47
max 4.38690185546875e-05
tot 7.58171081542969e-05
mAr:
HASH(0x557f81bfc268)
WWW_NUKI_CALLBACK
?
Attributes:
DockerHealthCheck 0
allowfrom ^192\.168\.150\.72$
room System->Net
userattr DockerHealthCheck
Patrick
Von unterwegs gesendet.
Zitat von: CoolTux am 28 Januar 2020, 20:35:17Möglich ist alles. Aber als ich die Instanz angelegt habe tauchte sie auch im Dropdown nicht auf, ein manuelles attr funktionierte aber (s. o.). D. h. irgendwas ist da am Modul verbogen.
Wäre es möglich das die Webinstanz nach dem Nuki Device definiert ist?
Zitat von: moskito am 29 Januar 2020, 16:44:47Ok, das bestätigt meine Vermutung eines Bugs.
Hatte das selbe Phänomen und siehe da, nach dem verschieben in der fhem.cfg nach vorne und anschließendem Neustart tauchte die angedachte WEB-Instanz im Dropdown auf.
Zitat von: moskito am 29 Januar 2020, 16:44:47
Hatte das selbe Phänomen und siehe da, nach dem verschieben in der fhem.cfg nach vorne und anschließendem Neustart tauchte die angedachte WEB-Instanz im Dropdown auf.
2020.02.01 06:52:40 3: NUKIDevice (NukiBridge) - autocreate new device Nuki_### with nukiId ###, model 0
Zitat von: eddy242 am 22 März 2020, 10:16:03
Hallo zusammen,
Mit dem Trick, das FHEMWEB für Nuki in der fhem.cfg vorzuziehen funktioniert das Callback nun auch stabil bei mir. Es werden aber nach wie vor nur die Zustände locked und unlocked ausgewertet, oder? In der App kann man ja auch sehen, ob die Tür geöffnet ist. Lässt sich das in das Modul integrieren?
Danke!
Zitat von: raisch am 26 März 2020, 17:55:45
Ich möchte mein Nuki-Lock bzw. -Bridge mit FHEM, aber natürlich ohne Internet betreiben. Ich glaube in diesem Thread gelesen zu haben, dass das möglich sein soll.
Nur: bei mir klappt das so nicht. Sobald ich der Bridge die Verbindung ins Internet verweigere, lässt sich das Lock nicht mehr öffnen etc.
bei mir schaut die config so aus:
defmod Nuki_Atelier NUKIBridge 10.17.xx.yy blabla
defmod Tuer_Atelier NUKIDevice 12345678 0
attr Tuer_Atelier IODev Nuki_Atelier
attr Tuer_Atelier event-on-change-reading unlatch.*:lock.*
attr Tuer_Atelier model smartlock
Was mache ich da falsch, oder muss es noch ergänzen?
danke
raimund
Zitat von: raisch am 26 März 2020, 18:57:57
Habs gerade selbst gelöst: das Problem war eine fehlende Firewall-Regel von der Nuki-Bridge zum fhem-Server. Jetzt gehts auch ohne Internet :)
Zitat von: antonwinden am 22 April 2020, 09:18:05Vorab: Du verzichtest damit natürlich auf alle Online-Features wie automatische Updates oder Fernöffnung über die Hersteller-App.
@PatrickR
Ich wäre auch interessiert daran Nuki ohne Internet funktionsfähig ist und wäre für eine Vorgehensweise dafür dankbar.
anton
nternals:
BRIDGEAPI 1.9
CFGFN
DEF 192.168.178.79 drfnhr
FUUID 5ed26f88-f33f-705c-275a-961b117d108c8d03
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.178.79
NAME Schloss_Laurin
NOTIFYDEV global,Schloss_Laurin
NR 575868
NTFY_ORDER 50-Schloss_Laurin
PORT 8080
STATE connected
TOKEN drfnhr
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.178.79
WEBHOOK_URL http://192.168.0.1:8083/fhem/NUKIBridge-192.168.178.79
READINGS:
2020-05-30 20:44:11 appVersion 1.4.6
2020-05-30 20:44:11 bridgeType Software
2020-05-30 20:44:11 currentTime 2020-05-30T18:44:16Z
2020-05-30 16:38:31 lastError invalid API token
2020-05-30 20:44:11 serverConnected 1
2020-05-30 20:44:11 serverId 279066280
2020-05-30 20:44:11 state connected
2020-05-30 20:44:11 uptime 14958
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
room Flur
webhookFWinstance WEB
webhookHttpHostname 192.168.0.1
Internals:
BRIDGEAPI 1.9
CFGFN
DEF 1 NukiBrigde1
DEVICETYPE NukiBrigde1
FUUID 5ed27066-f33f-705c-8105-8c40c94e8864bd66
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev Schloss_Laurin
NAME Wohnungstuer
NOTIFYDEV global,autocreate,Wohnungstuer
NR 575929
NTFY_ORDER 50-Wohnungstuer
NUKIID 1
STATE Initialized
TYPE NUKIDevice
VERSION v1.9.12
helper:
lockAction unlatch
Attributes:
IODev Schloss_Laurin
model
room Flur
Zitat von: noom0815 am 27 Mai 2020, 22:21:31
- für die Einbindung der Schlösser über die SW-Bridge benötigt man die nukiID
- diese kann man bei Verwendung der Hardware-Bridge in fhem auslesen und eine entspechende defintion anlegen
- wie man die entsprechende nukiID ohne HW-Bridge herausfindet, habe ich leider nicht herausgefunden - kann hierzu jemand einen Hinweis geben?
Zitat von: nocomment am 08 Juni 2020, 03:33:45Ja wird unterstützt.
Ich habs in der suche nicht gefunden.
Wird auch der Nuki opener unterstützt ?
https://nuki.io/de/opener/
Dankööö
LG
Zitat von: noom0815 am 02 Juni 2020, 12:16:10
Hallo zusammen,
gerne beantworte ich meine ursprünglichen Fragen wieder selbst:
- die nukiID entspricht dem hex-Wert der SmartLock ID in dezimal... ;)
@AlterMann:
Zunächst einmal würde ich nicht Deine ganzen Daten inkl. sämtlicher IPs, Token etc. hier öffentlich posten ::).
Zumindest Dein device ist m.M.n. nicht korrekt angelegt:Sollte dann eigentlich passen...
- im def musst Du die nukiID gefolgt von einer "0" eintragen
- prüfen, dass als <IODev-Device> weiterhin Schloss_Laurin eingetragen ist
Gruß,
Ian
Zitat von: CoolTux am 08 Juni 2020, 14:53:35
Ja wird unterstützt.
Eigentlich muss man gar nichts machen. Sobald die Bridge definiert wurde sollte automatisch auch das an der Bridge angehängte Device erkannt und eingerichtet werden. Voraussetzung man hat autocreate aktiviert.
Zitat von: AlterMann am 10 Juni 2020, 10:39:17
Hi CoolTux,
zunächst mal waren die "geheimen" Daten geändert, wäre aber auch nicht schlimm gewesen, denn das hat sich nun nochmal geändert, weil ich doch auf die Hardware umgestiegen bin! Damit geht es jetzt! Die SoftwareApp war tatsächlich nie richtig verbunden! Selbst bei der Hardware brauchte ich 7 Anläufe ehe es ging! Bluetooth scheint ein Pferdefuß zu sein! 30 cm scheinen schon Probleme zu machen, dann gehts wieder auf halber Treppe! Danke für Eure Arbeit und die gute Anleitung!
AM
Zitat von: AlterMann am 11 Juni 2020, 09:33:15
Sorry aber da steht Alter Mann und das stimmt, immer etwas verworren! :-) Also ich habe Nuki2.0 und die Hardwarebrigde und die laufen beide auf FHEM! Das mit dem Callback versuche ich gerade über meine IPV6 Instanz! Dort habe ich mal das Https abgeschalten! Etwas verwirrt war ich weil die Readings mal lock und dann wieder locked heißen. Ich habe einfach alles bei devstaticon eingetragen das System sucht sich das Richtige raus! Es geht alles ....Danke noch mal!
Eine Frage noch! Das Schloss hat einen Magneten und "sagt" ob die Tür auf oder zu ist. Dabei geht es um das Türblatt! Dieses Reading sehe ich in FHEM noch nicht....? Sorry aber ich weiß bei den 107 Seiten nicht ob die Frage schon aufgetaucht ist! Suche hat nix gesagt.
Danke noch mal das du dir Zeit nimmst!
AM
Zitat von: CoolTux am 11 Juni 2020, 09:46:44... jetzt aber schon* ;)
Das erkennen ob die Tür physisch auf oder zu ist bietet die API aktuell noch nicht.
Zitat von: PatrickR am 15 Juni 2020, 11:57:06Servus,
Mappt Dein Modul neue Felder automatisch auf Readings oder musst Du das erst per Hand einpflegen?
doorsensorState 2 2020-06-15 12:05:36
doorsensorStateName door closed 2020-06-15 12:05:36
Zitat von: OdfFhem am 26 Juli 2020, 13:21:59
@CoolTux
Bei Tests habe ich festgestellt, dass es neuerdings weitere json-Attribute gibt:
- /info liefert für die Bridge u.a. "wlanConnected": true zurück
- /list liefert für das Device u.a. "firmwareVersion": "2.7.30" zurück; dies befindet sich auf gleicher Ebene wie "deviceType", "nukiId", ...
Könnten diese json-Attribute als Readings bereitgestellt werden?
Desweiteren würde mich interessieren, ob die für das Device gelieferten json-Attribute state bzw. stateName in 2 weitere Readings namens lockState bzw. lockStateName bereitgestellt werden könnten; lockState gab es ja bereits früher und wurde im aktuellen Stand in state überführt. Da es mittlerweile zusätzlich auswertbare Readings doorsensorState bzw. doorsensorStateName gibt, wäre es vermutlich interessant, in state einen Gesamtzustand darzustellen, lock sowie doorsensor sollten aber auch getrennt auswertbar sein.
Zitat von: Thyraz am 02 August 2020, 11:14:23
Eine Idee wäre evtl. ein extra ,,Zuhause" anzulegen in das man Nuki integriert und hier eben nicht alle einladen?
Ansonsten sieht in HomeKit eben jeder alles. Das Problem ist also nicht Nuki-spezifisch.
Wir verwenden daher Nuki auch über die App und nicht über HomeKit.
Jüngeren Kindern kann man auch ein Nuki Fob in die Hand drücken.
Besser sowas als nen Schlüssel verlieren, da kann man dem Fob einfach die Berechtigung fürs Schloss entziehen.
Zitat von: Thyraz am 10 August 2020, 20:29:59
... über die HTTP API (also das was Fhem nutzt) das Klingeln an der Haustür (Nuki Opener) meldet?...
Zitat von: Thyraz am 18 August 2020, 10:03:22
Funktioniert, im Opener kommt dann ein neues Reading nach dem ersten Klingeln hinzu, auf dessen Events man reagieren kann. :)
Scheint nach ersten Tests auch recht verzögerungsfrei zu sein.
Solangsam taugt das Ding was. :P
Internals:
.FhemMetaInternals 1
BRIDGEAPI 1.9
CFGFN
DEF Entfernt
DEVICETYPE 0
FUUID 5f58ae91-f33f-17d1-2472-dc21d6c1591edcd6
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NBridge
LASTInputDev NBridge
MSGCNT 2382
NAME Nuki_1FDF8E54
NBridge_MSGCNT 2382
NBridge_TIME 2020-09-10 08:18:23
NOTIFYDEV global,autocreate,Nuki_1FDF8E54
NR 357610
NTFY_ORDER 50-Nuki_1FDF8E54
NUKIID Entfernt
STATE unlocked
TYPE NUKIDevice
VERSION v1.9.12
.attraggr:
.attrminint:
READINGS:
2020-09-10 07:47:39 batteryState ok
2020-09-10 08:18:23 deviceType smartlock
2020-09-10 07:47:39 doorsensorState 2
2020-09-10 07:47:39 doorsensorStateName door closed
2020-09-09 14:21:25 firmwareVersion 2.6.4
2020-09-10 07:47:39 mode door mode
2020-09-10 08:18:23 name Nuki_1FDF8E54
2020-09-10 08:18:23 nukiId
2020-09-10 08:18:23 paired true
2020-09-10 08:18:23 rssi -73
2020-09-10 07:47:39 state unlocked
2020-09-10 07:47:39 stateName unlocked
2020-09-10 07:47:39 success 1
helper:
Attributes:
DbLogExclude .*
IODev NBridge
alarmDevice Sensor
alarmSettings alarm4,|Nuki_1FDF8E54:unlatch||disarm
icon 1_nuki
model smartlock
room Haus->Haustür
ringactionTimestamp 2020-10-03T[b]10:01:52[/b]+00:00 2020-10-03 12:48:27
currentTime 2020-10-03T[b]10:53:15[/b]+00:00 2020-10-03 [b]12:53:05[/b]
Zitat von: Thyraz am 03 Oktober 2020, 14:14:01
Ich denke du suchst den electricStrikeActuation Set Befehl. ;)
defmod VR_NUKI_Haustuer NUKIDevice XXXXXXXXX 2
attr VR_NUKI_Haustuer IODev NBridge1
attr VR_NUKI_Haustuer alias Haustüre
attr VR_NUKI_Haustuer devStateIcon online:rc_GREEN:on offline:rc_RED:off Initialized:rc_GREEN
attr VR_NUKI_Haustuer event-on-update-reading ringactionState,state
attr VR_NUKI_Haustuer group Geräte
attr VR_NUKI_Haustuer icon 1_nuki_bridge
attr VR_NUKI_Haustuer model opener
attr VR_NUKI_Haustuer room Vorraum
attr VR_NUKI_Haustuer userReadings batterystate {my $batterystate = ReadingsVal($name,"battery","0");;;; $batterystate}
defmod watchdog_VR_Klingel watchdog VR_NUKI_Haustuer:rto.* 00:20:00 SAME setreading VR_NUKI_Haustuer rto_active online ;; setstate watchdog_VR_Klingel defined ;;
attr watchdog_VR_Klingel alias Nuki RTO active
attr watchdog_VR_Klingel devStateIcon defined:people_sensor Next.*:on-till
attr watchdog_VR_Klingel group Vorraum
attr watchdog_VR_Klingel icon user_unknown
attr watchdog_VR_Klingel room System
defmod act_VR_Klingel_Nuki notify VR_NUKI_Haustuer:ringactionState:.* { \
\
Log 1, "act_VR_Klingel_Nuki: ringactionState/event: ".$EVENT." - state: ".Value($NAME);;\
\
#rto active?\
if(index(Value($NAME), "rto") != -1)\
{\
#rto active\
fhem("setreading ".$NAME." rto_active rto_active");;\
}\
\
#reset rto state to online\
if((index($EVENT, "0") != -1) && (index(Value($NAME), "online") != -1))\
{\
#reset rto state to online\
fhem("setreading ".$NAME." rto_active online ;;");;\
fhem("setstate watchdog_VR_Klingel defined ;;");;\
}\
\
#someone rang?\
if(index($EVENT, "1") != -1) {\
#known or unkown?\
if(index(ReadingsVal($NAME,"rto_active", "online"), "online") != -1)\
{\
#someone unkown rang!\
Log 1, "act_VR_Klingel_Nuki: someone unkown rang!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!";;\
}\
#reset rto state to online\
fhem("setreading ".$NAME." rto_active online ;;");;\
fhem("setstate watchdog_VR_Klingel defined ;;");; \
}\
}
attr act_VR_Klingel_Nuki alias Klingel gedrückt - Nuki
attr act_VR_Klingel_Nuki group Vorraum
attr act_VR_Klingel_Nuki icon people_sensor
attr act_VR_Klingel_Nuki room System
2020.10.06 21:28:40 1: act_VR_Klingel: Es klingelt! (Hue Switch)
2020.10.06 21:28:42 1: act_VR_Klingel_Nuki: someone unkown rang!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Zitat von: Thyraz am 06 Oktober 2020, 20:18:17
Wobei ich zeitlich keine Probleme mehr habe beim Klingeln im Vergleich zur bisherigen Lösung mit einem ZWave Kontakt.
Die Nuki Bridge meldet das Klingeln bisher zuverlässig mit etwa einer Sekunde Verzögerung zum ZWave Kontakt.
Zitat von: FFHEM am 07 Oktober 2020, 11:20:50
Ich möchte das Smartlock - und das wollen hier ja wohl alle (?) - so weit wie möglich (von Updates abgesehen) vom Internet fernhalten.
Zitat von: popy am 08 Oktober 2020, 11:10:55
Bzgl. dem läuten, es funktioniert nicht zuverlässig, heute jemand geläutet und kein ringactionState 1.
ZitatFalls später einmal die Nuki-Server gehackt werden, hätten die Einbrecher eine perfekte Kombination aus Ort und digitalem Schlüssel.
Zitat von: Y. Lee am 18 Oktober 2020, 16:19:03
Habe soeben meine NukiBridge und das Schloss eingerichtet. Funktioniert soweit prima.
Jetzt wollte ich den Webhook einbauen. Laut Anleitung im Wiki soll der "webhookFWinstance" zum NukiDevice gemacht werden (Im der Anleitung wird "Haustuer" verwendet). Ich schaffe das aber leider nicht. Mein NukiDevice hat dieses Attribut gar nicht.
Bei der NukiBridge finde ich dieses Attribut, jedoch hilft das nichts. Ich bekomme den Status von Nuki einfach nicht in Fhem upgedated.
Vielen Dank für eure Hilfe!
ZitatDie Webinstanz welche du da angibst muss ohne SSL und ohne crfs sein. Daher dafür lieber eine separate Instanz anlegen.
Zitat von: Y. Lee am 18 Oktober 2020, 17:18:26
Danke CoolTux!
Alles klar. Aber nochmals zur Sicherheit (und weil es in der Anleitung anders steht): Dass ich den Webhook bei der Bridge einstelle, das ist in Ordnung so?
Internals:
BRIDGEAPI 1.9
DEF 10.10.23.111 ******
FUUID 5fb3bd97-f33f-787a-5dcf-1903c441d9ea2593
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 10.10.23.111
NAME NukiBridgeWhite
NOTIFYDEV global,NukiBridgeWhite
NR 719
NTFY_ORDER 50-NukiBridgeWhite
PORT 8080
STATE connected
TOKEN ******
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 83
WEBHOOK_LAST 2020-11-18 07:55:15
WEBHOOK_PORT 2388
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-10.10.23.111
WEBHOOK_URL http://10.10.23.1:2388/fhem/NUKIBridge-10.10.23.111
READINGS:
2020-11-17 13:10:05 bridgeType Hardware
2020-11-17 15:43:05 currentTime 2020-11-17T14:42:52+00:00
2020-11-17 14:51:06 firmwareVersion 2.7.0
2020-11-17 13:10:05 hardwareId 59xxxxx02
2020-11-18 05:04:23 lastError 10.10.23.111: No route to host (113)
2020-11-17 15:23:35 serverConnected 0
2020-11-17 13:10:05 serverId 41xxxxx64
2020-11-18 08:12:41 state connected
2020-11-18 08:21:12 uptime 59588
2020-11-17 13:10:05 wifiFirmwareVersion 2.1.13
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
event-on-change-reading .*
group System
icon 1_nuki_bridge
room ControlRoom
timestamp-on-change-reading .*
webhookFWinstance WEB__2388_app
webhookHttpHostname 10.10.23.1
Internals:
BRIDGEAPI 1.9
DEF 10.10.23.116 ******
FUUID 5c42d646-f33f-787a-8ff0-a79a68115d0b0dfc
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 10.10.23.116
NAME NukiBridgeBlack
NOTIFYDEV global,NukiBridgeBlack
NR 527
NTFY_ORDER 50-NukiBridgeBlack
PORT 8080
STATE disabled
TOKEN ******
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 2388
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-10.10.23.116
WEBHOOK_URL http://10.10.23.1:2388/fhem/NUKIBridge-10.10.23.116
READINGS:
2020-11-17 13:32:38 bridgeType Hardware
2020-11-17 13:33:26 currentTime jo
2020-11-17 13:32:38 firmwareVersion 1.17.1
2020-11-17 13:32:38 hardwareId 29******81
2020-11-17 13:43:27 lastError 10.10.23.116: No route to host (113)
2020-11-17 13:32:38 serverConnected 0
2020-11-17 13:32:38 serverId 17******58
2020-11-17 14:05:45 state disabled
2020-11-17 13:49:24 uptime 42
2020-11-17 13:32:38 wifiFirmwareVersion 1.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
lastDeviceAction:
deviceType 0
endpoint lockAction
nukiId 30******05
param lock
Attributes:
disable 1
event-on-change-reading .*
group System
icon 1_nuki_bridge
room ControlRoom
timestamp-on-change-reading .*
webhookFWinstance WEB__2388_app
webhookHttpHostname 10.10.23.1
2020-11-17_13:31:54.464 EG.Eingang.Nuki paired: true
2020-11-17_13:31:54.614 EG.Eingang.Nuki paired: false
Zitat von: choenig am 18 November 2020, 08:28:30
Sehr gerne:
Hier die neue:Code Auswählen
Internals:
BRIDGEAPI 1.9
DEF 10.10.23.111 ******
FUUID 5fb3bd97-f33f-787a-5dcf-1903c441d9ea2593
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 10.10.23.111
NAME NukiBridgeWhite
NOTIFYDEV global,NukiBridgeWhite
NR 719
NTFY_ORDER 50-NukiBridgeWhite
PORT 8080
STATE connected
TOKEN ******
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 83
WEBHOOK_LAST 2020-11-18 07:55:15
WEBHOOK_PORT 2388
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-10.10.23.111
WEBHOOK_URL http://10.10.23.1:2388/fhem/NUKIBridge-10.10.23.111
READINGS:
2020-11-17 13:10:05 bridgeType Hardware
2020-11-17 15:43:05 currentTime 2020-11-17T14:42:52+00:00
2020-11-17 14:51:06 firmwareVersion 2.7.0
2020-11-17 13:10:05 hardwareId 59xxxxx02
2020-11-18 05:04:23 lastError 10.10.23.111: No route to host (113)
2020-11-17 15:23:35 serverConnected 0
2020-11-17 13:10:05 serverId 41xxxxx64
2020-11-18 08:12:41 state connected
2020-11-18 08:21:12 uptime 59588
2020-11-17 13:10:05 wifiFirmwareVersion 2.1.13
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
event-on-change-reading .*
group System
icon 1_nuki_bridge
room ControlRoom
timestamp-on-change-reading .*
webhookFWinstance WEB__2388_app
webhookHttpHostname 10.10.23.1
Und hier die alte (die aktuell deaktiviert ist):Code Auswählen
Internals:
BRIDGEAPI 1.9
DEF 10.10.23.116 ******
FUUID 5c42d646-f33f-787a-8ff0-a79a68115d0b0dfc
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 10.10.23.116
NAME NukiBridgeBlack
NOTIFYDEV global,NukiBridgeBlack
NR 527
NTFY_ORDER 50-NukiBridgeBlack
PORT 8080
STATE disabled
TOKEN ******
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 2388
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-10.10.23.116
WEBHOOK_URL http://10.10.23.1:2388/fhem/NUKIBridge-10.10.23.116
READINGS:
2020-11-17 13:32:38 bridgeType Hardware
2020-11-17 13:33:26 currentTime jo
2020-11-17 13:32:38 firmwareVersion 1.17.1
2020-11-17 13:32:38 hardwareId 29******81
2020-11-17 13:43:27 lastError 10.10.23.116: No route to host (113)
2020-11-17 13:32:38 serverConnected 0
2020-11-17 13:32:38 serverId 17******58
2020-11-17 14:05:45 state disabled
2020-11-17 13:49:24 uptime 42
2020-11-17 13:32:38 wifiFirmwareVersion 1.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
lastDeviceAction:
deviceType 0
endpoint lockAction
nukiId 30******05
param lock
Attributes:
disable 1
event-on-change-reading .*
group System
icon 1_nuki_bridge
room ControlRoom
timestamp-on-change-reading .*
webhookFWinstance WEB__2388_app
webhookHttpHostname 10.10.23.1
Und so sah' das dann im Betrieb aus:Code Auswählen
2020-11-17_13:31:54.464 EG.Eingang.Nuki paired: true
2020-11-17_13:31:54.614 EG.Eingang.Nuki paired: false
LG
Christian
Zitat von: breezybadger am 18 November 2020, 08:43:36
Hi zusammen,
ein tolles Modul! Leider klappt bei mir die Erkennung der Klingel nicht (rto funktioniert per App) nur die readings von ringactionState bleibt bei 0. Hat jemand eine Idee was ich hier versuchen könnte?
Danke euch.
LG Breezy
020.11.18 11:44:53.753 4 : NUKIBridge (NUKI_B_Acer) - Response JSON: {"bridgeType":2,"ids":{"serverId":826085686},"versions":{"appVersion":"1.4.6"},"uptime":10967,"currentTime":"2020-11-18T10:44:52Z","serverConnected":true,"scanResults":[{"nukiId":534794661,"name":"Nuki_1FE051A5","rssi":-53,"paired":true}]}
2020.11.18 11:44:53.754 4 : NUKIBridge (NUKI_B_Acer) - Response ERROR:
2020.11.18 11:44:53.754 4 : NUKIBridge (NUKI_B_Acer) - Response CODE: 200
Internals:
BRIDGEAPI 1.9
DEF 1 NUKI_B_Acer
DEVICETYPE 0
FUUID 5fb4d8ac-f33f-74bb-047d-e3a5e56d74b32469
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NUKI_B_Acer
NAME NUKI2_Kueche
NOTIFYDEV global,autocreate,Kueche_Nuki2
NR 106575
NTFY_ORDER 50-Kueche_Nuki2
NUKIID 1
STATE Initialized
TYPE NUKIDevice
VERSION v1.9.12
Attributes:
IODev NUKI_B_Acer
model smartlock
Internals:
BRIDGEAPI 1.9
DEF 192.168.6.101 e09fm2
FUUID 5fb4d5fb-f33f-74bb-11a0-97bf4ea5aa7f2d97
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.6.101
NAME NUKI_B_Acer
NOTIFYDEV global,NUKI_B_Acer
NR 106574
NTFY_ORDER 50-NUKI_B_Acer
PORT 8080
STATE connected
TOKEN e09fm2
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8086
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.6.101
WEBHOOK_URL http://192.168.0.9:8086/fhem/NUKIBridge-192.168.6.101
READINGS:
2020-11-18 09:59:37 appVersion 1.4.6
2020-11-18 09:59:37 bridgeType Software
2020-11-18 09:59:37 currentTime 2020-11-18T08:59:36Z
2020-11-18 09:59:15 lastError http://192.168.6.101:8080/info?token=e09fm2: empty answer received
2020-11-18 09:59:37 serverConnected 1
2020-11-18 09:59:37 serverId 826085686
2020-11-18 09:59:37 state connected
2020-11-18 09:59:37 uptime 4651
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
verbose 5
webhookFWinstance WEB8086
webhookHttpHostname 192.168.0.9
2020.11.18 09:54:13.573 4: NUKIBridge (NUKI_B_Acer) - GetCheckBridgeAlive
2020.11.18 09:54:13.573 4: NUKIBridge (NUKI_B_Acer) - created uri: http://192.168.6.101:8080/info?token=
2020.11.18 09:54:13.574 4: NUKIBridge (NUKI_B_Acer) - Send HTTP POST with URL http://192.168.6.101:8080/info?token=
2020.11.18 09:54:13.574 4: NUKIBridge (NUKI_B_Acer) - run Write
2020.11.18 09:54:13.574 4: NUKIBridge (NUKI_B_Acer) - Call InternalTimer for GetCheckBridgeAlive
2020.11.18 09:54:19.317 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14335
2020.11.18 09:54:19.397 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14337
2020.11.18 09:54:19.578 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14338
2020.11.18 09:54:19.602 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14339
2020.11.18 09:54:19.625 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14340
2020.11.18 09:54:20.096 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14341
2020.11.18 09:54:20.117 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14342
2020.11.18 09:54:20.137 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14343
2020.11.18 09:54:20.413 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14344
2020.11.18 09:54:20.453 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14345
2020.11.18 09:54:20.473 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14346
2020.11.18 09:54:20.493 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14347
2020.11.18 09:54:20.513 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14348
2020.11.18 09:54:20.534 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14349
2020.11.18 09:54:20.554 1: Timeout for PRESENCE_DoLocalPingScan reached, terminated process 14350
2020.11.18 09:54:20.575 1: Timeout for PRESENCE_DoLocalFunctionScan reached, terminated process 14351
2020.11.18 09:54:36.194 4: NUKIBridge (NUKI_B_Acer) - Response JSON:
2020.11.18 09:54:36.194 4: NUKIBridge (NUKI_B_Acer) - Response ERROR: http://192.168.6.101:8080/info?token=e09fm2: empty answer received
2020.11.18 09:54:36.194 5: NUKIBridge (NUKI_B_Acer) - Bridge ist offline
2020.11.18 09:54:36.194 4: NUKIBridge (NUKI_B_Acer) - error while requesting: http://192.168.6.101:8080/info?token=e09fm2: empty answer received
2020.11.18 09:54:37.876 1: PERL ERROR: Bad arg length for Socket::sockaddr_family, length is 0, should be at least 2 at /usr/local/share/perl/5.26.1/IO/Socket/SSL.pm line 977.
2020.11.18 09:54:37.883 1: stacktrace:
2020.11.18 09:54:37.883 1: main::__ANON__ called by /usr/local/share/perl/5.26.1/IO/Socket/SSL.pm (977)
2020.11.18 09:54:37.883 1: (eval) called by /usr/local/share/perl/5.26.1/IO/Socket/SSL.pm (975)
2020.11.18 09:54:37.883 1: IO::Socket::SSL::_update_peer called by /usr/local/share/perl/5.26.1/IO/Socket/SSL.pm (811)
2020.11.18 09:54:37.884 1: IO::Socket::SSL::connect_SSL called by /usr/local/share/perl/5.26.1/IO/Socket/SSL.pm (1581)
2020.11.18 09:54:37.884 1: IO::Socket::SSL::start_SSL called by FHEM/HttpUtils.pm (533)
2020.11.18 09:54:37.884 1: (eval) called by FHEM/HttpUtils.pm (532)
2020.11.18 09:54:37.884 1: main::HttpUtils_Connect2 called by FHEM/HttpUtils.pm (447)
2020.11.18 09:54:37.884 1: main::__ANON__ called by fhem.pl (762)
2020.11.18 09:54:44.212 4: NUKIBridge (NUKI_B_Acer) - GetCheckBridgeAlive
2020.11.18 09:54:44.306 4: NUKIBridge (NUKI_B_Acer) - created uri: http://192.168.6.101:8080/info?token=
2020.11.18 09:54:44.307 4: NUKIBridge (NUKI_B_Acer) - Send HTTP POST with URL http://192.168.6.101:8080/info?token=
2020.11.18 09:54:44.307 4: NUKIBridge (NUKI_B_Acer) - run Write
2020.11.18 09:54:44.307 4: NUKIBridge (NUKI_B_Acer) - Call InternalTimer for GetCheckBridgeAlive
020.11.18 10:02:43.830 4 : NUKIBridge (NUKI_B_Acer) - Response JSON: {"bridgeType":2,"ids":{"serverId":826085686},"versions":{"appVersion":"1.4.6"},"uptime":4837,"currentTime":"2020-11-18T09:02:42Z","serverConnected":true,"scanResults":[{"nukiId":534794661,"name":"Nuki_1FE051A5","rssi":-54,"paired":true}]}
2020.11.18 10:02:43.831 4 : NUKIBridge (NUKI_B_Acer) - Response ERROR:
2020.11.18 10:02:43.831 4 : NUKIBridge (NUKI_B_Acer) - Response CODE: 200
Zitat von: CoolTux am 18 November 2020, 08:51:01
Richte mal einen zweiten separaten Webhook ein und konfiguriere diesen bei einen der beiden Bridges. Dann sollte es gehen.
2020-11-18_17:11:48.853 EG.Eingang.Nuki.Black paired: true
2020-11-18_17:11:48.853 EG.Eingang.Nuki.Black rssi: -64
2020-11-18_17:11:48.858 NukiBridgeBlack uptime: 583
2020-11-18_17:12:02.881 EG.Eingang.Nuki.Black rssi: -87
2020-11-18_17:12:02.881 EG.Eingang.Nuki.Black paired: false
2020-11-18_17:12:02.886 NukiBridgeWhite uptime: 91336
2020.11.18 17:17:02.601 4: NUKIBridge (NukiBridgeWhite) - GetCheckBridgeAlive
2020.11.18 17:17:02.601 4: NUKIBridge (NukiBridgeWhite) - created uri: http://10.10.23.111:8080/info?token=******
2020.11.18 17:17:02.602 4: NUKIBridge (NukiBridgeWhite) - Send HTTP POST with URL http://10.10.23.111:8080/info?token=******
2020.11.18 17:17:02.602 4: NUKIBridge (NukiBridgeWhite) - run Write
2020.11.18 17:17:02.602 4: NUKIBridge (NukiBridgeWhite) - Call InternalTimer for GetCheckBridgeAlive
2020.11.18 17:17:03.734 4: NUKIBridge (NukiBridgeWhite) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 59******02, "serverId": 41******64}, "versions": {"firmwareVersion": "2.7.0", "wifiFirmwareVersion": "2.1.13"}, "uptime": 91636, "currentTime": null, "wlanConnected": true, "serverConnected": false, "scanResults": [{"deviceType": 0, "nukiId": 60******36, "name": "Nuki_24******BC", "rssi": -58, "paired": true}, {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false}]}
2020.11.18 17:17:03.735 4: NUKIBridge (NukiBridgeWhite) - Response ERROR:
2020.11.18 17:17:03.735 4: NUKIBridge (NukiBridgeWhite) - Response CODE: 200
2020.11.18 17:17:03.735 5: NUKIBridge (NukiBridgeWhite) - Bridge ist online
2020.11.18 17:17:03.735 5: NUKIBridge (NukiBridgeWhite) - 1 == 1 and 1 > 0
[...Ziemlich häufig wiederholt...]
2020.11.18 17:17:03.740 5: NUKIBridge (NukiBridgeWhite) - 1 == 1 and 1 > 0
2020.11.18 17:17:03.740 5: NUKIBridge (NukiBridgeWhite) - return msg: {"deviceType": 0, "nukiId": 60******36, "name": "Nuki_24******BC", "rssi": -58, "paired": true} and tail: , {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false}]}
2020.11.18 17:17:03.740 5: NUKIBridge (NukiBridgeWhite) - Decoding JSON message. Length: 92 Content: {"deviceType": 0, "nukiId": 60******36, "name": "Nuki_24******BC", "rssi": -58, "paired": true}
2020.11.18 17:17:03.740 5: NUKIBridge (NukiBridgeWhite) - Vor Sub: Laenge JSON: 92 Content: {"deviceType": 0, "nukiId": 60******36, "name": "Nuki_24******BC", "rssi": -58, "paired": true} Tail: , {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false}]}
2020.11.18 17:17:03.741 5: NukiBridgeWhite: dispatch {"deviceType": 0, "nukiId": 60******36, "name": "Nuki_24******BC", "rssi": -58, "paired": true}
2020.11.18 17:17:03.741 5: NUKIDevice (NukiBridgeWhite) - Parse with result: {"deviceType": 0, "nukiId": 60******36, "name": "Nuki_24******BC", "rssi": -58, "paired": true}
2020.11.18 17:17:03.746 5: NUKIBridge (NukiBridgeWhite) - Garbage character before message: ,
2020.11.18 17:17:03.747 5: NUKIBridge (NukiBridgeWhite) - Garbage character before message:
2020.11.18 17:17:03.747 5: NUKIBridge (NukiBridgeWhite) - 1 == 1 and 1 > 0
2020.11.18 17:17:03.747 5: NUKIBridge (NukiBridgeWhite) - 1 == 1 and 1 > 0
2020.11.18 17:17:03.747 5: NUKIBridge (NukiBridgeWhite) - return msg: {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false} and tail: ]}
2020.11.18 17:17:03.747 5: NUKIBridge (NukiBridgeWhite) - Nach Sub: Laenge JSON: 93 Content: {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false} Tail: ]}
2020.11.18 17:17:03.747 5: NUKIBridge (NukiBridgeWhite) - Decoding JSON message. Length: 93 Content: {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false}
2020.11.18 17:17:03.747 5: NUKIBridge (NukiBridgeWhite) - Vor Sub: Laenge JSON: 93 Content: {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false} Tail: ]}
2020.11.18 17:17:03.747 5: NukiBridgeWhite: dispatch {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false}
2020.11.18 17:17:03.747 5: NUKIDevice (NukiBridgeWhite) - Parse with result: {"deviceType": 0, "nukiId": 30******05, "name": "Nuki_12******A9", "rssi": -87, "paired": false}
2020.11.18 17:17:03.751 5: NUKIBridge (NukiBridgeWhite) - Garbage character before message: ]
2020.11.18 17:17:03.751 5: NUKIBridge (NukiBridgeWhite) - Garbage character before message: }
2020.11.18 17:17:03.752 5: NUKIBridge (NukiBridgeWhite) - return msg: and tail:
2020.11.18 17:17:03.752 5: NUKIBridge (NukiBridgeWhite) - Nach Sub: Laenge JSON: 0 Content: Tail:
Zitat von: CoolTux am 18 November 2020, 18:31:39
Ah verstehe. Aber da kann FHEM aber nichts für. Das sind genau die Daten welche von der Bridge kommen. Warum auch immer erkennt die Bridge auch nicht gepairte Schlösser und listet die auf.
http://192.168.6.101:8080/info?token=xxx: empty answer received
020.11.18 10:02:43.830 4 : NUKIBridge (NUKI_B_Acer) - Response JSON: {"bridgeType":2,"ids":{"serverId":826085686},"versions":{"appVersion":"1.4.6"},"uptime":4837,"currentTime":"2020-11-18T09:02:42Z","serverConnected":true,"scanResults":[{"nukiId":534794661,"name":"Nuki_1FE051A5","rssi":-54,"paired":true}]}
2020.11.18 10:02:43.831 4 : NUKIBridge (NUKI_B_Acer) - Response ERROR:
2020.11.18 10:02:43.831 4 : NUKIBridge (NUKI_B_Acer) - Response CODE: 200
Zitat von: pc1246 am 19 November 2020, 07:03:10
Mal so kurz reingegraetscht. Wenn doch beide Bridges beide Schloesser sehen, dann reicht doch auch eine!?
Zitat von: riker1 am 19 November 2020, 07:13:04
Moin,
wollte meine Frage vonoben nochmal wiederholen.
kennt jemand den Grund und die Beschreibung
Error Code 200?
bridge connected true
Error auch emty responseCode Auswählenhttp://192.168.6.101:8080/info?token=xxx: empty answer received
Code Auswählen020.11.18 10:02:43.830 4 : NUKIBridge (NUKI_B_Acer) - Response JSON: {"bridgeType":2,"ids":{"serverId":826085686},"versions":{"appVersion":"1.4.6"},"uptime":4837,"currentTime":"2020-11-18T09:02:42Z","serverConnected":true,"scanResults":[{"nukiId":534794661,"name":"Nuki_1FE051A5","rssi":-54,"paired":true}]}
2020.11.18 10:02:43.831 4 : NUKIBridge (NUKI_B_Acer) - Response ERROR:
2020.11.18 10:02:43.831 4 : NUKIBridge (NUKI_B_Acer) - Response CODE: 200
Danke
Zitat von: CoolTux am 19 November 2020, 08:47:23
Das 200 bezieht sich auf den HTTP Response Code. Bedeutet alles ok.
bridge connected true heißt einfach das das Schloss mit der Bridge verbunden ist.
lastError
http://192.168.6.101:8080/info?token=xxx: empty answer received
Zitat von: riker1 am 19 November 2020, 09:41:05
Hallo Cooltux,
danke, aber es geht nicht, kann nicht schliessen
Kann nicht set getdevicelist erhalten.
Reading sagt auch Fehler?Code AuswählenlastError
http://192.168.6.101:8080/info?token=xxx: empty answer received
was kann ich prüfen?
Wo muss ich suchen?
Danke T
Zitat von: CoolTux am 19 November 2020, 12:32:37
dann verbose 5 bei der bridge und einmal befehl per set Kommando ausführen. Danach log per pm zu mir.
Zitat von: riker1 am 19 November 2020, 16:59:17
danke hast ne mail pm
1 NUKI_B_Acer
534794661 NUKI_B_Acer
Zitat von: CoolTux am 19 November 2020, 17:34:11
Ändere bitte einmal Deine DEF im NUKIDevice.
AusCode Auswählen1 NUKI_B_Acer
machst Du bitteCode Auswählen534794661 NUKI_B_Acer
Grüße
Zitat von: CoolTux am 19 November 2020, 17:34:11
Ändere bitte einmal Deine DEF im NUKIDevice.
AusCode Auswählen1 NUKI_B_Acer
machst Du bitteCode Auswählen534794661 NUKI_B_Acer
Grüße
Zitat von: Thyraz am 20 November 2020, 11:31:08
Du meinst eine Alternative zu Nuki?
Wenn du das schon hast, dann würde ich eher zur echten Bridge raten. Damit läuft es hier ja beim Rest problemlos.
Das dürfte günstiger kommen als ein anderes Schloß...
Zitat von: riker1 am 20 November 2020, 11:43:28
Hallo Cooltux,
schau mal bitte. Nur ne Kleinigkeit.
habe das attr disable 1 gesetzt. wollte nun wieder 0 setzen.
es gibt aber nur 1 als Ausprägung im Pulldown und es ist nicht in der Attributenliste im Gui enthalten
Danke
PS nach manuellem disable 0 erscheint disable in der Attirbutes liste.
Zitat von: CoolTux am 20 November 2020, 11:58:25
Das ist Absicht. Ich hab nie verstanden wieso man die 0 dafür nehmen soll wenn man das Attribut auch löschen kann und es damit automatisch null ist.
Zitat von: Thyraz am 20 November 2020, 11:31:08
Du meinst eine Alternative zu Nuki?
Wenn du das schon hast, dann würde ich eher zur echten Bridge raten. Damit läuft es hier ja beim Rest problemlos.
Das dürfte günstiger kommen als ein anderes Schloß...
Zitat von: riker1 am 20 November 2020, 12:07:05
ok, aber zum löschen sollte es doch zumindest in der Attributes list mit 1 erscheinen. Da ist es nicht aufgeführt
siehe hardcopy 1.
Internals:
BRIDGEAPI 1.9
DEF 10.6.34.52 7crtn1
FUUID 5e1ecab5-f33f-5153-72d2-68edda8825f3590f
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 10.6.34.52
NAME myNUKIBridge
NOTIFYDEV global,myNUKIBridge
NR 87
NTFY_ORDER 50-myNUKIBridge
PORT 8080
STATE disabled
TOKEN 7crtn1
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-10.6.34.52
WEBHOOK_URL http://10.6.8.35:8083/fhem/NUKIBridge-10.6.34.52
READINGS:
2020-02-03 07:11:29 bridgeType Hardware
2020-02-03 07:11:29 currentTime 2020-02-03T06:11:30+00:00
2020-02-03 07:11:29 firmwareVersion 1.13.1
2020-02-03 07:11:29 hardwareId 106474161
2020-01-31 16:35:28 lastError 10.6.34.52: Verbindungsaufbau abgelehnt (111)
2020-02-03 07:11:29 serverConnected 1
2020-02-03 07:11:29 serverId 11879130
2020-11-20 11:19:11 state disabled
2020-02-03 07:11:29 uptime 225369
2020-02-03 07:11:29 wifiFirmwareVersion 1.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
disable 1
room NUKI
webhookFWinstance WEB
webhookHttpHostname 10.6.8.35
Zitat von: CoolTux am 20 November 2020, 12:10:34
Eventuell ein Anzeigefehler bei dir. Bei mir wird es korrekt angezeigtCode Auswählen
Internals:
BRIDGEAPI 1.9
DEF 10.6.34.52 7crtn1
FUUID 5e1ecab5-f33f-5153-72d2-68edda8825f3590f
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 10.6.34.52
NAME myNUKIBridge
NOTIFYDEV global,myNUKIBridge
NR 87
NTFY_ORDER 50-myNUKIBridge
PORT 8080
STATE disabled
TOKEN 7crtn1
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-10.6.34.52
WEBHOOK_URL http://10.6.8.35:8083/fhem/NUKIBridge-10.6.34.52
READINGS:
2020-02-03 07:11:29 bridgeType Hardware
2020-02-03 07:11:29 currentTime 2020-02-03T06:11:30+00:00
2020-02-03 07:11:29 firmwareVersion 1.13.1
2020-02-03 07:11:29 hardwareId 106474161
2020-01-31 16:35:28 lastError 10.6.34.52: Verbindungsaufbau abgelehnt (111)
2020-02-03 07:11:29 serverConnected 1
2020-02-03 07:11:29 serverId 11879130
2020-11-20 11:19:11 state disabled
2020-02-03 07:11:29 uptime 225369
2020-02-03 07:11:29 wifiFirmwareVersion 1.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
disable 1
room NUKI
webhookFWinstance WEB
webhookHttpHostname 10.6.8.35
Kann das ein anderer bitte einmal testen?
Zitat von: CoolTux am 20 November 2020, 11:58:25Moin
Das ist Absicht. Ich hab nie verstanden wieso man die 0 dafür nehmen soll wenn man das Attribut auch löschen kann und es damit automatisch null ist.
Zitat von: pc1246 am 20 November 2020, 12:59:26
Moin
Das kann ich Dir eventuell erklaeren.
Wenn man etwas loescht, heisst das ja nicht zwingend, dass es auch wirklich weg ist (==0), sondern eventuell nur nicht mehr sichtbar.
Somit koennte der Zustand des Attributes immer noch "1" sein. Ich kenne das aus der PLC Programierung, und deshalb lieber auf "0" stellen koennen.
Gruss Christoph
Zitat von: CoolTux am 18 November 2020, 08:52:05
Hast Du auch ein Smartlock und das funktioniert korrekt? Es wird also ein schließen oder öffnen sofort erkannt von FHEM. Sprich der Webhook ist korrekt eingerichtet.
Zitat von: riker1 am 19 November 2020, 17:54:19
scheinbar war es das: 534794661 NUKI_B_Acer: Woher kommt die Zahl 534794661 ?
nun steht im state nicht mehr inizialize nun ist lock.
mit set device unlock ändert sich auch state zu unlock . aber es passiert nix.
Schein aber das Problem am Handy Android bridge zu sein. Dort leuchtet nun das Schloss rot. Signal sagt keine Verbindung.
Das handy liegt 1m entfernt und nichts wurde bewegt......
ist die Android bridge stabil? Gibt es bekannte Probleme hier? Android version 8
Danke
Zitat von: CoolTux am 24 November 2020, 11:29:52
Die Zahl ist die Nuki ID und sollte eigentlich automatisch ausgelesen werden beim ersten Anlegen des Devices
Internals:
BRIDGEAPI 1.9
DEF 192.168.6.141 6vinaf
FUUID 5fb6b834-f33f-74bb-9d6e-45ac72830c01005f
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.6.141
NAME NUKI_Bridge
NOTIFYDEV global,NUKI_Bridge
NR 106575
NTFY_ORDER 50-NUKI_Bridge
PORT 8080
STATE connected
TOKEN 6vinaf
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8086
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.6.141
WEBHOOK_URL http://192.168.0.9:8086/fhem/NUKIBridge-192.168.6.141
READINGS:
2020-11-24 10:38:24 bridgeType Hardware
2020-11-24 10:38:24 currentTime 2020-11-24T09:38:37+00:00
2020-11-24 10:38:24 firmwareVersion 2.8.0
2020-11-24 10:38:24 hardwareId 538644626
2020-11-24 08:10:20 lastError read from http://192.168.6.141:8080 timed out
2020-11-24 10:38:24 serverConnected 1
2020-11-24 10:38:24 serverId 1368560042
2020-11-24 14:53:14 state connected
2020-11-24 10:38:24 uptime 8974
2020-11-24 10:38:24 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
disable 1
room 1_Kueche,Z_Control
verbose 5
webhookFWinstance WEB8086
webhookHttpHostname 192.168.0.9
Zitat von: riker1 am 25 November 2020, 07:25:05
wo im Log finde ich die Zahl? Habe die Server ID gesehen von der Bridge. Am device noch nicht richtig.
Wenn ich ein neues Nuki anlege, muss ich die Nummer dann Wissen und wird die dann automatisch über die Bridge gefüllt? oder sehe ich die in der Nuki App irgendwo?
Danke
Experimentiere mit der Software Bridge Android.
Habe dazu meine HW Bridge disabled. Aber sie zeigt noch connected an obwohl disabled. Ist das so gewünscht?Code AuswählenInternals:
BRIDGEAPI 1.9
DEF 192.168.6.141 6vinaf
FUUID 5fb6b834-f33f-74bb-9d6e-45ac72830c01005f
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.6.141
NAME NUKI_Bridge
NOTIFYDEV global,NUKI_Bridge
NR 106575
NTFY_ORDER 50-NUKI_Bridge
PORT 8080
STATE connected
TOKEN 6vinaf
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8086
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.6.141
WEBHOOK_URL http://192.168.0.9:8086/fhem/NUKIBridge-192.168.6.141
READINGS:
2020-11-24 10:38:24 bridgeType Hardware
2020-11-24 10:38:24 currentTime 2020-11-24T09:38:37+00:00
2020-11-24 10:38:24 firmwareVersion 2.8.0
2020-11-24 10:38:24 hardwareId 538644626
2020-11-24 08:10:20 lastError read from http://192.168.6.141:8080 timed out
2020-11-24 10:38:24 serverConnected 1
2020-11-24 10:38:24 serverId 1368560042
2020-11-24 14:53:14 state connected
2020-11-24 10:38:24 uptime 8974
2020-11-24 10:38:24 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
disable 1
room 1_Kueche,Z_Control
verbose 5
webhookFWinstance WEB8086
webhookHttpHostname 192.168.0.9
Danke Thomas
020.11.18 11:44:53.753 4 : NUKIBridge (NUKI_B_Acer) - Response JSON: {"bridgeType":2,"ids":{"serverId":826085686},"versions":{"appVersion":"1.4.6"},"uptime":10967,"currentTime":"2020-11-18T10:44:52Z","serverConnected":true,"scanResults":[{"nukiId":534794661,"name":"Nuki_1FE051A5","rssi":-53,"paired":true}]}
Zitat von: CoolTux am 25 November 2020, 08:16:20
Wenn Du ein Log von 5 auf der Bridge machst dann sieht man es an dieser AusgabeCode Auswählen
020.11.18 11:44:53.753 4 : NUKIBridge (NUKI_B_Acer) - Response JSON: {"bridgeType":2,"ids":{"serverId":826085686},"versions":{"appVersion":"1.4.6"},"uptime":10967,"currentTime":"2020-11-18T10:44:52Z","serverConnected":true,"scanResults":[{"nukiId":534794661,"name":"Nuki_1FE051A5","rssi":-53,"paired":true}]}
Das ist der Response von der Abfrage der Bridge. Im JSON stehen die Informationen drin.
Beim disable wird die Bridgeabfrage eingestellt und keine Befehle mehr an die Bridge gesendet. Die Readings bleiben jedoch gleich.
Hi, danke super-.
Vorschlag, wenn disabled, sollte doch State oder STATE disabled anzeigen, fände ich besser, connected hatte mich verwirred.
Aber nur ne Kleinigkeit.
Danke für deine Arbeit.
defmod NUKI2_Unten NUKIDevice xxx NUKI_B_Gigaset
attr NUKI2_Unten IODev NUKI_B_Gigaset
attr NUKI2_Unten model
attr NUKI2_Unten room NUKI
attr NUKI2_Unten verbose 5
setstate NUKI2_Unten lock
setstate NUKI2_Unten 2020-11-26 16:11:30 batteryState ok
setstate NUKI2_Unten 2020-11-26 16:11:30 nukiId xxx
[b]setstate NUKI2_Unten 2020-11-26 08:19:15 state lock
setstate NUKI2_Unten 2020-11-26 16:11:30 stateName unlocked[/b]
setstate NUKI2_Unten 2020-11-26 16:11:30 success 1
setstate NUKI_B_Gigaset 2020-11-26 16:24:39 currentTime 2020-11-26T15:24:38Z
defmod NUKI_B_Gigaset NUKIBridge 192.168.6.101 xxx
attr NUKI_B_Gigaset verbose 5
attr NUKI_B_Gigaset webhookFWinstance WEB8086
attr NUKI_B_Gigaset webhookHttpHostname 192.168.0.9
setstate NUKI_B_Gigaset connected
setstate NUKI_B_Gigaset 2020-11-26 16:24:39 appVersion 1.4.6
setstate NUKI_B_Gigaset 2020-11-26 16:24:39 bridgeType Software
[b]setstate NUKI_B_Gigaset 2020-11-26 16:24:39 currentTime 2020-11-26T15:24:38Z[/b]
setstate NUKI_B_Gigaset 2020-11-26 16:17:27 lastError http://192.168.6.101:8080/info?token=xxx: empty answer received
setstate NUKI_B_Gigaset 2020-11-26 16:24:39 serverConnected 1
setstate NUKI_B_Gigaset 2020-11-26 16:24:39 serverId 593130172
setstate NUKI_B_Gigaset 2020-11-26 16:24:39 state connected
setstate NUKI_B_Gigaset 2020-11-26 16:24:39 uptime 22248
Zitat von: CoolTux am 26 November 2020, 17:53:42
Ich brauche ein richtiges list vom Service und eine Log 5 Ausgabe bitte.
Zitat von: riker1 am 26 November 2020, 20:49:09
Hi Cooltux, hast post. Danke
Readings batteryState ok 2020-11-27 18:02:42 nukiId 23125104 2020-11-27 18:02:42 state 255 2020-11-27 18:02:42 stateName unknown 2020-11-27 18:02:42 success 0 2020-11-27 18:02:42 |
Zitat von: riker1 am 27 November 2020, 18:27:30
Danke das Attribut model war es wohl
Hi CoolTux
mit ist aufgefallen, teste gerade einiges mit Reichweite.
Spiele da auch mit HW Bridge und Android rum.
die REadings sind nicht ganz konsistent. Wenn der das Device nicht erreicht, sollte nicht Batterie ok mit aktuellem Readingstimestamp stehen. oder?
Readings
batteryState ok 2020-11-27 18:02:42
nukiId 23125104 2020-11-27 18:02:42
state 255 2020-11-27 18:02:42
stateName unknown 2020-11-27 18:02:42
success 0 2020-11-27 18:02:42
Einige Ids verwirren mich:Was muss denn wo drinnen stehn?
- Serverid
Hardware ID
Nuki ID
einige IDs kann man aus der App ablesen, sind das die richtigen dann? oder sind das FHEM interne?
Danke für die Klarstellung.
Super Sache das.
VG T
attr NUKI2_Kueche valueFormat { batteryChargeState => "%0d%" }
attr NUKI2_Kueche valueIcon {'batteryChargeState.ok' => 'batterie@green', 'batteryChargeState.low' => 'batterie@red'}
Zitat von: riker1 am 28 November 2020, 09:13:27
Hi CoolTux,
eine Frage, wieso muss man bei der Device Dev die Bridge angeben
das wird doch dann über IODev gemacht?
Habe festgestellt, das ein Update des IODev dann aber nicht mehr die device definition ändert.
Erzeugt das Inkonstenzen?
Habe die devices zwischen Android und HW-Bridge gewechselt.
Danke VG T
Zitat von: riker1 am 28 November 2020, 09:28:16
Hi CoolTux,
bin am aufhübschen, aber komme an meine Grenzen.
Würde gerne die Batterieanzeige darstellen. Kommt vom CUL_HM Modul,
wie würde ich sowas für das Nuki machen?
DankeCode Auswählenattr NUKI2_Kueche valueFormat { batteryChargeState => "%0d%" }
attr NUKI2_Kueche valueIcon {'batteryChargeState.ok' => 'batterie@green', 'batteryChargeState.low' => 'batterie@red'}
Zitat von: CoolTux am 18 Juli 2016, 23:50:11
Für eine aktive Callback Funktion müßen noch zwei Attribute beim Smartlock Device eingerichtet werden.
webhookFWinstance - zu verwendende Webinstanz (darf keine Passwortabfrage beinhalten)
webhookHttpHostname - IP oder FQDN des FHEM Servers
Zitat von: Manos am 28 November 2020, 13:22:07
Hallo Leon,
beim "Smartlock Device" (ich gehe davon aus, damit is NUKIDevice gemeint) lassen sie sich bei mir diese zwei Attributen nicht einrichten. Bei NUKIBridge, ja.
2020-11-29_12:34:53 Nuki_1A486A85 unlatch
2020-11-29_12:35:00 Nuki_1A486A85 unlatch
2020-11-29_12:35:00 Nuki_1A486A85 batteryChargeState: 44
Internals:
BRIDGEAPI 1.9
CFGFN
DEF 440953477 0
DEVICETYPE 0
FUUID 5fc27135-f33f-d8e8-47e4-c55a7aa41eab66a6
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NBridge
LASTInputDev NBridge
MSGCNT 5485
NAME Nuki_1A486A85
NBridge_MSGCNT 5485
NBridge_TIME 2020-11-30 14:33:41
NOTIFYDEV global,autocreate,Nuki_1A486A85
NR 1265
NTFY_ORDER 50-Nuki_1A486A85
NUKIID 440953477
STATE unlatch door closed
TYPE NUKIDevice
VERSION v1.9.12
Helper:
DBLOG:
batteryChargeState:
meineDatenbank:
TIME 1606649700.56334
VALUE 44
state:
meineDatenbank:
TIME 1606649700.56334
VALUE unlatch
READINGS:
2020-11-29 12:35:00 batteryChargeState 44
2020-11-29 12:35:00 batteryCharging 0
2020-11-29 12:35:00 batteryState ok
2020-11-30 14:33:41 deviceType smartlock
2020-11-28 16:48:07 doorsensorState 2
2020-11-28 16:48:07 doorsensorStateName door closed
2020-11-28 16:48:07 mode door mode
2020-11-30 14:33:41 name Nuki_1A486A85
2020-11-30 14:33:41 nukiId 440953477
2020-11-30 14:33:41 paired true
2020-11-30 14:33:41 rssi -40
2020-11-29 12:35:00 state unlatch
2020-11-28 16:48:07 stateName unlocked
2020-11-29 12:35:00 success 1
helper:
Attributes:
DbLogInclude state,batterystate,doorsensorStateName,batteryChargeState,doorsensorState
IODev NBridge
event-on-change-reading state,doorsensorStateName,batteryChargeState,doorsensorState
event-on-update-reading state,batterystate,doorsensorStateName,batteryChargeState,doorsensorState
group NUKI
model smartlock
room Haus,Sicherheit
stateFormat state doorsensorStateName
Montag, 30. November 2020
Türsensor
Josef-Tuschl 5 - Tür geschlossen
05:59
Türsensor
Josef-Tuschl 5 - Tür geöffnet
05:59
Sonntag, 29. November 2020
Türsensor
Josef-Tuschl 5 - Tür geschlossen
12:35
Nuki Bridge
Josef-Tuschl 5 - Tür geöffnet
12:34
Türsensor
Josef-Tuschl 5 - Tür geöffnet
12:34
Türsensor
Josef-Tuschl 5 - Tür geschlossen
11:51
Türsensor
Josef-Tuschl 5 - Tür geöffnet
11:51
Türsensor
Josef-Tuschl 5 - Tür geschlossen
Internals:
BRIDGEAPI 1.9
DEF 192.168.1.104 fq3c3n
FUUID 5e29d21a-f33f-d8e8-d5d2-1dd6c62bd06e91c6
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.1.104
NAME NBridge
NOTIFYDEV global,NBridge
NR 894
NTFY_ORDER 50-NBridge
PORT 8080
STATE connected
TOKEN fq3c3n
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8084
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.1.104
WEBHOOK_URL http://192.168.1.10:8084/fhem/NUKIBridge-192.168.1.104
READINGS:
2020-12-01 17:05:13 bridgeType Hardware
2020-12-01 17:05:13 currentTime 2020-12-01T16:05:14+00:00
2020-12-01 17:05:13 firmwareVersion 2.8.0
2020-12-01 17:05:13 hardwareId 409057010
2020-11-30 17:44:33 lastError http://192.168.1.104:8080/info?token=fq3c3n: empty answer received
2020-12-01 17:05:13 serverConnected 1
2020-12-01 17:05:13 serverId 540476683
2020-12-01 17:05:13 state connected
2020-12-01 17:05:13 uptime 978155
2020-12-01 17:05:13 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
event-on-change-reading firmwareVersion,wifiFirmwareVersion,bridgeType,hardwareId,serverId,,serverConnected
group NUKI
icon 1_nuki_bridge
room Sicherheit
webhookFWinstance WEBNUKI
webhookHttpHostname 192.168.1.10
Zitat von: antonwinden am 01 Dezember 2020, 17:06:57
hier:Code AuswählenInternals:
BRIDGEAPI 1.9
DEF 192.168.1.104 fq3c3n
FUUID 5e29d21a-f33f-d8e8-d5d2-1dd6c62bd06e91c6
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.1.104
NAME NBridge
NOTIFYDEV global,NBridge
NR 894
NTFY_ORDER 50-NBridge
PORT 8080
STATE connected
TOKEN fq3c3n
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8084
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.1.104
WEBHOOK_URL http://192.168.1.10:8084/fhem/NUKIBridge-192.168.1.104
READINGS:
2020-12-01 17:05:13 bridgeType Hardware
2020-12-01 17:05:13 currentTime 2020-12-01T16:05:14+00:00
2020-12-01 17:05:13 firmwareVersion 2.8.0
2020-12-01 17:05:13 hardwareId 409057010
2020-11-30 17:44:33 lastError http://192.168.1.104:8080/info?token=fq3c3n: empty answer received
2020-12-01 17:05:13 serverConnected 1
2020-12-01 17:05:13 serverId 540476683
2020-12-01 17:05:13 state connected
2020-12-01 17:05:13 uptime 978155
2020-12-01 17:05:13 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
event-on-change-reading firmwareVersion,wifiFirmwareVersion,bridgeType,hardwareId,serverId,,serverConnected
group NUKI
icon 1_nuki_bridge
room Sicherheit
webhookFWinstance WEBNUKI
webhookHttpHostname 192.168.1.10
gruß anton
Internals:
BRIDGEAPI 1.9
CFGFN
DEF 440953477 0
DEVICETYPE 0
FUUID 5fc27135-f33f-d8e8-47e4-c55a7aa41eab66a6
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NBridge
LASTInputDev NBridge
MSGCNT 17144
NAME Nuki_1A486A85
NBridge_MSGCNT 17144
NBridge_TIME 2020-12-04 15:51:12
NOTIFYDEV global,autocreate,Nuki_1A486A85
NR 1265
NTFY_ORDER 50-Nuki_1A486A85
NUKIID 440953477
STATE unlocked door closed
TYPE NUKIDevice
VERSION v1.9.12
Helper:
DBLOG:
batteryChargeState:
meineDatenbank:
TIME 1606928427.71457
VALUE 44
doorsensorState:
meineDatenbank:
TIME 1606928427.71457
VALUE 2
doorsensorStateName:
meineDatenbank:
TIME 1606928427.71457
VALUE door closed
state:
meineDatenbank:
TIME 1606928427.71457
VALUE unlocked
READINGS:
2020-12-02 18:00:27 batteryChargeState 44
2020-12-02 18:00:27 batteryCharging 0
2020-12-02 18:00:27 batteryState ok
2020-12-04 15:51:12 deviceType smartlock
2020-12-02 18:00:27 doorsensorState 2
2020-12-02 18:00:27 doorsensorStateName door closed
2020-12-02 18:00:27 mode door mode
2020-12-04 15:51:12 name Nuki_1A486A85
2020-12-04 15:51:12 nukiId 440953477
2020-12-04 15:51:12 paired true
2020-12-04 15:51:12 rssi -41
2020-12-02 18:00:27 state unlocked
2020-12-02 18:00:27 stateName unlocked
2020-12-02 18:00:27 success 1
helper:
Attributes:
DbLogInclude state,batterystate,doorsensorStateName,batteryChargeState,doorsensorState
IODev NBridge
event-on-change-reading state,doorsensorStateName,batteryChargeState,doorsensorState
event-on-update-reading state,batterystate,doorsensorStateName,batteryChargeState,doorsensorState
group NUKI
model smartlock
room Haus,Sicherheit
stateFormat stateName doorsensorStateName
Anton Dürnberger
Josef-Tuschl 5 - Tür geöffnet
15:46
Türsensor
Josef-Tuschl 5 - Tür geöffnet
15:46
Türsensor
Josef-Tuschl 5 - Tür geschlossen
15:26
Türsensor
Josef-Tuschl 5 - Tür geöffnet
15:26
Zitat von: neyzen am 21 Dezember 2020, 20:10:29
Hallo,
ich hab eine Frage.
Wenn ich meine Nuki Aufschließe oder Zuschließe dauert es ca. 30 bis 40 sekunden bis FHEM das merkt und im state lock oder unlocked steht. Es sei den ich mach manuel ein statusrequest. Gibt es eine möglichkeit das der status Zeitnah ein aktualisierung bekommt?
Internals:
BRIDGEAPI 1.9
DEF 192.168.178.46 xxxxxx
FUUID 5fc3fb8a-f33f-2b39-7c32-572e59ba518f9853
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.178.46
NAME NUKIBridge
NOTIFYDEV global,NUKIBridge
NR 211
NTFY_ORDER 50-NUKIBridge
PORT 8080
STATE connected
TOKEN xxxxxx
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.178.46
WEBHOOK_URL http://192.168.178.25:8083/fhem/NUKIBridge-192.168.178.46
READINGS:
2020-12-21 21:06:50 bridgeType Hardware
2020-12-21 21:06:50 currentTime 2020-12-21T20:06:51+00:00
2020-12-21 21:06:50 firmwareVersion 2.8.0
2020-12-21 21:06:50 hardwareId 507891698
2020-12-18 18:31:11 lastError http://192.168.178.46:8080/info?token=xxxxx: empty answer received
2020-12-21 21:06:50 serverConnected 1
2020-12-21 21:06:50 serverId 203593790
2020-12-21 21:06:50 state connected
2020-12-21 21:06:50 uptime 461147
2020-12-21 21:06:50 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
event-on-change-reading wifiFirmwareVersion
room NUKI,Sicherheit
webhookFWinstance WEB
webhookHttpHostname 192.168.178.25
WEBHOOK_COUNTER 590
WEBHOOK_LAST 2020-12-22 19:54:09
WEBHOOK_COUNTER
56
Zitat von: CoolTux am 14 Dezember 2020, 13:13:15
Scheint so als wenn über den Webhook nicht immer korrekt die Daten kommen. Aber eigentlich sollte er schon spätestens beim nächsten interval update den korrekten Status bekommen. Hier wäre ein verbose 4 Log nicht schlecht.
2021-01-16_09:13:47 Nuki_Haustuer rssi: -60
2021-01-16_09:13:47 Nuki_Haustuer paired: true
2021-01-16_09:13:47 Nuki_Haustuer name: Nuki_XYXYXY
2021-01-16_09:13:47 Nuki_Haustuer nukiId: 59XYZXYZ
2021-01-16_09:13:47 Nuki_Haustuer deviceType: smartlock
2021-01-16_09:14:17 Nuki_Haustuer paired: true
2021-01-16_09:14:17 Nuki_Haustuer rssi: -60
2021-01-16_09:14:17 Nuki_Haustuer name: Nuki_XYXYXY
2021-01-16_09:14:17 Nuki_Haustuer deviceType: smartlock
2021-01-16_09:14:17 Nuki_Haustuer nukiId: 59XYZXYZ
2021-01-16_09:14:18 Nuki_Haustuer statusRequest
2021-01-16_09:14:18 Nuki_Haustuer batteryState: ok
2021-01-16_09:14:18 Nuki_Haustuer doorsensorState: 2
2021-01-16_09:14:18 Nuki_Haustuer mode: door mode
2021-01-16_09:14:18 Nuki_Haustuer locked
2021-01-16_09:14:18 Nuki_Haustuer batteryCharging: 0
2021-01-16_09:14:18 Nuki_Haustuer stateName: locked
2021-01-16_09:14:18 Nuki_Haustuer nukiId: 59XYZXYZ
2021-01-16_09:14:18 Nuki_Haustuer batteryChargeState: 58
2021-01-16_09:14:18 Nuki_Haustuer success: 1
2021-01-16_09:14:18 Nuki_Haustuer doorsensorStateName: door closed
2021-01-16_09:14:51 Nuki_Haustuer rssi: -60
2021-01-16_09:14:51 Nuki_Haustuer paired: true
2021-01-16_09:14:51 Nuki_Haustuer name: Nuki_XYXYXY
2021-01-16_09:14:51 Nuki_Haustuer nukiId: 59XYZXYZ
2021-01-16_09:14:51 Nuki_Haustuer deviceType: smartlock
Internals:
BRIDGEAPI 1.9
DEF 192.168.178.243 XYZXYZ
FUUID 5fXYZY94-f33f-2a61-86a1-5b5b5b59XYZXYZXY
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.178.243
NAME NukiBridge01
NOTIFYDEV global,NukiBridge01
NR 4731
NTFY_ORDER 50-NukiBridge01
PORT 8080
STATE connected
TOKEN XYZXYZ
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 5
WEBHOOK_LAST 2021-01-16 00:55:15
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.178.243
WEBHOOK_URL http://192.168.178.230:8083/fhem/NUKIBridge-192.168.178.243
READINGS:
2021-01-16 12:23:25 bridgeType Hardware
2021-01-16 12:23:25 currentTime 2021-01-16T11:23:32+00:00
2021-01-16 12:23:25 firmwareVersion 2.8.0
2021-01-16 12:23:25 hardwareId 53XYZXYZX
2020-12-19 11:19:41 lastError read from http://192.168.178.243:8080 timed out
2021-01-16 12:23:25 serverConnected 1
2021-01-16 12:23:25 serverId 1115XYZXYZ
2021-01-16 12:23:25 state connected
2021-01-16 12:23:25 uptime 3383797
2021-01-16 12:23:25 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 1
actionQueue:
Attributes:
room NUKI
webhookFWinstance WEB
webhookHttpHostname 192.168.178.230
Internals:
BRIDGEAPI 1.9
DEF 59XYZXYZX 0
DEVICETYPE 0
FUUID 5faXYZX8-f33f-2a61-4363-09744de6XYZXYZXY
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NukiBridge01
LASTInputDev NukiBridge01
MSGCNT 2289
NAME Nuki_Haustuer
NOTIFYDEV global,autocreate,Nuki_Haustuer
NR 4732
NTFY_ORDER 50-Nuki_Haustuer
NUKIID 59XYZXYZX
NukiBridge01_MSGCNT 2289
NukiBridge01_TIME 2021-01-16 12:26:34
STATE locked
TYPE NUKIDevice
VERSION v1.9.12
READINGS:
2021-01-16 09:14:18 batteryChargeState 58
2021-01-16 09:14:18 batteryCharging 0
2021-01-16 09:14:18 batteryState ok
2021-01-16 12:26:34 deviceType smartlock
2021-01-16 09:14:18 doorsensorState 2
2021-01-16 09:14:18 doorsensorStateName door closed
2021-01-15 16:26:55 firmwareVersion 2.9.10
2021-01-16 09:14:18 mode door mode
2021-01-16 12:26:34 name Nuki_23XYZXYZ
2021-01-16 12:26:34 nukiId 59XYZXYZX
2021-01-16 12:26:34 paired true
2021-01-16 12:26:34 rssi -60
2021-01-16 09:14:18 state locked
2021-01-16 09:14:18 stateName locked
2021-01-16 09:14:18 success 1
helper:
Attributes:
IODev NukiBridge01
model smartlock
room NUKI
Internals:
BYTES_READ 1108705
BYTES_WRITTEN 306559455
CONNECTS 388
DEF 8083 global
FD 7
FUUID 5e0XYZX5-f33f-2a61-aa1a-1e5ea9a0XYZXYZXY
NAME WEB
NR 12
NTFY_ORDER 50-WEB
PORT 8083
STATE Initialized
TYPE FHEMWEB
READINGS:
2021-01-15 16:23:42 state Initialized
Attributes:
JavaScripts codemirror/fhem_codemirror.js
comment 28.08.2018:
longpoll = 1 funktioniert ohne Websocket-Erweiterung im Reverse Proxy
altes Layout:
iconPath = default:fhemSVG:openautomation
stylesheetPrefix = default
F18:
iconPath = fhemSVG:openautomation:default
stylesheetPrefix = f18
csrfToken none
editConfig 1
iconPath default:fhemSVG:openautomation
longpoll 1
stylesheetPrefix default
sudo apt-get install libjson-perl
Zitat von: heikoh81 am 16 Januar 2021, 16:17:32
Ich habe einen Hinweis zum NUKI-Wiki-Eintrag (https://wiki.fhem.de/wiki/NUKI).
Bei der Einbindung meines Nuki in FHEM bin ich darüber gestolpert.
Dort steht:
Voraussetzung für ein fehlerfreies Laden ist die Installation von JSON (libperl-json).
Aus meiner Sicht heißt das Modul aber: libjson-perl
Könnte jemand mit Schreibberechtigung im Wiki den Eintrag verbessern, eventuell auch gleich der Hinweis zur Installation dazu:Code Auswählensudo apt-get install libjson-perl
Danke!
Grüße,
Heiko
Zitat von: heikoh81 am 16 Januar 2021, 12:31:23
Hallo Marko,
ich habe das Log jetzt einmal mit verbose 5 über lange Zeit laufen lassen, gestern ist die Abweichung des lock-Status dann wieder aufgetreten.
Aus dem Log sehe ich nicht, warum die Status-Änderung nicht in fhem erscheint.
Ein "set Nuki_Haustuer statusRequest" führt aber dazu, dass state und stateName wieder übereinstimmen.Code Auswählen
2021-01-16_09:13:47 Nuki_Haustuer rssi: -60
2021-01-16_09:13:47 Nuki_Haustuer paired: true
2021-01-16_09:13:47 Nuki_Haustuer name: Nuki_XYXYXY
2021-01-16_09:13:47 Nuki_Haustuer nukiId: 59XYZXYZ
2021-01-16_09:13:47 Nuki_Haustuer deviceType: smartlock
2021-01-16_09:14:17 Nuki_Haustuer paired: true
2021-01-16_09:14:17 Nuki_Haustuer rssi: -60
2021-01-16_09:14:17 Nuki_Haustuer name: Nuki_XYXYXY
2021-01-16_09:14:17 Nuki_Haustuer deviceType: smartlock
2021-01-16_09:14:17 Nuki_Haustuer nukiId: 59XYZXYZ
2021-01-16_09:14:18 Nuki_Haustuer statusRequest
2021-01-16_09:14:18 Nuki_Haustuer batteryState: ok
2021-01-16_09:14:18 Nuki_Haustuer doorsensorState: 2
2021-01-16_09:14:18 Nuki_Haustuer mode: door mode
2021-01-16_09:14:18 Nuki_Haustuer locked
2021-01-16_09:14:18 Nuki_Haustuer batteryCharging: 0
2021-01-16_09:14:18 Nuki_Haustuer stateName: locked
2021-01-16_09:14:18 Nuki_Haustuer nukiId: 59XYZXYZ
2021-01-16_09:14:18 Nuki_Haustuer batteryChargeState: 58
2021-01-16_09:14:18 Nuki_Haustuer success: 1
2021-01-16_09:14:18 Nuki_Haustuer doorsensorStateName: door closed
2021-01-16_09:14:51 Nuki_Haustuer rssi: -60
2021-01-16_09:14:51 Nuki_Haustuer paired: true
2021-01-16_09:14:51 Nuki_Haustuer name: Nuki_XYXYXY
2021-01-16_09:14:51 Nuki_Haustuer nukiId: 59XYZXYZ
2021-01-16_09:14:51 Nuki_Haustuer deviceType: smartlock
Den webhookHttpHostname von NukiBridge01 habe ich auf "192.168.178.230" (die IP des fhem-raspis) gestellt.
Soll ich hier mal "localhost" probieren?
Bei WEB habe ich attr WEB longpoll 1 - könnte das vielleicht ein Grund sein?
list NukiBridge01:Code Auswählen
Internals:
BRIDGEAPI 1.9
DEF 192.168.178.243 XYZXYZ
FUUID 5fXYZY94-f33f-2a61-86a1-5b5b5b59XYZXYZXY
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.178.243
NAME NukiBridge01
NOTIFYDEV global,NukiBridge01
NR 4731
NTFY_ORDER 50-NukiBridge01
PORT 8080
STATE connected
TOKEN XYZXYZ
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 5
WEBHOOK_LAST 2021-01-16 00:55:15
WEBHOOK_PORT 8083
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.178.243
WEBHOOK_URL http://192.168.178.230:8083/fhem/NUKIBridge-192.168.178.243
READINGS:
2021-01-16 12:23:25 bridgeType Hardware
2021-01-16 12:23:25 currentTime 2021-01-16T11:23:32+00:00
2021-01-16 12:23:25 firmwareVersion 2.8.0
2021-01-16 12:23:25 hardwareId 53XYZXYZX
2020-12-19 11:19:41 lastError read from http://192.168.178.243:8080 timed out
2021-01-16 12:23:25 serverConnected 1
2021-01-16 12:23:25 serverId 1115XYZXYZ
2021-01-16 12:23:25 state connected
2021-01-16 12:23:25 uptime 3383797
2021-01-16 12:23:25 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 1
actionQueue:
Attributes:
room NUKI
webhookFWinstance WEB
webhookHttpHostname 192.168.178.230
list Nuki_Haustuer:Code Auswählen
Internals:
BRIDGEAPI 1.9
DEF 59XYZXYZX 0
DEVICETYPE 0
FUUID 5faXYZX8-f33f-2a61-4363-09744de6XYZXYZXY
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NukiBridge01
LASTInputDev NukiBridge01
MSGCNT 2289
NAME Nuki_Haustuer
NOTIFYDEV global,autocreate,Nuki_Haustuer
NR 4732
NTFY_ORDER 50-Nuki_Haustuer
NUKIID 59XYZXYZX
NukiBridge01_MSGCNT 2289
NukiBridge01_TIME 2021-01-16 12:26:34
STATE locked
TYPE NUKIDevice
VERSION v1.9.12
READINGS:
2021-01-16 09:14:18 batteryChargeState 58
2021-01-16 09:14:18 batteryCharging 0
2021-01-16 09:14:18 batteryState ok
2021-01-16 12:26:34 deviceType smartlock
2021-01-16 09:14:18 doorsensorState 2
2021-01-16 09:14:18 doorsensorStateName door closed
2021-01-15 16:26:55 firmwareVersion 2.9.10
2021-01-16 09:14:18 mode door mode
2021-01-16 12:26:34 name Nuki_23XYZXYZ
2021-01-16 12:26:34 nukiId 59XYZXYZX
2021-01-16 12:26:34 paired true
2021-01-16 12:26:34 rssi -60
2021-01-16 09:14:18 state locked
2021-01-16 09:14:18 stateName locked
2021-01-16 09:14:18 success 1
helper:
Attributes:
IODev NukiBridge01
model smartlock
room NUKI
list WEB:Code Auswählen
Internals:
BYTES_READ 1108705
BYTES_WRITTEN 306559455
CONNECTS 388
DEF 8083 global
FD 7
FUUID 5e0XYZX5-f33f-2a61-aa1a-1e5ea9a0XYZXYZXY
NAME WEB
NR 12
NTFY_ORDER 50-WEB
PORT 8083
STATE Initialized
TYPE FHEMWEB
READINGS:
2021-01-15 16:23:42 state Initialized
Attributes:
JavaScripts codemirror/fhem_codemirror.js
comment 28.08.2018:
longpoll = 1 funktioniert ohne Websocket-Erweiterung im Reverse Proxy
altes Layout:
iconPath = default:fhemSVG:openautomation
stylesheetPrefix = default
F18:
iconPath = fhemSVG:openautomation:default
stylesheetPrefix = f18
csrfToken none
editConfig 1
iconPath default:fhemSVG:openautomation
longpoll 1
stylesheetPrefix default
Viele Grüße,
Heiko
Zitat von: CoolTux am 20 Januar 2021, 17:41:27
Hast Du ein Passwort für den webhook gesetzt? Also für die WEB Instanz welche als webhook definiert ist?
Zitat von: dobiwan am 12 Januar 2021, 14:46:07
Hallo zusammen,
ich habe die NUKI Bridge erfolgreich in fhem integriert. Leider wurden die Smartlocks nicht eingerichtet. Ich habe versucht sie händisch anzulegen, was auch funktioniert. Nur sehe ich leider keinen Status.
Hat schon jemand einen NUKI FOB integriert. Ich habe jetzt nicht alle 115 Seiten und Posts durchgelesen.
Vielen Dank für eure Hilfe
Zitat von: heikoh81 am 22 Januar 2021, 22:58:10
Nein.
set Nuki_Haustuer statusRequest
attr Nuki_Haustuer stateFormat stateName
attr Nuki_Haustuer stateFormat stateName
Zitat von: heikoh81 am 09 Februar 2021, 23:28:49
Danke für deine Antwort.
Wie könnte man dies debuggen?
Merkwüdig, dass es sonst noch niemand bemerkt hat.Code Auswählenattr Nuki_Haustuer stateFormat stateName
funktioniert bisher gut.
Zitat von: CoolTux am 08 Februar 2021, 12:56:22
Bitte gib mal ein list von der Bridge und eines vom Smartlock Device.
Grüße
Zitat von: CoolTux am 10 Februar 2021, 08:05:55
Bitte nur list. Also
list BRIDGEDEVICE
list SMARTLOCKDEVICE
Die DEF von Deinem Smartlock passt nicht.
define <name> NUKIDevice <Nuki-Id> <IODev-Device> <Device-Type>
!! Das ergibt den Fehler im Bild. !!
In der NOTIFYDEV vom NUKIDevice steht autocreate drin, das ist Unsinn. Wie ist das denn da rein gekommen?
!! Das weiß ich nicht, habe es nicht reingeschrieben. !!
Das wird beim Define automatisch mit eingtragen
Und Du solltest überlegen ob Du wirklich die Software Bridge verwenden möchtest, die Entwicklung dafür wurde eingestellt.
Zitat von: dobiwan am 11 Februar 2021, 09:14:39
Hier noch die List Ausgaben
Zitat von: CoolTux am 11 Februar 2021, 11:00:19Also wenn ich define Haustuer NUKIDevice 1 MyBridge 0 eingebe und das Device erzeugen will bekomme ich folgende Meldung zurück
Sorry aber so wird das nichts. Was bringt mir Dein Screenshot wenn ich nicht weiß was Du genau gemacht hast. Ich muss schon wissen wie Dein define aus schaut welches Du änderst.
Ich habe ehrlich keine Zeit für solche Halbherzigkeiten. Tut mir Leid.
Gib mir ein vernünftiges Fehlerbild. Übersichtlich wo ich erkenne was Du gemacht hast und wie das Resultat darauf aus sah.
Zitat von: CoolTux am 11 Februar 2021, 11:00:19
Lösche am besten das NUKIDevice noch mal und lasse es von der Bridge neu anlegen. Klappt das nicht lege es von Hand an und zwar so wie es die Commandref empfiehlt.
Zitat von: CoolTux am 10 Februar 2021, 00:34:28
Interessant wäre zu erfahren wann es genau immer so ist.
Es sollte sich definitiv darauf beschränken das es nur unterschiedlich ist wenn aus FHEM raus geschalten wird. Wenn am Schloss direkt oder über die App geschalten wird dürfte das nie passieren.
Zitat von: heikoh81 am 11 Februar 2021, 22:10:35
Wenn es zu einer Abweichung zwischen state und stateName kommt, wurde davor immer mit FHEM gesteuert.
Ich kontrolliere immer nachts vor dem Schlafengehen den Zustand der Haustür, deshalb fällt es mir nur da auf.
Ich habe neben der Haustür einen Taster, der für das Außenlicht gedacht war, umgewandelt in einen, der per MQTT an fhem meldet. Daraufhin erfolgt über ein DOIF dann der Befehl an die Bridge, abzuschließen.
Wir haben noch einen Ekey Uno Fingerprint Reader, der direkt am Nuki angelernt ist. Der wird aber nur tagsüber verwendet, und definitv nicht zum nächtlichen Abschließen, der hängt ja außen :D
Viele Grüße,
Heiko
VR_NUKI_Haustuer:ringactionState:.* {
Log 1, "act_VR_Klingel_Nuki: ringactionState/event: ".$EVENT." - state: ".Value($NAME);
#rto active?
if(index(Value($NAME), "rto") != -1)
{
#rto active
fhem("setreading ".$NAME." rto_active rto_active");
}
#reset rto state to online
if((index($EVENT, "0") != -1) && (index(Value($NAME), "online") != -1))
{
#reset rto state to online
fhem("setreading ".$NAME." rto_active online ;");
fhem("setstate watchdog_VR_Klingel defined ;");
}
#someone rang?
if(index($EVENT, "1") != -1) {
#known or unkown?
if(index(ReadingsVal($NAME,"rto_active", "online"), "online") != -1)
{
#someone unkown rang!
Log 1, "act_VR_Klingel_Nuki: someone unkown rang!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!";
}
#reset rto state to online
fhem("setreading ".$NAME." rto_active online ;");
fhem("setstate watchdog_VR_Klingel defined ;");
}
}
Zitat von: CoolTux am 11 Februar 2021, 16:04:25
Ich weiß ja das es für Euch einfacher ist wenn ich es mache und ich kann diese Auffassung auch verstehen, immerhin habe ich das Modul ja geschrieben. Aber wenn ich mal nicht so viel Zeit habe und ich Euch dennoch helfen möchte muss eine ordentliche Vorarbeit geleistet werden.
Schau mal hier
https://forum.fhem.de/index.php/topic,55756.msg1104230.html#msg1104230
Dort kann man erlesen wie man an die ID des NUKI Smartlock kommt. Man sieht bei verbose 5 der NUKI Bridge den JSON String wo das Nuki Smartlock drin samt ID aufgeführt wird.
Desweiteren ist die define Syntax
define <name> NUKIDevice <Nuki-Id> <IODev-Device> <Device-Type>
also
define Haustuer NUKIDevice <NUKI_ID_AUS_JSON_STRING> MyBridge 0
Das sollte eigentlich klappen. Wenn das nicht klappt dann lass bitte MyBridge weg, eventuell habe ich da nach dem Umbau was vergessen dann bitte ich um Entschuldigung.
Dann musst Du aber das IODEV über das Attribut korrekt setzen.
Wichtig am Ende für Dich ist die NUKI_ID, wenn Du die korrekt gesetzt hast dann wird es auch klappen.
Zitat von: Thyraz am 14 Februar 2021, 21:35:41Schnell = Instant 8)
Was bedeutet schnell für dich? ;)
Ich habe max. 2 Sekunden Verzögerung zum Relais das parallel dran hängt.
Meist weniger.
Da ich immer noch zu faul war das Relais abzuklemmen und für beides Push Notifications auf dem Handy habe, hab ich da die tägliche Kontrolle.
Komplettaussetzer hatte ich bisher keine.
Internals:
BRIDGEAPI 1.9
DEF 192.168.0.114 t****7
FUUID 60f9ca4b-f33f-****-7450-022024d5167f5ff3
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.0.114
NAME NUKIBridge
NOTIFYDEV global,NUKIBridge
NR 500
NTFY_ORDER 50-NUKIBridge
PORT 8080
STATE connected
TOKEN t****7
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 1
WEBHOOK_LAST 2021-07-30 23:01:22
WEBHOOK_PORT 8084
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.0.114
WEBHOOK_URL http://192.168.0.112:8084/fhem/NUKIBridge-192.168.0.114
READINGS:
2021-07-30 22:34:22 bridgeType Hardware
2021-07-30 22:34:22 currentTime 2021-07-30T20:34:21+00:00
2021-07-30 22:34:22 firmwareVersion 2.9.3
2021-07-30 22:34:22 hardwareId 5482**570
2021-07-30 22:34:22 serverConnected 1
2021-07-30 22:34:22 serverId 553196154
2021-07-30 23:11:31 state connected
2021-07-30 22:34:22 uptime 1492
2021-07-30 22:34:22 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
icon 1_nuki_bridge
room NUKI
verbose 5
webhookFWinstance WEBnuki
webhookHttpHostname 192.168.0.112
Internals:
BRIDGEAPI 1.9
DEF 592***821 0
DEVICETYPE 0
FUUID 60f9ca4b-f33f-0d64-****-a0ead5f6ffce4659
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NUKIBridge
LASTInputDev NUKIBridge
MSGCNT 7
NAME Garten
NOTIFYDEV global,autocreate,Garten
NR 501
NTFY_ORDER 50-Garten
NUKIBridge_MSGCNT 7
NUKIBridge_TIME 2021-07-30 23:11:31
NUKIID 592***821
STATE smartlock response error
TYPE NUKIDevice
VERSION v1.9.12
READINGS:
2021-07-30 22:56:36 IODev NUKIBridge
2021-07-30 23:01:22 batteryChargeState 88
2021-07-30 23:01:22 batteryCharging 0
2021-07-30 23:01:22 batteryState ok
2021-07-30 23:01:22 deviceType smartlock
2021-07-30 23:01:22 doorsensorState 2
2021-07-30 23:01:22 doorsensorStateName door closed
2021-07-30 22:52:10 firmwareVersion 2.10.8
2021-07-30 23:01:22 mode door mode
2021-07-30 22:52:10 name Garten
2021-07-30 23:11:31 nukiId 592***821
2021-07-30 22:34:22 paired true
2021-07-30 22:34:22 rssi -84
2021-07-30 23:11:24 state smartlock response error
2021-07-30 23:01:22 stateName locked
2021-07-30 23:11:31 success 0
helper:
Attributes:
genericDeviceType lock
icon 1_nuki
model smartlock
room Garten,HomeKit,NUKI
verbose 5
Internals:
BYTES_READ 415
BYTES_WRITTEN 0
CONNECTS 261
CSRFTOKEN csrf_499071***255409
DEF 8084 global
FD 7
FUUID 61045eea-***-0d64-fcfb-a47c83b9c862abc7
NAME WEBnuki
NR 18
NTFY_ORDER 50-WEBnuki
PORT 8084
STATE Initialized
TYPE FHEMWEB
READINGS:
2021-07-30 22:56:34 state Initialized
Attributes:
allowfrom 192.168.0.114
hiddenroomRegexp ^(?!NUKI)
room System
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - Response JSON: {"success": false}
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - Response ERROR:
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - Response CODE: 200
2021.07.30 23:21:51 5: NUKIBridge (NUKIBridge) - Bridge ist online
2021.07.30 23:21:51 5: NUKIBridge: dispatch {"nukiId":"592***821","success":false}
2021.07.30 23:21:51 5: NUKIDevice (NUKIBridge) - Parse with result: {"nukiId":"592***821","success":false}
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - created uri: http://192.168.0.114:8080/lockState?token=t****7&nukiId=592***821&deviceType=0
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - Send HTTP POST with URL http://192.168.0.114:8080/lockState?token=t****7&nukiId=592***821&deviceType=0
2021.07.30 23:21:51 5: NUKIDevice (Garten) - lockAction readings set for Garten
2021.07.30 23:21:51 4: NUKIDevice (Garten) - find logical device: Garten
2021.07.30 23:21:52 4: NUKIBridge (NUKIBridge) - Response JSON: HTTP 503 Unavailable
2021.07.30 23:21:52 4: NUKIBridge (NUKIBridge) - Response ERROR:
2021.07.30 23:21:52 4: NUKIBridge (NUKIBridge) - Response CODE: 503
2021.07.30 23:21:52 4: NUKIBridge (NUKIBridge) - Response from Bridge: 503, HTTP 503 Unavailable
Zitat von: freddeh am 30 Juli 2021, 23:26:07
Hi ihr Lieben,
ich scheitere aktuell an der Einbindung meines Nuki Smartlocks in FHEM.
Bridge:Code AuswählenInternals:
BRIDGEAPI 1.9
DEF 192.168.0.114 t****7
FUUID 60f9ca4b-f33f-****-7450-022024d5167f5ff3
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 192.168.0.114
NAME NUKIBridge
NOTIFYDEV global,NUKIBridge
NR 500
NTFY_ORDER 50-NUKIBridge
PORT 8080
STATE connected
TOKEN t****7
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 1
WEBHOOK_LAST 2021-07-30 23:01:22
WEBHOOK_PORT 8084
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-192.168.0.114
WEBHOOK_URL http://192.168.0.112:8084/fhem/NUKIBridge-192.168.0.114
READINGS:
2021-07-30 22:34:22 bridgeType Hardware
2021-07-30 22:34:22 currentTime 2021-07-30T20:34:21+00:00
2021-07-30 22:34:22 firmwareVersion 2.9.3
2021-07-30 22:34:22 hardwareId 5482**570
2021-07-30 22:34:22 serverConnected 1
2021-07-30 22:34:22 serverId 553196154
2021-07-30 23:11:31 state connected
2021-07-30 22:34:22 uptime 1492
2021-07-30 22:34:22 wifiFirmwareVersion 2.2.0
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
icon 1_nuki_bridge
room NUKI
verbose 5
webhookFWinstance WEBnuki
webhookHttpHostname 192.168.0.112
Smartlock:Code AuswählenInternals:
BRIDGEAPI 1.9
DEF 592***821 0
DEVICETYPE 0
FUUID 60f9ca4b-f33f-0d64-****-a0ead5f6ffce4659
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NUKIBridge
LASTInputDev NUKIBridge
MSGCNT 7
NAME Garten
NOTIFYDEV global,autocreate,Garten
NR 501
NTFY_ORDER 50-Garten
NUKIBridge_MSGCNT 7
NUKIBridge_TIME 2021-07-30 23:11:31
NUKIID 592***821
STATE smartlock response error
TYPE NUKIDevice
VERSION v1.9.12
READINGS:
2021-07-30 22:56:36 IODev NUKIBridge
2021-07-30 23:01:22 batteryChargeState 88
2021-07-30 23:01:22 batteryCharging 0
2021-07-30 23:01:22 batteryState ok
2021-07-30 23:01:22 deviceType smartlock
2021-07-30 23:01:22 doorsensorState 2
2021-07-30 23:01:22 doorsensorStateName door closed
2021-07-30 22:52:10 firmwareVersion 2.10.8
2021-07-30 23:01:22 mode door mode
2021-07-30 22:52:10 name Garten
2021-07-30 23:11:31 nukiId 592***821
2021-07-30 22:34:22 paired true
2021-07-30 22:34:22 rssi -84
2021-07-30 23:11:24 state smartlock response error
2021-07-30 23:01:22 stateName locked
2021-07-30 23:11:31 success 0
helper:
Attributes:
genericDeviceType lock
icon 1_nuki
model smartlock
room Garten,HomeKit,NUKI
verbose 5
FHEM Instanz:Code AuswählenInternals:
BYTES_READ 415
BYTES_WRITTEN 0
CONNECTS 261
CSRFTOKEN csrf_499071***255409
DEF 8084 global
FD 7
FUUID 61045eea-***-0d64-fcfb-a47c83b9c862abc7
NAME WEBnuki
NR 18
NTFY_ORDER 50-WEBnuki
PORT 8084
STATE Initialized
TYPE FHEMWEB
READINGS:
2021-07-30 22:56:34 state Initialized
Attributes:
allowfrom 192.168.0.114
hiddenroomRegexp ^(?!NUKI)
room System
Sowohl der Webhook scheint nicht zuverlässig zu funktionieren als auch das Öffnen/Schließen des Schlosses liefert immer nur einen Error 503...
Per App funktioniert alles...
Log eines Schließvorgangs:Code Auswählen2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - Response JSON: {"success": false}
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - Response ERROR:
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - Response CODE: 200
2021.07.30 23:21:51 5: NUKIBridge (NUKIBridge) - Bridge ist online
2021.07.30 23:21:51 5: NUKIBridge: dispatch {"nukiId":"592***821","success":false}
2021.07.30 23:21:51 5: NUKIDevice (NUKIBridge) - Parse with result: {"nukiId":"592***821","success":false}
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - created uri: http://192.168.0.114:8080/lockState?token=t****7&nukiId=592***821&deviceType=0
2021.07.30 23:21:51 4: NUKIBridge (NUKIBridge) - Send HTTP POST with URL http://192.168.0.114:8080/lockState?token=t****7&nukiId=592***821&deviceType=0
2021.07.30 23:21:51 5: NUKIDevice (Garten) - lockAction readings set for Garten
2021.07.30 23:21:51 4: NUKIDevice (Garten) - find logical device: Garten
2021.07.30 23:21:52 4: NUKIBridge (NUKIBridge) - Response JSON: HTTP 503 Unavailable
2021.07.30 23:21:52 4: NUKIBridge (NUKIBridge) - Response ERROR:
2021.07.30 23:21:52 4: NUKIBridge (NUKIBridge) - Response CODE: 503
2021.07.30 23:21:52 4: NUKIBridge (NUKIBridge) - Response from Bridge: 503, HTTP 503 Unavailable
Jemand eine Idee?
Zitat von: Udomatic am 31 Juli 2021, 07:51:46
In der Bridge hast du das Attribut webhookFWinstance mit WEBnuki gesetzt. Heist deine FHEM Webinstanz wirklich so? Im Standard ist das eigentlich immer nur WEB
2021.09.14 23:00:12.394 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 1115.
2021.09.14 23:03:02.386 1: Connection refused from 192.168.151.214:64364
2021.09.14 23:07:34.479 4: NUKIBridge (NUKIBridge) - created uri: http://192.168.151.214:8080/clearlog?token=SVUGQN
2021.09.14 23:07:34.480 4: NUKIBridge (NUKIBridge) - Send HTTP POST with URL http://192.168.151.214:8080/clearlog?token=SVUGQN
2021.09.14 23:07:34.718 4: NUKIBridge (NUKIBridge) - Response JSON: {"success": true}
2021.09.14 23:07:34.718 4: NUKIBridge (NUKIBridge) - Response ERROR:
2021.09.14 23:07:34.718 4: NUKIBridge (NUKIBridge) - Response CODE: 200
2021.09.14 23:07:34.729 5: NUKIBridge (NUKIBridge) - Bridge ist online
2021.09.14 23:07:34.729 5: NUKIBridge (NUKIBridge) - Rückgabe Path nicht korrekt:
{"success": true}
2021.09.14 23:08:04.571 3: NUKIBridge WEBHOOK (NUKIBridge) - empty message received
2021.09.14 23:10:13.657 4: NUKIBridge (NUKIBridge) - created uri: http://192.168.151.214:8080/info?token=SVUGQN
2021.09.14 23:10:13.657 4: NUKIBridge (NUKIBridge) - Send HTTP POST with URL http://192.168.151.214:8080/info?token=SVUGQN
2021.09.14 23:10:13.792 4: NUKIBridge (NUKIBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 701029150, "serverId": 2120965652}, "versions": {"firmwareVersion": "2.9.3", "wifiFirmwareVersion": "2.2.0"}, "uptime": 3700, "currentTime": "2021-09-14T21:10:13+00:00", "wlanConnected": true, "serverConnected": true, "scanResults": [{"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true}]}
2021.09.14 23:10:13.792 4: NUKIBridge (NUKIBridge) - Response ERROR:
2021.09.14 23:10:13.792 4: NUKIBridge (NUKIBridge) - Response CODE: 200
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - Bridge ist online
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - 1 == 1 and 1 > 0
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - 1 == 1 and 1 > 0
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - return msg: {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true} and tail: ]}
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - Decoding JSON message. Length: 92 Content: {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true}
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - Vor Sub: Laenge JSON: 92 Content: {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true} Tail: ]}
2021.09.14 23:10:13.796 5: NUKIBridge: dispatch {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true}
2021.09.14 23:10:13.796 5: NUKIDevice (NUKIBridge) - Parse with result: {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true}
2021.09.14 23:10:13.799 5: NUKIBridge (NUKIBridge) - Garbage character before message: ]
2021.09.14 23:10:13.799 5: NUKIBridge (NUKIBridge) - Garbage character before message: }
2021.09.14 23:10:13.799 5: NUKIBridge (NUKIBridge) - return msg: and tail:
2021.09.14 23:10:13.799 5: NUKIBridge (NUKIBridge) - Nach Sub: Laenge JSON: 0 Content: Tail:
2021.09.14 23:10:33.027 3: NUKIBridge WEBHOOK (NUKIBridge) - empty message received
NUKIBridge WEBHOOK (NUKIBridge) - empty message received
Zitat von: SimonHipp am 14 September 2021, 23:10:01
Hi Leute,
ich habe das Problem das zwar alles geht aber der State beim schließen/öffnen per APP sich nicht im Fhem verändert.
Webhook ist gesetzt, verbose5 der Bridge zeigt z.B. beim löschen des Logs folgenden Fehler:Code Auswählen2021.09.14 23:00:12.394 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/73_NUKIBridge.pm line 1115.
2021.09.14 23:03:02.386 1: Connection refused from 192.168.151.214:64364
2021.09.14 23:07:34.479 4: NUKIBridge (NUKIBridge) - created uri: http://192.168.151.214:8080/clearlog?token=SVUGQN
2021.09.14 23:07:34.480 4: NUKIBridge (NUKIBridge) - Send HTTP POST with URL http://192.168.151.214:8080/clearlog?token=SVUGQN
2021.09.14 23:07:34.718 4: NUKIBridge (NUKIBridge) - Response JSON: {"success": true}
2021.09.14 23:07:34.718 4: NUKIBridge (NUKIBridge) - Response ERROR:
2021.09.14 23:07:34.718 4: NUKIBridge (NUKIBridge) - Response CODE: 200
2021.09.14 23:07:34.729 5: NUKIBridge (NUKIBridge) - Bridge ist online
2021.09.14 23:07:34.729 5: NUKIBridge (NUKIBridge) - Rückgabe Path nicht korrekt:
{"success": true}
2021.09.14 23:08:04.571 3: NUKIBridge WEBHOOK (NUKIBridge) - empty message received
2021.09.14 23:10:13.657 4: NUKIBridge (NUKIBridge) - created uri: http://192.168.151.214:8080/info?token=SVUGQN
2021.09.14 23:10:13.657 4: NUKIBridge (NUKIBridge) - Send HTTP POST with URL http://192.168.151.214:8080/info?token=SVUGQN
2021.09.14 23:10:13.792 4: NUKIBridge (NUKIBridge) - Response JSON: {"bridgeType": 1, "ids": {"hardwareId": 701029150, "serverId": 2120965652}, "versions": {"firmwareVersion": "2.9.3", "wifiFirmwareVersion": "2.2.0"}, "uptime": 3700, "currentTime": "2021-09-14T21:10:13+00:00", "wlanConnected": true, "serverConnected": true, "scanResults": [{"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true}]}
2021.09.14 23:10:13.792 4: NUKIBridge (NUKIBridge) - Response ERROR:
2021.09.14 23:10:13.792 4: NUKIBridge (NUKIBridge) - Response CODE: 200
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - Bridge ist online
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - 1 == 1 and 1 > 0
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - 1 == 1 and 1 > 0
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - return msg: {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true} and tail: ]}
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - Decoding JSON message. Length: 92 Content: {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true}
2021.09.14 23:10:13.795 5: NUKIBridge (NUKIBridge) - Vor Sub: Laenge JSON: 92 Content: {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true} Tail: ]}
2021.09.14 23:10:13.796 5: NUKIBridge: dispatch {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true}
2021.09.14 23:10:13.796 5: NUKIDevice (NUKIBridge) - Parse with result: {"deviceType": 0, "nukiId": 701188340, "name": "Nuki_29CB48F4", "rssi": -55, "paired": true}
2021.09.14 23:10:13.799 5: NUKIBridge (NUKIBridge) - Garbage character before message: ]
2021.09.14 23:10:13.799 5: NUKIBridge (NUKIBridge) - Garbage character before message: }
2021.09.14 23:10:13.799 5: NUKIBridge (NUKIBridge) - return msg: and tail:
2021.09.14 23:10:13.799 5: NUKIBridge (NUKIBridge) - Nach Sub: Laenge JSON: 0 Content: Tail:
2021.09.14 23:10:33.027 3: NUKIBridge WEBHOOK (NUKIBridge) - empty message received
Zitat von: CoolTux am 16 September 2021, 07:16:21
Einen Fehler beim löschen des Logs kann ich nicht sehen. Ist alles korrekt soweit.
Hast Du eine nicht gesicherte HTTP Webinstanz für den Webhook?
{"mode": 2, "state": 3, "stateName": "unlocked", "batteryCritical": false, "batteryCharging": false, "batteryChargeState": 100, "doorsensorState": 1, "doorsensorStateName": "deactivated", "success": true}
NUKIBridge WEBHOOK (NUKIBridge) - empty message received
Zitat von: BM030 am 03 Oktober 2020, 12:56:39Das Thema möchte ich ausgraben. Ist bei mir auch so. Und nervt, weil ich das letzte Klingeln an der Haustür gerne korrekt angezeigt hätte. Sorry, falls ich Antworten übersehen habe bei 118 Seiten.
bei meinem Opener und bei der Bridge stimmen die Uhrzeiten nicht, ist das bei Euch auch so?
es "fehlen" 2 Stunden...
Internals:
BRIDGEAPI 1.9
CFGFN
DEF 10.11.0.189 CE9wBq
FUUID 616d896e-f33f-5738-db62-c858cbc63ddd3bfe
FVERSION 73_NUKIBridge.pm:v1.9.16-s20994/2020-01-16
HOST 10.11.0.189
NAME NUKIbridge
NOTIFYDEV global,NUKIbridge
NR 159580
NTFY_ORDER 50-NUKIbridge
PORT 8080
STATE connected
TOKEN CE9wBq
TYPE NUKIBridge
VERSION v1.9.16
WEBHOOK_COUNTER 0
WEBHOOK_PORT 8084
WEBHOOK_REGISTER sent
WEBHOOK_URI /fhem/NUKIBridge-10.11.0.189
WEBHOOK_URL http://192.168.0.202:8084/fhem/NUKIBridge-10.11.0.189
Helper:
DBLOG:
uptime:
myDbLog:
TIME 1634582022.07155
VALUE 13362
READINGS:
2021-10-18 20:33:42 bridgeType Hardware
2021-10-18 20:33:42 firmwareVersion 2.4.21
2021-10-18 20:33:42 hardwareId 615640794
2021-10-18 20:31:41 lastError read from http://10.11.0.189:8080 timed out
2021-10-18 20:33:42 serverConnected 0
2021-10-18 20:33:42 serverId 0
2021-10-18 20:33:42 state connected
2021-10-18 20:33:42 uptime 13362
2021-10-18 20:33:42 wifiFirmwareVersion 2.1.13
fhem:
infix NUKIBridge
helper:
iowrite 0
actionQueue:
Attributes:
group Zentrale
icon nuki_bridge
room Zentrale
webhookFWinstance WEBint
webhookHttpHostname 192.168.0.202
Internals:
BRIDGEAPI 1.9
CFGFN
DEF 676481901 0
DEVICETYPE 0
FUUID 616d89cd-f33f-5738-c841-2431a04f65453ec7
FVERSION 74_NUKIDevice.pm:v1.9.12-s21020/2020-01-20
IODev NUKIbridge
LASTInputDev NUKIbridge
MSGCNT 458
NAME Nuki_28524B6D
NOTIFYDEV global,autocreate,Nuki_28524B6D
NR 159656
NTFY_ORDER 50-Nuki_28524B6D
NUKIID 676481901
NUKIbridge_MSGCNT 458
NUKIbridge_TIME 2021-10-18 20:34:41
STATE unlock
TYPE NUKIDevice
VERSION v1.9.12
READINGS:
2021-10-18 16:50:53 IODev NUKIbridge
2021-10-18 20:32:07 batteryState low
2021-10-18 20:34:41 deviceType smartlock
2021-10-18 20:14:07 mode door mode
2021-10-18 20:34:41 name Nuki_28524B6D
2021-10-18 20:34:41 nukiId 676481901
2021-10-18 20:34:41 paired true
2021-10-18 20:34:41 rssi -72
2021-10-18 20:14:05 schloss unlocked
2021-10-18 20:32:01 state unlock
2021-10-18 20:14:07 stateName locked
2021-10-18 20:32:07 success 1
helper:
Attributes:
alias Türschloss
devStateIcon locked:secur_locked unlock:secur_open
group Haustür
icon im_key
model smartlock
room Zentrale,Übersicht
webCmd lock:unlock:unlatch
Zitat von: Mitch am 18 Oktober 2021, 20:35:03Code AuswählenInternals:
DEF 10.11.0.189 xxxxxx
WEBHOOK_URI /fhem/NUKIBridge-10.11.0.189
WEBHOOK_URL http://192.168.0.202:8084/fhem/NUKIBridge-10.11.0.189
READINGS:
2021-10-18 20:31:41 lastError read from http://10.11.0.189:8080 timed out
2021-10-18 20:33:42 serverConnected 0
2021-10-18 20:33:42 serverId 0
Attributes:
webhookFWinstance WEBint
webhookHttpHostname 192.168.0.202
{"bridgeType": 1, "ids": {"hardwareId": 615640794, "serverId": 0}, "versions": {"firmwareVersion": "2.4.21", "wifiFirmwareVersion": "2.1.13"}, "uptime": 20069, "currentTime": null, "wlanConnected": true, "serverConnected": false, "scanResults": [{"deviceType": 0, "nukiId": 676481901, "name": "Nuki_28524B6D", "rssi": -67, "paired": true}]}
{"bridgeType": 1, "ids": {"hardwareId": 409057010, "serverId": 540476683}, "versions": {"firmwareVersion": "2.10.4", "wifiFirmwareVersion": "2.2.0"}, "uptime": 607280, "currentTime": "2021-10-20T10:03:17+00:00", "wlanConnected": true, "serverConnected": true, "scanResults": [{"deviceType": 0, "nukiId": 440953477, "name": "Nuki_1A486A85", "rssi": -52, "paired": true}]}
VERSION v1.9.12
READINGS:
2021-10-04 03:17:52 IODev NuBridge
2021-10-20 21:57:01 batteryChargeState 40
2021-10-20 21:57:01 batteryCharging 0
2021-10-20 21:57:01 batteryState ok
2021-10-20 23:55:51 deviceType smartlock
2021-10-20 21:57:01 doorsensorState 2
2021-10-20 21:57:01 doorsensorStateName door closed
2021-10-19 20:10:22 firmwareVersion 2.11.8
2021-10-20 21:57:01 mode door mode
2021-10-20 23:55:51 name Nuki_12345678
2021-10-20 23:55:51 nukiId 12345678
2021-10-20 23:55:51 paired true
2021-10-20 23:55:51 rssi -36
2021-10-20 21:57:01 state unlocked
2021-10-20 21:57:01 stateName unlocked
2021-10-01 02:08:34 success 1
Zitat von: kjmEjfu am 09 November 2021, 13:46:26
Hat irgendwer eine Lösung gefunden, wie der automatische Update per Calback wieder funktioniert?
Die Variante mit statusRequest per At ist zwar möglich, aber nicht so ideal.
Zitat von: the-vince am 22 November 2021, 10:38:24
Moin CoolTux,
vielen Dank für die (Weiter-)Entwicklung. Mit dem Pro wurde das DeviceType für das Pro Lock angepasst. Das ist bei mir jetzt mit DeviceType=4 hinterlegt. Entsprechend läuft das Ansprechen nicht.
Vielleicht lässt sich die Änderung einpflegen? Wäre super!
Grüße
Vincent
Zitat von: marvin78 am 22 November 2021, 11:13:10
Du kannst, musst aber nicht.
Die API für direkten Zugriff, gibt es noch nicht, soweit ich das verstanden habe. Also für API: Weiterhin Bridge.
Zitat von: the-vince am 22 November 2021, 11:34:39
ich hab das Pro am Samstag bekommen. Leider sind die Einschränkungen aktuell noch ziemlich groß. API Zugriff gibt es aktuell nur via Bridge. Und die integrierte Bridge im Pro ist eigentlich nur ein WLAN Modul. Koppeln des Opener geht (noch) nicht.
Zitat von: kjmEjfu am 22 November 2021, 11:40:52
AFAIK soll sich das auch gar nicht ändern, deshalb versteht auch kaum jemand den Sinn der Pro.
Von Nuki war das am Anfang etwas missverständlich kommuniziert, mittlerweile steht aber recht deutlich drin "mit einem integrierten WiFi-Modul" (https://nuki.io/de/smart-lock-pro/). Nix mehr Richtung "integrierte Bridge".
Zitat von: CoolTux am 22 November 2021, 12:03:21
Ok verstehe. Und was macht die Lautstärke im vergleich zu den Vorversionen? Ist bei mir mit dem 1er noch so ein "Manko"