Hi team.
I just got some PT100 Lansitec devices which I’m trying to connect to TTN.
For dragino devices I usually copy to the TTN the DEVeui and I add the APPeui and APPkey from the TTN to the dragino device and I get an instant connection (this by AT commands).
But for Lansitec I can’t do that since I can’t have a physical access to the device, so what I did it was to type the Deveui and APPkey given by Lansitce but I didnt have any successfull result.
May I’d be forgetting someting?
Hey, I’d like to help you, but I’m not Lansitec support 
What data did Lansitec provide you with?
On the TTN side, you need DevEUI, AppEUI and AppKey. This assumes that the device uses OTAA.
AppEUI is normally generated by TTN (70 B3 D5 …), but you can actually add another one in the console. Then when configuring the specific device, you can set the DevEUI, select the alternate AppEUI (instead of the TTN-generated AppEUI) and also set your own AppKey.
Do you have (access to) a gateway to see what the device is sending?
If so, can you post the join attempt here?
Hi Bertrik, thanks for answering.
Actually Lansitec provided the DEVeui and APPkey, or at least that’s what I think that they sent me because of the lenght of the bytes here is one row from what they sent, in any case none of the columns specifies any name:
PT100 ||100-00191 || A || 70b3d5a4d6150002 || 2C26C50211000003 || fea5a6043d629292bcbfdec7b6ee3ad1
Also yeah I have access to my gateways, but I didnt know I was able to watch the data they are receipting from devices, I’m gonna take a look to it
My guess would be:
AppEUI = 70b3d5a4d6150002
DevEUI = 2C26C50211000003
AppKey = fea5a6043d629292bcbfdec7b6ee3ad1
Well, actually we both almost agree with the information, I just have the DevEUI identified because is printed in the device, so we would have:
DevEUI = 70b3d5a4d6150002
AppEUI = 2C26C50211000003
AppKey = fea5a6043d629292bcbfdec7b6ee3ad1
Which is already recorded in TTN except by the AppEUI which I can’t change into the device settings option for TTN also I can’t define my own AppEUI when creating a new TTN Application, that’s the reason I use to update the device’s default AppEUI for the one given by TTN
You can add an AppEUI, under the settings of the APP, for example
Then under device settings, you can select the AppEUI for your device:
I doubt that 70b3d5a4d6150002 is the DevEUI, the prefix of TTN application EUIs is typically 70B3D5. So I think you may have your DevEUI and AppEUI swapped.
Yeah, nice trick, I didnt know about it, thanks very much.
About the appEUI and devEUI I agree with you, but the problem is that Lansitec sent me this bytes “2C26C50211000003” for all the devices, the only one which is changing is the “70b3d5a4d6150002” bytes which increas 1 by 1 on each of the devices
This is the whole list
Updated For security I just deleted the uploaded image
Odd… I can only guess what their intention is, good luck!
That EUI is in their registered range. At the IEEE registry site you can search for their MA-S. Multiple organizations will have a range starting with 70 B3 D5. The range starting with those 3 groups includes The Things Network Foundation as well.
The EUI that is the same for all devices is probably the AppEUI, but the gateway console at TTN should tell you when a devices attempts to join. (Look at gateway traffic)
Its oke, thanks very much, anyway I’ve learned some new things I didnt know about this platform and my gateway
Thanks for the information given, I’ve checked on my ttn log for my gateways and I can see my other devices sending data, but I dont see anything from my Lansitec device even if I turn it off it won’t appear in my traffic record.