Lego City Hub Pybricks firmware installation fails for no reason GATT operation failed for unknown reason. on Chrome Windows 11

[mewohenlo]

Describe the bug
What is the problem?
So the error message pops up every time I have tried only when the firmware installation percentage reaches 50%

To reproduce
Steps to reproduce the behaviour:

1. Follow all the steps to the city hub firmware installation
2. Release the green power button on the hub.
3. Reaches 50%
4. See error: GATT operation failed for unknown reason.

Expected behaviour
What did you expect to happen instead?
For it to continue until it completes and I can program

Screenshots
There is a saying that a picture is worth 1000 words. Screenshots help to identify and solve problems.

[mewohenlo]

no still going

[dlech]

Make sure you have everything unplugged from the ports and you have fully charged batteries.

If you are still having trouble after that...

Are you using code.pybricks.com or beta.pybricks.com?

To troubleshoot the issue, we need logs as described in #270 or you can try reaching out to Microsoft as described in #918 (comment).

You could also try a different Bluetooth adapter. Some work better with Windows than others.

• Publish list of known compatible BLE dongles for Windows #921
• Connection failed for unknown reason.  #761

If you have another device with a different supported OS (Android, ChromeOS, Mac), you could try that too.

[tetaplaun]

Same problem here. Using a TP Link BT adapter on Win11 and code.pybricks.com. Any further suggestions?

EDIT:
Sorry, solved by this.

[laurensvalk]

If you have time, the best way to help us solve it is gather logs as described at the bottom of this post. Thanks!

[tetaplaun]

If you have time, the best way to help us solve it is gather logs as described at the bottom of this post. Thanks!

Solved by this
The instructions tell you to hold the button until it say to release it. The message appears too late (for me), therefore causing the problem. After reading the mentioned comment, it works.

[dlech]

Hopefully fixed by pybricks/pybricks-code@236ad56