We have several trackers in use and they are rebooting fairly often but not consistently among them. Some reboot more than others. Not sure if there is a reboot reason which causes a loss in connectivity or whether a loss in connectivity causes a reboot. We suspect the latter because the most rebooting system is in an area of poor coverage, but are open to the former. To try to debug, I capture the reboot reason and it works for DFU, FW updates, and I even inadvertently tested the panic. They all worked fine but in this case we are getting back a code 0 which translates to invalid reason.
Has anyone else seen connectivity related reboots? We’re running 2.0.1, semi-automatic mode threads enabled. I track connection status and don’t publish if there is no connection.
Why is the reboot reason code not valid? Is there anything we can do to get more information on the root cause? Is there anything our firmware code could do to trigger code 0 or would a firmware crash always be logged as such?
Thanks for any insight and hints on what to try next.