Can't Reconnect paired device after power cycling device #2

Fedack · 2021-09-17T07:36:39Z

When I attempt to reconnect a keyboard that's already been paired with Windows 10, I get this:
Started advertising
Central connected: 0
Central disconnected

Connecting for the first time seems to be fine, but as soon as I do a reset, it doesn't work.

Heerkog · 2021-09-17T07:52:56Z

This is odd. You're mentioning a reset. Is this a full power cycle on the keyboard? If so, the Bluetooth might require pairing again.

Note that this package does not (yet?) support Bluetooth bonding.

Fedack · 2021-09-17T08:49:07Z

What's happening is that it pairs fine the first time, then any time I do a d.start() it requires forgetting it in Windows Bluetooth then adding it again. I see, well that's unfortunate. Is there any intention to support it because aside of that, everything works superbly and was easy to implement. That is literally the only thing that'd prevent usage. For a peripheral being unable to pair once again is a requirement at this point. That said, it seems to be ATTEMPTING to. Windows tries to pair again but it seems the device rejects the pairing, then it tries again and again, it goes in a pairing loop.

…

On Fri, Sep 17, 2021 at 3:53 AM Heerko Groefsema ***@***.***> wrote: This is odd. You're mentioning a reset. Is this a full power cycle on the keyboard? If so, the Bluetooth might require pairing again. Note that this package does not (yet?) support Bluetooth bonding. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH7Y3L6IQ55J3X75H3JQPJLUCLXWHANCNFSM5EGMW6CQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

Heerkog · 2021-09-17T09:04:54Z

I'm assuming you are using my keyboard example and that you're calling d.stop() before calling d.start() for the second time.

The way this simple keyboard example works is that in the init, it calls self.keyboard.start(), where keyboard is the device from the package. When you call d.stop(), it calls self.keyboard.stop(), which stops all Bluetooth services. When you then call d.start(), it never calls self.keyboard.start() again. If you want this start/stop behavior, I suggest implementing a d.restart() method that first calls self.keyboard.start() and then calls the d.start() loop.

I hope this solves the issue!

Fedack · 2021-09-17T09:17:25Z

The issue I am experiencing is where I reset the device (by pressing the button or unplugging) then it tries to start again but doesn't succeed in reconnecting to Windows.

Heerkog · 2021-09-17T09:29:15Z

Ok, thanks. I think this is an issue where (somehow) Windows doesn't recognize the device as the same one that was paired earlier. I'm unsure why this is happening. It could be the lack of bonding, but I'm unsure. It could also be another Bluetooth issue. I would need to look into this, but can't promise quick results. As a temporary solution, you could consider starting/stopping the device and putting the device in some deep sleep mode instead of fully power cycling.

Fedack · 2021-09-17T09:47:58Z

Thank you for your answers, I'll try to fiddle with it. Hopefully you figure it out.

Heerkog · 2021-09-22T10:08:15Z

I have been able to replicate your issue. The issue appears when the bluetooth device is restarted either through a hardware reset or by the software calling stop(), creating a new device, and calling start() for the newly created device.

The issue is indeed a pairing/bonding issue. as confirmed through this MicroPython issue.

I have pushed a new version of the package, for which bonding and secure pairing can be enabled, that should work. I say should, because the ESP32 implementation of MicroPython does NOT support this behavior (as confirmed in the linked issue). I own only ESP32 devices and, therefore, can't test properly. Calling methods related to bonding, or secure pairing, on an ESP32 will result in errors. In case your hardware is not an ESP32 device, you may try the code from my latest push and call set_bonding(True) and set_le_secure(True) before calling start() from the package. Please do let me know about the results! In case your device is also an ESP32 device, it seems we will both have to wait until the behavior is supported in a future MicroPython build (if ever).

Fedack · 2021-09-22T10:12:41Z

Well, that's unfortunate since my device is an esp32. Thank you for your hard work. I'll keep it in mind for the future when I select hardware for ble. Do you reckon esp8266 have the same issue?

…

On Wed., Sep. 22, 2021, 6:08 a.m. Heerko Groefsema, < ***@***.***> wrote: I have been able to replicate your issue. The issue appears when the bluetooth device is restarted either through a hardware reset or by the software calling stop(), creating a new device, and calling start() for the newly created device. The issue is indeed a pairing/bonding issue. as confirmed through this <micropython/micropython#5767> MicroPython issue. I have pushed a new version of the package, for which bonding and secure pairing can be enabled, that *should* work. I say *should*, because the ESP32 implementation of MicroPython does NOT support this behavior (as confirmed in the linked issue). I own only ESP32 devices and, therefore, can't test properly. Calling methods related to bonding, or secure pairing, on an ESP32 will result in errors. In case your hardware is not an ESP32 device, you may try the code from my latest push and call set_bonding(True) and set_le_secure(True) before calling start() from the package. Please do let me know about the results! In case your device is also an ESP32 device, it seems we will both have to wait until the behavior is supported in a future MicroPython build (if ever). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH7Y3LY37NDQDG2MLVFWV6LUDGTJTANCNFSM5EGMW6CQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

Heerkog · 2021-09-22T10:25:28Z

The MicroPython Bluetooth documentation notes the following under the Pairing and bonding section:

This is currently only supported when using the NimBLE stack on STM32 and Unix (not ESP32).

This is all I know.

Fedack · 2021-09-22T10:28:20Z

Alright, thank you. Good thing this was a personal project and nothing more. Ultimately it's just an annoyance but can be worked around. I'm still surprised something as bad was left in. Esp32 is super popular and mostly because of its Bluetooth. Oh, wait esp8266 doesn't even have Bluetooth so that answers that question.

…

On Wed., Sep. 22, 2021, 6:25 a.m. Heerko Groefsema, < ***@***.***> wrote: The MicroPython Bluetooth implementation notes the following under the Bonding section <https://docs.micropython.org/en/latest/library/bluetooth.html#pairing-and-bonding> : This is currently only supported when using the NimBLE stack on STM32 and Unix (not ESP32). This is all I know. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH7Y3LYR7MHBOHKNJG4NYJTUDGVKHANCNFSM5EGMW6CQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

jd3096-mpy · 2022-07-26T04:41:49Z

Now esp32 micropython supported Pairing and bonding section,I have tested,it worked.
But esp32 is still can't auto reconnect paired device after power cycling device.
How to make it work?

Heerkog · 2022-07-26T07:42:19Z

Now esp32 micropython supported Pairing and bonding section,I have tested,it worked.

Do you have a source for this information? The documentation still says it's not supported for ESP32.

But esp32 is still can't auto reconnect paired device after power cycling device. How to make it work?

Call mouse.set_bonding(True) before mouse.start().

jd3096-mpy · 2022-07-26T09:10:27Z

Now esp32 micropython supported Pairing and bonding section,I have tested,it worked.

Do you have a source for this information? The documentation still says it's not supported for ESP32.

But esp32 is still can't auto reconnect paired device after power cycling device. How to make it work?

Call mouse.set_bonding(True) before mouse.start().

Thanks here is link
micropython/micropython#7008

Heerkog · 2022-07-26T09:47:40Z

Nice! Four days ago.

Can you try calling _ble.gap_pair(self.conn_handle) on line 243 and let us know if that works?

jd3096-mpy · 2022-07-26T11:47:00Z

_ble.gap_pair(self.conn_handle)

I test it with android phone,
I add code on line 243,it works
everytime esp32 restart, the phone remind me to pair
but the normal status is pair at the first time ,auto connected later
I try to Call set_bonding(True) before start() but it doesn't work
still disconnected instantly

Server created
get secret:  10 0 b'irk'
BLE on
Registering services
Writing service characteristics
Writing device information service characteristics
Writing battery service characteristics
Writing hid service characteristics
Advertiser created:  Mouse  with services:  [UUID(0x1812)]
Server started
Started advertising
Central connected:  1
Central disconnected:  1

when pair first time ,here are the print codes:

Server created
get secret:  10 0 b'irk'
BLE on
Registering services
Writing service characteristics
Writing device information service characteristics
Writing battery service characteristics
Writing hid service characteristics
Advertiser created:  Mouse  with services:  [UUID(0x1812)]
Server started
Started advertising
Central connected:  1
encryption update 1 1 0 1 16
Connection update
Connection update
Unhandled IRQ event:  4
Unhandled IRQ event:  4
Unhandled IRQ event:  4
Unhandled IRQ event:  4
Unhandled IRQ event:  4
Unhandled IRQ event:  4
Unhandled IRQ event:  4

Unhandled IRQ event: 4 means
_IRQ_GATTS_READ_REQUEST = const(4) not reply?

Heerkog · 2022-07-26T16:07:00Z

I'm going to assume that the _IRQ_GATTS_READ_REQUEST returns an event stating _GATTS_ERROR_INSUFFICIENT_ENCRYPTION, _GATTS_ERROR_INSUFFICIENT_AUTHENTICATION or something similar.

After calling set_bonding(True), can you call set_le_secure(True)?

You can set i/o capabilities by calling set_io_capability(capability) if you want. The standard value for this is _IO_CAPABILITY_NO_INPUT_OUTPUT with passkey 1234.

Heerkog · 2022-07-29T10:50:24Z

@jd3096-mpy did this work?

jd3096-mpy · 2022-08-21T03:51:22Z

@jd3096-mpy did this work?

passkey works
but it still can't connected auto after reboot

Heerkog changed the title ~~Can't Reconnect~~ Can't Reconnect paired device after power cycle Sep 17, 2021

Heerkog changed the title ~~Can't Reconnect paired device after power cycle~~ Can't Reconnect paired device after power cycling device Sep 17, 2021

Heerkog pinned this issue Jan 21, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can't Reconnect paired device after power cycling device #2

Can't Reconnect paired device after power cycling device #2

Fedack commented Sep 17, 2021

Heerkog commented Sep 17, 2021

Fedack commented Sep 17, 2021 via email

Heerkog commented Sep 17, 2021 •

edited

Fedack commented Sep 17, 2021

Heerkog commented Sep 17, 2021

Fedack commented Sep 17, 2021

Heerkog commented Sep 22, 2021

Fedack commented Sep 22, 2021 via email

Heerkog commented Sep 22, 2021 •

edited

Fedack commented Sep 22, 2021 via email

jd3096-mpy commented Jul 26, 2022

Heerkog commented Jul 26, 2022

jd3096-mpy commented Jul 26, 2022

Heerkog commented Jul 26, 2022

jd3096-mpy commented Jul 26, 2022 •

edited

Heerkog commented Jul 26, 2022 •

edited

Heerkog commented Jul 29, 2022

jd3096-mpy commented Aug 21, 2022

Can't Reconnect paired device after power cycling device #2

Can't Reconnect paired device after power cycling device #2

Comments

Fedack commented Sep 17, 2021

Heerkog commented Sep 17, 2021

Fedack commented Sep 17, 2021 via email

Heerkog commented Sep 17, 2021 • edited

Fedack commented Sep 17, 2021

Heerkog commented Sep 17, 2021

Fedack commented Sep 17, 2021

Heerkog commented Sep 22, 2021

Fedack commented Sep 22, 2021 via email

Heerkog commented Sep 22, 2021 • edited

Fedack commented Sep 22, 2021 via email

jd3096-mpy commented Jul 26, 2022

Heerkog commented Jul 26, 2022

jd3096-mpy commented Jul 26, 2022

Heerkog commented Jul 26, 2022

jd3096-mpy commented Jul 26, 2022 • edited

Heerkog commented Jul 26, 2022 • edited

Heerkog commented Jul 29, 2022

jd3096-mpy commented Aug 21, 2022

Heerkog commented Sep 17, 2021 •

edited

Heerkog commented Sep 22, 2021 •

edited

jd3096-mpy commented Jul 26, 2022 •

edited

Heerkog commented Jul 26, 2022 •

edited