I am running container HA. I would like to give it access to my Bluetooth dongle for some devices. It is currently running in default network_mode=bridge . Keeping it that way is much better because network_mode=host would mean I would have to expose ports on a dozen of other containers (Piper, Whisper, OpenWakeWord, Music Assistant…) if I want HA to be able to connect to them. This is really not ideal, I prefer to keep everything in a virtual docker network.
Macvlan is best docker networking method for HA in container. Trust me, you will love it. Also you can still use your services network to connect to other containers. It will also eliminate the mdns issues and other problems from using bridge networking
jchh
(my username is my initials (and my first name isn't John))
3
Is there an idiot’s guide to Macvlan? I have always struggled understanding it.
To be fair setting up macvlan gets complicated for those using Portainer. I honestly hadn’t realized this until I started rereading the docs posted above.
If using command line you can simply follow docker docs.
If using portainer there are actually 2 steps.
Step 1. Setup the network configuration to use the ethernet interface
step 2. create the network to use macvlan config setup in step1
STEP1
The portainer setup is pretty straigtforward and same settings of command line.
for me I have server network that uses IP range 192.168.10.1 - 224 and I want HA in this IP range so I setup docker macvlan config in portainer to use this
My DHCP does not assign within the IP RANGE I used. Docker will automatically assign the IP but when I create container I manually assign the IP. In either case I want to make sure docker and my router arent assigning same IPs so be to prevent this.
It is also possible to use IPV6 range
STEP2
You need to actually create the docker network that the containers will attach to and use.
after this the network is ready for use like below
I define the mac address and IP for the container so it shows in my router properly and IP is static.
On my LAN, I now have new devices showing up for each container I connected to that network. Is that normal ? Is there a way to still have them using the IP of the server or is it the normal behaviour ? I followed the docker docs a bit blindly, do you have recommendations ? I didn’t run into issues even when using Portainer. You can create networks directly from the compose in Portainer, no need to manually create it in Portainer network UI.
If networking is container to container just use docker network and no need to open port. If you notice my example I make “homeassistant” network. Maria db has no external connection and container connect to it at the hostname “hass_db” that instead of an IP.
Normally if you use macvlan you won’t use server IP. If you want to use server ip just use normal bridge mode. I use both. I use macvlan for Ha specifically because things like HomeKit and emulated hue don’t work with bride mode.
Side note.
You cannot connect to container using bridge mode from macvlan container using hostip:port. You MUST use Docker network as hostip:port is blocked to macvlan.
So Macvlan works great for DLNA players for example, and still allows me to use my bridges network. So it is great, but I found a limitation with this addon:
This addon is required to scan for nearby BLE devices, like my bluetooth scale.
When using Macvlan, it doesn’t find the hci0 bluetooth interface. What is strange is that HA’s bluetooth integration finds hci0, but it is useless for my devices. I am trying to understand why HA’s bluetooth integration works with Macvlan but not BLE monitor. I made a post about this in hope of finding more information [Bug]: Doesn't work with Docker macvlan - Bluetooth interface is not available · Issue #1301 · custom-components/ble_monitor · GitHub
Macvlan can’t connect to localhost and localhost cannot connect macvlan. Sorry, I should have mentioned this limitation. This holds true for docker container on same Host attempting connection to macvlan.
I’m not familiar with blue monitor but if it is integration or docker container you MUST use seperate docker bridge network for this communication. This is also better method.
Ok I see the limitation, it maybe what is blocking me from using BLE Monitor. But what do you mean by using a seperate docker bridge network for this communication ? My HA is already on a bridge network (so that Caddy can access HA to expose it) in addition to the macvlan network. How can I set that BLE Monitor uses a different network ? It only asks for a bluetooth interface mac address.
After reading the integrations docs I think maybe you just need to use the correct Mac. I presume it used a default Mac that is incorrect. According to below you should check the logs for available Mac. I would either test 5hem one by one if multiple are available or set it to use all as initial test.
bt_interface
MAC address of the Bluetooth interface/adapter (MAC address or list of multiple MAC addresses or “disable”)(Optional) This parameter is used to select the Bluetooth-interface of your Home Assistant host. When using YAML, a list of available Bluetooth-interfaces available on your system is given in the Home Assistant log during startup of the Integration, when you enable the Home Assistant logger at info-level. In the UI, both the MAC address and the hci number will be shown. If you don’t specify a MAC address, by default the first interface of the list will be used. If you want to use multiple interfaces in YAML, you can use the following configuration:
EDIT
I check log in you GitHub post and below look like blue monitor find Mac but cannot use it. Can you confirm what this Mac is for. Maybe you can assign Mac to docker bridge network and force it to use that if macvlan cause the problem
2024-01-17 22:17:05.422 DEBUG (MainThread) [custom_components.ble_monitor] Initializing BLE Monitor entry (config entry): <homeassistant.config_entries.ConfigEntry object at 0x7f75239e40>
2024-01-17 22:17:05.422 DEBUG (MainThread) [custom_components.ble_monitor] async_setup_entry: domain {‘bt_interface’: [‘00:1A:7D:DA:71:15’], ‘discovery’: False, ‘devices’: [{‘mac’: ‘0C:95:41:D7:4A:F8’, ‘report_unknown’: False, ‘restore_state’: ‘default’, ‘consider_home’: 180, ‘reset_timer’: 35, ‘track_device’: False, ‘use_median’: ‘default’, ‘tracker_scan_interval’: 20}], ‘report_unknown’: ‘Off’, ‘restore_state’: False, ‘batt_entities’: True, ‘period’: 60, ‘bt_auto_restart’: False, ‘hci_interface’: , ‘active_scan’: False, ‘use_median’: False, ‘log_spikes’: False, ‘is_flow’: False, ‘ids_from_name’: True}
2024-01-17 22:17:05.423 INFO (MainThread) [custom_components.ble_monitor] Available Bluetooth interfaces for BLE monitor: [“Don’t use Bluetooth adapter”]
2024-01-17 22:17:05.423 ERROR (MainThread) [custom_components.ble_monitor] Bluetooth interface with MAC address 00:1A:7D:DA:71:15 is not available
2024-01-17 22:17:05.423 WARNING (MainThread) [custom_components.ble_monitor] No configured Bluetooth interface was found, using default interface instead
2024-01-17 22:17:05.424 DEBUG (MainThread) [custom_components.ble_monitor] HCI interface is [‘disable’]
2024-01-17 22:17:05.424 DEBUG (MainThread) [custom_components.ble_monitor] async_setup_entry: {‘bt_interface’: [‘disable’], ‘discovery’: False, ‘devices’: [{‘mac’: ‘0C:95:41:D7:4A:F8’, ‘report_unknown’: False, ‘restore_state’: ‘default’, ‘consider_home’: 180, ‘reset_timer’: 35, ‘track_device’: False, ‘use_median’: ‘default’, ‘tracker_scan_interval’: 20}], ‘report_unknown’: ‘Off’, ‘restore_state’: False, ‘batt_entities’: True, ‘period’: 60, ‘bt_auto_restart’: False, ‘hci_interface’: [‘disable’], ‘active_scan’: False, ‘use_median’: False, ‘log_spikes’: False, ‘is_flow’: False, ‘ids_from_name’: True}
2
I have tried manually specifying the mac address in the yaml file like you show it (instead of letting the addon wizard detect it), and in both cases I have Bluetooth interface with MAC address 00:1A:7D:DA:71:15 is not available . This mac address is the address of the bluetooth adapter on the host. I can see it by doing. “hcitool dev” on the host. I’m not sure if setting this in docker would work as it is not the mac address of a network adapter.
