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

disable_adr not honored #538

Closed
KrestenHelstrup opened this issue Jun 30, 2021 · 1 comment
Closed

disable_adr not honored #538

KrestenHelstrup opened this issue Jun 30, 2021 · 1 comment

Comments

@KrestenHelstrup
Copy link

What happened?

LinkADRReq is present in unconfirmedDataDown even though disable_adr=true is present in the chirpstack-network-server.toml configuration file.

What did you expect?

I expect that LinkADRReqs are only present with disable_adr=false

Steps to reproduce this issue

Steps:

  1. Set disable_adr=true in chirpstack-network-server.toml
  2. Restart network server
  3. Send join request from device
  4. Send uplink from device
  5. Use chirpstack web interface frame view to see unconfirmedDataDown

Pictures from chirpstack

image
As seen adr is false in fCtrl but still LinkADRReq is present with a requested change in TX power

Your Environment

Component Version
Application Server v3.15.0
Network Server v3.13.0
Gateway Bridge v3.11.0
@KrestenHelstrup
Copy link
Author

@brocaar - Could you confirm if this is really a bug or expected behavior ?

@brocaar brocaar closed this as completed in 4e7fdb3 Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant