Issue with hotkeys and with automation

Submitted by fr500 on #1

Hi

I mapped a few hotkeys for some devices. Issue now is that I can't unmap them now, the device IDs changed or something and now I have a broken CTRL+0 key that I can't unbind...

Second, I have been trying to automate enabling/disabling auto use when moonlight connects, but my servers show as localhost:

NVIDIA SHIELD X1 (Proto) (localhost:7575)
NVIDIA SHIELD TV (Pro) (localhost:7575)
--> Dualshock 4 Wireless Adapter (localhost.1004)
--> XBOX One Wireless Adapter (localhost.1003)

Auto-Find currently on
Auto-Use All currently off
Reverse Lookup currently off
Reverse SSL Lookup currently off
VirtualHere Client not running as a service

so if I run the command like vhui64.exe -t "USE,localhost.1004"
I get a no such device message...

How can I fix that?

Submitted by Michael on Mon, 2022/02/21 - 17:43

#2

Hi, looks like three issues

The hostname is set to "localhost" on both shields. This is not correct, they should have unique hostnames. Can you see here https://www.reddit.com/r/ShieldAndroidTV/comments/or2547/comment/h6fp58… on how to set the hostname. After you do that, reboot the shield and see if its different to "localhost". Once thats fixed you can then refer to the specific server instead of localhost, as that is ambiguous.

You will need to set the virtualhere client back to its defaults if lost the hotkey. In the virtualhere client right click USB Hubs->Advanced Settings-> Defaults->Restore Default Settings.

The last issue is the address. Which should not change if the device is kept in the same port. But I think that is changing, e.g from 1004 to something else when you reboot the shield or unplug/re-plug the dualshock and xbox wireless adapter. Is that happening? can you confirm by seeing if the address has changed

Submitted by fr500 on Fri, 2022/03/11 - 10:25

#3

Sadly that procedure to change the hostname doesn't work, the device name is changed and even reflected in SAMBA, but not on virtualhere

Submitted by Michael on Fri, 2022/03/11 - 18:12

#4

I assume you rebooted after that change? You need to change the hostname to something unique otherwise its impossible for virtualhere to distinguish servers via the API.

Submitted by fr500 on Sat, 2022/03/12 - 08:42

#5

Yup I rebooted both units, no change.
I also attempted changing it on my DHCP server to no avail. It alwas shows as localhost even though it shows as shieldatv1 and shieldatv2 on my the network

Submitted by Michael on Sat, 2022/03/12 - 22:22

#6

OK i found the bug in the virtualhere app. Ill fix after the 20th March as im away on holidays this week.