So i currently have a node that is setup as a Router-Client for the device role. I have several other nodes all set up as Client. I have the admin channel set up on Channel 1 as per the document on all the nodes. I have one Client node hardwired (via USB) to a laptop that has meshtastic installed. I can request settings from all the nodes and get responses from all of them EXCEPT the node setup as the Router-Client. I have the Router-Client mode as I am using it as a repeater (so it doesn’t count as a hop) BUT I am also monitoring the battery and solar panel voltages/currents and want those downlinked over the air to my MQTT node for analysis.
I am seeing the Client-Router:
Connected to radio
Sending traceroute request to !0491b8c1 (this could take a while)
Route traced:
!55c6db90 → !0491b8c1
Does the Router-Client node not accept admin commands?
I have a similar setup going right now. I have a Client-Router attached the back of a solar panel of an off grid GMRS repeater. That Client-Router serves as a Meshtastic repeater and also has an INA260 monitoring the currant/voltage of the main 12 volt battery.
I have a primary channel at standard and then a secondary ‘admin’ channel. I am able to change the radio configuration on it remotely from another node and an Android device. No issues. I am about 1.5 miles from the Client-Router and about 2,000 feet in elevation lower. Never tried it from a computer connected to a node.
So how do you use another node that is not connected to a computer to send the admin commands?
I’m going to reflash the RAK (Eouter-Client) when I get a chance just in case that could be the problem. I can change any other mode at will. Just not the router-client.
Are there any nodes in your nodes list apart from the node your connected to? I believe then you should be able to choose one where it says “Configuring Node …”.
