[Bug]: Bluetooth (re) connectivity problem

[alligitor]

Category

BLE

Hardware

RAK4631

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.6.4

Description

I have recently upgraded my RAK4631 to 2.6.4 and my iOS app to 2.6.6 (1457).
I used to run FW 2.5 and what I'm describing is new after the upgrade.

My app will not reconnect to the radio if:

• It's connected

• Phone goes out of range and I don't cleanly do a "disconnect" from the app.
  For example, my phone is connected to the radio.
  I leave the radio behind and go down the street for a few minutes.
  When I come back, the app sees the radio, attempt a reconnect, but reports back a "bluetooth timeout".
  Connection will not be made until I reboot the radio.

• so far it seems like doing a disconnect manually, then going out of range, will not result in this issue.

I have tried a few things on the app side to no avail.

• kill the app and restart
• disable bluetooth on the phone, renable, and attempt to connect again.

Relevant log output

[caveman99]

Do you have another phone paired to the same radio? I have seen phones 'fighting' over the connection. Also please check if this problem still persists with the latest tech preview.

[alligitor]

1- the hardware is a RAK4631, not Heltec V3. got the two confused.
2- As for phones fighting, the chances are minimal. I have other phones that have paired with other radios but not this one. Is there a chance that an app on a phone, not paired with this RAK4631, tries to connect anyways?

Are there logs I can somehow get to help?

It seems like the problem is on radio side because rebooting it solves the issue, but to be sure: Any suggestion as how to isolate the issue between the app and radio?

[alligitor]

@caveman99 what exact version should I try? 2.6, 2.7, ...?

[alligitor]

Bump on this.... am I the only one with this bluetooth issue? It's driving me nuts. I have to keep rebooting my node and I loose messages that were in the radio.

I reset my radio to factory defaults, it's still happening.

I don't believe there are other phones fighting for connection to the radio but willing to debug. Are there any logs / tests that I can do?

I have two nodes and two phones.
iOS phone connected to the node that is having this issue.
Android phone connected to another node that seems to have constant connectivity.

[alligitor]

I got some logs from the App ...

• ForEach<FetchedResults, Int32, Optional<ModifiedContent<ModifiedContent<ModifiedContent<NavigationLink<TupleView<(ZStack<ModifiedContent<ModifiedContent<ModifiedContent<ModifiedContent<Image, _OpacityEffect>, _EnvironmentKeyWritingModifier<Optional>>, _EnvironmentKeyWritingModifier<Optional>>, _BrightnessEffect>>, ModifiedContent<CircleText, _BrightnessEffect>, VStack<TupleView<(HStack<TupleView<(_ConditionalContent<ModifiedContent<Image, _EnvironmentKeyWritingModifier<Optional>>, ModifiedContent<Image, _EnvironmentKeyWritingModifier<Optional>>>, _ConditionalContent<_ConditionalContent<Text, Text>, Text>, Spacer, Optional<Optional<_ConditionalContent<_ConditionalContent<Text, Text>, _ConditionalContent<Text, Text>>>>, Optional)>>, Optional<HStack>)>>)>, Never>, _FrameLayout>, ContextMenuModifier<ZStack<ModifiedContent<TupleView<(Optional<Button<Label<Text, Image>>>, Button<Label<Text, Image>>)>, StyleContextWriter>>>>, ConfirmationDialogModifier<ModifiedContent<Button, PrimitiveButtonStyleContainerModifier>, EmptyView>>>>: the ID 0 occurs multiple times within the collection, this will give undefined results!
• [BLE] Disconnected: XXXXXX Error Code: 6 Error: The connection has timed out unexpectedly
• [BLE] Disconnected: XXXXXX Error Code: 6 Error: The connection has timed out unexpectedly
• [BLE] Disconnected: XXXXXX Error Code: 6 Error: The connection has timed out unexpectedly
• Want Config timeout, retyring... (attempt 2/3)
• Want Config timeout, retyring... (attempt 3/3)
• Want config failed after 3 attempts, forcing disconnect
• [BLE] Forced disconnect due to want Config timeout
• Currently, only presenting a single sheet is supported. The next sheet will be presented when t he currently presented sheet gets dismissed.

I don't see anything informative in there but maybe rings a bell for someone.