We have a Sensor in chirpstack that keeps sending data fron frame counter 0 to 8. After that, it gives up and sends a new join and creates a new devNonce after a couple of minutes.
It repeats this pattern and does not seem to completely join. We’ve tried restarting the sensor, removing it from Chirpstack and adding it again, clearing devNonce, and disabling frame counter validation. It just keeps on going like this and we have no idea of what could be wrong.
I’ve tried looking for already existing cases but haven’t really understood the solution or if it’s even the same problem. Any idea?
Could this be the case if a sensor is for example configured to send confirmed payloads while gateways/broker expects unconfirmed? Because that is the only difference that I can see between this sensor and our other ones.
I must apologize. I think this is a false alarm. This sensor is sending data and at the same time having this issue so it might not even be an issue that it renews its sessions