Justin Thomas

Strangely, `lsusb` reports the Zooz sick under the Aeotec description: ~~~~~ idVendor 0x0658 Sigma Designs, Inc. idProduct 0x0200 Aeotec Z-Stick Gen5 (ZW090) - UZB ~~~~~

Exciting! 

I used the guide that @kpine posted and downloaded the files as directed there. It's included as specified there in the relative link in the downloaded file from https://www.silabs.com/development-tools/wireless/z-wave/embedded-development-kit. ~~~~~...

That ZEN32 node (85) was marked dead again during a heal process about an hour ago. [dead_node_85.log](https://github.com/zwave-js/node-zwave-js/files/7965019/dead_node_85.log) Definitely a lot going on right there. It looks like that might have...

Sounds good. I'll work on figuring out a way to do that. Maybe just letting the zniffer run for 8 hours at a time or something like that.

I assume I can export a capture file like tcpdump or Wireshark. I'll work on becoming more familiar with it. I wonder if anyone has worked on building a CLI...

It's been a little bit since I've seen a node die unexpectedly. I'm going to go ahead and close this and I'll reopen with trace data if it recurs.

Reopening to look at this log: [03T19.log](https://github.com/zwave-js/node-zwave-js/files/7998377/03T19.log) @AlCalzone this is the one I mentioned on the META ticket. There is indeed a little bit more context in that conversation that...

Ah, yes. I overlooked that. Here you go. [zwavejs_2022-02-03.log](https://github.com/zwave-js/node-zwave-js/files/8004666/zwavejs_2022-02-03.log)

That LZW31 (node 55) was in the wrong place in the zwavejs2mqtt list this morning and I noticed that it had a "-" in the "Zwave+" column. So I interviewed...