BE469 Text Changed

🧰 Built-In Apps and Drivers Built-in Drivers
1

I understand that things like this are not guaranteed, but as some point in the last couple months the text I was getting back from my locks changed. It used to include "thumb" when it was physically unlocked from the inside and I could use that to trigger the "next" door to unlock.

It was really nice to be able to discern which side of the door the user was.

Anyway...probably no more than a comment.

2

FWIW, the driver hasn't changed since platform version 2.3.5, so it must be something else. :slight_smile:

1 Like
3

Did you switch from z/ip gateway to zwjs?

2 Likes
4

Thanks...Yes. If that's it...why does that happen.

5

Z-Wave JS might be passing the data differently to the driver (it's a bit opinionated in what it does by default). If you enable debug logging, you should see more information about the "raw" data coming into the Hubitat driver. My guess is that it was looking for before (specific information in the AlarmReport, most likely) is no longer there or perhaps just pre-parsed a bit differently, and that could help figure out the difference.

And this is that "something else." :slight_smile:

2 Likes
6

Thanks guys...

I'm guessing what it boils down to is I can't really do anything about it...but will look at the output and see if there is anything else I can match.

Is there any chance at all a request to update the driver is possible? I know from other systems and groups as well that I'm not alone using the ability to decern which side of a locking system was opened from to drive rules. I'm just guessing...but BE469's are pretty common/popular...maybe still the most common.

7

Why not do this?

as suggested above, then share the output from (at least) keypad and thumbturn locks so someone can see what the difference is, if there is one in this case?

Yes, but no one can do that without information like the above. (Assuming it is still possible, which I imagine it would be at some level but would be easiest if the information is already there, which the above will tell.)

2 Likes
8

I am so...so sorry...My todo list is so long right now I forgot I had actually resolved this. Solved.

1 Like
9

Could you post the solution? It will be very useful to other users who have BE469 locks and who switched to ZWaveJS.

Many thanks!

1 Like
10

I was simply matching on text in rules. This works now. I used to match on "thumb"

Lock
Lock1648×1610 286 KB

2 Likes
11

What is this setting??

12

Matching the event text in the rule for "manually"...vs..."thumb" in the non-JS ZWAVE version of the antenna driver on the hub.

If you are not on the JS version you probably still can match on "thumb."

13

Just to update and to confirm...

I had to downgrade from the JS zwave version due to issues.

Going back to the old zwave brings back the original message containing "thumb" to match on in a rule from the driver

14

I had a lot of Schlage lock issues with JS. For example, the status of the locks was always incorrect.

I reverted back and things are back to normal. I hope there are JS improvements in the future to fix these issues.

15

Ya...the last thing I need behaving badly are locks

1 Like