Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    Change LoPy devEUI and LoRaWAN

    Scheduled Pinned Locked Moved LoPy
    lopylorawanotaa
    3 Posts 2 Posters 414 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B Offline
      bnjroos
      last edited by bnjroos

      Hi,

      I know it is possible to change the LoPy devEUI by using:

      fo = open("/flash/sys/lpwan.mac", "wb")
      mac_write=bytes([0x01,0xb1,0xd1,0x41,0x91,0x31,0xb1,0xb4])
      fo.write(mac_write)
      fo.close()
      

      I have been unable to find my answer on the internet, so I am gonna ask here, I hope it is in the right place:

      • Is it authorized by the LoRaWAN specification to change a devEUI on an end node?
      • Are there any restrictions or is it ok as long as we ensure that it remains unique ?

      For example, in case a LoPy device is faulty and we want to field replace it with a spare one without having to register it again in the back-end.

      Thank you,

      E 1 Reply Last reply Reply Quote 0
      • E Offline
        Eric73 @bnjroos
        last edited by

        @bnjroos It's not so simple and it depend on your lorawan network provider strategy about DevNonce (and it's lorawan specification version applyed to it's base station)
        PLease have a look at
        https://github.com/brocaar/loraserver/issues/116
        for more explication.
        When a device do a join request to network, it's send a number called DevNonce (random in lorawan 1.0.x) to the network, some network store this number and a device is not allowed to re-use this number before some time/retry count (1 year ? 1 month?).
        On lorawan 1.1 this number as to be incremental and stored in persitente memory inside the device.
        So it depend to your lorawan network provider if this change can be working or not.

        B 1 Reply Last reply Reply Quote 1
        • B Offline
          bnjroos @Eric73
          last edited by bnjroos

          @eric73 Thank you for your answer, I think it replies my question: It is possible however it depends on the network server allowed behavior.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post

          Pycom on Twitter

          Pycom