The Things Sandbox, aka The Things Community Edition underwent an GUI/front end update/refresh a couple of months back and sadly manufacturers are often slow to update their own documentation - some still call out old V2 instance info that sunset in late '20!
Just follow the instructions given and the link will take you to the redesigned TTS-Sandbox front end (eu1.cloud… or such other cluster as appropriate to where you are, I assume for you (DE?) then Eu1) where you will see a tab top left for application, follow your nose - add application (top right), create your application, then within in the application add/create your device - again follow the instructions you will see common themes and references.
Or indeed any TTN registered Gateway - I’m sure DGNO would love you to buy one of theirs but the fact is any LoRaWAN GW will work for you (note not a LoRa GW or SC/DCPF), either one of your own or a community deployed unit in your area. Sadly if you have no GW and are not in range of a community unit you will see no traffic. Recommendation is where possible get and deploy your own - adds to Community coverage and also allows you to debug device operation, join processes and data traffic.
Next step once you see device traffic in the Applcation tab or the specific Device tab is choose your prefered Integration to 3rd party or your own back end services and data processing system. You may or may not choose to add the device decoder provided by DGNO into the payload (uplink) formatter on the application (prefered) or device (if various revisions of devices under same application) tabs.
Thanks much! Unfortunately, scanning the QR code did not work - never mind. I entered the data manually and received the message:
an end device with JoinEUI and DevEUI is already registered as in application
It looks as if Dragino issues multiple devices with identical IDs for TrackerD -- LoRaWAN Tracker To avoid any hassle, I will return it and buy another make, if anyone had any recommendation for a similar tracker that works out-of-the-box.
This hasn’t been the case in the past - but distributors / sellers trying stuff out and not deleting it happens all the time.
LoRaWAN isn’t an appliance based system like WiFi so “out-of-the-box” is a bit open to interpretation. Nor is it very suitable for tracking due to the constraints of air time. LW is OK for asset location assuming you have a gateway in range. If you don’t, then no data so no location.
Perhaps if you tell us what you are trying to achieve - as in tracking what without owning a gateway - then we can advise better.
[quote=“descartes, post:4, topic:69569”]
sellers trying stuff out and not deleting it
[/quote] understood, thanks!
I have no use case yet. It is just an interest in the concept and see what a LW-tracker can and cannot do. Then, I will see.
I thought to start with a tracker as I do not need to own or resort to a gateway in range as it will eventually pass by one. Does only Dragino manufacture LW trackers that are useful?
Potentially - but it could be a very disheartening project as RF signal paths aren’t just about being ‘in-range’ which is a whole topic (forum search will help) in its own right.
No one produces LW trackers that are useful because LW can’t uplink tracking data often enough to track unless you are walking in an area with many gateways.
And on TTN if you start jogging, your track will have lots of gaps as you are likely end up with locations at 10 minute intervals, assuming coverage.
It will work fine as an asset locator but requires coverage. No coverage, no location.
Under more controlled conditions you can track. Or, to use an alternative way of considering tracking, then it’s a great option. By this I mean something like sensors on pallets so you can track their movement within a business - which includes transfers between sites - so pallet moved around on site, picked up and taken to another site, which then picks up the location. The software can consider the pallet on the truck when it was at the loading bay, scheduled for transfer and then no messages. And then when it arrives, it’s at the unloading bay.
But for having a snail trail on a map, either log to device storage or use a cellular data connection.
Much appreciate having asked that question in the first place and having put then things into perspective. I need to digest this information and find an appropriate use case. Thank you!