Ultraloq Pro Z-wave #5445
Comments
|
Having same issue, also the door status is always open. Doesn't seem to report the state of the sensors correctly. According to their zwave documentation both should be on the reports. Different parts of the door condition |
|
|
|
I'll try on Monday |
|
Thanks. There really should be two entities for the pro if the sensor is present. One for the lock, and one for the door sensor |
|
That's a bug in the device firmware, at least in v1.1.3 which my lock is on. which means Bolt and Latch states are supported, Door state isn't: Given that the manual states that Bolt and Door are supported, this seems like a bug. |
|
Despite that, I can't get the lock to report any change in door state. It always reports door open. |
|
Well that's not awesome. I send an email to them about this issue with this thread... Maybe they can fix it. Would be great to be able to get door status |
|
Hi @AlCalzone , I wonder if we can put some special code in to make a fix for this device and this version firmware? the outdoorhandle value is clearly matching the door sensor state. Or, if you can give me a quick hint where the related code is, I can try to make a change, then you can choose if you want to merge it in. Thanks. |
|
We don't hardcode such one-time device-specific behavior. |
|
I've heard that U-Tec finally managed to reproduce the issue, but no idea if and when this will be fixed. |
|
@AlCalzone do you have a link to their issue I can follow ? |
|
Nope, that was all back-channel information. Haven't head anything since. |
|
I would like to add that they have seemingly made no progress on fixing this issue and I have discovered a second issue and it seems others have as well. When the lock is triggered to lock, even if the locking process fails, say the door isn't closed all the way or something happens to make it not engage the deadbolt, the lock will beep and error out but the reported status to z-wave is that the lock was successful. This is dangerous as even though you should always manually check for security, it should report some kind of error or at least fallback to the previous state. Kind of disappointed in Ultraloq on the development of this. |
|
Yeah, the lock is good, but if they don't actually fix bugs then it's
really not a great choice
…On Tue, Jul 4, 2023, 10:31 TheOgre ***@***.***> wrote:
I would like to add that they have seemingly made no progress on fixing
this issue and I have discovered a second issue and it seems others have as
well.
When the lock is triggered to lock, even if the locking process fails, say
the door isn't closed all the way or something happens to make it not
engage the deadbolt, the lock will beep and error out but the reported
status to z-wave is that the lock was successful. This is dangerous as even
though you should always manually check for security, it should report some
kind of error or at least fallback to the previous state. Kind of
disappointed in Ultraloq on the development of this.
—
Reply to this email directly, view it on GitHub
<#5445 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADAEABHC2QPSLJ2OFVBKUTLXOQSNJANCNFSM6AAAAAAUXA6EVU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I completely agree. The firmware version of my lock is 02.26.0022 which, from how it reads, is from February of 2022, so no firmware updates in almost a year and a half. For something that's supposed to be a "Work With Home Assistant" product, that's a pretty unacceptable lack of updates especially when there are glaring bugs. |
|
We have decided to terminate the Works with Home Assistant relationship with Ultraloq. We had reported these issues with them and were discussing solutions. However, they ceased communication from their end and we have received no further updates. |
Good to see some action being taken about this. Thanks for keeping Home Assistant great! |
AlCalzone
added
the
cannot fix ❌
|
I'm afraid there's nothing to be done in this project, since the functionality is just broken. |
|
Could we update https://www.home-assistant.io/integrations/ultraloq/ ? |
|
New Z-Wave U-Bolt Pro, latest firmware applied, latest HAOS/core, status is still stuck at open for u_bolt_pro_z_wave_smart_lock_current_status_of_the_door. The app shows correctly so the position sensor is working. |
|
I still find it tricky to trigger changes of the sensor without mounting the lock in a doorframe, but I haven't managed to get the state in the app and HA out of sync. When the status does change, I see it in both. Might be a connectivity issue? |
Don't think so? After latest update the door status seems to be working slightly better. What consistently seems to not work is auto-lock after X seconds doesn't seem to update the lock status. Opening the door from outside and then it locking automatically when closed is working. But if I open it from HA, then it auto locks after 15 seconds... the status does not get updated. |
Wait, are we talking about the lock status or the door status? |
Sorry I kind of switched gears. Door open status seems to be a bit better since the latest update. However the auto-lock has been an issue since adding the lock. Anytime I manually unlock it, that gets tracked properly in HA. Anytime it automatically locks it seems to not get tracked. I hit the lock in HA, and the status changes but the lock does nothing which is what I'd expect. So it knows it's already locked at least! |
|
Ok I'll try to reproduce that tomorrow |
|
I have tested in our site. The lock updates the correct status after auto-lock. For testing door status,please move the lock body,don't move magnet. The version of my lock. Can you share me the testing video? We want more operate details to debug the issue. Thanks.
|
Ok I have some further testing results. Door open status seems to be working perfectly fine for the moment. Door lock status status when opened at the lock seems perfectly fine, including when it auto locks. When I open the lock via the app, and it auto locks, status is reported fine. It's only when I open the door via HA that this issue occurs. And it doesn't seem to matter which kind of card I use. I can open the lock, it will update the status, but when the lock auto locks the HA state still reflects unlocked. When I click it again, it will beep and indicate lock. Sometimes this can get totally out of sync where it think it's unlocked but it's actually locked or vice versa. So it's only when controlling via HA that this is occurring. I can try and make a video if it's helpful I just wanted to clarify that first. |
|
Can you give me a interface picture that you operate the lock and the status show ? |
I will try and upload something a bit later. I did want to add I found something else interesting today. I opened the lock from inside to go out. It captured the door and lock sensors fine. However, it did not capture either door unlock/lock or open/closed events when I came back, using the fingerprint sensor and the door automatically locking when I shut it. I'm not sure if maybe it just didn't have time to register those events or they didn't get sent or what. |
|
My testing enviroment is: a Iaptop ( installed HA virtual machine, Connected a SLUSB700A hub with new driver, edge Brower |
Ya not trying to muddy the waters. Just let me know what helps most to troubleshoot. I'm running a dedicated ASRock BeeBox, with HAOS running Virtualbox (latest version, extension manager installed and USB passthrough), on Windows 10, Zooz ZST10-700 with firmware 7.19.2. Doesn't matter if I login with the HA web interface, or the HA app., I get the same result. I have the magnet on the door frame as well. I am looking at the entity values/history directly for the most part. I know if those don't work then anything relying on them most likely won't either. |
|
Sorry, I just want to know how to reproduce the bug you mentioned in my side and try help debug. I will update If i have new info. |
|
100%! No need to apologize I appreciate your help. Will get you info soon. |
|
Any update on the last remaining bug? |
Hi Chris - apologies I was travelling for the better part of the last month and a half. I will shoot a video for you and post it. It is still happening for sure. |
|
Here's a quick video to illustrate what is happening: https://youtu.be/cmq1fcqTxyA In short: if I click the unlock button, the lock unlocks as expected. Sometimes it takes a second to register on the card in HA but that works pretty consistently. But notice once the door lock auto locks (10 seconds after the unlock), the status doesn't update in HA. It remains as "unlocked". If I click "lock" again in HA you'll notice you hear one beep and the status updates in HA. I guess the lock knows it's locked hence the single beep. For whatever reason HA just won't update with that manual action. This only happens when I use the unlock button on one of the cards. If I use the Utec app, the status updates for both when it unlocks and auto locks as expected. |
|
I agree, I have the same behavior in my instance. |
|
Thank you for sharing the video, I am experiencing the same with my lock. |
|
Interesting. Mine isn't doing that. I click the unlock button, it unlocks. Mine is set to auto lock after 30 seconds. It locks and the status in HA updates immediately. Interesting. If I set it to lock after 10 seconds, it does what you're experiencing. Setting it to 20 seconds works fine. Hopefully this helps with troubleshooting the bug. |
I was optimistic when I saw this but I'm still having mixed results. I set my timeout to 20 seconds. The first time I tried the HA unlock, it worked as you described above. So I tried it again in succession, and it didn't work. Same result as I was getting before. After about 30 minutes I tried again, this time it worked. Again, tried in succession, it didn't work. Using the app, it works flawlessly. I can unlock, auto-lock, then unlock again in succession and the status is updated in HA as expected. I will say I know when HA is not going to work because when I unlock the lock, it takes a few seconds for it to register in HA. When that happens, I know when it auto locks it's not going to update. When I unlock and it updates almost immediately, I know the auto lock status update is going to work. |
|
So HA removed the "Works With HA". Does that mean we are screwed? Just hope that U-Tec will fix it at some point? |
|
They fixed the issue and Home Assistant will offer users to update this firmware |
OK and where it is?? I still don't see firmware update. |
|
I find conflicting information on whether ULtraLoq is or is not a WWHA product. At this link: https://www.home-assistant.io/integrations/ultraloq/ it seems that it is, but I've seen threads that indicate ULtraLoq has been unresponsive to fixing issues and it has been removed from WWHA. I am considering replacing my current WiFi UltraLoq with the Z-Wave enabled version, but I don't want to do this if it is not reliably supported in HA. Can anyone shed some light on the state of UltraLoq support in HA? |
|
Late last month I did find a post on the Ultraloq forums talking about the same issue. In it someone from Ultraloq mentioned that a ticket would need to be opened and they would need to replace the lock. After opening the ticket and talking with someone they gave me this LINK to update the firmware from HA. That was about 2 weeks ago and things seem to be fixed. https://file.u-tec.com/homekit/U-BOLT-PRO-ZWAVE_V1.7.gbl TLDR. Use the above link from Ultraloq and give it a try. |
|
@Daguse how'd you install the firmware? I'm using HA with Z-Wave JS UI and I'm not sure how to upgrade with a downloaded firmware file. Both HA and Z-Wave JS UI shows the device is up-to-date with no option to provide my own firmware files. |
|
What firmware does it show? Mine says it's v1.5.3 which I assume is current for the z-wave model. I do see on their site that 1.41 is available, but it seems only for the wi-fi models. |
|
@zirdum in HA/Z-Wave-JS it shows 1.5.3, however, in U home it shows 02.26.0022. The FW link above seems to indicate it's 1.7 |
Thank you for posting this! It fixed my issues! |
and others
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there.
Describe the bug
[77-98-0-latchStatus] Current status of the latch is always reporting "OPEN"
U-tec support said the issue could be on the z wave hub side.
Thread of others reporting the same issue: https://community.u-tec.com/t/expand-and-fix-z-wave-capabilities/502/18
Device information
Manufacturer: u-tec
Model name: U Bolt Pro Z wave
Node ID in your network: <077>
How are you using
node-zwave-js?zwave-js-ui(formerlyzwavejs2mqtt) Docker image (latest)zwave-js-ui(formerlyzwavejs2mqtt) Docker image (dev)zwave-js-ui(formerlyzwavejs2mqtt) Docker manually built (please specify branches)ioBroker.zwave2adapter (please specify version)HomeAssistant zwave_jsintegration (please specify version)pkgnode-red-contrib-zwave-js(please specify version, double click node to find out)Which branches or versions?
zwave-js-ui: 8.6.3.c12b1c6
zwave-js: 10.3.1
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
zwavejs_current.log
The text was updated successfully, but these errors were encountered: