Disable Indigo communication for unused child devices?

Hi,

Is it "safe" to disable Indigo com for child devices that I dont use? My plan is to minimize z-wave traffic.
I have about 80+ child devices in my "N/A" folder, example in attached image. Allot of temperature, tamper and inputs I dont use.
One thing I have notised is that Indigo thinks my FGD212 switch 2 (input 2) is a dimmer?!? For all of my FGD212's.

Best regards, L

[jay (support)]

It won't hurt, but it likely won't help either. Disabling communication from Indigo only disables Indigo from initiating communication. If the device is a sensor of some kind, it will continue to broadcast it's status to Indigo so it won't really help with Z-Wave traffic reduction. There is no way to tell Z-Wave devices to stop broadcasting information for one of it's endpoints.

OK, thanks!

PS,

If I disable com on say a temperature device in a Qubino device that is not used and the device sends a report anyway to the controller. Is the controller receiving it and sends an ack in return or is the node going to retry to send the message until it gives up? That would result in even more traffic I guess :/

If the controller receives the traffic anyway and sends ack but Indigo don't react on it (or does it?) I can not see this traffic in the z-wave debug log and I might be misled to think there is less chatter on the network than it is. That would not help me in my quest for an optimized network

[matt (support)]

Disabling Indigo communication just makes Indigo ignore any incoming commands and not send commands to the module. The Z-Wave controller will always ACK messages from the module regardless, and Indigo will still log the messages when debug logging is ON.

Thanks! Then I will disable com on child devices I don't need.