Bulk registering Pi: How to differentiate the Pis?

[Jawa_weaved]

I installed and registered one of my Pi3. I named it Box1 in remote3. Everything works fine.

Now, I have six Pi3's (Box1 through Box6) Each one of them has the same image in the SD card as Box1.
Also, each device has a file in it MYNAME.txt which is its name , i.e. "Box1", "Box2" etc.
If I wanted to now bulk register these devices how should my entries look like ?
I don't want to boot each one and get its " interface MAC address or serial number stored in ROM" in order to created the csv file. Because these devices are shipped directly to my remote locations, but the sd card does go through my hands, so I can customize the card.
I have repordocued the help from Bulk registration below
Column A contains the REGISTRATION_KEY : what would I put for each of the Boxes.? The example says
The REGISTRATIONKEY value cannot be left blank and must be a value that the device can access on its own when booting in the field (such as an interface MAC address or serial number stored in ROM). The REGISTRATION_KEY does not need to be unique across devices or accounts. For example, the same REGISTRATION_KEY could be used to Bulk Register any number of devices._
Since it says it NEED not be UNIQUE, but something it accesses on its own during boot, can I have this be the value in MYNAME as above ?
Column B: similar question: Column B contains the HARDWARE_ID field for the device being registered. In this example we are using a dummy Wi-Fi MAC address (AA:98:76:54:32:10) from the device wlan0 interface with the colons removed.
Any ideas on how this can be achieved ?
Thanks a lot

[Funkanzan]

My suggestion is that you use the interactive installer, i.e. "sudo weavedinstaller" with a Pi at your location on each of the SD cards. Give each device a unique name and unique names for all services. Then you can ship these pre-registered SD cards off to your installation locations.

That's going to be easier than trying to get the bulk registration for your case.

[Jawa_weaved]

Thanks. A followup question is can the weavedinstaller be run from a script with input from a file ?
that way it can be run once at each installed location.

[Funkanzan]

Take a look also at /usr/bin/remot3it_register, which is a table driven installer. Scroll all the way to the bottom to edit the table showing which services you want installed. Then you can run:

sudo remot3it_register username password

and it should chunk through and install everything automatically. The device and service names in this case will be derived from the eth0 MAC with some other info appended on the end.

If you can handle some bash programming, you could also get the SERVICEBASENAME from the command line rather than the eth0 MAC.

[Jawa_weaved]

Thanks for your response. Luckily can handle bash reasonably.
I researched this:

/usr/bin/remote3_it--> calles routines in weavedlibrary.

It calls : makeConnection Protocol=$1(set to ssh), $2-->PORT(set to 22), $3-->$alias set to ("macaddress+random")

makeConnection then calls-->

 registerDevice which prompts user for "alias" (easy to use name)

 getSecret--> curl( regdevice url with deviceaddress=$uid, devicealias=$alias & hardwareid=$serialid)

Hence, the 'alias' should be passed somehow to remte3_it & to makeConnection so that in non-interactive mode it will use that without prompting for user. So I would be able to pass the "Box5" etc to it and then it will register device under that name.
Am I making sense.
Thanks !

[Jawa_weaved]

I meant "remot3it_register" above

[Funkanzan]

Look at the makeConnection() function which is called from remot3it_register. I believe this is a more convenient way of doing what you want.