Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node Activation without Uplink from Node to Application #408

andhir0012 opened this issue Jul 1, 2019 · 2 comments


None yet
2 participants
Copy link

commented Jul 1, 2019

Is this a bug or a feature request?

I think it is a feature based on the normal operation.

What did you expect?

Activation of a device should be completed if the device joins the LNS.
If the device sends an uplink frame for configuration purpose the activation should be done.

What happened?

Class-A device is a commercial product.
Device Activation is not completed.
I can start a so called configuration mode on a node. In this configuration mode the node sends an uplink WITHOUT payload data for 10 Minutes. This Uplink frame do not lead to activation in Application Server (I think because there is no payload within this frame).

What version are your using?

Loraserver version=3.0.2
Applicationserver version=3.0.0

How can your issue be reproduced?

Always the Node Joins the LNS

Could you share your log output?

time="2019-07-01T12:13:36Z" level=info msg="gateway/mqtt: uplink frame received"
time="2019-07-01T12:13:36Z" level=info msg="rx info sent to network-controller" dev_eui=70b3d5e75e006862
time="2019-07-01T12:13:36Z" level=info msg="device gateway rx-info meta-data saved" dev_eui=70b3d5e75e006862
time="2019-07-01T12:13:36Z" level=info msg="device-session saved" dev_addr=0075c057 dev_eui=70b3d5e75e006862

No log from Application Server.

Live LoraWan Frame where you can see the null payload


This comment has been minimized.

Copy link

commented Jul 9, 2019

What I'm planning to do is always forward an uplink event to the AS, even when FPort is empty or FPort = 0. With this LoRa Server will not wait with signaling the security-context change to the AS.

@brocaar brocaar closed this in 63613c0 Jul 9, 2019


This comment has been minimized.

Copy link

commented Jul 9, 2019

Thank you
for doing this changes. I will give you feedback about the functionality.

You do a very good job in this project.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.