I’m seeing many new users assume that they need to activate “router mode” to actually route messages, while all it does is enabling aggressing power save which actually makes it harder to troubleshoot a new mesh.
I would therefore ask to consider renaming “router mode” with something less of a misnomer, perhaps “power saving mode”. Thus, the preference could be set with “power_saving true”.
Have you put some time into testing router mode? It seems to break a lot of things for me… missing messages, BT never waking, etc. I’m still trying to narrow down the faults before I open a ticket. How well does it work for you?
The info surrounding router mode seems to be conflicting. What’s said in power.md (missing on github now???) doesn’t match what I see in mesh/NodeDB.h. Still trying to wrap my head around the power transitions and sleep cycles.
One way to work around this is to use the “admin” channel (it’s still new so getting reliable).
When set up, you can send a –dest message to the inaccessible node, changing the is_router mode. For example, when you want to be able to gain access to it, you can send it: meshtastic -dest !nodeid --set is_router false --reboot
The device will come up as a standard device for local use and you can just do the reverse when you’re ready to leave it in router mode.
This way, as long at you can talk to the node via the mesh, you can change its behavior.