The hub took too long to respond. Restart the hub and try again.

[ferhatozdmr]

Question
I ghis error when I am trying to connect my movehub to macos 10.15.7

Context
What are you trying to accomplish that led to this question?

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

[ferhatozdmr]

I have tried too many times. reinstalled original firmware and tried again. but I get the same error.

[dlech]

Could you please try some of the things in our Bluetooth Troubleshooting Guide to help us figure out what the problem is?

[ferhatozdmr]

Hi David, I couldn't get much info I guess. But here are some screenshots:

I can control it with out any problems through https://legoboost.azurewebsites.net/ this web site. I know it uses totally different protocol but I believe this shows that there is no hardware or communication issue between the hub and my computer. In pybricks case, it finds my hub, starts flashing the drive only at the last step it gives this error.

[ferhatozdmr]

I have installed the firmware on another windows machine, and now I connect it to my mac without ant issues. I don't know what the problem is installing firmware on a mac but if anybody has similar problem on mac, install the firmware on a windows pc and use your hub with your mac.

[dlech]

If you are able to capture the Bluetooth packets on your Mac, it would be interesting to compare it to #256.

[dlech]

We just released pybricks-code@1.0.0-rc.2 that fixed #256. Could you try flashing the firmware on your Mac using this new version to see if the problem on Mac is fixed as well?

[ferhatozdmr]

Hi David, Unfortunately still the same problem. I get the same error.”The hub took to long to respond” as soon as the installation reaches to %100. I did not have any problem when I try to flash using windows pc though.

…

On 17 May 2021, at 22:29, David Lechner ***@***.***> wrote:  We just released ***@***.*** that fixed #256. Could you try flashing the firmware on your Mac using this new version to see if the problem on Mac is fixed as well? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

[dlech]

Thanks for checking. If you have time, it would still be helpful to do a Bluetooth packet capture on the Mac. It would be nice if we could fix it in case other people have the same problem.

[ferhatozdmr]

Hi David, I will try to do my best for packet capture but I am not familiar how exactly to do it. I tried to follow your documentation but when I run the capture it seems like it is capturing everything, I couldn’t seperate just the bluetooth that the hub is connected to. Or I am doing it completely wrong :) I will give it another try.

…

On 17 May 2021, at 22:51, David Lechner ***@***.***> wrote:  Thanks for checking. If you have time, it would still be helpful to do a Bluetooth packet capture on the Mac. It would be nice if we could fix it in case other people have the same problem. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

[dlech]

It's been a while since I did that so I don't remember exactly where it is, but there are some filters in the PacketLogger.app that can be enabled to narrow it down to just Bluetooth traffic.

[laurensvalk]

I get the same error.”The hub took to long to respond” as soon as the installation reaches to %100.

I think I can reproduce this consistently on Android with the City Hub.

And I can add/confirm that the hub then goes back to blinking pink, so there's no firmware on the hub; it's not just a matter of restarting the hub.

If this is not reproducable for you @dlech, I'll try to find logs as needed.

[dlech]

I would rather start a new issue about Android since this one is about macOS.

[laurensvalk]

It was more to confirm that it can in fact get to 100% and still be without a valid firmware, which we weren't sure about yet in a recent discussion.

[pbochynski]

Hi,
I was struggling with the same issue today. Macbook Pro and Lego Move Hub. Firmware installation was failing with different reasons. Usually, the hub took too long to respond, but sometimes it was unexpected GATT error. Always few seconds after erasing the firmware. I tried all troubleshooting, started to analyze bluetooth logs, etc.
Then I had some hunch and I disconnected my magic mouse (connected by bluetooth). And now flashing works every time!
So my advice - disconnect all other bluetooth devices before you start flashing your hub.

[laurensvalk]

On the Move Hub specifically, fresh batteries seem to make a big difference as well.

[dlech]

Closing since Pybricks Code and the firmware has changed significantly since the initial report, so any reports of the same error message are not necessarily the same issue.

If anyone who has a problem that is fixed by turning off other Bluetooth devices, please capture Bluetooth logs as described here and post the results in #938. This seems to b a common problem and could help other users if we can understand it better.