ZigBee ( HUBSBSZ) Sengled not pairing in docker environment

Hi,
I am running latest version (0.100.2) of docker home assistant
I am unable to pair HUBSBZ-1 with any of my 4 brand new sengled bulbs
I have the following in configuration.yaml


zwave:
  usb_path: /dev/ttyUSB0

zha:
  usb_path: /dev/ttyUSB1
  database_path: /config/zigbee.db

If I delete the zigbee.db and restart docker , the file gets created
ls -al zigbee.db
-rw-r–r-- 1 root root 69632 Oct 21 20:33 zigbee.db

The following is in the home-assistant.log

"..
 
   File "/usr/src/homeassistant/homeassistant/components/zha/device_trigger.py", line 53, in async_get_triggers
    zha_device = await async_get_zha_device(hass, device_id)
  File "/usr/src/homeassistant/homeassistant/components/zha/core/helpers.py", line 149, in async_get_zha_device
    return zha_gateway.devices[ieee]
KeyError: 00:0d:6f:00:12:00:ad:29
2019-10-21 20:50:48 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.139819755362896] Error handling message: Unknown error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 19, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 177, in websocket_device_automation_list_actions
    actions = await _async_get_device_automations(hass, "action", device_id)
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 128, in _async_get_device_automations
    for domain in domains
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 102, in _async_get_device_automations_from_domain
    return await getattr(platform, function_name)(hass, device_id)
  File "/usr/src/homeassistant/homeassistant/components/zha/device_action.py", line 59, in async_get_actions
    zha_device = await async_get_zha_device(hass, device_id)
  File "/usr/src/homeassistant/homeassistant/components/zha/core/helpers.py", line 149, in async_get_zha_device
    return zha_gateway.devices[ieee]
KeyError: 00:0d:6f:00:12:00:ad:29
..."

any help will be greatly appreciated

Have you added the device to the docker run command to expose the USB stick to the container?

Thanks for taking the trouble to answer
No, but the ZWAVE works so I am assuming docker knows about both devices ?
How would I check ?
Thanks
STeven

Having the same problem, using Conbee II,
What i have done is adding on the docker compose the
devices:

  • /dev/ttyACM0
    (ttyACM0 is the device for the conbee ii)

anything else that should be done ? when adding the integrations i dont get any error,
Yet sometimes i get the above issue, and i couldn’t managed to add any zigbeee device.
(using ZHA)

Here is my docker-compose.yml for the HUSBZB-1

  homeassistant:
    container_name: homeassistant
    image: "homeassistant/home-assistant:0.100.3"
    network_mode: "host"
    volumes:
      - /opt/homeassistant:/config
      - /etc/localtime:/etc/localtime:ro
      - /etc/letsencrypt:/etc/letsencrypt:ro
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0:rwm
      - /dev/ttyUSB1:/dev/ttyUSB1:rwm
    restart: on-failure

If you are running it with docker run you would have to do:

docker run --device=/dev/ttyUSB0:/dev/ttyUSB0:rwm --device=/dev/ttyUSB1:/dev/ttyUSB1:rwm --network host homeassistant/home-assistant:0.100.3

Thanks Walt,
I was able to make it work with my config above, My full config is:

 homeassistant:
               container_name: homeassistant
               restart: always
               image: homeassistant/home-assistant
               volumes:
                 - /home/me/docker/homeassistant:/config
                 - /etc/localtime:/etc/localtime:ro
                 - /home/ezeitoun/docker/shared:/shared
               ports:
                 - 8123:8123
               devices:
                 - /dev/ttyACM0
               privileged: true
               environment:
                 - PUID=1000
                 - PGID=1000

It looks like although the original above error appear, it works
In my case, until i didnt paired a device really close to the stick nothing works,
Once i did it, the error above vanished, and i was able to pair everything.