You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configure with environment variables, or command-line arguments.
246
+
247
+
See `ttn-lw-migrate firefly {device|application} --help` for more details.
248
+
249
+
The following example shows how to set options via environment variables.
250
+
251
+
```bash
252
+
$ export FIREFLY_HOST=example.com # Host of the Firefly API
253
+
$ export FIREFLY_API_KEY=abcdefgh # Firefly API Key
254
+
$ export APP_ID=my-test-app # Application ID for the exported devices
255
+
$ export JOIN_EUI=1111111111111111 # JoinEUI for the exported devices
256
+
$ export FREQUENCY_PLAN_ID=EU_863_870 # Frequency Plan ID for the exported devices
257
+
$ export MAC_VERSION=1.0.2b # LoRaWAN MAC version for the exported devices
258
+
```
259
+
260
+
### Notes
261
+
262
+
- The export process will halt if any error occurs.
263
+
- Use the `--invalidate-keys` option to invalidate the root and/or session keys of the devices on the Firefly server. This is necessary to prevent both networks from communicating with the same device. The last byte of the keys will be incremented by 0x01. This enables an easy rollback if necessary. Setting this flag to false (default) would result in a "dry run", where the devices are exported but they will still be able to communicate with the Firefly server.
264
+
265
+
### Export Devices
266
+
267
+
To export a single device using its Device EUI (e.g. `1111111111111112`):
The Firefly LNS does not strictly enforce device to application relationships.
296
+
297
+
Setting the `--all` flag will export **all devices that are accessible by the API key**. The `application` command without the `--all` flag does nothing.
298
+
299
+
> Note: Please be cautious while using this command as this might invalidate all the keys of all the devices.
0 commit comments