yale keyless connected not reporting status
-
- Posts: 24
- Joined: 25 Nov 2018 13:57
yale keyless connected not reporting status
Hi
I've had a yale keyless connected smart lock working for years. I needed to update zwave.me and after a lot of pain I ended up updating to the latest version and factory resetting both the razberry and the lock. All comms work as expected and if I [refresh] I can get the current lock status, but it doesn't report manual locking or unlocking.
I read of a simiilar problem with z-wave.js and the solution was -
"For reference, your lock's configuration was updated in Z-Wave JS v10.8.0 to disable Supervision and increase report timeouts (same as global setting in ZUI). I would suspect that explains it. zwave-js/node-zwave-js#5417"
can I disable supervision and increase report timeouts in zwave.me? If so, how?
thanks
I've had a yale keyless connected smart lock working for years. I needed to update zwave.me and after a lot of pain I ended up updating to the latest version and factory resetting both the razberry and the lock. All comms work as expected and if I [refresh] I can get the current lock status, but it doesn't report manual locking or unlocking.
I read of a simiilar problem with z-wave.js and the solution was -
"For reference, your lock's configuration was updated in Z-Wave JS v10.8.0 to disable Supervision and increase report timeouts (same as global setting in ZUI). I would suspect that explains it. zwave-js/node-zwave-js#5417"
can I disable supervision and increase report timeouts in zwave.me? If so, how?
thanks
-
- Posts: 232
- Joined: 02 Mar 2020 22:41
Re: yale keyless connected not reporting status
Here's a way to disable supervision from the command line:
Please add a follow-up reply if this command causes the lock manual operation to be reported correctly so that other forum readers can benefit.
Code: Select all
curl -u admin:ADMIN_PASSWORD_GOES_HERE --globoff http://127.0.0.1:8083/JS/Run/zway.devices[DEVICE_ID_GOES_HERE].instances[0].Supervision.data.disabled=true
-
- Posts: 24
- Joined: 25 Nov 2018 13:57
Re: yale keyless connected not reporting status
thanks Neil, but I get
TypeError: Cannot read property 'data' of undefined
if I do
I get a whole load of json, so I'm targetting the correct entity.
If I search the json I don't see supervision anywhere
TypeError: Cannot read property 'data' of undefined
if I do
Code: Select all
curl -u admin:mypassword --globoff http://127.0.0.1:8083/JS/Run/zway.devices[23].instances[0]
If I search the json I don't see supervision anywhere
Re: yale keyless connected not reporting status
Have you tried just pasting it into a web browser?
If you already have a tab opened and did login to Z-Way you don't need to worry about the username and password.
If you already have a tab opened and did login to Z-Way you don't need to worry about the username and password.
Code: Select all
http://127.0.0.1:8083/JS/Run/zway.devices[23].instances[0].Supervision.data.disabled=true
-
- Posts: 232
- Joined: 02 Mar 2020 22:41
Re: yale keyless connected not reporting status
The error you reported "TypeError: Cannot read property 'data' of undefined" occurs if the device does not support the Supervision command class. You can check whether the Yale lock supports Supervision from the expert UI. Try browsing to the following:
http://YOUR_ZWAY_IP:8083/expert/#/configuration/interview/23
I'm pretty sure you won't see the command class "Supervision". In other words, the approach to disable Supervision does not apply to your Yale lock version. As such, you'll need a different approach.
To help you figure out what's needed, additional information is necessary. When you manually lock and unlock the door, what appears in the z-way-server log file? Also, a screenshot of what shows up in the Zniffer History when you manually lock/unlock the door would be helpful (go to expert UI->Analytics tab->Zniffer History).
http://YOUR_ZWAY_IP:8083/expert/#/configuration/interview/23
I'm pretty sure you won't see the command class "Supervision". In other words, the approach to disable Supervision does not apply to your Yale lock version. As such, you'll need a different approach.
To help you figure out what's needed, additional information is necessary. When you manually lock and unlock the door, what appears in the z-way-server log file? Also, a screenshot of what shows up in the Zniffer History when you manually lock/unlock the door would be helpful (go to expert UI->Analytics tab->Zniffer History).
-
- Posts: 24
- Joined: 25 Nov 2018 13:57
Re: yale keyless connected not reporting status
thanks for your help. you are correct, there is no supervision class. that "fix" must only work on the conexis
I don't have an analytics tab(!), but this is what appears in the log
both the normal and the expert UI steadfastly maintain the lock status hasn't changed and an email that I put on for any event on that device didn't trigger (it triggers when I lock/unlock from the UI)
PS it is now device 25 as I've excluded/included it a couple of times since the last post
I don't know if it's relevant, but I'm having trouble getting it to secure include. it just sticks on "wait for key verification". I have had it secure include before (S0, not S2) and still had problems, so I'm not sure if that's relevant. (or how to make it verify - it's sat 30cm from the razberry at the moment).
I don't have an analytics tab(!), but this is what appears in the log
Code: Select all
[10:01:19] INFO: [2024-12-19 10:01:19.110] [D] [zway] RECEIVED: ( 01 08 00 04 00 19 02 98 40 30 )
[10:01:19] INFO: [2024-12-19 10:01:19.110] [D] [zway] SETDATA devices.25.data.lastReceived = 0 (0x00000000)
[10:01:19] INFO: [2024-12-19 10:01:19.110] [I] [zway] Node 25:0 CC Security: sending Nonce Report
[10:01:19] INFO: [2024-12-19 10:01:19.110] [I] [zway] Adding job: Nonce Report to node 25
[10:01:19] INFO: [2024-12-19 10:01:19.110] [D] [zway] SENDING (cb 0x1a): ( 01 11 00 13 19 0A 98 80 A3 1C 1B B9 1F 53 E4 A5 05 1A F9 )
[10:01:19] INFO: [2024-12-19 10:01:19.117] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[10:01:19] INFO: [2024-12-19 10:01:19.117] [D] [zway] Delivered to Z-Wave stack
[10:01:19] INFO: [2024-12-19 10:01:19.134] [D] [zway] RECEIVED: ( 01 07 00 13 1A 00 00 02 F3 )
[10:01:19] INFO: [2024-12-19 10:01:19.134] [I] [zway] Job 0x13 (Nonce Report to node 25): Delivered
[10:01:19] INFO: [2024-12-19 10:01:19.134] [D] [zway] SendData Response with callback 0x1a received: received by recipient
[10:01:19] INFO: [2024-12-19 10:01:19.135] [D] [zway] SETDATA devices.25.data.lastSendInternal = **********
[10:01:19] INFO: [2024-12-19 10:01:19.135] [D] [zway] SETDATA devices.25.data.lastSend = 31194 (0x000079da)
[10:01:19] INFO: [2024-12-19 10:01:19.135] [D] [zway] Job 0x13 (Nonce Report to node 25): success
[10:01:19] INFO: [2024-12-19 10:01:19.135] [I] [zway] Removing job: Nonce Report to node 25
[10:01:19] INFO: [2024-12-19 10:01:19.155] [D] [zway] RECEIVED: ( 01 1E 00 04 00 19 18 98 81 70 67 72 8A 37 CC A4 10 FD 97 BF 35 34 A3 CE 33 59 18 39 FE 64 FD C8 )
[10:01:19] INFO: [2024-12-19 10:01:19.156] [D] [zway] SETDATA devices.25.data.lastReceived = 0 (0x00000000)
[10:01:19] INFO: [2024-12-19 10:01:19.156] [I] [zway] Node 25:0 CC Security: Received a secure message
[10:01:19] INFO: [2024-12-19 10:01:19.156] [D] [zway] SETDATA devices.25.instances.0.commandClasses.152.data.firstPart = **********
[10:01:19] INFO: [2024-12-19 10:01:19.156] [I] [zway] Node 25:0 CC Security: passing decrypted packet to application level: [ 71 05 13 fb ]
[10:01:19] INFO: [2024-12-19 10:01:19.156] [D] [zway] SETDATA devices.25.instances.0.commandClasses.113.data.V1event.alarmType = 19 (0x00000013)
[10:01:19] INFO: [2024-12-19 10:01:19.156] [D] [zway] SETDATA devices.25.instances.0.commandClasses.113.data.V1event.level = 251 (0x000000fb)
[10:01:19] INFO: [2024-12-19 10:01:19.156] [D] [zway] SETDATA devices.25.instances.0.commandClasses.113.data.V1event = Empty
PS it is now device 25 as I've excluded/included it a couple of times since the last post
I don't know if it's relevant, but I'm having trouble getting it to secure include. it just sticks on "wait for key verification". I have had it secure include before (S0, not S2) and still had problems, so I'm not sure if that's relevant. (or how to make it verify - it's sat 30cm from the razberry at the moment).
Re: yale keyless connected not reporting status
What version of Z-Way, what Razberry board and what firmware is on it?
-
- Posts: 24
- Joined: 25 Nov 2018 13:57
Re: yale keyless connected not reporting status
Firmware version v4.1.4
UI version v1.16.1
Built date 22-07-2024 01:37:26
not sure which razberry board I have - it's old - I think it's a razberry 2? It doesn't have the big hole in it if that helps
UI version v1.16.1
Built date 22-07-2024 01:37:26
not sure which razberry board I have - it's old - I think it's a razberry 2? It doesn't have the big hole in it if that helps
-
- Posts: 24
- Joined: 25 Nov 2018 13:57
Re: yale keyless connected not reporting status
this is odd, in expert mode it's reporting firmware is -
The current firmware version is: 5.04 [Bootloader: 21389]
The current firmware version is: 5.04 [Bootloader: 21389]
Re: yale keyless connected not reporting status
In the Expert UI does show something like this:
The latest (which is not really new by any stretch of the means) is:
It was released 4 years ago and I would suggest to upgrade the firmware, you might need to use the token of all to see all of the firmware upgrade options.
Code: Select all
Hardware
Vendor: RaZberry by Z-Wave.Me
Vendors Product ID: 1024 / 2
Z-Wave Chip: ZW0500
Code: Select all
Library Type: Static Controller
SDK Version: 6.82.01
Serial API Version: 05.39