Three RAK4631 lose their minds

So I have three RAK4631 and four T-Beams in a private mesh network. The system has been running for several months untouched. Today I noticed that a repeater dropped off the node. I went to investigate why it wasn’t being responsive. A little digging showed that the RAK4631 repeater had reverted (configuration wise) to the Meshtastic standard mesh network (my entire configuration settings were overwritten). The ONLY nodes that reverted back (factory reset???) were the RAK4631. NONE of the T-Beams reverted.

What in the world could be going on with these RAK4631??? Was I hacked or did the RAK4631 do a spontaneous factory reset???

Which firmware version?
Was it on solar or battery power? Might be a brownout in that case. If that happens at the wrong moment, it could corrupt the flash.

Two were on standard AC outlet power and one was on solar. I don’t believe it was a power supply issues since I am using different sources.

V2.2.22

Could have been hijacked. Did you change the default Bluetooth pin?

Yes, all units have a unique random PIN. That’s what I was thinking (and still think).

I’ve since turned the BT off on all the units now.

Seems weird that ONLY the RAKs were hacked (if that’s what happened)….

Any other ideas as to what could have cause this?

I am having the same issue with a RAK4631 based router. Had a random PIN set. Worked for a few days and then dropped off the network. Mine has a voltage supervision module connected to it that cuts power when the battery voltage drops to 2.95V, which mitigates the brown-out issue that makes the RAK4631 unable to come back from a depleted battery.
This is more than just a bit concerning. The RAK modules are the only ones usable for remote routers, and not only have they the annoying brownout issue, they now als loose their settings all on their own.

1 Like

Known issue for the ESP32. Seems to affect the Nordics too then.

Could you please try to provoke it an post a serial log into the bug ticket?