ZWaveNode::GetNonce node XX failed

Other Devices & Integrations Door Locks & Sensors
1

I’m getting a lot of the following errors, trying to communicate with a Yale lock. Typically after a period of inactivity of the lock:

01	01/24/12 13:20:22.401	ZWaveNode::GetNonce node 20 failed <0x2c49b680>
01	01/24/12 13:20:22.402	ZWaveNode::EncryptFrame m_iFrameID 14734 cannot get nonce node 20 command class 0x62 command 0x1 <0x2c49b680>

Sometimes the job (to unlock) gets executed up to 30 seconds later, sometimes it just fails:

01	01/24/12 13:23:43.461	ZWJob_SendData::JobFailed job#2756 :Unlock node 20 (0x9407e8) N:20 P:70 S:5 Priority 70 <0x2c09b680>
04	01/24/12 13:23:43.462	<Job ID="2756" Name="Unlock node 20" Device="23" Created="2012-01-24 13:20:19" Started="2012-01-24 13:20:22" Completed="2012-01-24 13:23:43" Duration="204.316705000" Runtime="201.57250000" Status="Aborted" LastNote="Transmit failed with code: 1" Node="20" NodeType="ZWaveDoorlock" NodeDescription="Door Lock"/> <0x2c09b680>

Looks like an issue with the encryption mechanism. Any thoughts?

(V3 1.5.254)

2

You could install my [tt]LSI[/tt] (Luup System Information) plugin and check the ‘Z-Wave Capabilities’ tab for Z-Wave devices that support beaming.

3

Thanks… I’m missing a couple of steps in your reasoning though. Why would knowing which devices support beaming help?

4

If your Yale lock is a FLiRS, moving beam capable Z-Wave devices closer to your lock might improve the reliability of the communication with your lock ([tt]http://wiki.micasaverde.com/index.php/Schlage_Lock#Secure_Z-Wave_Devices_Explained[/tt]).

5

You think it’s a common-or-garden comms problem, and the encryption angle is a red herring?

The lock is within 15 feet of the nearest z-wave mains unit and within 25 feet of three others. I’ll see which if any support beaming.

6

[quote=“autotoronto, post:5, topic:170298”]You think it’s a common-or-garden comms problem, and the encryption angle is a red herring?

The lock is within 15 feet of the nearest z-wave mains unit and within 25 feet of three others. I’ll see which if any support beaming.[/quote]

Have you ever figured out what the problem was?
Im getting the same problem on one of my Kwikset logs.

Flo

7

I haven’t pursued it. I haven’t installed the lock in the door yet, it’s still sitting on my desk.

8

As mentioned yesterday mine did exact the same… for about 3 hours… then it magically healed itself… no idea why. Wish I would understand the log - especially the encryption messages better…