Trying to get Z-Wave Stick to register

Submitted by focalfury on #1

Server: 2012R2
Client: Ubuntu 16.04 CLI

So I'm not sure if this is working or not but when I start the VirtualHere server the logs show the following message.
2017-02-20 22:05:35 INFO :Unmanaging device 1 [0624:0249]
2017-02-20 22:05:35 INFO :Unmanaging device 2 [0624:0248]
2017-02-20 22:05:35 INFO :Unmanaging device 6 [0658:0200]
2017-02-20 22:05:36 INFO :TCPServer starting...
2017-02-20 22:05:36 INFO :Listening on all network interfaces at port 7575 (IPv6 dual-stack)
2017-02-20 22:05:36 INFO :Registration called
2017-02-20 22:05:36 ERROR :Error A device attached to the system is not functioning. (0x0000001f) getting basic config 1 descriptor from hub node (maybe device is stuck, try replugging device on port 1)
2017-02-20 22:05:36 INFO :Found High speed device [0624:0249] "Avocent, USB Composite Device-1" at address 1
2017-02-20 22:05:36 INFO :Found Full speed device [0624:0248] "Avocent, USB Composite Device-0" at address 2

SO first off I'm not sure if it is working as expected.

When I run the "LIST" command I don't get any results back.

VirtualHere Client IPC, below are the available devices:
(Value in brackets = address, * = Auto-Use)

Auto-Find currently on
Auto-Use All currently off
Reverse Lookup currently off

I feel like I'm missing something basic. I've tried multiple ports on my server too with no change

Submitted by Michael on Tue, 2017/02/21 - 16:05

#2

The server is having difficulty reading the device type, i think if possible you should try a linux type server or perhaps osx. It looks like the virtualhere server for windows may not be compatible with that device.

Submitted by focalfury on Sat, 2017/02/25 - 13:33

#4

That worked!!!

Submitted by focalfury on Sat, 2017/02/25 - 13:46

#5

This might be a dumb question, but how do I select only the 0x0200 item to be used? When I list I get this.

Windows Hub (MK-HYPERV01:7575)
--> 0x0200 (MK-HYPERV01.5)
--> USB Composite Device-0 (MK-HYPERV01.2)
--> USB Composite Device-1 (MK-HYPERV01.1)

Submitted by Michael on Sat, 2017/02/25 - 14:42

#6

OK great, Just right click on the device and select "Use". Let me know if there are more issues as im not entirely sure the bug is completely fixed yet...

Submitted by Michael on Sat, 2017/02/25 - 16:37

#8

./vhclientx64_64 -t "USE,MK-HYPERV01.5"

(Note this only works if you purchased the server. If the server is not purchased you need to use the client gui instead)

You should upgrade to the latest kernel for ubuntu if you can as that fixes some bugs in usbip client in the kernel

Submitted by focalfury on Sun, 2017/02/26 - 10:28

#9

Thank you for your continued help, yes I purchased and I think I am very close to getting fully working. When I use that command i do get the result of OK, which I take it to mean we've successfully 'connected' this USB device to this Ubuntu CLI machine.

The last piece of the puzzle to me is to find out the path it is mounted. I used lsinput where I (believe) understand all USB devices will show up, but the results/information from this command do not match the vendor/product of the device.

Where can I find its path? I need it to put into a config that wants usb_path. An example of the path when physically attached would be /dev/ttyACM0

Thank you greatly for your continued support.

Submitted by focalfury on Sun, 2017/02/26 - 10:39

#10

I think I found it :) lsusb helped and I can see it showing the proper vendor/product ID

Submitted by focalfury on Sun, 2017/02/26 - 10:41

#11

shame I can't edit comments, sorry for the back and forth.

So lsusb definitely shows the device connected, however I still do need to know where it's path is so I can put it into a config. Thanks again I need it to put into a config that wants usb_path. An example of the path when physically attached would be /dev/ttyACM0

Submitted by Michael on Sun, 2017/02/26 - 17:05

#12

Try typing dmesg or grep ACM /var/log/syslog to see if it shows the driver binding to the z-wave. I think its meant to be a serial device