Associate nodes with serials

[dfein38347g]

Is there any way to associate nodes with serial numbers or friendly names? It is great to have this data but it is not as useful if I detect a panel's production decreasing with no knowledge of which panel it is. Perhaps there is a way to see node serial numbers?

[willglynn]

By serial number, do you mean the barcode? The barcode would be recoverable from the identifier on the wire; details, implementation.

As far as I know, friendly names ("A1") exist only in a configuration files on the CCA or in Tigo's web interfaces. We could make taptap understand a node list. What would be the most convenient input format? Alternately, if you had a way to provide this information to taptap, where would you get it, and how does the information look there?

[dfein38347g]

By serial number, do you mean the barcode? The barcode would be recoverable from the identifier on the wire; details, implementation.

As far as I know, friendly names ("A1") exist only in a configuration files on the CCA or in Tigo's web interfaces. We could make taptap understand a node list. What would be the most convenient input format? Alternately, if you had a way to provide this information to taptap, where would you get it, and how does the information look there?

Ah ok, yes the barcode. I don't need the friendly names in taptap if we have the barcode data. I don't see that output when running the observe command. Can we add the barcode data to the observe command?

[willglynn]

Node addresses (and thus barcodes) are communicated infrequently, about once a day. If you're not seeing "address": in the output, it's because taptap hasn't seen the controller request a node table, so it doesn't know the node addresses.