Replies: 1 comment
-
After flashing the nRF52 Full Erase file, I was able to reflash and change the radio settings. From looking at the log, it looks like it was just stuck in is_managed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was updating all my nodes and decided to try the remote admin ability on my RAK 4631 board and my Tbeam. After enabling the settings for the legacy admin channel and putting the public key of the Tbeam in the RAKs admin key, I tried sending a command. The command did not work and I got "error code: 36".
The bigger problem is that I tried to remove the admin channel and settings, which went fine for the TBeam, but is not working for the RAK.
When I try and change the channel settings in the app to match my other nodes, it says the settings are changed. However, when I reload the connection, the old settings come back.
When I try to delete the channel and edit the other channels via CLI, it says the settings are saved. However, when I connect to the radio again the admin channel is still there.
While in the app, if I change the key for a channel to match my other radio and save it, and then try to send a message, it doesn't acknowledge or come through on the other node.
I have tried factory resetting from the CLI as well which gives the message: Connected to radio
INFO file:node.py factoryReset line:620 Telling node to factory reset.
Then, after connecting to the radio, all the settings and firmware remain the same.
How can I factory reset my board or just change the channel settings so that it works again?
I've tried removing the UHF file from the board, unplugging the board completely for 10 minutes, and firmware updating to 2.5.8 all to no results as well.
Any help is appreciated!
Beta Was this translation helpful? Give feedback.
All reactions