Support

Hello everyone,

 I trying to work VirtualHere into our organization which by and large works fine. One problem though is with our virtual machines. They can reach the server fine, direct connect with IP, and check out a dongle but it gets returned quick with a "server timeout" message. This happens both with the virtual NICs in NAT and bridged mode.

 I think this is related to the server wanting to ping the clients. When using bridge mode in a vm the server can ping the vm but VirtualHere still times out.

Anyone using a Google Coral with VirtualHere? I seem to have more latency than I was expecting, but the connection between the client and the server seems fine (ping under 1ms, tests on Windows show similar for server itself). I am using the Coral with Frigate (CCTV) for AI object detection, and my inference speeds are around 40-50ms. I was basing it off this post over on the Home Assistant forums, they were getting around 25ms. 

Hello all,

I’m using VirtualHere as follows. I’m gaming downstairs on my sofa and TV via Moonlight>Sunshine on the AppleTV. My Sunshine host is in my office upstairs. First I was connecting the Xbox Controller (v1708) via Bluetooth to the AppleTV but this gives me too much latency and oid behavior.

So now switching to the Xbox Wireless Dongle (genuine Microsoft, version 6HN-00003). I have my server close by so I wanted to use this as VirtualHere Server.

Hi there. I want to use "8BitDo USB Wireless Adapter 2" via VirtualHere, but "8BitDo USB Wireless Adapter 2" has an unusual behavior that changes its device name depending on the wireless controller's connection status.
And every time the device changes its name, "Use this device" unexpectedly turned off.
Is there any way to make connection continues even if the device changes its name?
Since this device changes its name every second, "Auto-Use Device" does not solve this problem.
Thank you.

Client: Windows 10, VirtualHere Client 5.5.7

Server: Raspberry Pi 4, Raspberry Pi OS 64-bit, VirtualHere server 4.6.2

I tried to make a virtualhere usb server using RaspberryFi 4 and installed RaspberryFi OS on RaspberryFi first, then moved cloudhub-pi4-factory-sdcard.zip back to SD card using win32 diskimager and confirmed that CloudHub_xxxx is visible. But I entered the ip address to set up the connect via LAN in "I want my CloudHub to be part of an existing network". Then cloudHub is not displayed.
Reinstalling the OS on the SD card will still not work when you decompress and install cloudhub-pi4-factory-sdcard.zip.

Hello,

Were currently using Virtual Here on Windows 11 devices that are also connected to HP G2 and G4 Docks.

When users are WFH and using VHUI but then come back into the office and plug into their dock, none of their usb peripherals that in the dock are working and device manager shows:

Intel USB 3.1 eXtensible Host Controller 1.10 Microsoft

This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

Object Name already exists.

Hello,

Android Server doesn't start on cold boot for me on my Google TV (Android 11). It's possible to start the app itself using adb by running something like this 'adb shell monkey -p com.virtualhere.androidserver 1' but it starts in foreground and it's not optimal for me. There are workarounds but I don't like them: I can run it with home assistant for example and send "HOME" after to minimize it.

Couldn't start com.virtualhere.androidserver.DaemonService at all.

Hi.  A shot in the dark...

I bought VirtualHere a while back - I can see and use all the USB devices I have plugged in at home (the VirtualHere server on macOS Sonoma).  Typically I am only using a 3D mouse for work in CAD software on my work computer (Windows 10).  Other than some minor hiccups along the way, it's been good.

I have setup "Windows Hello" on the work (client) computer - both using a camera/face and a USB Fingerprint Key (Kensington VeriMark IT).  Both work "locally" at the work computer.

Hello,

Very happy user of VHere since... a long time. We are using encrypted connections to our VHere servers, and client certificates. We manage our own CAs.

Since a few weeks ago, SSL connections to one server fail without obvious (for us)  reasons. We had a certificate rotation for the related CA, so there may be something in this direction. We have disabled the client certs for this server (sslClientCerts=0), to limit the search for the problem. 

Here is a (short) log, client-side :