When and how would you use the SmartStart list where things got screwed up so bad that you had to?
I am using @jtp10181 's app and saving the backup .json file, both on hub and offline.
The SmartStart list saves the dsk's and associates them with SS names, nodes, and device names.
However, my SmartStart list has many blanks for Device Name and Node, see small sample below, even though the devices work just fine and are joined as LR.
This could point out a reason to keep the SS Name and Device Name synched, a manual process. I've neglected that a couple of times lately when re-assigning a device's duties. Perhaps I should make sure they're synched (again, a manual process)?
(side note: I have cloud backup-would that obviate the need for resorting to using the SmartStart list, from a radio info backup perspective? As in, the hub self destructs somehow and a replacement hub is required, with the devices still included to a non-existant hub.)
The linked device name is banking on the fact that the hub links the SS entry to a node ID so I can pull it and match it up. Usually if you pair with SS, it will keep that link and remember it.
If paired manually and added to SS later it wont know what node it is.
I seem to be the exception then, lol. See below.
If the node is mandatory for the backup to be useful, then....
I'm just trying to figure out how the list could be used in a restoration scenario, where the hub is trashed.
I suppose all devices would have to be factory reset before SS can work its pairing magic, one device at a time. Ugh. At least you'd save the OCR scan step. But still, ugh.
As a side note, if indeed a hub got trashed, could a cloud backup be used to restore to a new hub without doing the device factory reset dance?
