🔨 add bluetooth support inside the devcontainer

To facilitate development and testing of this integration, it is very
useful to enable Bluetooth support in the devcontainer.

The devcontainer configuration has been updated to support this.

A manual configuration step is required on the host system, and has
been documented on the README.

.devcontainer.json

@@ -1,6 +1,9 @@
 {
     "name": "ludeeus/integration_blueprint",
     "image": "mcr.microsoft.com/devcontainers/python:3.11-bullseye",
+    "runArgs": [
+        "-v/run/dbus:/run/dbus:ro"
+    ],
     "postCreateCommand": "scripts/setup",
     "forwardPorts": [
         8123

README.md

@@ -28,6 +28,79 @@ Platform | Description
 
 <!---->
 
+## FAQ
+
+### My WalkingPad device is not detected
+
+First, make sure no other Bluetooth device is connected to your WalkingPad.
+
+If your device is still not automatically detected by Home Assistant, it's
+probably due to the fact that its bluetooth name is unknown. In this
+case, you can try to add it manually to Home Assistant.
+
+First, launch a LE scan from your host system (or any other device with a
+Bluetooth LE scanner application) to get the MAC address of your WalkingPad
+device.
+
+For example, to launch a bluetooth LE scan, on linux, you can run:
+```
+$> sudo hcitool lescan
+
+LE Scan ...
+85:AA:BB:CC:DD:FF KS-ST-A1P
+85:AA:BB:CC:EE:FF KS-ST-A1P
+```
+
+Note the MAC address (`85:AA:BB:CC:DD:FF` in the previous example), then go to
+`Home Assistant` > `Settings` > `Devices and Services` > `Add integration` > Search for `Kingsmith Walkingpad`.
+
+It should open the manual configuration form. Enter the MAC address in the
+`Device` form field, any the name of your choice in the `Name` field.
+Click on `Submit` and cross your fingers!
+
+If it works, please open an issue here and tell me the Bluetooth name of your
+WalkingPad and which model it corresponds to. This will enable me to activate
+automatic detection for this model.
+
+## FAQ for developers
+
+### How to enable my bluetooth adapter in the devcontainer ?
+
+I've wasted some time on this problem, so here are a few pointers to get a working development environment.
+I assume you're running Linux. Sorry, I don't know how to do this for other operating systems.
+
+Everything is documented on the [Home Assistant Bluetooth page](https://www.home-assistant.io/integrations/bluetooth#additional-details-for-container-core-and-supervised-installs), but here is a summary of the
+steps to be performed **on your host system**:
+
+#### 1. Install and enable DBus-Broker
+
+See the [official dbus-broker instructions](https://github.com/bus1/dbus-broker/wiki) for more details. On Ubuntu I had to run the following commands:
+
+```
+sudo apt install dbus-broker
+sudo systemctl enable dbus-broker.service
+sudo systemctl --global enable dbus-broker.service
+
+reboot
+````
+
+#### 2. Ensure that bluez is installed
+
+You need to have Bluez >= 5.63 installed on your host system.
+
+#### 3. Ensure that your dbus socket is in /run/dbus
+
+It should be OK in most case, but if your DBus socket is not
+in `/run/dbus`, you might have to tweak the .devcontainer.json (see `runArgs`).
+
+
+#### 4. Profit
+
+Then, you can run the devcontainer and start Home Assistant with `scripts/develop`.
+
+You might have a TLS error on the first run in the logs. Just restart the command and everything should be fine, your bluetooth adapter should be detected by Home Assistant.
+
+
 
 ***