Self.lib = Library(library_path, callback_dispatcher)įile "/usr/local/lib/python3.4/site-packages/tellcore/library.py", line 312, in _init_įile "/usr/local/lib/python3.4/ctypes/_init_.py", line 429, in LoadLibraryįile "/usr/local/lib/python3.4/ctypes/_init_.py", line 351, in _init_ Auto detected elevation: 177ġ6-09-06 22:26:52 : Could not initialize Tellstick.įile "/usr/src/app/homeassistant/components/sensor/tellstick.py", line 50, in setup_platformįile "/usr/local/lib/python3.4/site-packages/tellcore/telldus.py", line 107, in _init_ ![]() ![]() Replace 'temperature_unit: ☌' with 'unit_system: metric'ġ6-09-06 22:26:52 nfig: Incomplete core config. Sep 6 22:21:10 unTRUE kernel: usb 2-1.7: new full-speed USB device number 5 using ehci-pciĪlso having these errors in the Home-Assistant Log:ġ6-09-06 22:26:51 nfig: Found deprecated temperature unit in core config, expected unit system. Sep 6 22:20:57 unTRUE kernel: usb 2-1.7: USB disconnect, device number 4 Problem is I only see this in the syslog when I plug in the device: But I have the same problem, but with a Tellstick USB device. 07:20:49.300 Detail, contrlr, Notification: Notification - TimeOut 07:20:49.300 Detail, contrlr, Removing current message 07:20:49.300 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s) 07:20:48.298 Info, Serial port /dev/ttyS0 opened (attempt 1) 07:20:48.298 Info, Trying to open serial port /dev/ttyS0 (attempt 1) 07:20:48.298 Info, mgr, Added driver for controller /dev/ttyS0 It says serial port opened, but I still get errors. On the docker, there is something called /dev/ttyS0. Is there a certain variable, path, port or device I need to specifically map on the docker container parameters beyond what I've done? Is there something completely different that I'm missing? Does this path not mean the same thing as say C:\ would I Windows? I've also tried to specifically map /dev/bus/usb/001/007 to /dev/bus/usb/001/007 and also mapped to /dev/ttyUSB0, but nothing changes. But for some reason, why I tell the docker to look at that path, it does not recognize the device. Inside the specific docker I'm looking at, without any type of mapping, if I docker exec /bin/bash into it, I can navigate to /dev/bus/usb and find the same lists of devices. I see a a few posts mentioning /dev/ttyUSB0 or /dev/ttyS0, but I don't know what the connection is. I can find the specific path of this USB device on /dev/bus/usb/001/007. This changes if I unplug and replug, but that's a problem for another day. The device I need to pass through is on Bus 001 and is Device 007. Integrated Rate Matching Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Integrated Rate Matching Hubīus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 004: ID 0781:5571 SanDisk Corp. When I run command lsusb on my unRAID console, I get:īus 002 Device 002: ID 8087:0024 Intel Corp. The one I'm using in this case is Home-Assistant.įor starters, I have located the proper USB device on my unRAID hardware. I imagine this would be the same process for any docker needing to see a USB device. From there, I would like the container to be able to read from this Z-Wave Stick. I originally posted this on a specific container support thread, but realized this is specific to the usage of docker in general, not the specific container I was using.įor transparency, I'm attempting to attach my Z-Wave stick to my unRAID console.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |