RAK4631 Companion Repeat Mode disables all TX/RX until factory reset

[mabrams-us]

Hardware

• RAK4631
• RAK19003 baseboard
• US915
• MeshCore Companion firmware v1.17.1
• MeshCore iOS app
• iPhone

Description

My RAK4631 operates normally in Companion mode until I enable Repeat Mode. Immediately after Repeat Mode is enabled, the radio becomes completely inactive: it neither transmits nor receives MeshCore traffic.

Turning Repeat Mode back off does not restore operation. The RAK remains unable to transmit or receive. A factory reset and complete reconfiguration are required to make the radio functional again.

After the factory reset, TX and RX work normally as long as Repeat Mode remains disabled.

Steps to reproduce

1. Factory-reset the RAK4631.
2. Configure it as a US915 Companion.
3. Confirm that it transmits and receives normally.
4. Open the Companion radio settings.
5. Enable Repeat Mode.
6. Attempt to send or receive a message.
7. Observe that there is no TX or RX activity.
8. Disable Repeat Mode.
9. Test TX and RX again.
10. Observe that the radio remains inoperative.
11. Factory-reset and reconfigure the RAK.
12. Confirm that normal TX and RX operation returns.

Expected behavior

Enabling Companion Repeat Mode should allow the RAK4631 to continue transmitting and receiving its own messages while also repeating eligible MeshCore packets.

Disabling Repeat Mode should return the radio to normal Companion-only operation.

Actual behavior

Enabling Repeat Mode completely disables TX and RX. Disabling Repeat Mode does not recover the radio. Recovery requires a factory reset and complete reconfiguration.

Repeatability

The failure is reproducible. Normal operation returns after a factory reset, and the failure occurs again when Repeat Mode is enabled.

Radio configuration

• Region: US915
• Bandwidth: 31 kHz
• Frequency: 910.525 MHz
• Spreading factor: SF7
• Coding rate: CR5 (4/5)
• TX power: 22
• Default path-hash size: 2-byte
• Repeat mode: OFF
• Telemetry: OFF for now

Additional information

This appears to be a persistent configuration or firmware-state bug because the radio remains inoperative after Repeat Mode is switched back off. The factory reset clearing the failure suggests that enabling Repeat Mode may save an invalid or incompatible radio state to persistent storage.

[jschrempp]

According to AI: "When enabled, the mode locks your radio to specific off-grid presets (such as 433 MHz, 869 MHz, or 918 MHz) so you do not accidentally interfere with standard public mesh routes"

Could this explain the behavior?

[mabrams-us]

No,  the node was set to 918.  You are given those three choices when repeat is enabled.On Sep 6, 2026, at 3:23 PM, Jim Schrempp ***@***.***> wrote:jschrempp left a comment (meshcore-dev/MeshCore#3367) According to AI: "When enabled, the mode locks your radio to specific off-grid presets (such as 433 MHz, 869 MHz, or 918 MHz) so you do not accidentally interfere with standard public mesh routes" Could this explain the behavior? —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[mabrams-us]

I would expect the repeat on the same preset to assist other radios on that preset that may not be able to reach a dedicated repeater.  I’m not a MeshCore developer, so I can’t explain the code workings beyond the interface and function.  Enabling or reseting the repeater mode back to off should not disable a radio.On Sep 6, 2026, at 3:23 PM, Jim Schrempp ***@***.***> wrote:jschrempp left a comment (meshcore-dev/MeshCore#3367) According to AI: "When enabled, the mode locks your radio to specific off-grid presets (such as 433 MHz, 869 MHz, or 918 MHz) so you do not accidentally interfere with standard public mesh routes" Could this explain the behavior? —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[jschrempp]

I would expect the repeat on the same preset to assist other radios on that preset

I'm not an expert, but I don't think that's how it is designed. When you go into Companion repeater mode you have to select one of those three frequencies. At that point you will not be able to talk with any radio on any of the presets. You will only be able to talk with other nodes that have also selected the same frequency.

[liamcottle]

The Companion Repeat mode forces the companion node on to a different frequency. It will not allow the node to repeat packets on the public meshes selectable in the radio presets list.

This is intentional, to prevent public meshes from becoming unusable from having 10,000 companions repeating.

It's specifically intended for camping/hiking purposes etc. When you disable companion repeat mode, you will need to select your radio preset again, as the node would still be on the alternative frequency when disabled.

It is possible to flash custom firmware that allows companion repeat on public meshes, if you really need it, but this isn't something the core project is offering by default at this time.

[mabrams-us]

Thank you for the information.  On Sep 6, 2026, at 9:07 PM, Liam Cottle ***@***.***> wrote:liamcottle left a comment (meshcore-dev/MeshCore#3367) The Companion Repeat mode forces the companion node on to a different frequency. It will not allow the node to repeat packets on the public meshes selectable in the radio presets list. This is intentional, to prevent public meshes from becoming unusable from having 10,000 companions repeating. It's specifically intended for camping/hiking purposes etc. When you disable companion repeat mode, you will need to select your radio preset again, as the node would still be on the alternative frequency when disabled. It is possible to flash custom firmware that allows companion repeat on public meshes, if you really need it, but this isn't something the core project is offering by default at this time. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>