Danalock Siri #136
Comments
|
No idea. I do not have such a device. |
|
This is what I am getting in logs, maybe it might help you [2/7/2019, 9:50:03 PM] [FibaroHC2] Setting value to device: 47 parameter: Lock Target State |
|
Hi, I have the same issue as well. All works, but Siri sometimes responds that it wasn't able to unlock while the lock really unlocks... How can I help? |
|
@MindaugasRam, I don't think it is related to the issue but I see a misconfiguration from your logs. and do not forget to remove the last "," |
|
Thanks. I fixed that. But as you said it is not relaited to danalock. Still getting that Siri error. |
|
@ilcato I found that someone managed to fix that on viera damianxd/homebridge-vera@c59f269. If you could look into it, when you have time, and fix as well if it is possible. Thanks |
|
Can you post a clean log? |
|
[3/7/2019, 8:35:41 PM] [FibaroHC2] didFinishLaunching. |
|
When I am asking siri door status (8:36:22), it says without problem and no errors. Just when I am asking to lock or unlock I am having that issue. |
|
Let me recap: the problem is that you see the following line in the log: |
|
Yes. Command to lock or unlock doors is executed correctly, but Siri says “I wasn’t able to lock/unlock doors”. If I am asking Siri “what is door status” it answers correctly. |
|
Which value did you put into |
|
"doorlocktimeout": "3" |
|
In my case, changing doorlocktimeout values is not affecting the behavior.
I tried 0, 3 (the time needed for the lock and actually fully lock) and
higher values.
What is this parameter used for really?
…On Fri, Mar 8, 2019 at 10:54 AM ilcato ***@***.***> wrote:
Which value did you put into doorlocktimeout parameter?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AsX6ZrSjPo-kWXqahmfvRdCowfE-4Fycks5vUiU3gaJpZM4ap3Dj>
.
|
IT should signal via IFTTT a mismatch between the command sent to the lock and the real status after N seconds. @MindaugasRam put it to 0 or better remove the line from the config.json and try again please. |
|
So if you're not using IFTT, it's not needed. Right ?
…On Fri, Mar 8, 2019 at 11:44 AM ilcato ***@***.***> wrote:
In my case, changing doorlocktimeout values is not affecting the behavior.
I tried 0, 3 (the time needed for the lock and actually fully lock) and
higher values. What is this parameter used for really?
… <#m_-4142118382916493341_>
IT should signal via IFTT a mismatch between the command sent to the lock
and the real status after N seconds.
@MindaugasRam <https://github.com/MindaugasRam> put it to 0 or better
remove the line from the config.json and try again please.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AsX6Zh6rO2Oh5eKL0ZISiQby59yWwDvqks5vUjDtgaJpZM4ap3Dj>
.
|
Correct |
|
I deleted all line. Still same |
|
it works good with Siri Shortcuts |
@MindaugasRam, what did you find in this commit that let you think about a solution ? |
|
@MindaugasRam, can you send me the configuration of the device through the rest api? |
|
I've been searching and found this ptz0n/homebridge-verisure#29, but I am not familiar with coding so thought you might be able to see that code and maybe find solution for yours :) |
|
rest api - what do you mean? I am running homebridge in docker on synology nas, where you want me to look for it? |
connect to http://HOME_BRIDGE_IP/docs select devices insert the device id of the lock read the response and sen it to me. |
|
http://HOME_BRIDGE_IP:port/docs - brings me to homebridge home page |
|
{"id":250,"name":"Doorlock","roomID":17,"type":"com.fibaro.doorLock","baseType":"com.fibaro.securityMonitoring","enabled":true,"visible":true,"isPlugin":false,"parentId":199,"remoteGatewayId":0,"interfaces":["accessControlEvent","battery","fibaroFirmwareUpdate","zwave","zwaveAlarm"],"properties":{"parameters":[],"pollingTimeSec":0,"zwaveCompany":"Poly-control","zwaveInfo":"3,4,61","zwaveVersion":"1.2","alarmLevel":"0","alarmType":"0","batteryLevel":"70","batteryLowNotification":"true","categories":"[\"security\"]","configured":true,"dead":"false","deadReason":"","defInterval":"0","deviceControlType":"0","deviceIcon":"79","emailNotificationID":"0","emailNotificationType":"0","endPointId":"0","firmwareUpdate":"{\"info\":\"\",\"progress\":0,\"status\":\"UpToDate\",\"updateVersion\":\"1.2\"}","log":"","logTemp":"","manufacturer":"","markAsDead":"true","maxInterval":"0","minInterval":"0","model":"","nodeId":"39","parametersTemplate":"0","productInfo":"1,14,0,9,0,1,1,2","pushNotificationID":"0","pushNotificationType":"0","remoteGatewayId":"0","saveLogs":"true","secured":"0","serialNumber":"h'————-","smsNotificationID":"0","smsNotificationType":"0","stepInterval":"0","updateVersion":"","useTemplate":"false","userDescription":"","value":"false"},"actions":{"abortUpdate":1,"reconfigure":0,"retryUpdate":1,"secure":0,"setInterval":1,"startUpdate":1,"unsecure":0,"updateFirmware":1},"created":1551769772,"modified":1551769772,"sortOrder":94}
…On Fri, Mar 8, 2019 at 7:31 PM MindaugasRam ***@***.***> wrote:
http://HOME_BRIDGE_IP:port/docs - brings me to homebridge home page
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AsX6Zj8DbnZ0Qu2rL51l4hpNCpRDb5Kaks5vUp59gaJpZM4ap3Dj>
.
|
|
Thanks @carlittoer |
|
@MindaugasRam, @carlittoer, |
|
Homecenter app status is correct. Siri answers in no time, like straight away. It takes about 3-5 secs to change lock status. Homecenter app is quicker to report correct value, diferrence 2-3 secs |
|
when the device (lock) starts to lock or unlock, siri gives the error message. |
|
I can't find where do I need to change those values. Could you please clarify which line. Mine lock works no issues, but if you guys want me to try smth for you please be more specific I am not so smart ;) |
|
Same here: Siri closes lock, but immediately responds she was not able to, even while the lock is still operating. Changing "doorlocktimeout" parameter to 0 or 15 has no effect Danalock V3 Z-Wave via Fibaro HC2 Here is my log file: What is different: I do not have the error line mentioned above Let me know, if I can contribute further. |
|
@MindaugasRam This is good to hear. I assumed so already reading the conversation. @ilcato May I ask to update the package at npm to 2.2.1. |
|
@Krillle yes you have to update it manually. Copy paste. And restart |
|
@MindaugasRam Thanks for your answer. I think I will wait for the update at npm then. |
|
Published current master version in pm as 2.2.1. @Krillle, please install the upgrade and check if it works for you. @carlittoer, @MindaugasRam please install from nom and report potential issues back here. |
|
@ilcato Thanks for updating npm. No clue why. |
|
@Krillle, try to uninstall and reinstall it. |
|
@ilcato Uninstall went smooth. Install hangs again. Now I am stuck. |
|
@ilcato Here is some more detailed error message: Do you need the full log? |
|
yes |
|
Here it is: /root/.npm/_logs/2019-04-08T14_15_31_171Z-debug.log |
|
It seems it was a local problem. |
|
@ilcato I checked with 2.2.1: |
|
@ilcato I installed in office and at home now. Actually it works most of the cases, but not always. A) Door is immediately unlocked after being locked - and then declared correctly as "I could not lock door". This happened several times. B) Randomly Siri states she could not lock or unlock the door, despite she did. Can be she has this problem only opening the doors. But I can't find a reproducible scheme. Here is the log excerpt to such a behavior: |
|
Hi !
How many times does your danalock turn to lock the door? One or two?
I found out that mine (2 turns) needs 4 seconds to complete the operation.
In that case timeout variables (currently inside the code) should be
increased to 4s
…On Mon, Apr 8, 2019 at 10:31 PM Christian Wegerhoff < ***@***.***> wrote:
@ilcato <https://github.com/ilcato> I installed in office and at home
now. Actually it works most of the cases, but not always.
There is two types of weird behavior:
A) Door is immediately unlocked after being locked - and then declared
correctly as "I could not lock door". This happened multiple times.
B) Randomly Siri states she could not lock or unlock the door, despite she
did. Here is the low excerpt to such a random behavior:
Apr 08 21:25:18 Homebridge homebridge[3775]: [2019-4-8 21:25:18] [FibaroHC2] Setting value to device: 233 parameter: Lock Target State
Apr 08 21:25:18 Homebridge homebridge[3775]: [2019-4-8 21:25:18] [FibaroHC2] Setting value to device: 273 parameter: Lock Target State
Apr 08 21:25:18 Homebridge homebridge[3775]: [2019-4-8 21:25:18] [FibaroHC2] Command: secure, value: 0, to: 233
Apr 08 21:25:18 Homebridge homebridge[3775]: [2019-4-8 21:25:18] [FibaroHC2] Command: secure, value: 0, to: 273
Apr 08 21:25:18 Homebridge homebridge[3775]: [2019-4-8 21:25:18] [FibaroHC2] Getting value from device: 233 parameter: Lock Current State
Apr 08 21:25:18 Homebridge homebridge[3775]: [2019-4-8 21:25:18] [FibaroHC2] Getting value from device: 273 parameter: Lock Current State
Apr 08 21:25:22 Homebridge homebridge[3775]: [2019-4-8 21:25:22] [FibaroHC2] Getting value from device: 273 parameter: Lock Target State
Apr 08 21:25:22 Homebridge homebridge[3775]: [2019-4-8 21:25:22] [FibaroHC2] Getting value from device: 233 parameter: Lock Target State
Apr 08 21:25:24 Homebridge homebridge[3775]: [2019-4-8 21:25:24] [FibaroHC2] Updating value for device: 273 parameter: Lock Current State, value: true
Apr 08 21:25:24 Homebridge homebridge[3775]: [2019-4-8 21:25:24] [FibaroHC2] Updating value for device: 273 parameter: Lock Target State, value: true
Apr 08 21:25:25 Homebridge homebridge[3775]: [2019-4-8 21:25:25] [FibaroHC2] Getting value from device: 233 parameter: Lock Current State
Apr 08 21:25:25 Homebridge homebridge[3775]: [2019-4-8 21:25:25] [FibaroHC2] Getting value from device: 273 parameter: Lock Current State
Apr 08 21:25:34 Homebridge homebridge[3775]: [2019-4-8 21:25:34] [FibaroHC2] Setting value to device: 233 parameter: Lock Target State
Apr 08 21:25:34 Homebridge homebridge[3775]: [2019-4-8 21:25:34] [FibaroHC2] Setting value to device: 273 parameter: Lock Target State
Apr 08 21:25:34 Homebridge homebridge[3775]: [2019-4-8 21:25:34] [FibaroHC2] Command: unsecure, value: 0, to: 233
Apr 08 21:25:34 Homebridge homebridge[3775]: [2019-4-8 21:25:34] [FibaroHC2] Command: unsecure, value: 0, to: 273
Apr 08 21:25:34 Homebridge homebridge[3775]: [2019-4-8 21:25:34] [FibaroHC2] Getting value from device: 233 parameter: Lock Current State
Apr 08 21:25:34 Homebridge homebridge[3775]: [2019-4-8 21:25:34] [FibaroHC2] Getting value from device: 273 parameter: Lock Current State
Apr 08 21:25:38 Homebridge homebridge[3775]: [2019-4-8 21:25:38] [FibaroHC2] Getting value from device: 273 parameter: Lock Target State
Apr 08 21:25:38 Homebridge homebridge[3775]: [2019-4-8 21:25:38] [FibaroHC2] Getting value from device: 233 parameter: Lock Target State
Apr 08 21:25:39 Homebridge homebridge[3775]: [2019-4-8 21:25:39] [FibaroHC2] Updating value for device: 173 parameter: Current Temperature, value: 25.90
Apr 08 21:25:39 Homebridge homebridge[3775]: [2019-4-8 21:25:39] [FibaroHC2] Updating value for device: 273 parameter: Lock Current State, value: false
Apr 08 21:25:39 Homebridge homebridge[3775]: [2019-4-8 21:25:39] [FibaroHC2] Updating value for device: 273 parameter: Lock Target State, value: false
Apr 08 21:25:41 Homebridge homebridge[3775]: [2019-4-8 21:25:41] [FibaroHC2] There was a problem setting value to Lock: 233
Apr 08 21:25:51 Homebridge homebridge[3775]: [2019-4-8 21:25:51] [FibaroHC2] Setting value to device: 233 parameter: Lock Target State
Apr 08 21:25:51 Homebridge homebridge[3775]: [2019-4-8 21:25:51] [FibaroHC2] Setting value to device: 273 parameter: Lock Target State
Apr 08 21:25:51 Homebridge homebridge[3775]: [2019-4-8 21:25:51] [FibaroHC2] Command: secure, value: 0, to: 233
Apr 08 21:25:51 Homebridge homebridge[3775]: [2019-4-8 21:25:51] [FibaroHC2] Command: secure, value: 0, to: 273
Apr 08 21:25:51 Homebridge homebridge[3775]: [2019-4-8 21:25:51] [FibaroHC2] Getting value from device: 233 parameter: Lock Current State
Apr 08 21:25:51 Homebridge homebridge[3775]: [2019-4-8 21:25:51] [FibaroHC2] Getting value from device: 273 parameter: Lock Current State
Apr 08 21:25:55 Homebridge homebridge[3775]: [2019-4-8 21:25:55] [FibaroHC2] Getting value from device: 273 parameter: Lock Target State
Apr 08 21:25:55 Homebridge homebridge[3775]: [2019-4-8 21:25:55] [FibaroHC2] Getting value from device: 233 parameter: Lock Target State
Apr 08 21:25:59 Homebridge homebridge[3775]: [2019-4-8 21:25:59] [FibaroHC2] Updating value for device: 273 parameter: Lock Current State, value: true
Apr 08 21:25:59 Homebridge homebridge[3775]: [2019-4-8 21:25:59] [FibaroHC2] Updating value for device: 273 parameter: Lock Target State, value: true
Apr 08 21:26:08 Homebridge homebridge[3775]: [2019-4-8 21:26:08] [FibaroHC2] Setting value to device: 233 parameter: Lock Target State
Apr 08 21:26:08 Homebridge homebridge[3775]: [2019-4-8 21:26:08] [FibaroHC2] Setting value to device: 273 parameter: Lock Target State
Apr 08 21:26:08 Homebridge homebridge[3775]: [2019-4-8 21:26:08] [FibaroHC2] Command: unsecure, value: 0, to: 273
Apr 08 21:26:08 Homebridge homebridge[3775]: [2019-4-8 21:26:08] [FibaroHC2] Command: unsecure, value: 0, to: 233
Apr 08 21:26:08 Homebridge homebridge[3775]: [2019-4-8 21:26:08] [FibaroHC2] Getting value from device: 233 parameter: Lock Current State
Apr 08 21:26:08 Homebridge homebridge[3775]: [2019-4-8 21:26:08] [FibaroHC2] Getting value from device: 273 parameter: Lock Current State
Apr 08 21:26:12 Homebridge homebridge[3775]: [2019-4-8 21:26:12] [FibaroHC2] Getting value from device: 273 parameter: Lock Target State
Apr 08 21:26:12 Homebridge homebridge[3775]: [2019-4-8 21:26:12] [FibaroHC2] Getting value from device: 233 parameter: Lock Target State
Apr 08 21:26:13 Homebridge homebridge[3775]: [2019-4-8 21:26:13] [FibaroHC2] Updating value for device: 273 parameter: Lock Current State, value: false
Apr 08 21:26:13 Homebridge homebridge[3775]: [2019-4-8 21:26:13] [FibaroHC2] Updating value for device: 273 parameter: Lock Target State, value: false
Apr 08 21:26:15 Homebridge homebridge[3775]: [2019-4-8 21:26:15] [FibaroHC2] There was a problem setting value to Lock: 233
Apr 08 21:26:26 Homebridge homebridge[3775]: [2019-4-8 21:26:26] [FibaroHC2] Setting value to device: 233 parameter: Lock Target State
Apr 08 21:26:26 Homebridge homebridge[3775]: [2019-4-8 21:26:26] [FibaroHC2] Setting value to device: 273 parameter: Lock Target State
Apr 08 21:26:26 Homebridge homebridge[3775]: [2019-4-8 21:26:26] [FibaroHC2] Command: secure, value: 0, to: 233
Apr 08 21:26:26 Homebridge homebridge[3775]: [2019-4-8 21:26:26] [FibaroHC2] Command: secure, value: 0, to: 273
Apr 08 21:26:26 Homebridge homebridge[3775]: [2019-4-8 21:26:26] [FibaroHC2] Getting value from device: 233 parameter: Lock Current State
Apr 08 21:26:26 Homebridge homebridge[3775]: [2019-4-8 21:26:26] [FibaroHC2] Getting value from device: 273 parameter: Lock Current State
Apr 08 21:26:30 Homebridge homebridge[3775]: [2019-4-8 21:26:30] [FibaroHC2] Getting value from device: 273 parameter: Lock Target State
Apr 08 21:26:30 Homebridge homebridge[3775]: [2019-4-8 21:26:30] [FibaroHC2] Getting value from device: 233 parameter: Lock Target State
Apr 08 21:26:33 Homebridge homebridge[3775]: [2019-4-8 21:26:33] [FibaroHC2] Updating value for device: 273 parameter: Lock Current State, value: true
Apr 08 21:26:33 Homebridge homebridge[3775]: [2019-4-8 21:26:33] [FibaroHC2] Updating value for device: 273 parameter: Lock Target State, value: true
Apr 08 21:26:33 Homebridge homebridge[3775]: [2019-4-8 21:26:33] [FibaroHC2] Getting value from device: 233 parameter: Lock Current State
Apr 08 21:26:33 Homebridge homebridge[3775]: [2019-4-8 21:26:33] [FibaroHC2] Getting value from device: 273 parameter: Lock Current State
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AsX6ZtyyrgH1nBol5HXrStZbslu1hXF0ks5ve5kggaJpZM4ap3Dj>
.
|
|
The locks needs 2x 360° turns. But here indeed is probably the reason why Siri has a problem opening: Opening the door at home includes one more turn approx 270° to unlatch the second bolt (German standard outer door). This bolt is held for 3 seconds before it is released and the opening operation is finished. (Here is an example of this operation. Old Danalock but same procedure: youtu.be/HBdI2Jt8C1I) Unlocking the door in office does not include the additional unlatching, so no additional 270° + 3 seconds wait. So we need two different timeouts for opening and closing. And opening timeout it is dependent on if opening the second latch is included or not. |
|
Not sure to understand, unfortunately I do not have such a device. |
|
@ilcato The issue is: Besides that, unlocking of the lock sometimes takes a little longer than 4 seconds. This means: In my configuration i suppose the timeout would be 4 seconds for locking and 8 seconds for unlocking (including holding deadbolt open for 3 seconds). |
|
@Krillle, @MindaugasRam, @carlittoer in the 2.2.3 version you can specify the delays in config.json. Please try tinkering with it and understand if each of you can find a suitable config. |
|
@ilcato This is great. Thank you! |
|
Can you please give a short explanation what these two values are specifying exactly? |
|
I change both values to "7", but no change. Response from Siri is given after the lock has stopped operating now. Nevertheless the is confirming the locking as successful, but still claims tat opening would not be possible. So no change. What's weird: Home App is now sending an additional status Notification before the lock starts operating. |
|
@Krillle these values delay the time at which a response to HomeKit is given allowing the correct status change in Fibaro Home Center. When the seconds specified are elapsed a query to Fibaro Home Center is executed and the response to HomeKit is returned. Please check when the status of the lock change in Fibaro Home Center starting from the command asked in HomeKit. |
|
@ilcato But for the one which is holding back the bolt I get a negative reply when opening, even with a delay of 10 seconds. Homecenter is showing the status already as open after 4 seconds, while the bolt is still held back. So this doesn't seem to be the reason while opening lock does not give a positive response. But in the end I can live with that. :-) |
|
Too much cases for me to understand without testing a real physical device. |
|
Tested this with both values at 8 seconds. It's working properly. |
|
Hi again all ! Since the last fix (delay of 8 secs), I've been noticing a slower response from the home app to show the device statuses. After some tests, it appears that the home app is waiting the same 8 secs to show the devices statuses (stuck on updating...). Anything can be done for the lock device only ? Remember, the issue was Siri's incorrect response when locking / unlocking the lock, not the actual home app switch. |
Hi,
plugin works great, thanks for it. I have only issue with Siri. When I ask Siri to open or close lock, it does but responses it was unable to do it. Home kit app works perfectly. Just Siri responses are faulty.
Any thoughts how to fix it. Thanks
The text was updated successfully, but these errors were encountered: