Free VirtualHere for SteamLink (USBIP)

[Limer]

Want to try VirtualHere before you buy the Steam version?
One transferred USB device is enough for you?
Then this maybe just for you.

I build a small SteamLink Native App which enables you to use free VirtualHere USB Clients[virtualhere.com] for one USB device at a time.

Be aware that someone (guess who) is deleting post concerning this topic/possibility in the VH for SL discussions.

A few details

• The first time you start the VHUSB app it downloads the free VirtualHere USB Server[virtualhere.com] "vhusbdarm"[virtualhere.com] and starts it. To circumvent any potential license[virtualhere.com] issues I didn't included the binary, even though I don't see any.
  
• The VirtualHere USB Server keeps running as long the SL is not power cycled. So you only need to start it once in while.
  
• Starting the app while the daemon is already running is no problem (the new instance quits after it sees the already running one).
  
• It contains a preconfigured config[virtualhere.com] (see below).
  
• VH Clients can connect to the SL the whole time the SL is running. Not just when you stream from a PC.
  
• The downloaded VH server binary on the SL is most likely less efficient than the integrated one.
  If you experience problems possibly related to this you can investigate by enabling SSH on the SL, connecting to the SSH an running "top" to monitor CPU usage.

DOWNLOAD

sha256 = 9aeff21f64fd6518ff4d4d8980d3f1b54cb813457d6e08a765d33cf614008f0f
from GitHub[github.com]

(old sha256 = fecd9fb73e83c14acc95ceb81f8561016b664ff053551fc4fccf8f185b4c6785)

How to install[github.com]

What's inside the vhusb.tgz

1. ./vhusb/bin/config.ini
   

   ;see here for more infos: https://virtualhere.com/configuration_faq
   
   ;SrvName can be changed from the client - this is just a useful start.
   ServerName=$HOSTNAME$
   
   ;UseAVAHI=0
   ;IgnoredDevices=
   ;IgnoredBuses=
   ;AllowedDevice= <- only allow the keyboard you're using?!
   ;CompressionLimit=
   

   
   
2. ./vhusb/icon.png
   
3. ./vhusb/vhusb.sh
   

   #!/bin/sh
   
   cd ./bin
   
   executable=vhusbdarm
   
   if [ -f $executable ]
   then
   	echo Run VHUSB Server in background mode.
   	exec ./$executable -b
   else
   	echo Downloading the VHUSB Server with WGET.
   	wget https://virtualhere.com/sites/default/files/usbserver/vhusbdarm
   	# MISSING! Check return code, file etc...
   	chmod a+x ./$executable
   	echo ... and running it in background mode.
   	exec ./$executable -b
   fi
   
   #NOTES:
   # GUI Idea - enable user to edit the config.ini and (re)start the vhusbdarm daemon (automatically if config was modified).
   # Pid management? for later killing?
   # How to Verify integrity of the downloaded server? Show sha256s of binary on first install or sth?
   # If the "App" is removed while the daemon is still running, the files/dirs are removed but the daemon stays until the next powercycle.
   #   ... don't know what happens if the daemon tries to use it's config.ini
   

   
   
4. ./vhusb/toc.txt
   

   name=VHUSB
   icon=icon.png
   run=vhusb.sh
   

To modify it and/or integrate the vhusbdarm binary just unpack everything and repack it as a .tgz (.tar.gz).
NOTE: Keep in mind that the text files need the Linux EOL-character "LF". They won't work with Windows's "CR+LF".

I used PeaZip[www.peazip.org].


From the notes in some files you can gather that this is far from perfect, but it's a start.

Have fun!


Disclaimer - I was not the first one to think of this general possibility. I got the idea, searched a little bit and found this thread/post.

[Limer]

Uploaded a slightly modified version to GitHub (name and icon.png changed)

[fox]

Just wanted to say this works great! Thanks for writing this script :)

[TheHarunoki]

Thanks a lot, Now I can play wii games on my living room!
edit: Is it possible to install it in the steamlink, without needing the usb in every boot?

[Limer]

*insert some expression of gratitude*

I'm glad others find it useful.

Publicado originalmente por Harunoki:

edit: Is it possible to install it in the steamlink, without needing the usb in every boot?

What? I don't understand your question. I could hazard a guess at what you mean but I think I answered that guessed question in the main/first post of this topic:

Publicado originalmente por Limer:

The VirtualHere USB Server keeps running as long the SL is not power cycled. So you only need to start it once in while.

Starting fVHusb automatically every time the SLink is powered on may be possible but would most likely require manual modifications of files on the SLink over SSH. And those changes probably won't survive a firmware update.

[76561197977459721]

hey,thanks a lot, that was what i was looking for, i use it to connect the windows xbox one controller dongle with the steam link and it works nearly flawless. The obnly problem remaining is, that I now can only connect one controller with the dongle, when i try to pair a second controller, the lights flash but the do not establish a connection and i lack the knowledge to solve the problem. I believe that the dongle counts as one device, which should not be a problem for the virtual here client version,which allows only one device, no matter how many controllers are connected to the dongle, any ideas?

[xcsgamer]

There is also a way that when you buy virtualhere for steam link that you can autostart it and use the license at every steam link you have.

Because if you buy it it work only when you start streaming but with his app it work always like a charm :)

App will get released of a friend soon at the Steam Link App Store that is coming.

[Milt]

Got this working last night. Absolutely perfect for my Logitech racing wheel and pedals. Thank you!

For those also trying to get a Logitech wheel working: I ran in to an error from the VirtualHere windows client "Operation not permitted" (-1) trying to use this device". The solution, as found elsewhere on the internet, was to right click on the wheel listing in the virtualhere client, click "custom event handler" and add the following line:

onReset.$VENDOR_ID$.$PRODUCT_ID$=

[Doc [De]Fusas]

Hey, thanks fo posting this. Unfortunately, it doesn't work for me. When trying to connect to connect to my USB-device the VirtualHere Client tells me that "When running as as service you can only conenct to purchased servers."

[TheChickenAgent]

Publicado originalmente por Doc DeFusas:

Hey, thanks fo posting this. Unfortunately, it doesn't work for me. When trying to connect to connect to my USB-device the VirtualHere Client tells me that "When running as as service you can only conenct to purchased servers."

Hey @Doc [De]Fusas,
Did you put the needed files on a USB stick, plug that USB into your Steam link and start your Steam link? I am just trying to help

[Doc [De]Fusas]

Publicado originalmente por TheChickenAgent:

Publicado originalmente por Doc DeFusas:

Hey, thanks fo posting this. Unfortunately, it doesn't work for me. When trying to connect to connect to my USB-device the VirtualHere Client tells me that "When running as as service you can only conenct to purchased servers."

Hey @Doc [De]Fusas,
Did you put the needed files on a USB stick, plug that USB into your Steam link and start your Steam link? I am just trying to help

Yes, I did. Also clicked that "VHUSB" symbol just to make sure that the script was executed - otherwise it wouldn't show the USB devices in the software.

[Limer]

Publicado originalmente por Doc DeFusas:

Hey, thanks fo posting this. Unfortunately, it doesn't work for me. When trying to connect to connect to my USB-device the VirtualHere Client tells me that "When running as as service you can only conenct to purchased servers."

That sounds like you're using the wrong client or in the wrong configuration (as a windows service and not a 'normal' program).

[Doc [De]Fusas]

Publicado originalmente por Limer:

Publicado originalmente por Doc DeFusas:

Hey, thanks fo posting this. Unfortunately, it doesn't work for me. When trying to connect to connect to my USB-device the VirtualHere Client tells me that "When running as as service you can only conenct to purchased servers."

That sounds like you're using the wrong client or in the wrong configuration (as a windows service and not a 'normal' program).

I just downloaded the program linked in the post and executed it. There was no configuration what so ever.

Edit: turns out that I had in fact some service installed that interfered with the program. Works like a charm now. Thanks!

[Tralalero Tralala]

Wonderful app, I got my xbone controller working with the dongle, so I can use the mini jack. But here's my problem, it seems like my controller is only working with Steam in Big picture, not in the SL main menu, so I need a mouse to start streaming every time the SL wakes up... What am I doing wrong?

[doveman007]

Thanks for this Limer. I might actually be able to use my Steamlink now as so far I've had a nightmare with my Xbox360 controller not working a lot of the time (for example it worked in GTA V on Win 8.1 but in Win 10 it doesn't and if the controller disconnects it's impossible to reconnect it to the game, which is not a problem with the receiver plugged into the PC).

I'm curious why this workaround is necessary though, when the Steamlink already has the VH server built-in and the client is freely available? I saw this guide about setting up a headless PC which uses VH and he didn't seem to need to use any workaround https://steamcommunity.com/app/353380/discussions/0/405690850608608088/

[doveman007]

Hmm, hasn't worked very well for me unfortunately. I'd connect my SL to the PC and then use the client to assign my Xbox360 controller to the PC but sometimes after doing that I couldn't control the Steam Big Picture UI with my controller, sometimes there would be a mouse pointer which I could move with one of the sticks and other times the SL would "lose" the controller so that it was prompting me to connect one, whilst the VH client still showed it connected. Once I had to power-cycle the SL to get the controller to reconnect and another time I had to unassign it in the VH client.

So the SL experience is still a very big mess which requires me to keep walking between my living room and the room where the PC is in to try and get it working, mostly without much success.