Specific AppEUI on staging.thethingsnetwork.org

Hi,

I have the same problem.
My node is seen by my gateway, but messages(ack) are never sent to my App.
I suppose that every Ascoel node has the same AppEui.
I am able to receive message with an mDot (because I can setup the AppEui on it).
How can I setup my gateway or my app to be able to receive message from devices that cannot be programmed ?

Best regards,
Alexander

If you go to your application settings in the console, you can add the EUI under EUIs. If that doesn’t work for you, you could try using the ttnctl devices set command (doc).

1 Like

I already have tried to add the AppEui sent by my node, so I will try the ttn client.
Thanks for the quick answer, I will let you know if I found a solution.

Hi again,
I’m sorry but I am really unable to find out the problem.
Here two screen shots with my devices settings and the message that my gateway received.

If someone has any idea… I’m stuck on this since yesterday…

When APP and Devuce EUI match and the back-end does not recognize the OTAA request the App Key might be the issue. Did you program your device with the App Key in the correct format?

Hi, thank you for replying

I am not able to program my device, it’s a Magnetic sensor from Acoel.
I past a link to the device specification:
http://www.ascoel.it/forum/images/pdf_ascoel/CM868LR_eng.pdf

I was thinking to set an app key on my app (from my device), but I cannot find what my device is using to do its ACK…

Hi,

have you got an instruction manual of this product?

Alex

Hi,
I found this manual, but i haven’t found a solution in it…

I have also found it now… you are right is seems programmable through messages sent from the server but nowhere they talk about App EUI, Dev EUI or App Key very strange!

Alex

Hi Veldars,

can you show me where you purchased this module on the web?

Thank you
Alessandro

I purchased this module here:

http://www.dataprint.fr/solutions-m2m-et-iot/capteur-magnetique-lora-ascoel

thanks you for your interest

Hi Veldars, I contacted that company (they are 70km away from me) and from the first reply I suspect they are not happy about dealing with private customers. I’m now waiting for a reply and I hope with a solution to the mystery :slight_smile:

Alex

Many thanks for your implication

Here the reply from ascoel:

Generally, we provide the sensors and the reference keys so that you can then connect the sensors to a LoRa network.
We usually only sell to companies

Whoever sold you the product should have supplied it

Alex

Ok, thanks,
I will see with the company that sells me this sensor and I let you know if they have forgot to give me something.

If you’ve got your own gateway, then peek in its logs (or even easier: see the gateway’s Traffic page in TTN Console) to see if it’s trying to do an OTAA Join when powering up. If not, then you’re out of luck as you cannot use a pre-programmed ABP DevAddr.

(As an aside: staging.thethingsnetwork.org should no longer be used, if it’s still operational to start with.)

Thanks for your helps, the seller forgot to put a paper with device’s credentials, so they send it by email and now all works perfectly.

Many thanks for your help.

1 Like

Hello,
I was finally able to get a Ascoel Device CM868LRCB connected to TTN. The really provide a pre-configured AppKey and AppEui which has to be set in the TTN settings. It appears that the same for all Ascoel device AppEui doesn’t hurt.
There is a USB connector inside the device which gives you access to a serial console connection. There it is possible to change the AppEui and AppKey also to the TTN generated items. To do this you need to enter privileged user access and every device has different passwords which are normally provided with the device from the manufacture.

Closing this topic because it’s referring to a version of ttn that was discontinued more than a year ago.