"Device ID Already In Use" Error

• Related Articles

• Where can I find the default Device EUI, App EUI and App Key for LoRaWAN sensors?

  Device EUI This is the ID on the label located on the sensor itself.  The barcode provided can also be used to read the Device EUI. Application EUI  By default this is set to: 0101010101010101.  This can be customized in the factory for production ...

• What happens if you try to add a device using the DE command and a device trips that is already learned? Does it take up another slot in memory?

  No it will not take another slot. When an endpont is added, whether through the DE (discover endpoint) command or manually using the AE (add endpoint) command, if the endpoint already exists it will not be duplicated.

• I want to set up the encryption in the field by broadcasting session key, can you give steps/commands which I can use to analyze this feature?

  In order to broadcast the session key in the field, a provisioning key must be set in advance. The provisioning key encrypts the session key and ensures that no unencrypted key is ever broadcast. At the factory or at some point prior to field ...

• The manual mentions that in sniffer mode, the device ID is reported “of the associated endpoint” (6.4.2.3). Does that mean it cannot sniff message from other coordinators?

  Yes, it will sniff out any packets whether it comes from a coordinator or endpoint. The sniffer is a special diagnostic mode and thus is not operating as either a coordinator or endpoint itself.

• How would a radio transmit underflow (error 001C) happen? I’m not getting this error, but I was just wondering what it would mean that I’m doing wrong if I were to see it.

  That would simply indicate an internal error, there is no known way to create this error as a user.