Weiser GED2150 suddenly not showing boltStatus / lock status in HA

[daytonturner]

I'm not sure whats happening here, I recently noticed that my Weiser SmartCode 10 Touchscreen lock is not reporting boltStatus correctly as lock state in Home Assistant. This was working previously. Not sure if it has to do with the recent upgrade to 2023.8.2, but all the other parameters are reporting correctly.

I've tried to step through debugging, but its not clear to me how HA maps zwave-js parameters to HA entity state.

Looking at the zwave-js-ui, as well as the websocket raw packet information, I do see that the node is reporting proper boltState as locked:

2023-08-18T19:51:52.297Z - VALUE UPDATED 
Arg 0:
└─commandClassName: Door Lock
└─commandClass: 98
└─property: boltStatus
└─endpoint: 0
└─newValue: locked
└─prevValue: locked
└─propertyName: boltStatus

And value updates show in zwaveJS logs

2023-08-18 13:38:19.530 INFO Z-WAVE: [Node 009] Value updated: 98-0-doorStatus open => open
2023-08-18 13:38:19.537 INFO Z-WAVE: [Node 009] Value updated: 98-0-boltStatus locked => locked
2023-08-18 13:38:19.541 INFO Z-WAVE: [Node 009] Value updated: 98-0-latchStatus open => open

I also see latchStatus in these updates:

2023-08-18T19:51:52.301Z - VALUE UPDATED 
Arg 0:
└─commandClassName: Door Lock
└─commandClass: 98
└─property: latchStatus
└─endpoint: 0
└─newValue: open
└─prevValue: open
└─propertyName: latchStatus

But looking in my HA states, i see:

All of the other data seems to be populating into the HA Device:

But despite the boltStatus being correct in zwave-js, HA doesnt seem to be reporting it in the lock state.

What else can I check to verify that the boltStatus is being correctly interpreted by HA?

Apologies if i'm posting this in the wrong repository, i wasnt sure if it should start here or in node-zwave-js

[kpine]

Bolt and Latch status are not supported in HA.

The lock entity state is based on "Current lock mode". Your screenshot from ZUI shows that Z-Wave JS is reporting the lock state as "Unknown", which is exactly what HA is reporting.

[daytonturner]

Well.. that would certainly explain it, I didn’t realize it wasn’t coming from boltStatus. I’m not sure why all of a sudden “current lock mode” would fail to report status when other values are definitely updating, and lock control commands work, but I suppose I can start by re-interviewing or excluding/including again. Thanks for the insight! Dayton

…

________________________________ From: kpine ***@***.***> Sent: Friday, August 18, 2023 7:40 PM To: zwave-js/zwave-js-ui ***@***.***> Cc: daytonturner ***@***.***>; Author ***@***.***> Subject: Re: [zwave-js/zwave-js-ui] Weiser GED2150 suddenly not showing boltStatus / lock status in HA (Issue #3231) Bolt and Latch status are not supported in HA. The lock entity state is based on "Current lock mode". Your screenshot from ZUI shows that Z-Wave JS is reporting the lock state as "Unknown", which is exactly what HA is reporting. — Reply to this email directly, view it on GitHub<#3231 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACZEPSJZMXIRQ3MS3Q5WRETXWARR3ANCNFSM6AAAAAA3WAEYC4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[kpine]

You can also try collecting driver debug logs:

• https://zwave-js.github.io/node-zwave-js/#/troubleshooting/index?id=rule-1-use-the-driver-log-luke
• https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

[robertsLando]

Closing this as not a zui related issue. Feel free to open the issue in HA core if needed