Closed MichaelSchaaf999 closed 2 years ago
smaragdschlange
commented
2 years ago Hi, Please enter a valid token. The token is supposed to be 4 or 5 digits long. It looks like you've tried to enter a hashed token. Hashed tokens are valid for one request only.
Regards, Sven
MichaelSchaaf999
commented
2 years ago Dear Sven,
Mmmhhhhhh, 4 or 5 digits…. THIS is the API Token that the NUKI online access is providing:
@.***
@.***
Is this NOT the token we are talking about?
Best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Smaragdschlange @.> Antworten an: "smaragdschlange/ioBroker.nuki" @.> Datum: Samstag, 26. Februar 2022 um 18:13 An: "smaragdschlange/ioBroker.nuki" @.> Cc: Michael Schaaf @.>, Author @.***> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Hi, Please enter a valid token. The token is supposed to be 4 or 5 digits long. It looks like you've tried to enter a hashed token. Hashed tokens are valid for one request only.
Regards, Sven
— Reply to this email directly, view it on GitHubhttps://github.com/smaragdschlange/ioBroker.nuki/issues/64#issuecomment-1052331495, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYA5AWXFKPWZVNVWLCSHX3U5EC47ANCNFSM5PBT4GDA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
MichaelSchaaf999
commented
2 years ago Dear Sven,
I generated a new token (showing as long as before, but different, ob course…): And the adapter seems to connect. @.***
But: No information in the objects…
@.***
Any advice?
Best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Michael Schaaf @.> Datum: Samstag, 26. Februar 2022 um 18:26 An: "smaragdschlange/ioBroker.nuki" @.>, "smaragdschlange/ioBroker.nuki" @.> Cc: Author @.> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Dear Sven,
Mmmhhhhhh, 4 or 5 digits…. THIS is the API Token that the NUKI online access is providing:
@.***
@.***
Is this NOT the token we are talking about?
Best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Smaragdschlange @.> Antworten an: "smaragdschlange/ioBroker.nuki" @.> Datum: Samstag, 26. Februar 2022 um 18:13 An: "smaragdschlange/ioBroker.nuki" @.> Cc: Michael Schaaf @.>, Author @.***> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Hi, Please enter a valid token. The token is supposed to be 4 or 5 digits long. It looks like you've tried to enter a hashed token. Hashed tokens are valid for one request only.
Regards, Sven
— Reply to this email directly, view it on GitHubhttps://github.com/smaragdschlange/ioBroker.nuki/issues/64#issuecomment-1052331495, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYA5AWXFKPWZVNVWLCSHX3U5EC47ANCNFSM5PBT4GDA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
smaragdschlange
commented
2 years ago Hi again, no we're talking about different things. My adapter is using the NUKI bridge API, npo the Web API. The token I am talking about (the one to be used in the adapter settings) is provided by the bridge. You can get the bridge token via web browser (harware bridge) : http://ip.of.your.bridge:8080/auth or via Nuki bridge App (software bridge). This is a description of the /auth API call: "Enables the api (if not yet enabled) and returns the api token. If no api token has yet been set, a new (random) one is generated. When issuing this API-call the bridge turns on its LED for 30 seconds. The button of the bridge has to be pressed within this timeframe. Otherwise the bridge returns a negative success and no token."
Regards, Sven
MichaelSchaaf999
commented
2 years ago Dear Sven,
thanks a lot: Of course you are right – I did not understand that the adapter has to use the bridge and we had to talk about the bridge token, not the NUKI token. I first had to find out how to access the bridge: Since the installation of NUKI and bridge I never ever had tried to access the bridge again, because it just worked.
Progress: I found out how to access the bridge, I activated the HTTP Api and entered this token in your adapter.
Messages now:
2022-02-27 09:24:07.868
warn
State "nuki.0.350365181.actions.action" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.869
warn
State "nuki.0.350365181.info.firmwareVersion" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.869
warn
State "nuki.0.350365181.states.doorState" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.869
warn
State "nuki.0.350365181.states.state" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.869
warn
State "nuki.0.350365181.info.mode" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.868
warn
State "nuki.0.350365181.actions.lockAction" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.868
warn
State "nuki.0.350365181.states.lockState" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.868
warn
State "nuki.0.350365181.states.timestamp" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.867
warn
State "nuki.0.350365181.info.batteryCritical" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.867
warn
State "nuki.0.350365181.info.deviceType" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.865
info
Lock list requested: http://192.168.178.15:8080/list?ts=2022-02-27T08:24:04Z&rnr=55294&hash=adf6d56dabbc830478fd5cacef6c89803d678894b6e9e542f1438f2adb0b5670
@.*** nuki.0
2022-02-27 09:24:01.362
warn
State "nuki.0.149584537.info.timestamp" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:01.362
warn
State "nuki.0.149584537.info.wifiFirmwareVersion" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:01.362
warn
State "nuki.0.149584537.info.firmwareVersion" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:01.360
info
Bridge Info requested: http://192.168.178.15:8080/info?ts=2022-02-27T08:24:01Z&rnr=53635&hash=3da2d52e149d84c8cd228ec17266f277c0961eb3482948d912f0789e449d5576
And: No entries in the object list for NUKI.
Means: The adapter now is trying to access the bridge but there seem to be some discrepancies in field definitions – correct? What do you advise?
Best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Smaragdschlange @.> Antworten an: "smaragdschlange/ioBroker.nuki" @.> Datum: Sonntag, 27. Februar 2022 um 06:18 An: "smaragdschlange/ioBroker.nuki" @.> Cc: Michael Schaaf @.>, Author @.***> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Hi again, no we're talking about different things. My adapter is using the NUKI bridge API, npo the Web API. The token I am talking about (the one to be used in the adapter settings) is provided by the bridge. You can get the bridge token via web browser (harware bridge) : http://ip.of.your.bridge:8080/auth or via Nuki bridge App (software bridge).
Regards, Sven
— Reply to this email directly, view it on GitHubhttps://github.com/smaragdschlange/ioBroker.nuki/issues/64#issuecomment-1053154791, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYA5ASKVGGFEDW5VF4AYLTU5GXZLANCNFSM5PBT4GDA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
MichaelSchaaf999
commented
2 years ago Dear Sven,
p.s.: I restarted the adapter. And now there is more progress…
@.*** So this seems to work now as intended. Very good!
Question: Which time interval do you recommend for updating? 3 mins? 30 mins? In other words: If the NUKI lock is operated the result / status is provided AFTER this interval, correct?
Or: Should I deactivate the “Periodic Status Actualization”? What does it mean? @.***
Can I update the lockAction to lock and unlock the NUKI?
@.***
Best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Michael Schaaf @.> Datum: Sonntag, 27. Februar 2022 um 09:25 An: "smaragdschlange/ioBroker.nuki" @.>, "smaragdschlange/ioBroker.nuki" @.> Cc: Author @.> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Dear Sven,
thanks a lot: Of course you are right – I did not understand that the adapter has to use the bridge and we had to talk about the bridge token, not the NUKI token. I first had to find out how to access the bridge: Since the installation of NUKI and bridge I never ever had tried to access the bridge again, because it just worked.
Progress: I found out how to access the bridge, I activated the HTTP Api and entered this token in your adapter.
Messages now:
2022-02-27 09:24:07.868
warn
State "nuki.0.350365181.actions.action" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.869
warn
State "nuki.0.350365181.info.firmwareVersion" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.869
warn
State "nuki.0.350365181.states.doorState" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.869
warn
State "nuki.0.350365181.states.state" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.869
warn
State "nuki.0.350365181.info.mode" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.868
warn
State "nuki.0.350365181.actions.lockAction" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.868
warn
State "nuki.0.350365181.states.lockState" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.868
warn
State "nuki.0.350365181.states.timestamp" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.867
warn
State "nuki.0.350365181.info.batteryCritical" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.867
warn
State "nuki.0.350365181.info.deviceType" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:04.865
info
Lock list requested: http://192.168.178.15:8080/list?ts=2022-02-27T08:24:04Z&rnr=55294&hash=adf6d56dabbc830478fd5cacef6c89803d678894b6e9e542f1438f2adb0b5670
@.*** nuki.0
2022-02-27 09:24:01.362
warn
State "nuki.0.149584537.info.timestamp" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:01.362
warn
State "nuki.0.149584537.info.wifiFirmwareVersion" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:01.362
warn
State "nuki.0.149584537.info.firmwareVersion" has no existing object, this might lead to an error in future versions
@.*** nuki.0
2022-02-27 09:24:01.360
info
Bridge Info requested: http://192.168.178.15:8080/info?ts=2022-02-27T08:24:01Z&rnr=53635&hash=3da2d52e149d84c8cd228ec17266f277c0961eb3482948d912f0789e449d5576
And: No entries in the object list for NUKI.
Means: The adapter now is trying to access the bridge but there seem to be some discrepancies in field definitions – correct? What do you advise?
Best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Smaragdschlange @.> Antworten an: "smaragdschlange/ioBroker.nuki" @.> Datum: Sonntag, 27. Februar 2022 um 06:18 An: "smaragdschlange/ioBroker.nuki" @.> Cc: Michael Schaaf @.>, Author @.***> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Hi again, no we're talking about different things. My adapter is using the NUKI bridge API, npo the Web API. The token I am talking about (the one to be used in the adapter settings) is provided by the bridge. You can get the bridge token via web browser (harware bridge) : http://ip.of.your.bridge:8080/auth or via Nuki bridge App (software bridge).
Regards, Sven
— Reply to this email directly, view it on GitHubhttps://github.com/smaragdschlange/ioBroker.nuki/issues/64#issuecomment-1053154791, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYA5ASKVGGFEDW5VF4AYLTU5GXZLANCNFSM5PBT4GDA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
smaragdschlange
commented
2 years ago Hi Michael, please try to delete your instance of the NUKI adapter and create a new one.
Regards, Sven
MichaelSchaaf999
commented
2 years ago Dear Sven,
so this seems to work now as intended. Very good! Excellent.
Question: Which time interval do you recommend for updating? 3 mins? 30 mins? In other words: If the NUKI lock is operated the result / status is provided in IOBroker AFTER this interval, correct?
Or: Should I deactivate the “Periodic Status Actualization”? What does it mean? @.***
Best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Danke im Voraus Michael Schaaf
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Smaragdschlange @.> Antworten an: "smaragdschlange/ioBroker.nuki" @.> Datum: Sonntag, 27. Februar 2022 um 17:54 An: "smaragdschlange/ioBroker.nuki" @.> Cc: Michael Schaaf @.>, Author @.***> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Hi Michael, please try to delete your instance of the NUKI adapter and create a new one.
Regards, Sven
— Reply to this email directly, view it on GitHubhttps://github.com/smaragdschlange/ioBroker.nuki/issues/64#issuecomment-1053613781, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYA5AVTYS722YNOG2GCILTU5JJL3ANCNFSM5PBT4GDA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
smaragdschlange
commented
2 years ago Hi Michael, the interval is meant to be used if, for some reason, the callback from the Nuki doesn't work. It is just an alternative way to get the lock state and should be disabled if callbacks are working.
Reguards, Sven
MichaelSchaaf999
commented
2 years ago Dear Sven,
thank you: This is very helpful.
This morning the lock state was not shown correctly in the IOBroker datapoint, it still said ´not locked´ (the Nuki-setup locked it yesterday evening at 10 p.m.). Must I tick “Callback” then? And not the interval?
I first tried with the “Intervall” and the status came to IOBroker immediately (because while saving the entries the adapter was restarted, I read in the bottom line:
@.***
So: Just try with the “Benutze Callback” ticked? And not the Intervall? Or un-tick the Callback and tick the Intervall?
Thanks, best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Smaragdschlange @.> Antworten an: "smaragdschlange/ioBroker.nuki" @.> Datum: Montag, 28. Februar 2022 um 18:48 An: "smaragdschlange/ioBroker.nuki" @.> Cc: Michael Schaaf @.>, Author @.***> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Hi Michael, the interval is meant to be used if, for some reason, the callback from the Nuki doesn't work. It is just an alternative way to get the lock state and should be disabled if callbacks are working.
Reguards, Sven
— Reply to this email directly, view it on GitHubhttps://github.com/smaragdschlange/ioBroker.nuki/issues/64#issuecomment-1054509028, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYA5ARFWOPKMIALC44EQZTU5OYONANCNFSM5PBT4GDA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
smaragdschlange
commented
2 years ago Hi, yes, as I wrote before: the interval is just an alternative solution if callback is not working. Regards, Sven
MichaelSchaaf999
commented
2 years ago Hi,
intervall: Understood.
But what about the „Callback“? I understand your explanation that Callback should work, normally. But for this purpose: @.*** Must I tick “Benutze Callback”? And not the Intervall? And then test if the callback is working? Without ticking “Benutze Callback” this is not working, right?
Thx Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Smaragdschlange @.> Antworten an: "smaragdschlange/ioBroker.nuki" @.> Datum: Donnerstag, 3. März 2022 um 07:57 An: "smaragdschlange/ioBroker.nuki" @.> Cc: Michael Schaaf @.>, Author @.***> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Hi, yes, as I wrote before: the interval is just an alternative solution if callback is not working. Regards, Sven
— Reply to this email directly, view it on GitHubhttps://github.com/smaragdschlange/ioBroker.nuki/issues/64#issuecomment-1057734780, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYA5AQB2766WWAJEKGP2JDU6BPEBANCNFSM5PBT4GDA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
smaragdschlange
commented
2 years ago Hi, of course you need to check the use callback checkbox in order to use the callback function! If you use neither of the updating solutions (no interval and no callback) the adapter would never know the state of the Nuki, right? So, yes, please tick the "Benutze Callback" and the adapter will get an update each time the Nuki changes its lock state. I'm sorry, I really thought this was implied in my previous answers.
Regards, Sven
MichaelSchaaf999
commented
2 years ago Thanks, Sven,
very much appreciated.
As you explain it now: It’s clear to me. Before that I was not sure whether the tick of the callback checkbox was necessary. Perhaps five or eight words as an explanation in the GUI would help (e.g.: “Tick callback, this is standard” or similar) – I did not find those, well: Can be my deficiency, don’t know.
Well, now I am a couple of days with “Benutze Callback” and without “Periodische Statusaktualisierungen” and it all seems to work. Well: The “states” seem to take a couple of seconds sometimes, but the reason for this for sure can be seen in the Nuki-lock and/or the Nuki-bridge or the communication in between.
I am fine now!
@.***
I know: Some redundant data here – but this is still my test-lab of the Nuki-visualization. I will fine-tune this.
Thanks again for your continuous support and your patience to answer questions. Best Michael
Michael Schaaf | fon +49 172 5233633 | fax +49 7172 9340030 | mail @.**@.>
Von: Smaragdschlange @.> Antworten an: "smaragdschlange/ioBroker.nuki" @.> Datum: Freitag, 4. März 2022 um 06:08 An: "smaragdschlange/ioBroker.nuki" @.> Cc: Michael Schaaf @.>, Author @.***> Betreff: Re: [smaragdschlange/ioBroker.nuki] Adapter Nuki Smart Lock 1.6.0 installed, API fetched from nuki.io BUT an error is thrown in IOBroker's log (Issue #64)
Hi, of course you need to check the use callback checkbox in order to use the callback function! If you use neither of the updating solutions (no interval and no callback) the adapter would never know the state of the Nuki, right? So, yes, please tick the "Benutze Callback" and the adapter will get an update each time the Nuki changes its lock state. I'm sorry, I really thought this was implied in my previous answers.
Regards, Sven
— Reply to this email directly, view it on GitHubhttps://github.com/smaragdschlange/ioBroker.nuki/issues/64#issuecomment-1058833362, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYA5ATKVEWEEEXTPZC7WULU6GLFZANCNFSM5PBT4GDA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
Adapter is running with token inserted:
...but the log throws an error:
What am I expected to do?
BR Michael