6.3.0: Bluetooth commissioning is not available

[olavt]

I tried to commission a Matter over Thread device using 6.3.0 and got this error:

Bluetooth commissioning is not available.

6.2.2 works fine.

[marcelveldt]

You need to assign a bluetooth adapter when starting the server. Not sure if we also expose that to docker

[olavt]

Can you explain a bit more on how this is working and why behavior changed?

[olavt]

Shouldn't the new releases default to the 6.2.2 behavior if the new Bluetooth capabilities are not used / specified and not fail?

[agners]

Can you explain a bit more on how this is working and why behavior changed?

The behavior changed with #799.

To restore what the Server did before, just pass --bluetooth-adapter 0 to the container.

Shouldn't the new releases default to the 6.2.2 behavior if the new Bluetooth capabilities are not used / specified and not fail?

The problem is that, at least in the past, there were issues when Home Assistant and the Matter Server used the same adapter. So rather then default to adapter 0, currently Bluetooth is disabled so the user needs to make a conscious decision which adapter to use (and potentially disable on HA side).

[marcelveldt]

Can you actually pass that to the container or do we need to add a environmental variable ?

[olavt]

Passing "--bluetooth-adapter 0" to the "docker run" command does not work.

It would be great if a feature could be added to support setting this option when running in a Docker container.

[agners]

I just checked, it works here. Make sure you pass the default command line (as in CMD of the Dockerfile) as well! So e.g.

    ...
    ghcr.io/home-assistant-libs/python-matter-server:stable --storage-path /data --paa-root-cert-dir /data/credentials --bluetooth-adapter 0

Also created a PR to clarify this in the readme, see #826.

[olavt]

Thanks! Adding the command options after the image name works!