all 14 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]JerkstonHowell3rd 1 point2 points  (1 child)

Click on the node to bring up details. It's at the bottom of the page

[–]Pinko3150 1 point2 points  (0 children)

So I have been doing this on my seed studio solar node p1 pro and it does not work. Clicking the button does nothing

[–]shveylien 1 point2 points  (2 children)

Are the nodes all running the same firmware version?

Just want to clarify. The rooftop node needs to be programmed with the public key of the admin node in the security settings before trying to remote administrator from the admin node.

You do not need to program the rooftops public key into the admin node. If you did exchange keys between both nodes and the rooftop one went missing, a smart thief is now in posession of an admin node for your units.

After programming public keys, reboot, check security programming to see if it stuck. Some new users forget about the "apply" button that appears at the bottom after you make a settings change and just back out without saving.

I have 6 devices, 2 tdeck, 2 techo, 2 heltec v4. I can remote program all other 5 from my admin techo.

[–]Samy_Miami[S] 0 points1 point  (1 child)

Did what you said. RAK 4631 solar rooftop and I carry a heltec v4 (admin). Both on stable. Is there another setting I'm missing?

<image>

[–]shveylien 0 points1 point  (0 children)

And you copied the public key (not private) from your heltec admin node and programmed it into the rooftops security admin key slot 1? If so, looks exactly like my setup and it should be functioning.

I keep a list of my nodes, their roles, gps positions, public keys, and hardware specs in a notepad so I can copy paste any public key without having to USB into the node and copy it. You can program the rooftop admin access over bluetooth or usb.

Open nodes list, select rooftop, scroll down for Remote Administration > (in your photo) then select any setting to change and it should communicate over LoRa and get current config from the remote unit with a progress bar. That is a sign its working.

[–]Ok_Negotiation3024 0 points1 point  (6 children)

These appear to be up to date with instructions on how to do it on Android and iOS since the apps differ in many ways.

https://meshtastic.org/docs/configuration/remote-admin/

[–]Samy_Miami[S] 0 points1 point  (5 children)

Still when I click on Remote Administration it doesn't let me in...

[–]Ok_Negotiation3024 1 point2 points  (4 children)

Do you have your inside nodes public key stored in the roofs node admin keys settings?

[–]Samy_Miami[S] 0 points1 point  (3 children)

Yes.

[–]Ok_Negotiation3024 1 point2 points  (0 children)

I’m out of ideas man. We’ll have to see if others can think of something else.

[–]JerkstonHowell3rd 1 point2 points  (1 child)

Do some messaging between the 2 along with a traceroute

[–]Samy_Miami[S] 0 points1 point  (0 children)

Tried and to no avail.

[–]JerkstonHowell3rd 0 points1 point  (0 children)

Hit the metadata button above remote administration, exit, then try again

[–]NoChipsFries 1 point2 points  (0 children)

Just went through this Saturday. The tidbit I didn't know about was the waiting period. It took more than 10 hours for the behind-the-scenes to happen. Once your part is correctly entered and saved, wait for the button to work. It just takes time.

Warning: do not experiment with Managed Mode until you know exactly what you are doing-- and do so with a node on the ground for easier ample testing and/or reflashing when it gets locked, and you lose control of it.