Web Flasher Error: "Selected device is not an RNode"

[gridbasedotnet]

Flashing a wisblock 4631.

First flash went fine. Had an issue with bluetooth connection post flash so I reset and tried again. Same error.

Now, when trying to reflash, once I get to provision the EEPROM, or set firmware hash, I get an error that reads, "Selected device is not an RNode"

have tried wiping the EEPROM, etc. Was able to erase and reflash meshtastic, but error persists when flashing RNode.

[Lentrave]

Have the same problem.

[Lentrave]

Have the same problem.

I just found that the error is cause by the USB Hub I have. Just plug the board direct to your computer usb port and you will be fine.

[EmceeWill]

I encountered the same problem and then it got worse.

Sequence:

1. I successfully flashed the Rnode CE (v 1.75) firmware to a Heltec Lora32 v3.
2. I tried to set up bluetooth using flasher buttons. I got a message from the flasher that the device I'd just installed was "not an Rnode." (Perhaps it doesn't recognize the CE firmware as an Rnode?)
3. I tried to investigate through CLI: Rnodeconf -i /dev/ttyUSB0
4. I got an message in Rnodeconf that the device signature could not be verified.
5. I decided to reflash.
6. Now the Flasher (second round) has started but gone nowhere and has been hung for 15 minutes ("Flashing: please wait...").

I've been having real difficulties with Rnode and the Heltec Lora32 v3, particularly things associated with Bluetooth (I have 2 of them, so it isn't just one bad egg). Am I unique in this situation?

[markqvist]

Just for info, I have some updates coming up to both RNS, Sideband and (potentially) the RNode firmware that should solve most of the Bluetooth Low Energy problems. It seems particularly bad on Heltec V3, and hopefully these new updates should make it a lot more smooth sailing.

[AloofPenny]

still getting this

[jktrigg]

I'm getting this on a Heltec V3 with RNode 1.85 from the official site. Flash appears to go OK, then provisioning fails with "not an RNode".

[psycho9x]

I'm still getting this on a HeltecV3. Any solutions yet?