You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node A is primary. Node B is remote. Nodes are communicating directly with good signal strength. Remote administration is setup and confirmed working properly between nodes. Node A is able to change the settings on node B using remote administration.
Expected Behavior
Node A (primary) should be able to power off or reboot node B (remote) by tapping on the appropriate command listed at the bottom of the screen under the “Nodes -> Administration” menu for node B (see attached screen capture).
Current Behavior
After tapping on either the power off or reboot command on node A and acknowledging the command confirmation dialogue, nothing happens on node B. Node B fails to either power off or reboot via remote administration.
Participation
I am willing to submit a pull request for this issue.
Additional comments
No response
The text was updated successfully, but these errors were encountered:
Firmware Version
2.5.7
What did you do?
Node A is primary. Node B is remote. Nodes are communicating directly with good signal strength. Remote administration is setup and confirmed working properly between nodes. Node A is able to change the settings on node B using remote administration.
Expected Behavior
Node A (primary) should be able to power off or reboot node B (remote) by tapping on the appropriate command listed at the bottom of the screen under the “Nodes -> Administration” menu for node B (see attached screen capture).
Current Behavior
After tapping on either the power off or reboot command on node A and acknowledging the command confirmation dialogue, nothing happens on node B. Node B fails to either power off or reboot via remote administration.
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: