Virtual here client shows hub + connected devices. Windows does not see any of them.

Submitted by jeroenv on #1

Hi,

I cant get VirtualHere to work :(

Situation:
- VirtualHere server for the Raspberry pi (1 version B).
- Windows 10 machine as client (As a service).

If I run VirtualHere client gui I can see the hub and the attached devices. But windows itself does not see any device. I have a pulse8 usb cec adapter and an USB bluetooth adapter connected to the Server. One thing to note is that the client says "(In use by you)" after both devices. I don't understand how that is possible if windows doesn't see them.

Any help is appreciated :(
Jeroen

Submitted by Michael on Sat, 2016/11/26 - 18:38

#2

Have a look in windows Device Manager when you are using the usb devices via virtualhere. Do you see the devices listed there? Perhaps with a exclamation mark next to them. If so can you see the tell me the error code?

Also note you cannot use the client as a service with the free server . You can use the client as a GUI instead.

Submitted by jeroenv on Sat, 2016/11/26 - 22:42

#3

I have a licence for the full server version. In case of my first post I could not see the devices in the device manager. But I had some random success with the bluetooth device. I had it plugged into my pc directly, windows recognized the device and installed the drivers. Then I inserted the device in the pi and it showed up in windows as well.

Unfortunately now again it doesnt :/. Virtual here client still sees the usb devices inserted in the server. Windows itself doesnt.

Submitted by Fischi on Fri, 2016/12/02 - 06:22

#4

"If I run VirtualHere client gui I can see the hub and the attached devices. But windows itself does not see any device. I have a pulse8 usb cec adapter and an USB bluetooth adapter connected to the Server. One thing to note is that the client says "(In use by you)" after both devices. I don't understand how that is possible if windows doesn't see them "

I have the same behaviour : After a random time my UZB1 z-wave stick doesn't work anymore, the client shows the hub and the
"connected " USB device. "(In use by you)" but the win7 device manager shows an exclamation mark beside the UZB1.
After unplugging and replugging the UZB1 the device manager shows it right without the exclamation mark and all is working
again.
Is there a possibility to get it running again without unplugging and replugging ???

Fischi

Submitted by jeroenv on Wed, 2016/12/07 - 04:45

#6

That exact image is what I started with (was the latest raspian when I bought the virtualhere licence). And it didnt work with that image either. Retried it just now to confirm it. The same devices directly connected to the pc work perfectly.

Really disappointed :/. Bought an expensive licence for one specific physical device. Doesnt work on that device in any configuration. And worst of all my intended setup does not work so I still need to walk to the other side of the house to control the pc via the keyboard/mouse :/

Submitted by jeroenv on Thu, 2016/12/08 - 05:07

#8

Tried that version. Doesn't work either. There must be a way to get this to work otherwise you wouldnt be selling this version (I hope).

Submitted by Michael on Thu, 2016/12/08 - 09:30

#9

Can you give me ssh access to your pi? Perhaps i can login and try to use those devices from my office and see if i can find the problem....email me details to mail [at] virtualhere.com (mail[at]virtualhere[dot]com)

Submitted by Fischi on Mon, 2016/12/12 - 19:33

#10

Hi Michael,
I've tried v3.0.9
1. There come often double entries in the win7 client for my RasperryPi (two RasperryHubs are shown).
I've only one connected .
2. I've marked "debug"
Where is the debug log stored in my PC -I can't find it.

Fischi

Submitted by Michael on Mon, 2016/12/12 - 21:11

#11

So im assuming 3.0.9 fails also, then its very likely a kernel issue in raspbian.

1. Do you have the IP address specified AND the auto find on? If so it may find the same server twice. Remove the server manually specified.
2. Actually the debug is a bit difficult to get in windows 7 because its written to the kernel log which is only visible in realtime using DebugView. I dont think its particularly helpful in this situation.

What error number appears when the zwave shows an exclamation (Right click UZB stick -> Properties -> Device Status) ?

Submitted by Michael on Mon, 2016/12/12 - 21:14

#12

@jeroenv can you try this, right click on the Bluetooth adapter and select "Custom Event Handler..." and enter exactly this string

onReset.$VENDOR_ID$.$PRODUCT_ID$=

and then press OK. now try using the bluetooth adapter again via virtualhere, its is better now?

Submitted by Fischi on Mon, 2016/12/12 - 22:18

#13

1. The version before 3.0.9. didn't show the behavior with the double entries - there must be something wrong in 3.0.9 .
2. It would be nice to have the debug log entry in realtime because I want to analyze this with HomeSeer to trigger events eg. rasbperry restart .
Where to find the entry ?
"What error number appears when the zwave shows an exclamation (Right click UZB stick -> Properties -> Device Status) ?"
This exclamation mark didn't occur again until now, after occuring again I will send you the error number.

Fischi

Submitted by Michael on Tue, 2016/12/13 - 08:00

#14

1. The double entry issue happens due to a technical limitation. It will be fixed at some point soon

2. The log format is only readable by me as it logs the data in a limited format due to the fact its in the main path of the usb processing. The log is written to the windows kernel logging system. Using DebugView is how you see it, there are reasons its logged this way due to the fact some logging must take place in a raised IRQ level.

Regarding testing for raspberry connectivity, you just need whats called a "watchdog" which e.g is just a script that just pings something every few seconds and if its not heard from then raspberry pi has network issues.

Submitted by Michael on Tue, 2016/12/13 - 10:39

#15

@jeroenv i also wanted to add, some bluetooth controllers have firmware that needs to be uploaded immediately as soon as it is plugged in and a USB RESET command upsets this sequence. Therefore if you disconnect the usb reset command given by the command in the previous posting it should work around this issue and the bluetooth dongle should be usable over virtualhere

Submitted by jeroenv on Tue, 2016/12/27 - 08:53

#16

Hi Michael,

I tried the custom event handler. At first it did not seem to work. But for some reason after a week I now see the bluetooth adapter consistently. Don't know why that happened. still running latest wheezy and VirtualHere 3.0.9. Think I will leave it at that as long as it stays working.

Jeroen

Submitted by jeroenv on Thu, 2017/01/12 - 07:09

#17

Maybe I was lucky last time. Now it stopped working again (after 2 weeks away from home).

Submitted by Michael on Thu, 2017/01/12 - 09:21

#18

I think that it might require a few tries, try unplugging it putting in the pc and the unplugging it and putting it back in the pi and using it. By the way, make sure you use the optimized build for the pi because if you are using bluetooth via virtualhere the radio data is sent and there is usually a lot so its cpu intensive in brief periods.