Living Legend

Looks like that could be it. I set the config to /dev/ttyACM0 and I no longer am getting the same errors.

It's the Aeon Labs Aeotec Z-Wave Z-Stick, Gen5. I do not believe it needs drivers. When I unplug and replug in the device, am I checking the syslog of my unraid system, or of my container? When I check unraid, I get this: May 24 09:14:49 Tower kernel: usb 1-1.3: USB disconnect, device number 9 May 24 09:14:57 Tower kernel: usb 1-1.3: new full-speed USB device number 10 using ehci-pci May 24 09:14:57 Tower kernel: cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device

If I do the above, and run: --device /dev/bus/usb/001/009 (it's now 009 rather than 007 after taking out and putting USB stick back in) I can go add the usbutil package (this does not stick, and needs to be added after each reset), and run lsusb. It returns the EXACT same thing running lsusb would on the unRAID terminal. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 009: ID 0658:0200 Sigma Designs, Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I tested, and even without the --device /dev/bus/usb/001/009 addition, these are still returned with lsusb. If I go to my .yaml file and add the line zwave: usb_path: /dev/bus/usb/001/009 I still get numerous errors. From the home-assistant.log file: 16-05-24 08:03:10 openzwave: Z-Wave Notification DriverFailed : {'nodeId': 255, 'notificationType': 'DriverFailed', 'homeId': 0} 16-05-24 08:03:20 homeassistant.components.zwave: zwave not ready after 30 seconds, continuing anyway From the OZW_Log file: 2016-05-24 08:09:04.146 Always, OpenZwave Version 1.4.252 Starting Up 2016-05-24 08:09:05.313 Info, Setting Up Provided Network Key for Secure Communications 2016-05-24 08:09:05.313 Warning, Failed - Network Key Not Set 2016-05-24 08:09:05.313 Info, mgr, Added driver for controller /dev/bus/usb/001/009 2016-05-24 08:09:05.314 Info, Opening controller /dev/bus/usb/001/009 2016-05-24 08:09:05.314 Info, Trying to open serial port /dev/bus/usb/001/009 (attempt 1) 2016-05-24 08:09:05.314 Error, ERROR: Failed to set serial port parameters 2016-05-24 08:09:05.314 Error, ERROR: Failed to open serial port /dev/bus/usb/001/009 2016-05-24 08:09:05.314 Warning, WARNING: Failed to init the controller (attempt 0) Suggestions?

On the docker, there is something called /dev/ttyS0. There is no ttyUSB0. If I add the extra parameter instead of --device=/dev/bus/usb/001/009:/dev/ttyS0 It says serial port opened, but I still get errors. 2016-05-24 07:20:48.298 Info, mgr, Added driver for controller /dev/ttyS0 2016-05-24 07:20:48.298 Info, Opening controller /dev/ttyS0 2016-05-24 07:20:48.298 Info, Trying to open serial port /dev/ttyS0 (attempt 1) 2016-05-24 07:20:48.298 Info, Serial port /dev/ttyS0 opened (attempt 1) 2016-05-24 07:20:48.299 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2016-05-24 07:20:48.299 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc 2016-05-24 07:20:48.299 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9 2016-05-24 07:20:48.299 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb 2016-05-24 07:20:48.299 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa 2016-05-24 07:20:48.300 Detail, 2016-05-24 07:20:48.300 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2016-05-24 07:20:49.300 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s) 2016-05-24 07:20:49.300 Detail, contrlr, Removing current message 2016-05-24 07:20:49.300 Detail, contrlr, Notification: Notification - TimeOut

These are the errors I get within the docker: 2016-05-24 06:46:01.929 Info, mgr, Added driver for controller /dev/bus/usb/001/009 2016-05-24 06:46:01.929 Info, Opening controller /dev/bus/usb/001/009 2016-05-24 06:46:01.929 Info, Trying to open serial port /dev/bus/usb/001/009 (attempt 1) 2016-05-24 06:46:01.929 Error, ERROR: Failed to set serial port parameters 2016-05-24 06:46:01.929 Error, ERROR: Failed to open serial port /dev/bus/usb/001/009 2016-05-24 06:46:01.929 Warning, WARNING: Failed to init the controller (attempt 0) EDIT: I went through the post, but it basically says what your response did. Still unsure howto connect this thing!

And these tags you mention are added to the "Extra Parameter" line in the docker setup? Should privileged be on or off? Also, when you say to check in the syslog to know if it's being assigned to ttyUSB0, do I ADD this tag, or CHANGE to this tag? I will review the oscam thread in your signature next.

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. For transparency, I'm attempting to attach my Z-Wave stick to my unRAID console. From there, I would like the container to be able to read from this Z-Wave Stick. I imagine this would be the same process for any docker needing to see a USB device. The one I'm using in this case is Home-Assistant. For starters, I have located the proper USB device on my unRAID hardware. When I run command lsusb on my unRAID console, I get: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 007: ID 0658:0200 Sigma Designs, Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The device I need to pass through is on Bus 001 and is Device 007. This changes if I unplug and replug, but that's a problem for another day. I can find the specific path of this USB device on /dev/bus/usb/001/007. I see a a few posts mentioning /dev/ttyUSB0 or /dev/ttyS0, but I don't know what the connection is. 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. But for some reason, why I tell the docker to look at that path, it does not recognize the device. 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. 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? Thanks for any insight to this issue!

I still for the life of me can't figure out how to pass my USB device connected to unRAID straight through to my docker. I'm currently using Home Assistant and I want it to be able to recognize my Z-Wave Stick. When I run command lsusb on my unRAID console, I get: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 007: ID 0658:0200 Sigma Designs, Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub UnRAID clearly recognizes my device. I have tried every combination I can think of on the "Extra Parameters" option using the --device= command, and have also tried to add a device through the "Add Configuration" screen even though I don't get how that works since there is no target. Has anyone had any luck with this?

ANd what about that Couch Potato error? Does that have something to do with the Kodi-Headless mapping? If I say to scan entire library it works, but when I notify to scan a specific directory to save time, nothing happens...

My sig has a tutorial I made a longgggg ways back, but some is still relevant. I'd ignore at least the first 3 steps and go straight to 4 or 5. Kodi-Headless isn't about centralizing a database. It's more to have an instance of Kodi running 24/7 so that updates can happen fluidly and allow your client devices to be up to date the moment they're powered on. It depends on your experience with this stuff to know how simple or detailed things needs to be explained. I'll start with a very simple explanation of how to centralize your libraries across devices. 1. Install an instance of the mariaDB docker. 2. Log in to your server using something like HeidiSQL to access your databases. Create a user/pass combo which you will use in your advancedsettings.xml file. 3. Copy the template advancedsettings.xml file on the Kodi wiki. You'll just need this part of it: <advancedsettings> <videodatabase> <type>mysql</type> <host>"YOUR UNRAID SERVER IP ADDRESS</host> <port>3306</port> <user>YOUR USERNAME</user> <pass>YOUR PASSWORD</pass> </videodatabase> <musicdatabase> <type>mysql</type> <host>YOUR UNRAID SERVER IP ADDRESS</host> <port>3306</port> <user>YOUR USERNAME</user> <pass>YOUR PASSWORD</pass> </musicdatabase> </advancedsettings> This advancedsettings.xml file needs to be placed in the userdata folder of all client devices looking to read off of the server's database. 4. Start up an instance of Kodi, add your sources and update your library. At this point, as the library is updated, the database is written to a centralized location, your unRAID server. Now, anytime a client device logs in, as long as the advancedsettings.xml file was done properly, rather than look locally, it was be routed to the centralize database. Obviously this is a super abridged version that would need much greater clarification for someone with little experience with this stuff. Maybe in the coming weeks I'll try and find time to make some sort of video showing and explaining from start to finish how to get something like this going. ******************* On a side note, if any of the pros get a shot to look at my post a few back, I still have a few questions: Question #1 - If it is important to make sure that all library scans/updates are done through the same client (Kodi-Headless), what's the optimal way to make changes to the library, such as changing which artwork you would like to appear for certain movies? Since there is no GUI do I have to do this directly in the db? Can I do it on another client device without everything burning in an eternal grease fire? Question #2 - I'm also having a random issue with Couch Potato and Kodi. I can send a notification for a full system scan, but when I ask to just scan the specific folder of the new movie, CP says it does, but Kodi never seems to get the message. Couch Potato Log Excerpt: [o.core.notifications.xbmc] Sending request to 192.168.1.3:8080: [{"jsonrpc": "2.0", "params": {"message": "Downloaded ****", "image": "https://raw.github.com/RuudBurger/CouchPotatoServer/master/couchpotato/static/images/notify.couch.small.png", "title": "CouchPotato"}, "method": "GUI.ShowNotification", "id": "GUI.ShowNotification"}, {"jsonrpc": "2.0", "params": {"directory": "/movies/****"}, "method": "VideoLibrary.Scan", "id": "VideoLibrary.Scan"}] [o.core.notifications.xbmc] Returned from request 192.168.1.3:8080: [{u'jsonrpc': u'2.0', u'id': u'GUI.ShowNotification', u'result': u'OK'}, {u'jsonrpc': u'2.0', u'id': u'VideoLibrary.Scan', u'result': u'OK'}] I thought I had the answered solved when I realized I had never mapped /movies in the container to my movie folder on the server, but this didn't solve the problem. As I mentioned, the Kodi log doesn't even have a line for this scan request. However, if I change to perform a full scan, I receive the same as above except Kodi actually runs the scan and it is shown in the Kodi log. EDIT 2: After turning on debugging, I get this message when trying to only scan specific folders: 02:20:24 T:46959299913472 DEBUG: webserver: request received for /jsonrpc 02:20:24 T:46959299913472 DEBUG: JSONRPC: Value does not match any of the enum values in type 02:20:24 T:46959091689216 NOTICE: Thread JobWorker start, auto delete: true 02:20:24 T:46959091689216 NOTICE: VideoInfoScanner: Starting scan .. 02:20:24 T:46959091689216 DEBUG: CAnnouncementManager - Announcement: OnScanStarted from xbmc 02:20:24 T:46959091689216 NOTICE: VideoInfoScanner: Finished scan. Scanning for video info took 00:00

I finally set up Kodi-Headless as a docker. I also have mariaDB as a docker to sync the libraries across my client devices. In regards to the headless instance, at this point, my usage is utilizing the fact that it's running on a server and always on. CP and Sonarr are set to notify this instance of Kodi when downloads are completed and then prompt for a library scan. After the scan, all other devices can see the updated library. Question #1 - Besides this, what are the uses of Kodi-Headless? Question #2 - If it is important to make sure that all library scans/updates are done through the same client (Kodi-Headless), what's the optimal way to make changes to the library, such as changing which artwork you would like to appear for certain movies? Since there is no GUI do I have to do this directly in the db? Can I do it on another client device without everything burning in an eternal grease fire? Thanks again for all the hard work guys. I'm going to have to think about making some more tutorials soon to give back and possibly lessen the load on all of the questions you guys are bombarded with! EDIT 1: I'm also having a random issue with Couch Potato and Kodi. I can send a notification for a full system scan, but when I ask to just scan the specific folder of the new movie, CP says it does, but Kodi never seems to get the message. Couch Potato Log Excerpt: [o.core.notifications.xbmc] Sending request to 192.168.1.3:8080: [{"jsonrpc": "2.0", "params": {"message": "Downloaded ****", "image": "https://raw.github.com/RuudBurger/CouchPotatoServer/master/couchpotato/static/images/notify.couch.small.png", "title": "CouchPotato"}, "method": "GUI.ShowNotification", "id": "GUI.ShowNotification"}, {"jsonrpc": "2.0", "params": {"directory": "/movies/****"}, "method": "VideoLibrary.Scan", "id": "VideoLibrary.Scan"}] [o.core.notifications.xbmc] Returned from request 192.168.1.3:8080: [{u'jsonrpc': u'2.0', u'id': u'GUI.ShowNotification', u'result': u'OK'}, {u'jsonrpc': u'2.0', u'id': u'VideoLibrary.Scan', u'result': u'OK'}] I thought I had the answered solved when I realized I had never mapped /movies in the container to my movie folder on the server, but this didn't solve the problem. As I mentioned, the Kodi log doesn't even have a line for this scan request. However, if I change to perform a full scan, I receive the same as above except Kodi actually runs the scan and it is shown in the Kodi log. EDIT 2: After turning on debugging, I get this message when trying to only scan specific folders: 02:20:24 T:46959299913472 DEBUG: webserver: request received for /jsonrpc 02:20:24 T:46959299913472 DEBUG: JSONRPC: Value does not match any of the enum values in type 02:20:24 T:46959091689216 NOTICE: Thread JobWorker start, auto delete: true 02:20:24 T:46959091689216 NOTICE: VideoInfoScanner: Starting scan .. 02:20:24 T:46959091689216 DEBUG: CAnnouncementManager - Announcement: OnScanStarted from xbmc 02:20:24 T:46959091689216 NOTICE: VideoInfoScanner: Finished scan. Scanning for video info took 00:00