CloudServer issues

12 posts / 0 new
Last post
berkinet
CloudServer issues

Server: GL-MT300N-V2
Version: 3.8.1
USB device: Aeotec Stick Gen5 (ZW050x_USB_VCP_ PC_Driver (https://aeotec.com/z-wave-usb-stick)
Client hardware: MacOS 10.14.3
VH Client version: 4.6.5

#1) I am unable to properly mount the USB device on the client Mac. When connected directly to the Mac, the USB device appears as
/dev/cu.usbmodemxxxxx and /dev/tty.usbmodemxxxxx

However, when using VH the devices are not created in /dev
The OS-X system reporter shows:
Communication Device:

    Product ID: 0x0200
    Vendor ID: 0x0658 (Sigma Designs, Inc.)
    Version: 0.00
    Speed: Up to 12 Mb/sec
    Location ID: 0x14300000 / 27
    Current Available (mA): 500
    Extra Operating Current (mA): 0

By the way, Aeotec reports this on their web site:
"The Z-Stick Gen5 now uses UZB drivers instead of Silabs UART to USB. There is no need to install the UZB drivers in OSX and Linux as these OS already have drivers that will allow the use of the Z-Stick Gen5 without the UZB drivers. For further support materials, please refer to our support section."

#2) The CloudServer Advanced properties include an option to "Update Firmware..." However, I cannot find such firmware on your site. Presumably, the system image linked in the install instructions is current. But, where else would I look to check if there were new versions?

Thanks for the help... I am looking forward to getting this working as it will solve a number of problems.

Richard

berkinet
Should have included this

The server log:
Thu Jan 31 16:32:18 2019 kern.info kernel: [ 744.119584] usb 2-1: new full-speed USB device number 5 using ohci-platform
Thu Jan 31 16:32:18 2019 user.debug vhusbdchglmt300nv2[904]: Warning, could not open device product file /sys//devices/platform/101c1000.ohci/usb2/2-1/product, error 2 (No such file or directory)
Thu Jan 31 16:32:18 2019 user.info vhusbdchglmt300nv2[904]: Found Full speed device [0658:0200] "0x0658, 0x0200" at address 21
Thu Jan 31 16:32:28 2019 kern.info kernel: [ 753.929626] usb 2-1: reset full-speed USB device number 5 using ohci-platform
Thu Jan 31 16:32:28 2019 user.info vhusbdchglmt300nv2[904]: Device 21 [0658:0200] BOUND to connection 4
Thu Jan 31 16:32:29 2019 kern.info kernel: [ 754.789613] usb 2-1: reset full-speed USB device number 5 using ohci-platform
Thu Jan 31 16:32:37 2019 user.info vhusbdchglmt300nv2[904]: Remote Admin script sent to client at 192.168.5.118
Thu Jan 31 16:32:18 2019 kern.info kernel: [ 744.119584] usb 2-1: new full-speed USB device number 5 using ohci-platform
Thu Jan 31 16:32:18 2019 user.debug vhusbdchglmt300nv2[904]: Warning, could not open device product file /sys//devices/platform/101c1000.ohci/usb2/2-1/product, error 2 (No such file or directory)
Thu Jan 31 16:32:18 2019 user.info vhusbdchglmt300nv2[904]: Found Full speed device [0658:0200] "0x0658, 0x0200" at address 21
Thu Jan 31 16:32:28 2019 kern.info kernel: [ 753.929626] usb 2-1: reset full-speed USB device number 5 using ohci-platform
Thu Jan 31 16:32:28 2019 user.info vhusbdchglmt300nv2[904]: Device 21 [0658:0200] BOUND to connection 4
Thu Jan 31 16:32:29 2019 kern.info kernel: [ 754.789613] usb 2-1: reset full-speed USB device number 5 using ohci-platform
Thu Jan 31 16:32:37 2019 user.info vhusbdchglmt300nv2[904]: Remote Admin script sent to client at 192.168.5.118

Michael
.

1. No for some reason at the moment serial devices wont appear via virtualhere and osx 10.14 not much can be done about that until apple improves support

2. You just download the firmware updates from https://www.virtualhere.com/hardware and then select that file when you click Update Firmware... from the CloudHub interface

berkinet
This is very disappointing

This is very disappointing news. BTW, oddly the older Z-stick with the silabs driver, seems to work on the same setup described above.

Can you point me to more details in the 10.14 serial isssue.

... and, how can I access the cloudHub vis ssh? (mine is licensed)

Michael
.

You can just use e.g putty https://www.ssh.com/ssh/putty/mac/ for osx and ssh to the ip address of your cloudhub, username = root no password

Yes its a pain, some devices wont work via virtualhere. They were all working nicely up to osx 10.10 , in 10.11 apple entirely removed support for USB Host drivers from 3rd parties. Since there have been a lot of complaints from different companies apple has gradually put support back into osx again for 3rd party drivers. It gets better as time goes on. 10.12 when they first put some support for usb drivers back in they were pretty buggy. Now most devices work again via virtualhere. There is no release notes from apple that say this because its confidential

berkinet
No joy with ssh...

No joy with ssh...
Jjust to make sure I was completely following your instructions, I installed putty and did: plink -l root -ssh 192.168.5.79
and when prompted for the password, I got access denied. This is, of course, the same result I got using the built-in ssh command: ssh root@192.168.5.79

Note, I have never disabled ssh in the server config.

berkinet
And, juts a bit more

And, juts a bit more information. I was able to properly mount the Z-Stick Gen5 on a Win-7 VM (VirtualBox). The only thing of interest is the VH Windows client needed to down load 2 drivers, apparently after discovering the Z-Stick. Prior to the driver download, the Z-Stick was listed by its product ID (0x0200) afterwards it was correctly identified, and worked.

Michael
.

Yes windows and linux clients work fine with serial ->USB devices via virtualhere.

You dont need to use plink. Just open putty (or putty.exe on windows) and just put in the ip address of the cloudhub, select SSH as the connection type and then press connect. The login prompt will appear and put in root as the username and then press enter and then you will be at the terminal on the cloudhub

berkinet
On MacOS “putty” is not

On MacOS “putty” is not directly installed, only plink and a few other utilities. But, using
ssh root@192.168.5.79 should work equally well and it doesn’t.

berkinet
Just to keep myself honest, I

Just to keep myself honest, I tried putty on a win-7 machine and got the same result: Access denied

Michael
.

This is from my osx 10.14 to the GL-MT300NV2 (see below) so it definitely works from a mac using just ssh. The only other thing i can suggest is to just reset the firmware. You can do that from the virtualhere client by right clicking on the server ->Properties->Configure->Advanced->Restore defaults.

Last login: Sat Feb  2 19:59:48 on console
michaels-iMac-2:~ michael$ ssh root@192.168.0.8
The authenticity of host '192.168.0.8 (192.168.0.8)' can't be established.
RSA key fingerprint is SHA256:KxmnCSMobw0VS+KBWdXSDvqCWf7Y3Z2hmy2bNykiA30.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.8' (RSA) to the list of known hosts.


BusyBox v1.29.3 () built-in shell (ash)

VirtualHere CloudHub_43e992
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@CloudHub_43e992:~# 

berkinet
OK! A reset did the trick.

OK! A reset did the trick. All I can think of is that I had selected Enable/Disable ssh from the Config->Advanced menu, and then canceled out. Anyway I now have access... though, for the moment, I am not sure it will actually help with anything.

And, a note for those who may be reading this exchange and really want to install PuTTY on MacOS*. If you want the GUI version, use MacPORT to do the install. Homebrew will only install the command line apps, and they are exactly what you have in Terminal already. BTW, if you do want the GUI, you must also install X11 from – http://xquartz.macosforge.org/landing/ and then, in your Terminal window (or .bashrc) enter export DISPLAY=:0.0

* IMHO, there isn't much reason to have PuTTY on MacOS, if you have the skills to actually install it, then you can also probably get by just fine with the Terminal and ssh.

Log in or register to post comments