Orne Brocaar

It was not fixed, but in the end I created a work-around and released v3.3.3. Could you test again with this version?

I can not reproduce your results: ``` ________ _ _____ __ __ _ / ____/ /_ (_)________ / ___// /_____ ______/ /__ (_)___ / / / __ \/ / ___/...

If you configure channels 0 - 7, then I believe the first LinkADRReq already contains chMaskCntl = 7 to turn everything off, the second LinkADRReq mac-command then contains the channels...

> Now here is an example where the node doesn't receive the confirmed ACK for some reason. **It resets its channel plan after the 8 uplink retransmissions** I'm not sure...

> Why periodically send the linkAdrReq at all if it isn't going to include the full channel plan The LinkADRReq command has two purposes: 1. Setting the channel-mask 2. Setting...

This issue has been brought up a couple of times. What happens is that when a device is really close to the gateway, it will over-drive the gateway hardware causing...

Yes, I'm planning to address this, but I don't have an ETA for this yet.

@cairb please note that the mutex only applies to a single instance. In case of multiple instances it doesn't prevent an other NS instance from handling the "ghost" join-request.

I have just pushed the following change: https://github.com/brocaar/chirpstack-network-server/commit/1b505944a63ebdb8b3556211d8f9e76e606f516a. I believe this should fix at least the duplicated OTAA accept in case of a ghost uplink.

I believe the issue is since the NS can't return the margin for LR-FHSS:  For LoRa uplinks, ChirpStack uses the SNR reported by the gateway to derive the margin...