I’m running a gateway and was able to successfully register it with TTN. At least that’s something.
I bought two SenseCAP T1000-E for LoRaWAN tracker and don’t know how to register them. The TTN form asks for the JoinEUI, DevEUI, and Appkey. On the SenseCAP T1000-E, I have the serial number, key, EUI, FCC, and MAC address. However, the SenseCAP T1000-E isn’t listed. Ultimately, it’s just a standardized radio protocol, so shouldn’t all devices send comparable information?
Has anyone already connected these small trackers?
The protocol is standard, but the format of the payload is up to manufacturer. Not being in the list of devices isn’t an issue, it’s a convenience that can configure some other non-critical functionality, like the payload decoder so you can see the values in the console.
But that’s not relevant. What you need is the JoinEUI and AppKey for the device which should be on the documentation that it came with. That bit is part of the standard. The DevEUI & AppKey is / should be unique to each device, so it won’t be something a stranger can come up with. The device docs may tell you how to find that info out, either from the device, the supplier or accompanying paperwork.
I have this tracker working all okay with the Things Network.
To get the keys you require needs the SenseCap app on a mobile device (Android I use).
Install the SenseCraft app, tip, you don’t need to register for an account, there is a small “Skip” option in the top right hand side of the app sign in page, then it confirms you are entering the Device professional settings. Find the T1000-E in the list of supported products, and on the tracker itself, make sure it is on and press the button 3 times quickly. The green light flashes, you should see the device is picked up and now can connect to it, use Advanced Configuration.
Under settings you will have the Device EUI, App EUI (this is the Join EUI) and App Key all listed.
Other settings worth changing using the app. LoRaWAN ADR is enabled by default, this means when connecting to a local gateway it will see it has a strong signal and will optimize the transmissions based on that. This may work fine if you are tracking things that are never far from a gateway, but if you go further away the tracker may take some time before it realises it is no longer being heard and then turns up the power. So depending on your use case you may want to turn ADR off and set it to DR0 - DR0, this will give you the best range at the expense of battery life, but also means you can’t update very frequently either as you can use up all the allowed airtime easily.
The decoder is a bit basic, and it doesn’t expose a normalised output, so you will not see the location show up in the Things portal. I’ve tweaked it so that the location will show up, drop me a message if you want this.