Hmmm… I’ll check this when I get home. Maybe it just paired wrong. Does it report who unlocked?
- Deadbolt
- Lever
- Bundle
- Cloud Platform
- Ultraloq
- Accessories
Hmmm… I’ll check this when I get home. Maybe it just paired wrong. Does it report who unlocked?
Out of curiosity, what hub are you using?
I just checked and none of my locks are working after migrating from C7 to C8. I suppose I’ll have to re-pair them myself. Definitely worked on C7, hence the data in my screenshot.
I ended up having like 6 ghost Z-Wave devices. I didn’t realize how bad my mesh was after the C8 migration. Doh. Re-pairing the lock to see if it works properly now.
Does not appear to support sending the lock code used.
I just got a Zwave lock today, and added to my Home Assistant. To say I’m disappointed at the functionality is an understatement. I’m returning it to Amazon for a full refund. Absolute garbage.
Do better U-Tec.
I agree such a nice lock needs better Zwave access to internal features, including door open / close status, the ability to disable auto locking (“Party Mode”), disable exterior unlocking (“Privacy Mode”), and ability to lock or unlock “ALL”. Essentially, improve the integration features of the Uloq Pro Lock with home automation, including HomeSeer - Please?
I just bought and installed the U Bolt Pro Z-Wave. I noticed the Door Status in Home Assistant via Z-Wave immediately went to unknown after getting added to my network. The door lock/unlock functionality works great however. I saw a user above that seemingly had more information like what users locked/unlocked the door. The documentation on Z-Wave JS DB only seemed to have inclusion/exclusion instructions. Have I missed something along the way or is control over the lock the only supported functionality at the moment?
Well I’m gonna add my voice to that since it’s been a year of people complaining and not even an answer from U-Tec.
The price-point is very high. I assumed it would have the standard Zwave functions, but it doesn’t. We should be able, at the very least, to know who (or what code, or even just what method key vs. code) was used. Keypad + Fingerprint means this would be a very simple security keypad, but as it stands I need a separate one.
Please please fix that!
Unfortunately, I have not been able to get this to function.
Funny enough, I saw this reply and then shortly after I noticed I received an notification in HA that the firmware on my lock had an update 1.1.3 → 1.5 with the note ‘Fixed door state issue’. Wondering if someone at u-tec read our plea and pushed an update.
Attempting this update, so far it’s stalled around 26% I think so I took the batteries out of the device and restarted my Z-Wave add-on in HA.
Attempting this update again and we’ll see
Have you gotten this to update and do you know if it’s correctly reporting door status now?
I also attempted this update last night and stalled at 26%, haven’t come back to it yet. But the lock is still working.
The second attempt at upgrading failed as well.
I rebooted my HAS guest from my host, and then attempted to update another lock, and it actually updated fine!
It’s now correctly showing the door status, and the status for the lock updated after it auto-locked. We’ll need to see how this continues to report, but that much more functionality is now available.
I didn’t have an issue with the update, though it did take awhile (~15-20 minutes). The door status didn’t work initially but a few cycles of opening/closing the door and using the lock it seems to be working now!
There’s no update available on the Utec app, unfortunately. I doubt I will ever be able to push something via Z-Wave from Hubitat. I’m surprised that HA has that option. I assume you’re using a USB Z-Wave stick of some sort? I might need to set up my 700-series stick on HA and add as a secondary controller or something.
EDIT:
CAUTION
Abnormal behavior has started after this firmware upgrade. Lock was not responding to physical interaction or Zwave. After opening the battery compartment, the lock started responding to physical touch and Zwave commands. Now is the wave lock status is no longer reporting accurately through zwave.
Edit 2:
Using the Zwave heal option seems to have improved the issue with Zwave not properly reporting the status of the lock, but not completely This was my first troubleshooting attempt and it seems to have solved the issue.
My lock is installed on a completely metal door/gate so the door status was never reliable in the app, but I do see the field Current status of the door in HomeAssistant (I believe its new but I wasn’t paying attention to since it has been unreliable).
Original:
I have also upgraded to the new 1.5 firmware. The upgrade via HomeAssistant went smoothly for me. I have not noticed any improvements but also have not seen any new issues related to the upgrade (I was concerned it could make things worse).
I run zwavejs2mqtt in a docker container (as well as HA) and use a Zooz 700 Series Z-Wave Plus S2 stick.
After upgrading did you not see the new sensors show up under your lock in your zwave integration?
Personally, I am running a hardware Z-Wave hub, so I cannot test this. I have no idea where HA even gets firmware like this.
Does anyone have a copy of the firmware file?
