+Matt Reynolds <mattreynolds@chromium.org> recently answered this on
StackOverflow: https://stackoverflow.com/a/77574518/4275660
We intentionally don't provide access to the serial number since it is a
unique persistent identifier. Can you expand on your use case for accessing
the true device serial number and why the id attribute is insufficient?
[image: Google Logo]
Reilly Grant
Software Engineer
reillyg@google.com
Google Chrome
On Fri, Dec 1, 2023 at 1:18 AM dilara.yurtalan@web.de <
dilara.yurtalan@web.de> wrote:
> Hey,
>
> my name is Dilara and I am a frontend developer from Germany.
> Currently Im working on a project where we use the web-bluetooth API.
>
> In this project we want to access the serialnumbers of our own devices.
> And thats where my problem starts and the reason why Im contacting you.
>
> I already figured out, that I first need to access the device_information
> service from the Gateway. I also receive some characteristics, like
> firmware, modelname, manufacturer.
> When I try to access the serial_number_string characteristics, I get the
> information, that this UUID is blocked on the browser console.
>
> Im very new to this whole web-bluetooth topic, therefore my question to
> you:
> is there any way to access the serial number on my own web app with my own
> device from my company Im working for?
> If so, how?
>
> I would be very happy if there would be a way for me to access this
> information.
>
> I attached you the console error and the code snipped.
>
> Have a nice day
> Dilara :)
>