Extended NIF in a mdns TXT record



As explained in the documentation, Extended NIF frames are presented for each discovered device through the TXT field on a resource query.

I am successfully able to resolve all the data I need, but I find the documentation insufficient when it comes to the format of the extNIF.

  1. Can someone point me to the correct document describing the NIF in detail, including how to find data on extra bytes provided by extended command classes? I can only find mentionings of this without a proper technical description. If a command is extended like the commands pointed to in the example in document SDS11633-3 page 9, 1st paragraph - where is this information to be obtained so that I can correctly parse the NODEINFO?

  2. The XML database used for dynamic command parsing does not contain information on the format of the NIF bytes related to a extended command (as far as I can tell). The provided example code does not use the NODEINFO in any way, or parse it for that matter. So there is actually nothing explaining how to do this.




My experience is that it is better to get the node information directly from the ZIP Gateway than using the mDNS resource announcement. You can get the node information from the ZIP Gateway using the “Network Management Proxy CC”. See section 4.4.5 in this document: http://zwavepublic.com/sites/default/files/command_class_specs_2017A/SDS13784-4%20Z-Wave%20Network-Protocol%20Command%20Class%20Specification.pdf.

The Name and Location can be accessed through the Cmd’s in section 4.24 of this document: http://zwavepublic.com/sites/default/files/command_class_specs_2017A/SDS13782-4%20Z-Wave%20Management%20Command%20Class%20Specification.pdf

Finally to get the Meter types and Sensor types supported by a device, you will need to request the information directly from the devices. You can do this with the Z/IP CC described in section 4.8 in this document: http://zwavepublic.com/sites/default/files/command_class_specs_2017A/SDS13784-4%20Z-Wave%20Network-Protocol%20Command%20Class%20Specification.pdf

I hope this helps,