Mike G

I found that if you continue to use the same connection to the modem ( mine is a B535-333) ... that after a few minutes (maybe 300 seconds or calling...

Same here... boot loop with TLS. Then it started working. Unfortunately, I didn't have logcapture in minicom running when it started working at the time. Will see if I can...

> I should also mention the T3-S3's and Heltecs are having this same issue. So it's not even a T-deck related issue. > > Is anyone using a custom MQTT...

I have been ill the past three weeks, better now but a lot of things have piled up. Nice that it has been committed. Let's keep this open for now....

> sorry - I just noticed this bug (thanks @GUVWAF !). I think I just pushed identical changes in [geeksville@d017fc7](https://github.com/geeksville/Meshtastic-esp32/commit/d017fc7a5d392eb35b197c104a33ab2c533bc6ea) . I'll also be adding a commit tomorrow to fix...

> File "C:\Users\v-b2\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\bleak\backends\winrt\client.py", line 974, in start_notify await winrt_char.write_client_characteristic_configuration_descriptor_async( OSError: [WinError -2140864507] The attribute requires authentication before it can be read or written The same with linux... when not paired....

Meshtastic python-cli doesn't do it yet... but the may be a prompt that shows elsewhere regarding the pin. not sure for windows... but in linux shell it's bluetoothctl .. depending...

As mentioned [here...](https://github.com/meshtastic/firmware/issues/3760#issuecomment-2247769450) haven't been able to do anything with this. Have a chance to look at this again now. Todo: * add the original HELTEC_TRACKER to the `#ifdef` *...