Heltec v4 BLE bug - only first cli-command can be successful (not interactive-mode), while not restarted PC's BT-dongle

[HDDen]

Hello!

I have two devices flashed as "Companion Bluetooth" - Heltec v4 and Lilygo T-Echo. When I try to connect to the v4 node and execute a command, for example, 'meshcore-cli -d"90:XX:XX:XX:XX:F5" clock', only the first command execution is successful, with a response like "Current time : 2026-01-05 04:51:29 (1767577889)" to the console. Subsequent runs return errors - "INFO:meshcore:Couldn't find device" or "ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={})». These errors return until I reconnect my PC's bluetooth adapter manually, or do it programmatically via a python script.

There are no such problems with the other device, on the t-echo. All calls are handled normally.

Also, the node on v4 works correctly in interactive mode, never giving an error. Also, the node functions stably when my iPhone is connected to it.

I tried changing the firmware versions, from 1.9.0 to the current 1.11.0 with a full erasing, but it didn't help. I use meshcore-cli on windows 10.

I'm attaching screenshots of the console and logs, also py-script to reconnect bluetooth-dongle.

The first screenshot is a demonstration of the problem with trying to "revive" the node by resetting the BT adapter, the second is a comparison with the t-echo.

meshcore-ble-error.log

restart-bt-en.py

[fdlamotte]

I would suspect some bluetooth issue, probably firmware side ... (with some help from mccli of course ;))
There is a new bluetooth implementation in the work for esp32s, which might help solve the issue

sadly I'm in a rush right now (finalizing moving abroad) won't probably do anything before next week ...