Jump to content
Flirc Forums
Sign in to follow this  
PeterMac

Search button from keyboard on Flirc

Recommended Posts

Hello,

I bought Flirc for my Nvidia Shield TV to learn Voice Search key and first I learn Windows key by command line (by this command flirc_util.exe record_api 8 0) which work fine but what I noticed now this command always turn on Google Assistant not real Voice Search in apps like on YouTube, Spotify etc.

I connected my Logitech K400 Plus keyboard which have "Search" key on F5 key (this is not F5 key, on this keyboard to push F5 you have to push it with FN, without combination with FN it's a Search key), and this key work corectlly, on Home menu it turn on Google Assistant, on YouTube app turn on Voice searching exactly the same as orginal Shield remote.

So my question is how to learn this "Search" key on Flirc ?

I will be very appreciate for help.

 

-font-b-Logitech-b-font-Wireless-Touch-Keyboard-font-b-K400-b-font-Plus-with.jpg

Edited by PeterMac

Share this post


Link to post
Share on other sites

The correct buttons for the Shield are all from the HID Consumer table (despite what NV seems to mention).  The Search is 0x221 AC Search.  This is not supported by the current Flirc software as it can't do any consumer codes above a certain number.

If Flirc were updated to support all consumer usage table codes it would be a lot more versatile as a general purpose HID input device. There are many USB-enabled products that may still employ very custom HID solutions, but a composite device with keyboard & consumer at a minimum would do most everything posters here are interested in.  

This is a great suggestion: 

 

IMO, why stop there though. Full support for all (sensible) usage tables would be even better.  Gaming device, LED, Generic desktop,  simulation - this would require being able to set a lot more parameters than the current keyboard-only codebase allows.

Edited by foto808

Share this post


Link to post
Share on other sites

@foto808 well, it's not that easy. It's not enough to send a hid report with specific hid usage, the device needs to first send a hid descriptor telling the host system what it is and what it does. If you send gamepad usage codes without first telling host system that you're a gamepad, the system won't know what to do with that report.

Also many hid codes have extra payload like the X/Y axis position.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×