Why chirpstack send mac command LinkADRReq,NewChannelReq, despite with ADR disabled

[brocaar]

@guillaume_fernandez

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).