Cannot try it out

Hi,

I'm highly interested in purshasing a licence, but I want to try it out first. Not working yet.

The server is running on a synology NAS, I want to access the USB key from a debian buster virtual machine.
Here's what I did :
wget https://www.virtualhere.com/sites/default/files/usbclient/scripts/virtu…
wget https://www.virtualhere.com/sites/default/files/usbclient/vhclientx86_64
chmod +x ./vhclientx86_64
sudo mv ./vhclientx86_64 /usr/sbin
sudo mv virtualhereclient.service /etc/systemd/system/virtualhereclient.service
systemctl daemon-reload
systemctl enable virtualhereclient.service
systemctl start virtualhereclient.service
/usr/sbin/vhclientx86_64 -t "LIST"
--> lists correctly my usb keys
/usr/sbin/vhclientx86_64 -t "use,NAS.12"
--> FAILED

How come ?
Thank you so much in advance !

#2

No you cant use the console client in the free version of the server. You need to use the GUI client or purchase a license.

#3

Oh ok. Fair enough, I'll jump then.
Apparently we need to input the licence in the purchase form ? How does it work for the console client ?
< Right Click USB Hubs -> License... -> Copy to Clipboard>>

#4

Sure you can use this command

./vhclientx86_64 -t "LIST LICENSES"

It will output a line like, for example:

Hub Name,s/n=asdfasdfasdf,1 device

Just paste that whole line into the https://www.virtualhere.com/purchase

Then when you get the license key you can enter

./vhclientx86_64 -t "LICENSE SERVER,key you received"

#5

Ok now the client started ok, but I cannot access the USB stick from the VM... I'm completely stuck.
I'm trying to use a zigbee stick on Home Assistant with zigbee2mqtt (cannot mount using the VM because it unmounts regularly, that's why I need virtualhere).
Any advice ?

#6

Try this

Reboot the client pc just to make sure the dmesg and syslog is clean
1. In a terminal session, run tail -f /var/log/syslog
2. Then in another terminal run
./vhclientx86_64 -t "USE..."
3. Does the log show anything when you try to use the device? Like usb errors or something?

#7

debian VirtualHere Client: Could not connect to 1.2.3.4:7575
debian VirtualHere Client: Server ping timeout, shutting down connection 91...
debian VirtualHere Client: Could not connect to 192.168.0.XX:7575

thanks for the help, appreciate it

#8

Seems like its not connecting to the virtualhere server. Are you *sure* you have access available and port 7575 is not blocked by a firewall.

E.g can you telnet to port 7575 on that server ip address and does it connect and characters show up after a few seconds?

#9

Seems like you're right but I deactivated the firewall so I don't know why it doesn't pass through... telnet also fails
Looking again what could block...

#10

Found it ! It's in application portal of DSM that I had to open the port.
zigbee2mqtt still not working though... Headache is not over

#11

OK "USE" the device via virtualhere then have a look in syslog , does it show the zigbee device connecting and a serial port device in /dev

#12

Got this now :
Mar 24 13:32:39 debian VirtualHere Client: Server ping timeout, shutting down connection 271...
Mar 24 13:32:39 debian VirtualHere Client: Server ping timeout, shutting down connection 270...
Mar 24 13:32:39 debian VirtualHere Client: Data stream corruption, compressedSize=1347703880, uncompressedSize=825110831
Mar 24 13:32:39 debian VirtualHere Client: Data stream corruption, compressedSize=1347703880, uncompressedSize=825110831
Mar 24 13:32:46 debian VirtualHere Client: Could not connect to 1.2.3.4:7575

On top of the Data stream corruption, why is it trying to connect to 1.2.3.4 ?

#13

OK actually i see you are running on synology, so the virtualhere server runs on port 17570 so you need to open that port, not port 7575 sorry

So put in

./vhclientx86_64 -t "MANUAL HUB ADD,synologyipaddress:17570"

then type

./vhclientx86_64 -t "LIST"

and you should see your device listed there

Can you do that and it shows the zigbee device?

#15

Well probably by virtualhere server ^^ I can't open the port but I tried anyway.
The device is listed. I did "use" and trying to connect zigbee2mqtt I've got a different error message maybe linked to a firmware problem IDK need to investigate a little bit more. I'll report here, thanks for your help

#16

No idea where this new error comes from. Seems to connect but I tried using another zigbee stick and result is the same...
It just doesn't work. Is it the NAS, is it HA, is it zigbee2mqtt ? I've posted on a few forums, will see in a few days if it resolves.

#17

OK when you are using the zigbee2mqtt does it show up ok in the client VM when you type

lsusb

Can you see it there? And also can you see a serial device under /dev ?