Greetings,

I use a Universal Devices ISY 994i PRO paired to a Yale Z-Wave enabled smart lock. The lock and hub were working fine until recently. When querying the lock in the mobile app, it would come back with Status Unknown and the battery level on the lock disappeared. Clicking Lock or Unlock on the mobile app did nothing. The lock did not operate.

I just replaced the batteries on the lock. Even though the hub reported 95% remaining on the batteries before this happened, I know it's been a few months since I installed this lock with original batteries.

The lock works now since changing the batteries, but I'm seeing this on the Java-based dashboard when querying the lock.

[ZW-TX-FAILED] enc=Ok uid=2.0 cmd=0x20.02 BASIC

Should I remove and re-add the lock in Z-Wave? Or what else could be going on?
 

Sounds like you are having communication issues. You should think about improving your Zwave mesh.

The hub and the smart lock are about 12 feet apart. The only physical interference between the smart lock and the hub is a hollow core wood door.

Granted, in light of what's happening now, I could have made a placement mistake. I installed the hub right next to a wireless access point that does 2.4 and 5 GHz. But the hub communicates via 900 MHz, or so I understood. So it shouldn't be an issue. Or would it?

I also use a Levitton smart outlet that also dubs as an extender. I bought it sometime ago in case signal range became an issue. I just installed and turned it on last night. This morning, the hub lost communication with the hub again.

Any pointers on improving coverage would be appreciate. Thanks again.

If you search the form preferably with google ( site:forum.universal-devices.com Yale ) you will find many users with issues communicating with Yale locks.  I recall a post (although I could not find it with a quick search) that stated the only way the lock would work reliably was with the ISY within a few feet. The same users stated communication would not work through a repeater, possibly due to the security level.  There are other users with posts having issues similar to yours when batteries are not close to 100%. Other locks work much better, although some require the device to be very close to the ISY during initial inclusion.  I assume there is an issue with this manufacturer, if locks from other manufactures function correctly at a much greater distance.

I have a couple of Schlage locks about equal distance from the ISY, some 20-30 feet through 70+ year old 1.5" plaster walls and backer board. For context to the extent of signal degradation in the home,  it is almost impossible to get WiFi outside of the home, 20-30 feet from the access point.  One lock is hard wired to my whole home 12v system, with voltage transformer the other is using batteries.  The wired unit rarely reports an unknown status, the battery unit more often especially when batteries are low, although both will report correct status on query.  

41 minutes ago, Javi said:

If you search the form preferably with google ( site:forum.universal-devices.com Yale ) you will find many users with issues communicating with Yale locks.  I recall a post (although I could not find it with a quick search) that stated the only way the lock would work reliably was with the ISY within a few feet. The same users stated communication would not work through a repeater, possibly due to the security level.  There are other users with posts having issues similar to yours when batteries are not close to 100%. Other locks work much better, although some require the device to be very close to the ISY during initial inclusion.  I assume there is an issue with this manufacturer, if locks from other manufactures function correctly at a much greater distance.

I have a couple of Schlage locks about equal distance from the ISY, some 20-30 feet through 70+ year old 1.5" plaster walls and backer board. For context to the extent of signal degradation in the home,  it is almost impossible to get WiFi outside of the home, 20-30 feet from the access point.  One lock is hard wired to my whole home 12v system, with voltage transformer the other is using batteries.  The wired unit rarely reports an unknown status, the battery unit more often especially when batteries are low, although both will report correct status on query.  

This depends on firmware. Up to 5.0.16, Yale worked perfectly with the Isy.  After that is when issues started happening with communication and some features not working. One example is being able to tell the difference between keypad locking and manual locking (there's more). Since the op didn't give any system details, he may be experiencing other issues vs. it simply doesn't work

My ISY is running 5.3.0. Are you saying the fix is downgrading it to 5.0.16?

I had this running for a few months without issues from what I could tell.

I don't know if this matters, but I noticed neighboring Google Home pop up on my Android phone recently. I'm assuming this is similar automation as the ISY. Could this possibly interfere?

Ok, I think I just did something stupid to this.

I did factory reset on ISY. Now I'm trying to repair the Yale lock to it, but the lock wants to remove itself first from Z-Wave.

There's supposed to be a factory reset button on the lock, which is not in the location where the documentation says it is.

Did I just brick this lock?

The best option is to restore your backup If you have a one.  If you do not search "excluded <lock name>" on Google and there should be a few videos/instructions. 

@tired_runner My Yale assure lock requires a code to exclude/include. There is no factory reset button.

Entroll: PIN followed by # Press 7 # Press 1 # Unenroll: PIN followed by # Press 7 # Press 3 #

When I added my lock back in after upgrading to Polisy it took several tries. Then afterwards, communication was flakey for a while but eventually is more stable now as Z-Wave network seemed to learn/heal on its own - I would say 99%. I have 20+ Z-Wave devices.

Here is information on mine... strange the last route was the node 4 family room bird lamp which is just about the furthest away Z-Wave device from it LOL, but not sure it uses it because it looks like it is also talking direct to ISY.

Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ] ----------------------------------------------
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ] Front Door
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ] ZW007_1 uid=7 security=S0 type=4.64.3 mid=297 tid=32770 pid=1536 model=5
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ] Association Group ID 1
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x5E  V2   ZWAVEPLUS_INFO
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x72  V2   MANUFACTURER_SPECIFIC
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x98  V1   SECURITY
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x5A  V1   DEVICE_RESET_LOCALLY
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x73  V1   POWERLEVEL
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x86  V2   VERSION
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ] - Secure
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x80  V1  BATTERY
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x62  V2  DOOR_LOCK
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x85  V2  ASSOCIATION
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x59  V1  ASSOCIATION_GROUP_INFO
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x71  V4  NOTIFICATION
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x70  V1  CONFIGURATION
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x63  V1  USER_CODE
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x8A  V2  TIME
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x8B  V1  TIME_PARAMETERS
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x4C  V1  DOOR_LOCK_LOGGING
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x4E  V3  SCHEDULE_ENTRY_LOCK
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  x7A  V3  FIRMWARE_UPDATE_MD
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    -  xEF  V0  MARK
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ] 
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ] Last working route from ISY to Node   7 - Front Door
Mon 03/14/2022 11:57:27 AM : [ZWAVE-TX        ] [01040092076E]                          REQ ZW_GET_LAST_WORKING_ROUTE 
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ]    - Node   4 - Family Room Bird Lamp
Mon 03/14/2022 11:57:27 AM : [ZW-SHOW         ] 
Mon 03/14/2022 11:57:27 AM : [ZWAVE-TX        ] [01070080070000FD82]                    REQ ZW_GET_ROUTING_INFO 
Mon 03/14/2022 11:57:27 AM : [ZWAVE-TX        ] [01070080070100FE80]                    REQ ZW_GET_ROUTING_INFO 
Mon 03/14/2022 11:57:28 AM : [ZWAVE-TX        ] [01070080070001FF81]                    REQ ZW_GET_ROUTING_INFO 
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ] Node   7 - Front Door has the following neighbors
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node   1 - [This ISY]
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node   2 - Living Room Outlet Front
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node   3 - WaterCop
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node   4 - Family Room Bird Lamp
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node   8 - Dining Room Salt Lamp
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  14 - ZW 014 Binary Switch
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  15 - Downstairs Hallway
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  16 - Family Room Xmas Tree
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  17 - Master Bedroom Lamp
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  18 - Living Room Xmas Tree
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  19 - Rec Room N
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  21 - Dining Room Lamp
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  22 - Main Bathroom Light
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ]    - Repeater - Node  27 - Outside Xmas
Mon 03/14/2022 11:57:28 AM : [ZW-SHOW         ] 
Mon 03/14/2022 11:57:28 AM : [ZWAVE-TE        ] [85/05] Assoc Groupings Get ACK,AUTO,EXPLORE To=0x07
Mon 03/14/2022 11:57:28 AM : [ZWAVE-TX ZW007_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x07
Mon 03/14/2022 11:57:29 AM : [ZWAVE-RX ZW007_1] [98/80] Security Nonce Report - nonce=[53A7FE92E4ACA80B] ACK,AUTO,EXPLORE From=0x07
Mon 03/14/2022 11:57:30 AM : [ZWAVE-RX ZW007_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x07
Mon 03/14/2022 11:57:30 AM : [ZWAVE-TX-NONCE  ] ...
Mon 03/14/2022 11:57:30 AM : [ZWAVE-RD        ] [010A001307038506012500AB]              REQ ZW_SEND_DATA 
Mon 03/14/2022 11:57:30 AM : [ZW-SHOW         ] Node   7 - Front Door has 1 association group
Mon 03/14/2022 11:57:30 AM : [ZWAVE-TE        ] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x07
Mon 03/14/2022 11:57:30 AM : [ZWAVE-TX ZW007_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x07
Mon 03/14/2022 11:57:30 AM : [ZWAVE-RX ZW007_1] [98/80] Security Nonce Report - nonce=[0BE4471BCE14DCC1] ACK,AUTO,EXPLORE From=0x07
Mon 03/14/2022 11:57:31 AM : [ZWAVE-RX ZW007_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x07
Mon 03/14/2022 11:57:31 AM : [ZWAVE-TX-NONCE  ] ...
Mon 03/14/2022 11:57:31 AM : [ZWAVE-RD        ] [010D001307068503010100012500B0]        REQ ZW_SEND_DATA 
Mon 03/14/2022 11:57:31 AM : [ZW-SHOW         ]    Associations for group 001 of ZW007_1 Front Door
Mon 03/14/2022 11:57:31 AM : [ZW-SHOW         ]    Max Associations = 1 
Mon 03/14/2022 11:57:31 AM : [ZW-SHOW         ]       - Node   1 - [This ISY] 
Mon 03/14/2022 11:57:31 AM : [ZW-SHOW         ] 
Mon 03/14/2022 11:57:31 AM : [ZW-SHOW         ] ----------------------------------------------

 

Edited March 14, 20223 yr by brians

Exclude can be done from from any zwave controller, does not have to be the same controller which included the device.

Thanks @brians

After googling "Exclude Yale smartlock" the important tidbit of information I was missing was proximity to hub from lock. To pair/unpair, they have to be one foot apart at most.

The lock took the commands without issue when I placed the hub next to it.

Interestingly, while repairing the lock, I received the same ZW-TX-FAILED at the dashboard. It paired successfully, but that message still appeared.

When doing manual sync to hub, it shows [ZW-TX-FAILED] enc=Ok uid=6.0 cmd=0x20.02 BASIC. So far the lock shows up at dashboard as usual.

I suppose I'll monitor for now and see if it does it again.

Thanks again for your help everyone.