Cant connect to RNode

[hejagithub]

I'm trying to connect to my Heltec v3 RNode for the first time on Android using bluetooth but it keeps talking about an incorrect pin or passkey without prompting me. I'm not entirely sure if this is a bug with Rnode but I hope someone knows the answer this. I installed using the rnodeconf --autoinstall command and linked on to this tutorial. I followed all the steps by holding down the PRG button for a few seconds and I saw the pairing code and bluetooth logo come up.

[rbomze]

I am today in a similar situation. there seems not to be any feedback at all. One thing you should know: Shutdown the app and restart. There should definitely be a more direct approach, as forcefully restarting the app after config change. I used quite a time to figure that out.
Didn't got it working, works fine with nomadnet on linux with serial connection.

[hejagithub]

I havent really downloaded the app yet since I havent gotten past the pairing step first in the tutorial yet

[markqvist]

Did you hold down the prg button for 5+ seconds to put it into pairing mode before trying to pair it with Android?

(Not just pressing once to enable Bluetooth)

[rbomze]

Ok... i just realized that. I came from Meshtastic where the config happily allowed to set 27dBm. But we need some error message. It is really frustrating to see Sideband not connecting to the RNode without knowing what's wrong.

[gretel]

Ok... i just realized that. I came from Meshtastic where the config happily allowed to set 27dBm. But we need some error message. It is really frustrating to see Sideband not connecting to the RNode without knowing what's wrong.

think it's frustrating to configure something without having an actual effect.

[hejagithub]

Ok... i just realized that. I came from Meshtastic where the config happily allowed to set 27dBm. But we need some error message. It is really frustrating to see Sideband not connecting to the RNode without knowing what's wrong.

why are you replying here make your own discussion i dont think we are having the same problem

[rbomze]

Ok... i just realized that. I came from Meshtastic where the config happily allowed to set 27dBm. But we need some error message. It is really frustrating to see Sideband not connecting to the RNode without knowing what's wrong.

why are you replying here make your own discussion i dont think we are having the same problem

Both our problems match the topic 'Cant connect to RNode', although the problem is different.

[hejagithub]

Ok... i just realized that. I came from Meshtastic where the config happily allowed to set 27dBm. But we need some error message. It is really frustrating to see Sideband not connecting to the RNode without knowing what's wrong.

why are you replying here make your own discussion i dont think we are having the same problem

Both our problems match the topic 'Cant connect to RNode', although the problem is different.

Oh ok

[hejagithub]

Did you hold down the prg button for 5+ seconds to put it into pairing mode before trying to pair it with Android?

(Not just pressing once to enable Bluetooth)

Yes

[markqvist]

I'm actually a bit confused as to what is not working here? Are you getting any error messages when trying to pair the RNode with your Android device? Or is it not visible when trying to scan for pairable devices? Or something completely different?

If you can explain exactly what is going wrong, at what step of the process, it will make it much easier to figure out what is wrong. So basically, describes what steps you took, and where things start going not as you expected.

[hejagithub]

I'm actually a bit confused as to what is not working here? Are you getting any error messages when trying to pair the RNode with your Android device? Or is it not visible when trying to scan for pairable devices? Or something completely different?

If you can explain exactly what is going wrong, at what step of the process, it will make it much easier to figure out what is wrong. So basically, describes what steps you took, and where things start going not as you expected.

What is going on is when I try to pair it with the android instead of asking for the pin it immediately says the pin is incorrect

[stephen304]

I'm having a similar issue but in my case specifically I encountered 2 issues: the terminal command rnodeconf --bluetooth-pair /dev/ttyACM1 has stopped outputting the pairing pin. I successfully paired an hour ago but I stupidly decided to forget the pairing and re-pair, and now every time I enter pair mode it just says "Putting device into Bluetooth pairing mode. Press enter to exit when done". No matter how many times I press to pair on my phone, the pin entry screen comes up but the terminal is still waiting and doesn't output a pin. I tried toggling my phone's bluetooth, rebooting, and reflashing the rak4631 using --eeprom-wipe and then --autoinstall, but it doesn't seem like it's detecting my phone trying to pair and so it doesn't show a pin so I have been unable to re-pair.

Before I was having pairing issues, I had successfully paired but it kept saying "RNode interface down" in the connectivity status. I had RNode enabled under Connectivity and made sure I filled out a frequency and enabled connect using bluetooth, but no matter how many times I gracefully exited using the menu option and restarted sideband it still said "interface down"

[stephen304]

So mysteriously it started outputting pairing pins again when I paired on my phone - nothing else seems to have changed so I'm not sure what was happening 🙃

It took a few restarts of the node and the app but it also finally went from "interface down" to on-air. One thing that did change there was that it only went on-air once the bluetooth status went from "connected" to just "saved", not sure if there is something related there but the interface didn't want to be up right after it was paired for some reason and required some reboots.