[Bug] Unexpected error when connecting too fast.

[laurensvalk]

Original issue
When connecting to a hub after turning it on, there is often a Bluetooth error. Trying again fixes it.

This has happened for as long as I remember, but reproducing it has been an issue.

Reproducible variant
When quickly connecting to a hub after disconnecting, there is often a Bluetooth error. Trying again fixes it.

This seems quite similar.

To reproduce

The following is done with an Inventor Hub with the latest firmware, but I have previously seen this happen with all hubs.

Screencast.from.18-10-22.09.38.10.webm

Is it possible to wait a while for getPrimaryService to get ready?

[dlech]

What operating system are you using? We have quite a few reports already for this error on Windows.

We've already added a 1 second delay in pybricks/pybricks-code@a869675 to try to work around this.

Can you include Wireshark logs, D-Bus logs, etc?

[laurensvalk]

Ubuntu 22.04.

I might be able to get logs on Thursday or Friday.

[dlech]

Does pybricks/pybricks-micropython@1815b8e make a difference?

[laurensvalk]

Does pybricks/pybricks-micropython@1815b8e make a difference?

Doesn't seem like it.

It does seem to be triggered way less often, or even solved entirely*. I'll keep an eye out for it today.

*There's a slight UX issue remaining, so I'll post that over in #600

[laurensvalk]

We've already added a 1 second delay in pybricks/pybricks-code@a869675 to try to work around this.

Interestingly, even a 10 second delay here doesn't help.

By contrast, waiting 10 seconds before clicking the button always works.

[dlech]

Since we have made an improvement, should we call this good enough and close the issue?