From 7dc66611cdfbefcea0d290e01e0fbd4b873908c6 Mon Sep 17 00:00:00 2001 From: Volker Stolz Date: Sun, 23 Jul 2023 23:24:41 +0200 Subject: [PATCH] Add limitations of using containers for developing hardware (#1672) Co-authored-by: Franck Nijhof --- docs/development_environment.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/development_environment.mdx b/docs/development_environment.mdx index f2bd5184..4987b9d6 100644 --- a/docs/development_environment.mdx +++ b/docs/development_environment.mdx @@ -21,6 +21,10 @@ You'll need to set up a development environment if you want to develop a new fea The easiest way to get started with development is to use Visual Studio Code with devcontainers. This approach will create a preconfigured development environment with all the tools you need. This approach is enabled for all Home Assistant repositories. [Learn more about devcontainers.](https://code.visualstudio.com/docs/devcontainers/containers) +:::note +As this approach uses containers, you may face challenges exposing hardware like USB devices & adapters (onboard Bluetooth, Zigbee, ...) into the container for testing. This is possible when developing on a Linux host; however, you cannot directly access such hardware if you are using a Windows or MacOS computer for development. +::: + **Prerequisites** - [Docker](https://docs.docker.com/get-docker/)