I have a device in SF9, which can sendi a big datagram sometimes(> 60octet). I want to keep this SF9, so the device frame tells to chirpstack ADR=FALSE
Ok, it rssi is strong, -68dBM, and I understand Chirstack want to change the ADR
And it what I see .Chirptack 4 try to send pending MAC commands to the device ( it sends a downlink after a uplink)
Please note that a LinkADRReq can also be used to update channel-mask configuration of the device. Even if the device sends with adr: false, ChirpStack might still send a LinkADRReq mac-command to sync channel-mask related settings.
The NewChannelReq mac-command is not related to ADR.
You need to look at the content of the LinkADRReq mac-commands to understand what exactly ChirpStack tries to change. You can inspect the content in the LoRaWAN frames tab of the device.
However, there’s something unique about how these devices are activated. Currently, they got automatically deactivated by Chirpstack due to an extended period of being unplugged (> 30 days).
Essentially, we manufactured the devices, conducted tests, registered them on our CS network, and they retained their session. Subsequently, we dispatched them to the customer, who installed them after a lapse of 45 days. Consequently, Chirpstack deactivated them automatically.
As a response, we reactivated them through the Grpc API (using the last devadr, session, and network key)… and this process succeeded without requiring a new join sequence.
However, it’s possible that Chirpstack might be expecting something else. Consequently, it views the device as not being sufficiently initialized. So it trys to send something about freq channel and rx window ?
I think that when you reactivated the devices through the gRPC API, that ChirpStack will assume these devices are using the standard frequencies (868.1, .3 and .5) and thus re-sends the NewChannelReq mac-commands during the first downlink(s).
Once the device acknowledges these mac-commands, ChirpStack will not re-send these again during the lifetime of the device-session.
Note that you can increase the device-session TTL in the chirpstack.toml configuration file if you do not want the device-session to expire after one month (which is the default setting).