Thank you very much!
There was a second sticker inside the box, which I’ve missed…
Thank you!
1 Like
Hello I have the same problem.
On the label it is written: APP EUI A000000000000101 but it does not work. How to do?
Please Help me
Do you own a gateway where you can check the EUIs of the join request? Is there information on the application traffic?
Have you checked the EUIs and AppKey match the label? No typing errors? No B that should be 8 or the other way around?
I did not make a typo.
My EUI app is: A000000000000101
Is it possible?
My gateway is an LG01 dragino
That is not a gateway, that’s a Single Channel Packet Forwarder that can only hear one channel with a limited range of Spreading Factors at a time, whereas the device is expecting to talk to a real gateway that can listen on 8 channels, all SF’s at the same time.
Because of the disruptive impact on the TTN community network we would ask you to remove it immediately.
You will see on the Dragino website that it is not for use for LoRaWAN.
1 Like
that was a usefull hint. thanks
Hello, which gateway to choose for outdoor use with two dragino lsn50?
Is the DLOS8 dragino a good choice?
I don’t personally own one myself, but I do have an LPS8, it’s indoor version. I haven’t heard anything bad about the outdoor variant so I’d be happy to buy one if I had the need.
Actually, I think that is not true. You can setup LSN50 V2 to work in single channel mode and LG01N can manage to forward it, only downside (as far as I understand) is that, you have to use ABP instead of OTAA to join. I managed to connect it this way, the only problem is, that I can see data incoming into the Gateway in TTN but cannot see it in Application. Any ideas?
Here is info from their documentation, that LG01N can support LoraWAN protocol.
It does not support LoRaWAN and should not be used on TTN as it causes issues for other users (and yourself). Please disconnect it now. Dragino explicitly calls those devices LoRa gateways not LoRaWAN gateways on their website and in their documentation.
Yes, you are using incompatible hardware and not using OTAA as recommended. As a result you are running into issues. Disconnect the LG01, use a proper LoRaWAN gateway and if you still have issues we will will provide support. For incompatible hardware which should not be used we do not offer support on the forum.
They even have pre-defined settings for TTN 
OLD data from a product brief that is not being updated as …old device!
See current web page here…scroll down nice RED text!
protocol is the message system…not the standard or specification(which calls out min8 channels…)
Now please do as requested and remove from the network…
Selective quoting isn’t a strategy for assistance that is likely to get you long term community support:
clearly has this on it.
You’ve asked for assistance from the community and the community is telling you that your Single Channel Packet Forwarder is not suitable for use on The Things Network, a community network that needs LoRaWAN compliant gateways to run properly.
Please disconnect your LG01N. We will be happy to help you with connection issues when you have a compliant gateway.
OK, so why the hell their latest firmware has these predefined V2/V3 settings for TTN if they are not compatbile? Any other services that I can use? Don’t have an option to quickly replace this one with another gateway.
This forum is for TTN so it’s a bit much to expect us to recommend another service but you may want to look at Chirpstack.
As for the why, perhaps you need to direct your question to Dragino.
OK, thank you. Don’t worry, I could not be your customer anyways because of current hardware, but will get back when I got compatible by remembering good deeds 
FYI, you can’t be a customer - TTN is a free service and we are volunteers.
But you are more than welcome when you have an 8 channel gateway.
As Nick says you need to ask Dragino for full answer but suspect in large part it is the typical practice within the industry of having common core firmware/software across a number of devices & families - even if ‘options’ do not always reflect actual device capabilities or system implementations. You can use this in your own private deployments, where limited functionality may be adequate and you do not impact other users.
For anyone else reading at a later date this is classic ‘Caveat Emptor’, and why we strongly recommend researching and reading around the subject before diving in and buying kit…here the TTN Forum is your friend (use search) as there have been lots of posts about suitabiity of equipment over the years, and many Forumites more than willing to share their experiences and opinions of targeted hardware or to make suggestions based on declared needs. Also make sure you read full, and current, information from potential vendors and if clarification needed ask them or ask on the Forum - Forumites dont always pull their punches and if we think something is not suitable or a poor choice likely you will hear it 