ChromeOS -> Chrome 126.0.6478.132 is not seeing hub to pair, but Edge is

[n-davey]

Hi,
I have a hub with pybricks firmware installed.
Current Chrome on ChromeOS does not see the hub to pair to, but Edge on the same machine works fine.
Earlier version of Chrome (125 or earlier, I don't recall) did work.

Any thoughts or help on how this can be resolved?

[BertLindeman]

Hi,

On my windows 11, I use Google Chrome Version 126.0.6478.127 (Official Build) (64-bit) without any problem.

[laurensvalk]

Does it persist when you close the Edge browser?

Do you see any errors in the console? You can open the developer console by pressing ctrl+shift+i and selecting the Console tab:

[n-davey]

Chrome Device Log:

[dlech]

FWIW, it is working on my Chrombook with the same Chrome version. So it seems likely that it is just an issue with your computer.

Are you running Edge on the same chromebook? How was Edge installed, as an android app?

[n-davey]

Hmm thanks.. interesting.. Wonder what's changed then..

Yes Edge is on the same Chromebook, Android app installed via Play Store.

I found a test page for the Web Bluetooth API (https://googlechrome.github.io/samples/web-bluetooth/device-info-async-await.html?namePrefix=Pyb), ran this in Chrome and it can see the hub to pair with.

I deleted the data and reset the permissions for pybricks in Chrome, retried and still can't see hub to pair with, strange..

[dlech]

Maybe you tried to pair the device in the ChromeOS system settings instead of in the browser? From looking at the ChromeOS source code, it looks like devices paired this way will be filtered out in the browser. So you would have to unpair it via the ChromeOS settings first.

Although, that doesn't seem likely if it is showing up on a generic page.

Source is here if anyone else wants to have a look: https://source.chromium.org/chromium/chromium/src/+/refs/tags/126.0.6478.132:device/bluetooth/chromeos/bluetooth_utils.cc;l=315;bpv=0;bpt=0

[n-davey]

Hi,
It's not paired in OS Bluetooth, double checked that to be sure.. :)

It's interesting that the hub is visible to be paired in one tab (chrome sample) but not from another tab (pybricks)..

I'll keep tinkering.. there will be something simple somewhere that's breaking it..

[Turbopsych]

I have the exact same issue, did you find a solution?

[n-davey]

I never found a solution to the original issue. But, can report that doing a check today, the problem now seems to be resolved.
ChromeOS 128.0.6613.133 and Chrome is confirmed working again.