Eric Stiff

On 4/22/2024 at 10:04 AM, videostorm said:

Sleep is 0xc 0x0034  which translates to 2000052 in QHIDCODE    (conversion detail in the protocol manual, but mainly just hex to dec conversion)

Technically it is Android KEYCODE_POWER in the table.  The Android key code column lists how each HID key is used (or ignored) by Android.

Part of what throws me off is that in the IRUSB protocol manual SLEEP is listed as QHIDCODE3002000 

1 hour ago, videostorm said:

Hi Eric,

The QHIDCODEs are built into our C4 driver (to respond to navigator commands etc).  Are you looking for a specific code that isn't available via navigator?

Our protocol for the QHIDCODE mapping is at: https://www.video-storm.com/manuals/IrUSB_protocol.pdf

The Android reference for the base HID codes is:  https://source.android.com/docs/core/interaction/input/keyboard-devices#hid-keyboard-and-keypad-page-0x07

 

Welp, this goes to show why I was never able to get into true programming as a lot of this I just find confusing. I was really just wanting a good QHIDCODE reference just for the sake of having it. The two most important commands (2002035 for home and 2000052 for sleep) I already have thanks to you providing them to me 4 years ago in another thread. Except that looking at the PDF you linked, it lists a completely different code for sleep. So now I'm even more confused.

Tagging @videostorm since this involves their great little IrUSB device.

My Google Fu is failing me and I cannot find a reference source for all the QHIDCODE commands for Android TV devices, specifically the nVidia Shield.  I had a reference for them 4 years ago but have since lost it. Could anyone point me in the correct direction please?

Thank you,

Eric

Here's the explanation on Long Press from @videostorm

22 minutes ago, istreich said:

Thanks Eric. Very helpful to know that. Surprising that the native driver does not include those. They seem to be as important features to have, not really nice to have.

Is long press in both drivers? Working well?

I don't know about the Nvidia driver. @videostorm provides a long press option but not with the "select" button. This is a limitation of the C4 remote itself because the "select" button does not actually provide a long press capability. It only sends a "single tap" no matter how long you hold the button.

3 minutes ago, istreich said:

Eric, can you share with is better on Videostorm than native Control4. Would be great as it is unclear what functionality differences are. Thanks

VideoStorm also provides direct access to the colored buttons, plus the ability to add commands for direct app access in case there is an app that doesn't have a Universal Mini Driver. 

1 hour ago, feffe said:

I can gladly tell you guys all that a IP based driver is now avaiable. Just got my "SHIELD TV" discoverd in Composer and added it to my living room and connected HDMI.

Works lika a charm!

I've loaded it too but I'm not "using" it. I still much prefer the VideoStorm driver's functionality.

Never mind, "draw over other apps" got turned off with the update.

On 6/28/2020 at 4:38 PM, Eric Stiff said:

I can now confirm this does not work.  I have to put the full QHID command in a custom app line and call them that way.  Also, I am now getting this repeating error code in the Shield LUA window (the filename is different because I pack Nvidia icons into the c4z so I'm not looking at Fire TV icons for my Nvidia Shield):

LUA_ERROR [id: 383][name: Universal Android Driver With Nvidia Icons][file: mediaplayer_android_irusb_shield.c4z][method: ReceivedFromNetwork]: [string "Lua Code"]:762: attempt to compare number with nil

This error goes away when I reboot but eventually comes back.

On 6/29/2020 at 10:43 AM, videostorm said:

That error message is an old bug related to the play status readback that sometimes shows up.  Please open a support ticket at https://netplay.freshdesk.com/  and post your lua log and the navigator commands you are using.  Hopefully we can finally isolate it to fix it.

@videostorm It comes back without me using any navigator commands and just keeps scrolling about once a second.

4 hours ago, WhyPhy said:

The "attractive, user-friendly splash screen" is a great suggestion. The existing splash screen is pure confusion for end users. It makes it look like the device has been hacked by ad-ware. It should look like specialized control software the user paid to have installed by a smart home professional.

Precisely why as a smart home professional I use custom programming to take care of such issues. 

Just now, Eric Stiff said:

I'm doing custom programming along with a contact sensor through one of the relays on mine to detect a loss of power. It checks the relay state once a day in the early AM and also when the project loads at controller boot up. When it determines power has been lost because the really is now open, there is a 15 minute delay to make sure everything is booted and settled, a cancel command is sent, then a home command, then a sleep command.

This is also why I wish the Sleep state was a checkable status on the Shield. Currently Power On or Power Off are the only states listed and when it's "sleeping" it still registers as "On." This may be a limitation of Android itself and something @videostorm doesn't have any ability to work with.

11 minutes ago, elee532 said:

 

What about a screen that says something instructional for the non techie? Family members have powered on to find this screen after an unplanned reboot, and had no idea what to do. Maybe something like "Irusb successfully launched to control your Nvidia Shield. Press the Menu button to go back to the Shield home screen."

I'm doing custom programming along with a contact sensor through one of the relays on mine to detect a loss of power. It checks the relay state once a day in the early AM and also when the project loads at controller boot up. When it determines power has been lost because the really is now open, there is a 15 minute delay to make sure everything is booted and settled, a cancel command is sent, then a home command, then a sleep command.

16 minutes ago, Eric Stiff said:

I can now confirm this does not work.  I have to put the full QHID command in a custom app line and call them that way.  Also, I am now getting this repeating error code in the Shield LUA window (the filename is different because I pack Nvidia icons into the c4z so I'm not looking at Fire TV icons for my Nvidia Shield):

LUA_ERROR [id: 383][name: Universal Android Driver With Nvidia Icons][file: mediaplayer_android_irusb_shield.c4z][method: ReceivedFromNetwork]: [string "Lua Code"]:762: attempt to compare number with nil

 

This error goes away when I reboot but eventually comes back.

@videostorm Ok, I was wrong.  I did a hard reboot and when the IrUSB app started the error message came back.

55 minutes ago, Eric Stiff said:

I considered that but wasn't 100% sure because it only references the CCC part when inserted into the script.

 

I can now confirm this does not work.  I have to put the full QHID command in a custom app line and call them that way.  Also, I am now getting this repeating error code in the Shield LUA window (the filename is different because I pack Nvidia icons into the c4z so I'm not looking at Fire TV icons for my Nvidia Shield):

LUA_ERROR [id: 383][name: Universal Android Driver With Nvidia Icons][file: mediaplayer_android_irusb_shield.c4z][method: ReceivedFromNetwork]: [string "Lua Code"]:762: attempt to compare number with nil

This error goes away when I reboot but eventually comes back.

5 minutes ago, videostorm said:

Use the Send_HID command.  The parameters are ABBBCCC from the full command.  Home is QHIDCODE2002035\r (A=2, BBB=2, CCC=35)

I considered that but wasn't 100% sure because it only references the CCC part when inserted into the script.

34 minutes ago, Eric Stiff said:

It's actually the "Guide" command (mapped to Home which is the Circle button) when held too long that opens this menu.  I would most definitely prefer the direct "Sleep" command.  I'll punch that in and see how it does.

The reason I want Cancel the current action and then execute the Guide (Home) command is to make sure the Shield is on the home screen before it goes to sleep. There isn't an option for it to go Home and then go to Sleep, it's just either/or. If I have it just go Sleep and then Home on Power On, the next time I start the app I was running before turning things off, it will start where it left off. I don't want that. Also, there have been times when just using "Go Home on Room Off" hasn't actually gone Home.  The biggest offender has been Amazon. 

Edit:  It looks like the only way to run a custom QHID command is in one of the custom app fields.

25 minutes ago, videostorm said:

Most likely, the "Push Enter" command you are using holds the virtual key too long.

You could just send the sleep command to the shield (QHIDCODE2000052\r), use the sleep timer, or send the short press select HID command (QHIDCODE2000065\r).

It's actually the "Guide" command (mapped to Home which is the Circle button) when held too long that opens this menu.  I would most definitely prefer the direct "Sleep" command.  I'll punch that in and see how it does.

@videostorm Something I've encountered with custom programming.  The included screenshot of code will quite often act like a long press on the Circle button resulting in the situation in the photo instead of putting the Shield to sleep.

20 hours ago, videostorm said:

Yes, our free driver (on our web site) supports this.  Make sure you are using the latest driver and IRUSB firmware.

Is there any place on the website where the current driver version is referenced?  Currently there are only three ways I know of to figure out the current version

1) It's mentioned here.

2) Download it again and try to update it in composer. It will either update or it will fail because the versions are equal.

3) Download it and open the xml to read the version number.

Having it listed on the site would save a lot of time. 

1 hour ago, drmark12pa said:

What setting are you using in Composer other than 2000ms and on your Shield?  My Shield initially lights up and light goes off when using miniapp.  Then have to hit WATCH again to get it going so new driver has not solved anything for me at all

This is how the driver is setup in my system and the related programming.  The programming at the top is there for when the power glitches and the Shield reboots.  I wired the 12V output to the common on a relay and the N.O. of the relay to the contact sensor input. So when the power glitches, the relay will open and the system will know once it's booted that the Shield is now awake. I have to hit guide to close the IRUSB app because Android does not yet support background loading of an app. I have a 10 minute delay to make sure everything is fully loaded and the driver will be able to control the system.

On 5/6/2020 at 12:24 PM, videostorm said:

We just released a new driver version (19 / 3.6) which addresses this.  The latest Shield os takes a little longer to wake from sleep, so we made the launch delay longer to compensate (from 500ms to 1000ms).  We also added the "AppDelay" property to allow you to adjust this yourself if needed.

Latest driver is on our web site as always.

HOORAAAAAAAYYYY!!!!!!!!!  The default 1000 was still too slow for my Shield but 2000 works just fine. I didn't bother trying anything in between as the TV still takes several seconds longer than that to display an image.  The Disney Plus and Hulu UMDs are also now working and the built in Disney Now for the colored buttons still fires up Disney Plus too.

The only other option I think would be cool to have is a dual "On Room Off" action.  I'd like to be able to tell the Shield to go Home and then tell it to Sleep. I don't want to tell it just to go to sleep on "Room Off" as there are some that when they get tired they just hit room off without even stopping whatever they are watching thinking it will just either stop or go home so they can resume later. Yes I know it can automatically go to sleep after a certain amount of time, but I want it to go to sleep pretty quickly after the room is off. I can do this through programming with one small "issue:"  sleep is not a valid choice under conditional checks, just Power On or Power Off; Sleep apparently does not equal Power Off. I attached a screenshot of the conditional programming I used to make the sure the Shield is truly put to Sleep. So what I observe is this: when the Shield isn't used, the LED is off, I press Room Off after I have been watching Dish TV, after 5 to 10 seconds the Shield LED turns on, then a second later turns off. "Sleep Now" is the first option when Menu is opened. So when the Shield goes to sleep it apparently still registers as "On."  My next step is to experiment with variables to prevent it from waking up the Shield just to put it back to sleep. lol

Thank you @videostorm!!!!!!!!!!!!!!!!!!!!!!!!

1 hour ago, fbrea said:

Hi Eric any luck. I'm also interested. Want to do custom drivers for streaming apps like stremio, and many others on my Shield

It wasn't me looking for help, it was msgreenf asking the question. I was just tagging VideoStorm in case they could help. BTW, if you need remote help, @msgreenf is a great person to ask.

On 4/20/2020 at 9:12 PM, msgreenf said:

 

Does anyone have an example of a custom mini driver for shield? I have the qlaunch but I need the right driver template.

 

@videostorm?

2 hours ago, Eric Stiff said:

Support ticket submitted for when the schedule permits. 

 

In the driver.xml there are both "power_delay" and "power_command_delay" entries.  Changing these and re-adding the driver had no effect.  

On 4/7/2020 at 11:35 AM, videostorm said:

There is likely a timing / order of commands issue at play on your room power up.  Please submit a support ticket at http://netplay.freshdesk.com/

Include the LUA log for the problematic sequence.  Also the exact hardware (Shield & C4 controller) and any other pertinent info.  We can then reproduce the issue.

Disney Plus is currently named "Disney Now" in the driver.  Use the mini driver for Disney Now for Disney Plus.

Support ticket submitted for when the schedule permits.