# Z-wave U-bolt reporting incorrect status in Hubitat
**URL:** https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990
**Category:** ULTRALOQ Smart Lock
**Tags:** u-bolt-pro-zwave
**Created:** [June 1, 2025, 11:42pm UTC](https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990 "2025-06-01T23:42:29Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Sean12](https://community.ultraloq.com/u/Sean12)
#### Post date: [June 1, 2025, 11:42pm UTC](https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990/1 "2025-06-01T23:42:29Z")
I will submit a ticket on this as well, but thought I’d check the community for insight as well.
I’ve been using 2 u-bolt-pro Z wave locks in my new home for over a year now. Both are part of my Hubitat Z-wave network which is very stable and they have not dropped off. One lock reports it’s lock/unlock status reliably as expected. The other does not.
Similar to complaints I have seen in other threads, the defective lock NEVER updates it’s locked/unlocked status via Z-wave when it is changed manually or by fingerprint. If I change it using the app, or via a Z-wave dashboard then it will update. If I send a refresh command from Hubitat to the lock, it will usually correctly update. It just seems to fail in pushing a change initiated at the lock.
I saw Home assistant users are being individually sent a firmware update that fixes the problem on HA. Will the same update work with Hubitat? Can I safely update the lock firmware via Hubitat given that it needs to use a generic Z-wave lock driver?
Odd that one lock works and the other does not. Both are showing firmware version: 02.26.0022
Thanks for any help.
---
### Author:  [@Savy](https://community.ultraloq.com/u/Savy)
#### Post date: [June 6, 2025, 6:12am UTC](https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990/2 "2025-06-06T06:12:16Z")
@Sean12 Hi Sean, we have contacted you in [ticket #493875](https://xthingsservice.zendesk.com/agent/tickets/493875), please kindly check your email. Thanks!
---
### Author:  [@Vasilos](https://community.ultraloq.com/u/Vasilos)
#### Post date: [June 27, 2025, 6:59pm UTC](https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990/3 "2025-06-27T18:59:07Z")
Same issue, incorrect reporting of lock status over zwave, the lock itself is reporting it is unlocked via zwave (refresh, new status, still showing unlocked). Can we call get the fix?
---
### Author:  [@Savy](https://community.ultraloq.com/u/Savy)
#### Post date: [July 4, 2025, 10:13am UTC](https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990/4 "2025-07-04T10:13:30Z")
@Vasilos Hi Vasilos, we have contacted you in [ticket #500972](https://xthingsservice.zendesk.com/agent/tickets/500972), please kindly check your email. Thanks!
---
### Author:  [@Simeon](https://community.ultraloq.com/u/Simeon)
#### Post date: [February 5, 2026, 5:58am UTC](https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990/5 "2026-02-05T05:58:47Z")
Im also having the same issue with status reporting in home assistant
---
### Author:  [@Savy](https://community.ultraloq.com/u/Savy)
#### Post date: [February 6, 2026, 8:46am UTC](https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990/6 "2026-02-06T08:46:53Z")
@Simeon Hi Simeon, we have contacted you in [ticket #542324](https://xthingsservice.zendesk.com/agent/tickets/542324), please kindly check your email. Thanks!
---
### Author:  [@Simeon](https://community.ultraloq.com/u/Simeon)
#### Post date: [July 30, 2026, 3:36am UTC](https://community.ultraloq.com/t/z-wave-u-bolt-reporting-incorrect-status-in-hubitat/10990/7 "2026-07-30T03:36:58Z")
I update to the latest firmware, excluded from home assistsnt and reconnected and Im still having the same issue. The lock fails to update the status sporadically. This is causing my automations to fail and is really upsetting. I have 4 of these locks ☹