Barry Byford comments

Results 87 comments of


                                            Barry Byford

Outdated docs about Peripheral config

Yes, well spotted. Looks like they got missed with 7e4bf7459c98ad592f20a34bffe96bd599e1d618

Outdated docs about Peripheral config

No, you should not need to use `sudo`. As the `ukBaz.bluezero` name is not being claimed then it can be done without `sudo`

Outdated docs about Peripheral config

When you run `bluetoothctl` do you have to run that with `sudo` also?

Outdated docs about Peripheral config

OK, let me run some tests

Outdated docs about Peripheral config

I've done a fresh install of Bluezero and checked that there is no `ukBaz.bluezero` is `/etc/dbus-1/system.d/`. I think your issue is coming from else were. ``` (venv) [bash]python-bluezero $ python...

Outdated docs about Peripheral config

I've tested it on two systems: ``` $ uname -a Linux TestMachine1 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST 2021 armv7l GNU/Linux ``` And ``` $ uname -a Linux...

Outdated docs about Peripheral config

I think it is adding user `pi` to group `bluetooth` that is the key bit. ``` pi@raspberrypi4b:~ $ sudo usermod -G bluetooth -a pi ```

Outdated docs about Peripheral config

OK. I think this sounds like a general RPi setup rather than an issue with Bluezero. Can I go ahead and close this issue?

BlueZ DBus API changes after 5.43

doc/device-api.txt ``` string AddressType [readonly] Possible values: "public" - Public address "random" - Random address ```

Allow services to be primary without forcing them to be advertised

The original vision for Bluezero was to have [three levels of API](https://github.com/ukBaz/python-bluezero/blob/main/docs/overview.rst#bluezero-api-complexity). The thought being that through the use of "sensible defaults" people could get something up and running quickly....