Constant Z-Wave Errors

[Wadenut]

Since moving to the SmartStick+ a few months ago, I've seen incessant Z-Wave Errors. Restarting the interface or restarting HS generally clears them up for a while, maybe a day, before they reappear.
PI version is currently: 3.0.1.261

I'd never had such problems using the Z-Troller, ever!
Now, maybe I've jumped the gun here, but I've just finished ordering a Z-Net in hopes of improvement. At least I'll be able to place it more centrally.

An example of the errors:
Z-Wave Error - Failed sending Z-Wave command to device xxx (This occurs most often on random devices. Even those closest to the Smartstick and which have a direct path to the interface.

Z-Wave Warning SmartStick - Secure message received from node 73. It was successfully decrypted but the data sequence ID is out of sequence. (Not Processed)
(Again on random devices, several times per day until a manual restart.)

And then, today for the first time,
Z-Wave Error - In converting Z-Wave data bytes to a value, Size is reported as 6, but length is 5 and is=00-00-B6-00-22
z-Wave Error - In converting Z-Wave data bytes to a value, Size is reported as 6, but length is 5 and is=00-00-AB-00-3F
etc, etc. Repeated 14 times in succession, different data each time..

IDEAS?

[simplextech]

May want to bump to the 262 version of the z-wave plugin to see if that helps any.

[Wadenut]

I'll see if I can locate that.
Meantime, I've been watching the /ZWaveConfig Page. Just before I restarted HS3 a half hour ago, there were more than 60 threads listed, most inactive. After the restart, 27 and now up to 34 with no errors as yet at 35 minutes uptime. Wondering if there's something there.

[Wadenut]

And, no 262 to be found. Pulled?

[simplextech]

And, no 262 to be found. Pulled?

It's in the updater in the beta section.

[Wadenut]

Naturally. The one place I didn't think to look.
Thx. (BTW, up over 40 threads at 1 hour)

[simplextech]

I don't think the threads or an issue or an item to be concerned with. I just checked my system and it's over 40 threads close to 50 back and forth as threads launch and complete and such.

The send/receive Queues are more important to see if things are getting blocked.

[sparkman]

Typically I have seen those types of errors/warnings in z-wave systems with a lot of traffic. Not sure why restarting would fix it for a while though. Could it be queued polls that clog traffic if they happen in quick succession? Resetting would clear the queues. FWIW, I have 38 threads after restarting the plugin almost 4 days ago with 122 nodes with about 1/3 battery powered devices and using a z-net.

[Wadenut]

The threads were just something I'd noticed.

I do try to keep polling to a minimum, and only poll devices which have the possibility of being turned on/off locally, then polled usually at no more than 15 minute intervals. Light switches are all Instant Status and require no polling.
As for queued messages, there were none indicated. This of course doesn't mean that at the moment the errors occur, there wouldn't be. We'll see.
I have only 59 nodes here with 9 of them being battery, including three Schlage locks, three Z-Combos, two motion sensors and one door/window sensor (still rely on X10RF for these functions). None of the battery devices have ever shown the errors I'd mentioned.
Also, in scripts, I don't send needless commands either. Generally test for device status before a command is sent. My Z-Wave traffic should actually be quite minimal.

I'll let things go overnight and see what the morning brings.

Snapshot (on 262 now):
Uptime: 1 Hour, 20 Minutes, 32 Seconds

Network xxxxxxxx xxxxxxxx	Node ID: 1 # Nodes: 59	CMD Q: 0	Poll Q: 0	WakeUp Q: 0	TX Q: (empty)			Frames In: Total=939, MGD=1	Report Buff: 11
Thread Info: Id: 7532, Time: 00:00:00.1716011, State: Wait, Name: - Id: 4232, Time: 00:00:00, State: Wait, Name: - Id: 7764, Time: 00:00:00.0312002, State: Wait, Name: - Id: 8112, Time: 00:00:00, State: Wait, Name: - Id: 6976, Time: 00:00:00, State: Wait, Name: - Id: 3472, Time: 00:00:24.8353592, State: Running, Name: - Id: 2516, Time: 00:00:00.0156001, State: Wait, Name: - Id: 2688, Time: 00:00:00.6552042, State: Wait, Name: - Id: 796, Time: 00:00:00, State: Wait, Name: - Id: 968, Time: 00:00:00, State: Wait, Name: - Id: 3268, Time: 00:00:00.0624004, State: Wait, Name: - Id: 4100, Time: 00:00:01.0764069, State: Wait, Name: (ZWaveSaveItem)_20-Aug-2019 15:53:15.84403192 Id: 4084, Time: 00:00:00, State: Wait, Name: - Id: 1092, Time: 00:00:00, State: Wait, Name: - Id: 872, Time: 00:00:00.1560010, State: Wait, Name: - Id: 6488, Time: 00:00:00.1248008, State: Wait, Name: - Id: 7116, Time: 00:00:00.9672062, State: Wait, Name: ZWave_Receive_Thread_SmartStick Id: 4176, Time: 00:00:00.2184014, State: Wait, Name: (System)_Z-Wave Commands_SmartStick_20-Aug-2019 15:53:17.57501599 Id: 3160, Time: 00:00:00.1560010, State: Wait, Name: - Id: 5492, Time: 00:00:00.0468003, State: Wait, Name: (System)_20-Aug-2019 15:53:17.63105502_Z-Wave_API_Commands_SmartStick Id: 7268, Time: 00:00:00.0156001, State: Wait, Name: ZWave_Frame_Thread_SmartStick Id: 3960, Time: 00:00:00.0468003, State: Wait, Name: - Id: 7944, Time: 00:00:00.2808018, State: Wait, Name: (System)_20-Aug-2019 15:53:47.72208952_Z-Wave Polling Id: 1088, Time: 00:00:00.0468003, State: Wait, Name: ApplicationCommandHandler_SmartStick_20-Aug-2019 15:55:36.70388508 Id: 6744, Time: 00:00:00.1716011, State: Wait, Name: NodeChangeEvent Thread Id: 5384, Time: 00:00:00.0156001, State: Wait, Name: (System)_20-Aug-2019 15:58:22.60385086_WakeUp_Processing Id: 6204, Time: 00:00:00.0312002, State: Wait, Name: - Id: 7056, Time: 00:00:00.0156001, State: Wait, Name: - Id: 5436, Time: 00:00:00.0468003, State: Wait, Name: - Id: 5044, Time: 00:00:00.0468003, State: Wait, Name: - Id: 3924, Time: 00:00:00.0936006, State: Wait, Name: - Id: 2408, Time: 00:00:00.0156001, State: Wait, Name: - Id: 6248, Time: 00:00:00.0624004, State: Wait, Name: - Id: 1864, Time: 00:00:00.0156001, State: Wait, Name: - Id: 8012, Time: 00:00:00.0468003, State: Wait, Name: - Id: 7952, Time: 00:00:00.0468003, State: Wait, Name: - Id: 2056, Time: 00:00:00.0624004, State: Wait, Name: - Id: 7840, Time: 00:00:00.1092007, State: Wait, Name: - Id: 7564, Time: 00:00:00, State: Wait, Name: - Id: 1888, Time: 00:00:00.0624004, State: Wait, Name: - Id: 6832, Time: 00:00:00.0312002, State: Wait, Name: - Id: 4832, Time: 00:00:00.0156001, State: Wait, Name: - Id: 5320, Time: 00:00:00, State: Wait, Name: - Id: 3944, Time: 00:00:00, State: Wait, Name: - Id: 840, Time: 00:00:00.0156001, State: Wait, Name: - Id: 4260, Time: 00:00:00.0312002, State: Wait, Name: - Id: 6120, Time: 00:00:00, State: Wait, Name: - Id: 212, Time: 00:00:00.0156001, State: Wait, Name: - Id: 3704, Time: 00:00:00.0156001, State: Wait, Name: - Id: 7256, Time: 00:00:00, State: Wait, Name: - Id: 4724, Time: 00:00:00, State: Wait, Name: - Id: 6344, Time: 00:00:00, State: Wait, Name: - Id: 6304, Time: 00:00:00, State: Wait, Name: - Id: 2380, Time: 00:00:00, State: Wait, Name: - Id: 1524, Time: 00:00:00, State: Wait, Name: -

Home |

[Wadenut]

hmmmm. So far so good on the errors overnight on 262. Had one "Z-Wave Warning SmartStick - Secure message received from node 73". Node 73 is a Schlage lock. I noticed this morning that it was set to poll the child devices at 12 hour intervals (mainly for battery tracking). I don't believe this is necessary with these locks and have turned its polling off. It's just possible too that when I included that lock, I'd done so securely (no way to determine now I think), so if this does continue perhaps I'll bring it inside and re-include it. My other two locks were polling as well (now turned off) but have never shown this particular error.

Thinking now I might have saved myself $230 (CDN) on the Z-Net had I held off a while on that order. No matter; it's always good to have a backup plan.

[simplextech]

At some point the SmartStick+ will fail so then you can use the Z-Net. It may be several years... but hey bright side right?

I'm actually thinking of replacing my SmartStick+ with another Z-Net just to separate the stick from the server to provide more location/placement freedom.

[Wadenut]

At some point the SmartStick+ will fail so then you can use the Z-Net. It may be several years... but hey bright side right?

That's my reasoning. Everything fails eventually. The stick is only three months old so there's time yet.
On the other hand, the Z-Troller never missed a beat in nearly fifteen years, and its display was somehow reassuring, but it can't handle the newer S2 devices so it had to be replaced.
Perhaps re-purpose the stick on the Pi.

[Wadenut]

Now I'm wondering (it's the hacker subroutine in my head always running in the background):

Pi + Z-Net Image + HS Smartstick+ = Spare Z-Net?

Also, any point hoping to add a small LCD screen (perhaps touchscreen) to the Z-Net for watching activity ? Seems to me to be a reasonable upgrade.

[langenet]

When I switched to HS3 from HS2, I had queue issues with the Z-troller which just frustrated me. So I went for the Z-Net and have never looked back. I'm beginning to worry about failure as well - especially power cycling it since it's UNIX based OS and the potential for the SD card to corrupt/fail. I will likely get a replacement SD card - though, I'm not sure which brand is good and the capacity required. I've also been thinking on getting another Z-Net just to keep in the box for that day when all hell breaks loose...
WAF factor is a high determining factor in keeping the CFO happy.

[jvm]

I would have assumed we'd see z-wave controllers based on the 700 series Z-wave chip sets by now as those chips were announced at the end of 2018 -- has anybody seen anything on that front?