Admittedly, this might be a stupid question, but here goes...

I am very new to Zwave, and am surprised by the MANY “sub” devices/nodes I get when I add a new device. In most cases, I don’t want or need most of these. For example, I often JUST want a simple open/close for a door sensor, but I get glass break, tamper, maybe another tamper, a “notify”, maybe a tilt, etc, etc. It takes up lots of space, makes things confusing, and for me is just a big PITA. So... what’s the best strategy for getting rid of all the unwanted “extras”? I would just delete them as I did with Insteon (without issue), but as I still don’t understand this “include/exclude” business and fear I’ll royally mess up my system, especially if I need to later remove the entire device. Any help appreciated, so thanks in advance.

You can create a folder in the Admin Console to put your unwanted nodes in. 

I create a couple folders

- Unused-Ready: Real nodes on the device that I'm not using now, but might some day. I have an iolinc in my garage that I'm only using the sensor on today. Someday, I may come up with an idea for the contacts. Also disabled devices that I've taken out of service in the spares box.

- Unused-BoneYard: Nodes that aren't usable or I will never use. Open / Close sensors come with and Open and a closed nodes.. I don't need or want both, etc.
 

31 minutes ago, dbuss said:

You can create a folder in the Admin Console to put your unwanted nodes in. 

 

1 hour ago, dbuss said:

You can create a folder in the Admin Console to put your unwanted nodes in. 

That's how I handle mine as well

For Insteon devices, I just group them, if they are not usable, and forget about it. 

Deleting them doesn't stop the data flow behind the scenes, and they can be hard to get back, if ever needed.

Edited October 5, 20196 yr by larryllix

Well, the folder approach has been my approach as well. Thanks for your replies. Now it’s off to seeing how I can actually view sensor data on my devices, which is proving to be a hug challenge.