[Bug]: Heltec v3: while pairing the BLE Pin is just shown for <1 Second, if ever

[Elektron79]

Category

BLE

Hardware

Heltec V3

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

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

Firmware Version

2.7.9 beta

Description

Hi,

when i initiate the Pairing of a smartphone or PC, the Pin is only visible for <1 Seconds on the display. Somtimes nothing is shown

Relevant log output

[thebentern]

I have not been able to reproduce this. Do you have an aggressive screen timeout or router role configured?

[Elektron79]

No, the Heltec is in Client Role and the display remains on. It just switches back after <1 second to the „normal view“.

[Xaositek]

I have attempted and unable to reproduce. Can you retest with 2.7.10 to determine if you can provide reproduction steps? Perhaps a video also may be useful.

[Elektron79]

Please find video attached, it was created with the last beta version

https://github.com/user-attachments/assets/21f88ee8-485b-4a49-bb92-60c88722dd65

[Xaositek]

I just tested on 2.7.10 connecting from macOS and was not able to replicate.

Which device are you connecting from?

DEBUG | ??:??:?? 21 [Power] Battery: usbPower=1, isCharging=1, batMv=4680, batPct=100
INFO  | ??:??:?? 29 Use random passkey
INFO  | ??:??:?? 29 *** Enter passkey 789117 on the peer side ***
DEBUG | ??:??:?? 29 BluetoothStatus PAIRING, key=789117
E NimBLEDevice: ble_gap_security_initiate: rc=2 
....
DEBUG | ??:??:?? 50 [NimbleBluetooth] Got client heartbeat
INFO  | ??:??:?? 50 [NimbleBluetooth] Client wants config, nonce=69420
DEBUG | ??:??:?? 50 [NimbleBluetooth] Got 5 files in manifest
INFO  | ??:??:?? 50 [NimbleBluetooth] Start API client config
DEBUG | ??:??:?? 50 [NimbleBluetooth] Queue_size 2

[Elektron79]

It is a windows 11 pc and I used the webclient in the chrome browser. But I also noticed this behavior in earlier version with an iPhone

[github-actions[bot]]

This issue has not had any comment or update in the last month. If it is still relevant, please post update comments. If no comments are made, this issue will be closed automagically in 7 days.

[github-actions[bot]]

This issue has not had any comment since the last notice. It has been closed automatically. If this is incorrect, or the issue becomes relevant again, please request that it is reopened.