I first saw this issue in April, when my solar Gitfos GAT562 (nRF52840-based and using the RAK4631 firmware, as per the vendor's suggestion), configured as a repeater and working continuously for weeks, stopped responding. Firmware version was 1.14.1. Upon a hard reset, the device name became Repeater FFFF and the public key FFFFFFFFFFFFFFFF.
Surprisingly, the frequency preset stayed the same, so a hard reset worked, though the node info was broadcast like this and the admin password had been replaced with random data. Just in case, I replaced the device with another GAT562.
Two weeks later, it stopped responding. This time, the public key remained intact, but I was unable to communicate with the device via radio. Inspecting the device through the USB interface, I noted that the frequency preset was changed to 2500.0,500,12,8. A quick reflash didn't solve it, so I had to fully erase the device and install the firmware from scratch.
I know the issue is a bit open-ended and the cause is borderline impossible to pin down, but I've decided to raise the ticket in case other people are experiencing the same issue and someone has an insight on how to solve it.
For the developers, if there's any other information I could provide to help investigate the matter, please let me know.
I first saw this issue in April, when my solar Gitfos GAT562 (nRF52840-based and using the RAK4631 firmware, as per the vendor's suggestion), configured as a repeater and working continuously for weeks, stopped responding. Firmware version was 1.14.1. Upon a hard reset, the device name became
Repeater FFFFand the public keyFFFFFFFFFFFFFFFF.Surprisingly, the frequency preset stayed the same, so a hard reset worked, though the node info was broadcast like this and the admin password had been replaced with random data. Just in case, I replaced the device with another GAT562.
Two weeks later, it stopped responding. This time, the public key remained intact, but I was unable to communicate with the device via radio. Inspecting the device through the USB interface, I noted that the frequency preset was changed to
2500.0,500,12,8. A quick reflash didn't solve it, so I had to fully erase the device and install the firmware from scratch.I know the issue is a bit open-ended and the cause is borderline impossible to pin down, but I've decided to raise the ticket in case other people are experiencing the same issue and someone has an insight on how to solve it.
For the developers, if there's any other information I could provide to help investigate the matter, please let me know.