blackwinds

sudo cat /var/log/upstart/bluetoothd.log ... 2018-12-31T02:40:32-0800 btacd stoped. 2018-12-31T02:41:38-0800 Mon Dec 31 02:41:38 PST 2018 2018-12-31T02:41:38-0800 start bluetoothd 2018-12-31T02:41:38-0800 going to start btacd 2018-12-31T02:41:38-0800 btacd started.

sudo cat /var/log/messages | grep -i blue ... 2018-12-31T02:40:37-08:00 DiskStation [84869.599934] init: bluetoothd main process (23812) killed by KILL signal 2018-12-31T02:41:38-08:00 DiskStation bluetoothd[8765]: Failed to open RFKILL control device 2018-12-31T02:41:39-08:00 DiskStation bluetoothd[8765]: Unknown command complete for opcode 19

admin@DiskStation:~$ hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 5C:F3:70:92:D5:8F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:37487 acl:0 sco:0 events:612 errors:0 TX bytes:36935 acl:0 sco:0 commands:609 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'DiskStation-0' Class: 0x6c0100 Service Classes: Rendering, Capturing, Audio, Telephony Device Class: Computer, Uncategorized HCI Version: 4.0 (0x6) Revision: 0x153a LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15)

admin@DiskStation:~$ dmesg | grep -i blue [ 16.954370] Bluetooth: Core ver 2.19 [ 16.954385] Bluetooth: HCI device and connection manager initialized [ 16.954392] Bluetooth: HCI socket layer initialized [ 16.954393] Bluetooth: L2CAP socket layer initialized [ 16.954397] Bluetooth: SCO socket layer initialized [ 16.956755] Bluetooth: RFCOMM socket layer initialized [ 16.956760] Bluetooth: RFCOMM ver 1.11 [ 16.957633] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 16.957637] Bluetooth: HIDP socket layer initialized [ 16.977731] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=153a lmp_ver=06 lmp_subver=220e [ 17.582244] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=153a lmp_ver=06 lmp_subver=220e

I setup a Dell T20 with DS3615xs of Jun's loader. I did check the hardware compatibility list. Then I bought a Kinivo BTD-400 Bluetooth dongle because it is in the list. When I connect it, it doesn't work. The blue light is up. I did check dmesg and /var/log/messages. I found the firmware is missing. It seems to me the DS3615XS doesn't support it at all. Never mind, I download the firmware and put it in /lib/firmware/brcm folder. Then I found there is maybe a bug for this BT support because when I direct plug the dongle in, the DSM expects BCM20702A0-0a5c-21e8.hcd. But when I reboot, it asks for "BCM920702 Bluetooth 4.0-0a5c-21e8.hcd". It is so upset. Do they really have QE? Anyway, I put both name in that folder. Then check the log again, it seems like the firmware is loaded successfully. However, the kernel suddently killed it. 2018-12-30T03:06:34-08:00 DiskStation [ 1916.840592] init: bluetoothd main process (26477) killed by KILL signal 2018-12-30T03:07:30-08:00 DiskStation bluetoothd[8747]: Failed to open RFKILL control device 2018-12-30T03:07:31-08:00 DiskStation bluetoothd[8747]: Unknown command complete for opcode 19 There are no further information provided. I don't know what can I do now. Can anybody give some clue? I did check the bluetoothd service, it is disabled. I enabled it manually but it still the same. It doesn't work. There is nothing showing up from control panel -> wireless -> bluetooth. I checked hdiconfig -a, it looks good. thanks

All right, I eventually resolved the problem. There is a pub source intel ftdi driver for linux available at http://www.ftdichip.com/Drivers/D2XX.htm. just install the driver. the device is still /dev/ttyACM0. everything works fine. Now my synology dsm is running on dell poweredge T20, I installed HomeAssistant as z-wave controller. My smart-home system rocks!

Here are more information from z-wave log. We can see that the HomeAssistant try to talk to /dev/ttyACM0 as a serial device. It should be a USB device. There should be a /dev/ttyUSB0 but I could not see it. 2018-01-07 08:20:49.368 Always, OpenZwave Version 1.4.2586 Starting Up 2018-01-07 08:20:51.348 Info, Setting Up Provided Network Key for Secure Communications 2018-01-07 08:20:51.348 Warning, Failed - Network Key Not Set 2018-01-07 08:20:51.348 Info, mgr, Added driver for controller /dev/ttyACM0 2018-01-07 08:20:51.348 Info, Opening controller /dev/ttyACM0 2018-01-07 08:20:51.348 Info, Trying to open serial port /dev/ttyACM0 (attempt 1) 2018-01-07 08:20:51.348 Info, Serial port /dev/ttyACM0 opened (attempt 1) 2018-01-07 08:20:51.348 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2018-01-07 08:20:51.348 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc 2018-01-07 08:20:51.348 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9 2018-01-07 08:20:51.348 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb 2018-01-07 08:20:51.348 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa 2018-01-07 08:20:51.348 Detail, 2018-01-07 08:20:51.348 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2018-01-07 08:20:52.348 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s) 2018-01-07 08:20:52.348 Detail, contrlr, Removing current message 2018-01-07 08:20:52.348 Detail, contrlr, Notification: Notification - TimeOut 2018-01-07 08:20:52.348 Detail, 2018-01-07 08:20:52.348 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc 2018-01-07 08:20:53.348 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s) 2018-01-07 08:20:53.348 Detail, contrlr, Removing current message 2018-01-07 08:20:53.348 Detail, contrlr, Notification: Notification - TimeOut 2018-01-07 08:20:53.348 Detail, 2018-01-07 08:20:53.348 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9 2018-01-07 08:20:54.349 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s) 2018-01-07 08:20:54.349 Detail, contrlr, Removing current message 2018-01-07 08:20:54.349 Detail, contrlr, Notification: Notification - TimeOut 2018-01-07 08:20:54.349 Detail, 2018-01-07 08:20:54.349 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb 2018-01-07 08:20:55.349 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s) 2018-01-07 08:20:55.349 Detail, contrlr, Removing current message 2018-01-07 08:20:55.349 Detail, contrlr, Notification: Notification - TimeOut 2018-01-07 08:20:55.349 Detail, 2018-01-07 08:20:55.349 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa 2018-01-07 08:20:56.349 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s) 2018-01-07 08:20:56.349 Detail, contrlr, Removing current message 2018-01-07 08:20:56.349 Detail, contrlr, Notification: Notification - TimeOut 2018-01-07 08:21:30.722 Error, mgr, Manager::GetDriver failed - Home ID 0x00000000 is unknown 2018-01-07 08:21:30.722 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver 2018-01-07 08:21:30.722 Info, mgr, Manager::WriteConfig failed - _homeId 0 not found 2018-01-07 08:21:31.723 Detail, Notification: DriverRemoved 2018-01-07 08:21:31.723 Always, *************************************************************************** 2018-01-07 08:21:31.723 Always, ********************* Cumulative Network Statistics ********************* 2018-01-07 08:21:31.723 Always, *** General 2018-01-07 08:21:31.723 Always, Driver run time: . . . 0 days, 0 hours, 0 minutes 2018-01-07 08:21:31.723 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, Total messages successfully received: . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, Total Messages successfully sent: . . . . . . . . . . . . 5 2018-01-07 08:21:31.723 Always, ACKs received from controller: . . . . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, *** Errors 2018-01-07 08:21:31.723 Always, Unsolicited messages received while waiting for ACK: . . 0 2018-01-07 08:21:31.723 Always, Reads aborted due to timeouts: . . . . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, Bad checksum errors: . . . . . . . . . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, CANs received from controller: . . . . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, NAKs received from controller: . . . . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, Out of frame data flow errors: . . . . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 0 2018-01-07 08:21:31.723 Always, Messages dropped and not delivered: . . . . . . . . . . . 5 2018-01-07 08:21:31.723 Always, *************************************************************************** 2018-01-07 08:21:31.723 Warning, WARNING: Tried to write driver config with no home ID set 2018-01-07 08:21:33.723 Info, mgr, Driver for controller /dev/ttyACM0 removed

Hello, I installed HomeAssistant as a docker image and run it on DSM 6.0 (Jun's loader). The problem is, it doesn't support my USB z-wave dongle. My server is Dell poweredge T20. It has an Intel 8 / C220 USB 3.0 eXtensible Host Controller. But for DSM, it doesn't have the usb serial package for it. Could anybody suggest how can I get that driver? I have zero experience to build the driver by myself. thanks