Beantwoord

Where to find AppEUI

  • 18 februari 2017
  • 49 reacties
  • 2082 keer bekeken


Toon eerste bericht

49 reacties

Reputatie 1
Badge
Hi Jeroen. I use the dev portal
Reputatie 3
Badge +1
What kind of device do you use?. @IAS and I both use a RN2483.
Reputatie 1
Badge
I use the same. I am not sure if RN2483 supports otaa by default or something need to be coded in the logic? in any case i am using a sensor with rn2483
Reputatie 3
Badge +1
You got it connected via OTAA right? Can you share the code / settings you used to connect via OTAA?
Reputatie 1
Badge
App Key : 11111111111111111111111111111111
App EUI : the one provided by Tim
Dev EUI : My Lorawan DEV EUI
Reputatie 3
Badge +1
Of course you used your keys, but beside those keys did you do anything to get OTAA working?
Reputatie 1
Badge
no that s all I did

the app key i had to make manually but it had to be of a certain minimum lenght otherwise it doesnt get provisioned in the device
Reputatie 3
Badge +1
Ok thanks, I do exactly the same.
@Tim is it possible that the devices that got registered right after OTAA functionality was added to the Dev Portal use another (old) AppEUI? At this moment there is nothing else I can think of to fix this problem. Maybe you can look at the logging from the connectionserver and check what's wrong?
Reputatie 1
Badge
@Jeroen10 Today I tried using OTAA again and to my surprise it works (without me changing anything, just powering the LoRa device).

I notice that the user interface of the developer portal looks slightly different, @Tim can you confirm that the portal was updated somewhere in the last one or two days and/or that an issue with OTAA has been resolved?
Reputatie 7
Badge +11
I notice that the user interface of the developer portal looks slightly different, @Tim can you confirm that the portal was updated somewhere in the last one or two days and/or that an issue with OTAA has been resolved?
Well, that really seems to be an coincidence. I think they forgot to activate your device after the OTAA join request was processed. We've set your device manually to activated on friday 🙂
Reputatie 1
Badge
Thanks @Tim. In the mean time I added several OTAA nodes and they all activated within a few minutes from registering. So I'm happy with that.
Reputatie 7
Badge +11
Thanks @Tim. In the mean time I added several OTAA nodes and they all activated within a few minutes from registering. So I'm happy with that.
Great, good to hear it's working well 😃
@Tim
When wil de app eui be shown in the developer platform?
Could you send me the app eui. We want to run some tests.
Reputatie 3
Badge +1
@Robg66 you should use 0059AC0000010120 as AppEUI. This is now also described in the documentation on the developer portal.
Hello, i used 0059AC0000010120 as app_eui and app_key using the lopy. Device eui retreived from te LoPy (my device). OTAA does not seem to work, my device is not connecting, using ABP the device messages are showing up in the dev portal.

Any ID what could be going wrong?
Reputatie 7
Badge +11
Hello @DenDeze, something is definitely going wrong here. When I look at our OTAA join requests, the last registration on the Developer Portal was like a week ago. So the join requests haven't reached our end.

This can be due to old firmware on your device. Is there new firmware available? To be honest, this is the first LoPy I´ve seen, so I don´t have any experience with this device.
@Tim Just upgraded my firmware, still not working 😞
Reputatie 7
Badge +11
Hi @DenDeze, I've just used a keyword query on LoPy, and many of these devices have already been logged on to our network. Some of these have been registered by OTAA. I expect it to work for you too as well.

Maybe i've found the problem. The Dev EUI 0059AC0000010120 is already activated on an expired account and have been activated with OTAA before. This account isn't active for 1,5 months now. I think this is the reason. Did you take over this device from a former owner? Can you try again? I've removed the device now.
Hello @Tim, my device ID is different then the one you posted. The LoPy is brand new.

0059AC0000010120 is the APP_KEY, i found somewhere on the forum that we need to use the same code as APP_EUI for the OTAA activation (APP_EUI AND APP_KEY must be provided to the LoPy).
Reputatie 7
Badge +11
Hi @DenDeze Right, I may have read your post incorrectly. The AppKey can be made up and must be 16 bytes long, you don't need to use the same value as AppEUI for that. When I look at some random devices, it looks like you can put any value there. I've seen 1111111111111 but also 12345 or any other random value. Make sure you have enough signal to sent the join request, can you try again and let me know what error message you're got returned?
@Tim, the problem with the LoPy is that i does not return error's, it just keeps trying.

SF in ABP mode is 7, all my ABP send messages show up in the Developer Portal. OTAA still no luck...
Reputatie 7
Badge +11
Hi @DenDeze, it seems we still haven't got an OTAA join request from your device..
My suggestion is we let one of our specialist take a look, if you have any valuable information to provide us, please let me know. Can you sent me a private message with your contact details?
@TimHi Tim, kan je mij ook de APPEUI geven van de developer portal? Groet, Jeroen
Reputatie 7
Badge +11
Hi @JeroenD, de AppEUI voor de developer portal is 0059AC0000010120
Succes!

Reageer