![]() Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2. So you can use this keyword on Google to find related information and users having similar issues with the Bluetooth adapter. Unifying Receiverīus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) The 0a12:0001 part is the most important part, because it is the ID of the chipset running inside the Bluetooth adapter. LibreELEC:~ # cat /sys/firmware/devicetree/base/model Using CSR8510 external BT dongle instead because of metal case. Internal bluetooth is disable via dtoverlay=disable-bt in config txt. Even when using the CLI the GUI tries to show the code field with the invisible numbers. I tried it on the CLI, which allowed me to see the pairing code numbers, but it's not possible to enter them on the keyboard. Additionally I was not able to enter any numbers and press return, the GUI is locked in that state. ModuleNotFoundError: No module named 'bluetooth'īus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 003: ID 1005:b155 Apacer Technology, Inc.īus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.Problem: Adding a bluetooth keyboard works until the code to enter in the keyboard for pairing is shown. Result = self.fn(*self.args, **self.kwargs)įile "/usr/src/app/homeassistant/components/device_tracker/bluetooth_tracker.py", line 35, in setup_scanner Thus when enabling the bluetrooth tracker in HA config i get error at startup: Error setting up platform bluetooth_trackerįile "/usr/src/app/homeassistant/components/device_tracker/_init_.py", line 183, in async_setup_platformįile "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run Tried the procedure suggested by and yes the docker command created directory /dev/ttyUSB0 as mentioned. : could not open port /dev/ttyUSB0: Is a directory: ‘/dev/ttyUSB0’ Raise SerialException(msg.errno, “could not open port ”.format(self._port, msg)) Ser = rial_for_url(*args, **kwargs)įile “/usr/local/lib/python3.6/site-packages/serial/ init.py”, line 88, in serial_for_urlįile “/usr/local/lib/python3.6/site-packages/serial/serialposix.py”, line 247, in open ![]() IsADirectoryError: Is a directory: ‘/dev/ttyUSB1’ĭuring handling of the above exception, another exception occurred:įile “/usr/src/app/homeassistant/components/sensor/dsmr.py”, line 116, in connect_and_reconnectįile “/usr/local/lib/python3.6/asyncio/coroutines.py”, line 212, in coroįile “/usr/local/lib/python3.6/site-packages/serial_asyncio/ init.py”, line 410, in create_serial_connection Self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK) 12:05:30 ERROR (MainThread) Error connecting to DSMRįile “/usr/local/lib/python3.6/site-packages/serial/serialposix.py”, line 244, in open I create my containers using the following command:ĭocker run -d -e TZ=Europe/Amsterdam -name=“hass-0-67-1” -restart=always -privileged -net=host -p 8123:8123 -v /share/HomeAssistant/hass/config:/config -v /dev/ttyUSB0:/dev/ttyUSB0 -v /dev/ttyUSB1:/dev/ttyUSB1 homeassistant/home-assistant:0.67.1 python -m homeassistant -config /configĪnyone else got the same problems? Tried reverting back to working docker image 0.67.1 and safestored config. When looking at the dev directory there are indeed two folders created, rights look ok. It has been running very smoothly for a couple of months but started to throw errors on enabling my DSMR and RFXTRX devices with error 21 referring to a directory.īoth devices are listed when using “dmesg | grep tty” as ttyUSB0 and ttyUSB1. Starting a couple of days ago I am unable to get my USB devices active in HA anymore running in containerstation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |