Beantwoord

Where to find AppEUI

  • 18 February 2017
  • 49 reacties
  • 2571 keer bekeken
Toon eerste bericht

49 reacties

Amine Mouadden MBA
Reputatie 1
Badge
Hi Jeroen. I use the dev portal
Amine Mouadden MBA
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
Amine Mouadden MBA
Reputatie 1
Badge
App Key : 11111111111111111111111111111111
App EUI : the one provided by Tim
Dev EUI : My Lorawan DEV EUI
B
Reputatie 3
Badge
@tim. Maybee you can help me where i can find this key.
markruys
Hi Tim,

We need to test OTAA on the dev portal too. Please provide us with the AppEUI too.

Cheers,

Mark
Jeroen10
Reputatie 3
Badge +1
I've got the same question as @IAS. Since OTAA only recently added to the Developer Portal there is no documentation / Tutorial / information available yet.
Jeroen10
Reputatie 3
Badge +1
@Tim to setup a connection via OTAA with the RN2483 you have to give the AppKey, AppEUI and DevEUI as parameters. I want to know If I can get up and running with OTAA because that is the way to go if we want to go to the real LoRa platform, and if there are any differences in the communication, and test encryption options.
Jeroen10
Reputatie 3
Badge +1
@Tim I already tried with a random AppEUI. I get the following output:

Port open
[initOTA]
[init]
[sleep]
[wakeUp]
[resetDevice]
[expectString] expecting RN.(RN2483 0.9.5 Mar 24 2015 14:15:33) found a match!
The device type is RN2483
[setPowerIndex]
[setMacParam] pwridx = 1
[expectString] expecting ok.(ok) found a match!
[setSpreadingFactor]
[setMacParam] dr = 5
[expectString] expecting ok.(ok) found a match!
[setMacParam] deveui = [array][expectString] expecting ok.(ok) found a match!
[setMacParam] appeui = [array][expectString] expecting ok.(ok) found a match!
[setMacParam] appkey = [array][expectString] expecting ok.(ok) found a match!
[setMacParam] adr = on
[expectString] expecting ok.(ok) found a match!
[joinNetwork]
[expectString] expecting ok.(ok) found a match!
[expectString] expecting accepted.......(denied)Error loading network settings!
Jeroen10
Reputatie 3
Badge +1
@Tim any updates? Or can you send @IAS and me the hidden AppEUI and then look for a common solution?
Jeroen10
Reputatie 3
Badge +1
I still can't join the network via OTAA.

[joinNetwork]
[expectString] expecting ok.(ok) found a match!
[expectString] expecting accepted.......(denied)Error loading network settings!

Is the AppEUI for all OTAA devices the same?
@IAS can you connect with the given AppEUI?
Jeroen10
Reputatie 3
Badge +1
Yes, still the same error. @Tim can you check the AppEUI one more time? I already triple checked the AppKey and DevEUI.
Jeroen10
Reputatie 3
Badge +1
@Tim I also still got the same problem as @IAS (denied). Is it possible the AppEUI only works with newly registered devices after you sent us the AppEUI? Is there something else we can try?
@Amine Mouadden MBA do you use the Developer Portal or the Thingpark network?
Jeroen10
Reputatie 3
Badge +1
What kind of device do you use?. @IAS and I both use a RN2483.
Jeroen10
Reputatie 3
Badge +1
You got it connected via OTAA right? Can you share the code / settings you used to connect via OTAA?
Jeroen10
Reputatie 3
Badge +1
Of course you used your keys, but beside those keys did you do anything to get OTAA working?
Jeroen10
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?
I
Reputatie 1
Badge
I'm looking for AppEUI's for testing AND for production because a number of devices are ready for permanent deployment if OTAA testing is successful (and my other problem with SSL is resolved).
I
Reputatie 1
Badge
@Tim Which "OTAA value" do you mean?

I've added a random AppEui to one of my nodes and it doesn't connect or show up in the debugging. When I use SF7 ABP firmware on the same node then I see the messages coming in, so OTAA not working is not a range problem.

Microchip RN2483:
mac set deveui 0004A30B0019691C
mac set appeui 0662E9027DDA707A
mac set appkey 0662E9027DDA707A86F917FCFCF8E411
mac set adr on
mac join otaa
denied

DevEUI & AppKey are copied from the 'devices' page on the portal.
I
Reputatie 1
Badge
Sorry for the late response, been away for some time. I tested OTAA just now and no success:
sys reset
RN2483 1.0.1 Dec 15 2015 09:38:09
mac set pwridx 1
ok
mac set dr 5
ok
mac set deveui 0004A30B0019691C
ok
mac set appeui xxxxxxxxxxxxx120
ok
mac set appkey 0662E9027DDA707A86F917FCFCF8E411
ok
mac set adr on
ok
mac join otaa
denied

DevEUI & AppKey correspond to the device settings. The AppEUI is as provided by @Tim

Any ideas?
D
@Tim, any updates on making the APP_EUI available? I was trying out the KPN developer portal, but the lack of a APP_EUI is currently stopping me from evaluating the KPN LoRa network, so I'd be much interested in any update on the APP_EUI so I could run some evaluations. 🙂
D
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?
D
@Tim Just upgraded my firmware, still not working 😞
D
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).
D
@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...

Reageer


Forumvoorwaarden