yale keyless connected not reporting status
Re: yale keyless connected not reporting status
The 4.1.4 is the Z-Way software version, the 5.04 is the firmware on the Razberry card. Upgrading Z-Way does not upgrade the firmware on the Razberry board.
-
- Posts: 203
- Joined: 02 Mar 2020 22:41
Re: yale keyless connected not reporting status
The log snippet provides useful information. You'll need to do additional testing to see what messages the lock sends when it's manually locked and unlocked.
Based on the log information you provided, the Easy Scripting app should be able to solve your problem. The Easy Scripting app is very useful and powerful. It lets you write JavaScript code to listen for Z-Wave messages from a device/command class and then take an action. When I want to do complex if/then logic, the Easy Scripting app is what I use. Note that the app needs to be used carefully since it runs in the main Z-Way processing thread - a poorly written app can destabilize your entire Z-Way setup. If that happens, just stop the Easy Script app. With that warning out of the way, let's make progress.
The log shows:
Assuming your lock (device 25) sends an alarm message (command class 113) with alarmType=18 or 21 when the door is locked and alarmType=19 or 22 when the door is unlocked, something like the following Easy Scripting code should work:
Since I don't have a Yale lock, you'll need to test/debug the Easy Script app. If you get stuck, please post the z-way-server log file that shows what happens when you manually lock and unlock the door.
Based on the log information you provided, the Easy Scripting app should be able to solve your problem. The Easy Scripting app is very useful and powerful. It lets you write JavaScript code to listen for Z-Wave messages from a device/command class and then take an action. When I want to do complex if/then logic, the Easy Scripting app is what I use. Note that the app needs to be used carefully since it runs in the main Z-Way processing thread - a poorly written app can destabilize your entire Z-Way setup. If that happens, just stop the Easy Script app. With that warning out of the way, let's make progress.
The log shows:
Code: Select all
[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
Code: Select all
### ZWayVDev_zway_25-0-113
console.log("In Easy Scripting App - alarmType, level:", vdev("ZWayVDev_zway_25-0-113").V1event.alarmType.value(),vdev("ZWayVDev_zway_25-0-113").V1event.level.value());
if (vdev("ZWayVDev_zway_25-0-113").V1event.alarmType.value() == "18" || vdev("ZWayVDev_zway_25-0-113").V1event.alarmType.value() == "21") {
vdev("ZWayVDev_zway_25-0-113").set("metrics:level", "close")
}
if (vdev("ZWayVDev_zway_25-0-113").V1event.alarmType.value() == "19" || vdev("ZWayVDev_zway_25-0-113").V1event.alarmType.value() == "22") {
vdev("ZWayVDev_zway_25-0-113").set("metrics:level", "open")
}
-
- Posts: 24
- Joined: 25 Nov 2018 13:57
Re: yale keyless connected not reporting status
thanks. if I can work out how to get into easy scripting, I'll give it a go!
-
- Posts: 24
- Joined: 25 Nov 2018 13:57
Re: yale keyless connected not reporting status
having said that though, shouldn't it just work?! it always used to...
-
- Posts: 203
- Joined: 02 Mar 2020 22:41
Re: yale keyless connected not reporting status
I don't know what changed from when the Yale lock manual operation was being reported correctly to when lock status reporting stopped working. One possible explanation is that Z-way software for Alarm command class processing has changed. Unfortunately, since the Z-Way developers do not share the source code for command class processing, we can only guess the software has changed. I expect other explanations are possible. Fortunately, the Easy Scripting app provides a seamless workaround. Perhaps @PoltoS will share more information.
Please note that I'm simply a user of Z-Way software and am trying to help other Z-Way users. On a tangent... it may be worth considering changing to the default Z-Wave software package used by Home Assistant, called Z-Wave JS, as it is completely open source and should work with your hardware.
I've attached a screenshot that shows how to add an Easy Scripting app. From the main UI, click on the three horizontal bar icon, choose "Apps" from the pulldown menu and click on the "+" button for the Easy Scripting app. Although there's a learning curve to using this app, I think it's worth the effort, assuming you're comfortable writing a small amount of JavaScript code. I rely on this app to support the Zooz Zen 32 scene controller - the app responds to scene requests and controls the LED indicators.
Please note that I'm simply a user of Z-Way software and am trying to help other Z-Way users. On a tangent... it may be worth considering changing to the default Z-Wave software package used by Home Assistant, called Z-Wave JS, as it is completely open source and should work with your hardware.
I've attached a screenshot that shows how to add an Easy Scripting app. From the main UI, click on the three horizontal bar icon, choose "Apps" from the pulldown menu and click on the "+" button for the Easy Scripting app. Although there's a learning curve to using this app, I think it's worth the effort, assuming you're comfortable writing a small amount of JavaScript code. I rely on this app to support the Zooz Zen 32 scene controller - the app responds to scene requests and controls the LED indicators.