Sometimes I get the event "Break in message sequence" and it's solved with disengage, but sometimes I get the event with the same sequence number (176 inferior 176) and I can't solve it with disengage because I always receive the same sequence number. Why my sigfox chip is sending always the same sequence number? How can I reset it? It's a firmware or a sigfox backend configuration problem?
Thanks in advance!
Answer by nlesconnec · Mar 23 at 08:36 AM
Indeed, this looks weird, as if your device wasn't properly setting the
sequence number in the protocol headers.
I'd suggest to get in touch with the support team (http://support.sigfox.com) to be able to share details about your device, its firmware version, ...
In case you don't have an access to the support platform, please get in touch with me at firstname.lastname@example.org