CLI Relay commands required for managing an installation

[HeadBoffin]

Summary

Querying an application to find relays and served devices needs multiple calls. Finding out which index/slots are in use requires a 16 calls, one for each index. This is relatively a minor inconvenience but does result in a lot of unnecessary interaction. With an application with many devices this could take a while to find the relays.

Current Situation

There is no relays list <application-id>.

This would supply a list of relays to:

relays devices list <device-id-of-relay>

which ideally returns the forwarding-rules index that it occupies. I've got to relays uplink-forwarding-rules list <app-id> <relay-id> --device-id but we don't get the indexes back.

Why do we need this? Who uses it, and when?

This will facilitate an efficient retrieve of the current configuration and save issues managing served devices with tracking indexes.

The users are likely to be field engineers who have to deploy or add to an installation or replace devices or relays.

Proposed Implementation

As per current situation - some additional command options to get the data back.

I'm working on a GUI interface that works but has to do the queries described above. Once it & the hardware get out in to the wild there may be some further enhancements identified.

As there is a work-around there is no urgent requirement.

Contributing

• I can help by doing more research.
• I can help by implementing the feature after the proposal above is approved.
• I can help by testing the feature before it's released.

Validation

• The feature is tested in a staging environment.
• The feature is documented in The Things Stack Documentation

Code of Conduct

• I agree to follow TTN's Community Code of Conduct.

[KrishnaIyer]

Thanks for the issue. We'll get back to this in a future milestone.