christophers

Spoken like a true AV guy. This is why our industry sucks at networking. 

If you are a network guru should you be asking this? 

HI.  We have not seen this. Have you submitted a help desk ticket for us to look your system?  The email system should allow up to 50 emails (from all our drivers combined) per day.  This has been the same for years.
 
Please put a support ticket in @ https://help.drivercentral.io and we can help you out.
 
Thanks!

It has been posted multiple times.

Post the chat, don’t post the chat, delete the post, post the chat... make up your mind... 🙄
Then you post a link that we can’t access...
This is the first time I have seen Mitch really irritated and all I can say is that he has given lots of us on this site good service and good advice over the years... 
So I draw my own conclusions...

yep yep and yep. if they built that in, we wouldn't have a need for WU anymore. 

The other issue is the lack of a shortcut for "Guide" and "Previous Channel"...unless I am missing something.

Support for this was added with today's V4

actually just did this, i enabled a few options to keep things "cleaner":
- enable developer options (go to settings > about > and tap the build number like 30 times, will show prompts)
- go to developer options (up a level) and enable "stay awake"
- in developer options, i also asked it to tear down apps after exit instead of keeping them active in background to prevent any potential conflicts. 

Ok have implemented the home button mapped to guide as per request.
Remember our driver has automatic room on and room off functionality built in.  This means that you can cast content to your shield from your phone, tablet or event using Google Home and Control4 will automatically turn on the tv, receiver to the right input.
After a period of silence Control4 will turn off the system if the shield is still the current selected source in case you have paused and have forgotten about it (definable in the driver's properties)
https://www.chowmainsoft.com/irusb-control4

Looks like you have it correct.  There was an issue in the driver.  Try version 1.7 (on our site now).  It first checks for a package name match, but if not found will search for a key name match or "Custom App X" match.

Ok, we have an update to both the IRUSB Android App and the Control4 driver.
Changes are:
Added checks in the app to automatically wake your device if we receive a QLAUNCH command and the device is currently asleep Added a new QWAKE command that will automatically wake your device if asleep.  The new C4 driver will send this when "powering on" the source. Added a new option to Sleep the device on room off Added a new property with the current PLAY state of the device Added events for device starts and stops playing media REMEMBER that when the IRUSB app updates you may need to unplug and replug the IRUSB device to restart it.  We try to limit app updates to as few as possible to avoid inconveniencing people who have their devices set to auto update apps.

Here is my setup.  I have hunter douglas fans.  They have built in RF fan speed controllers.  No way to bypass.  So what I did was use their RF remote and turn it on full speed. Then wired in the c4 fan speed controller and  i use that adjust the speed.

I wouldn't recommend the tear down apps after exit.  That could have strange consequences since it that type of behavior is contrary to the standard Android app life cycle.
I do understand disabling CEC, since the Shield will otherwise send ON whenever it wakes and OFF when it sleeps.  If you TV is already controlled by another method or has other sources this isn't a good thing.
Disabling sleep (if CEC is off) shouldn't be needed in general.  Most key commands (nav commands) via IRUSB will wake the shield.  C4 doesn't really know when the shield sleeps though, which is why when you select the device/apps you still need to press a key to wake it up.  We could add something to the app to detect if the device is asleep and wake it without the extra key command if people find it necessary?
If you run into any other issue please let us know so we can get it fixed.  Thanks!

actually just did this, i enabled a few options to keep things "cleaner":
- enable developer options (go to settings > about > and tap the build number like 30 times, will show prompts)
- go to developer options (up a level) and enable "stay awake"
- in developer options, i also asked it to tear down apps after exit instead of keeping them active in background to prevent any potential conflicts. 

one additional thing with the shield: make sure you turn off HDMI CEC and set "go to sleep" to "never" otherwise it will have issues

one additional thing with the shield: make sure you turn off HDMI CEC and set "go to sleep" to "never" otherwise it will have issues

i've actually moved back to the VS driver from chowmain driver due to being able to set "go to home on power off" within the driver itself. without this, my receiver wasn't seeing any new video (b/c i almost exclusively use plex) and requiring me to press buttons a few times to create enough video movement in order to "wake up" the receiver's video processor. 

fwiw, here's my assessment: 
- both drivers are awesome ,and provide super fast control over IP and direct app launching.
- videostorm driver is less "sexy" with the shield icon. my guess is that it's designed for all android tv devices whereas alan's driver has individual drivers for 4 or 5 separate units such as the foxtel box, xiaomi box, etc. 
- videostorm driver requires IP address to be placed in the connections field instead of the main driver "page" . not a huge deal, just a bit different
- [disclaimer: i use tons of alan's drivers and they're all pretty f'n amazing] alan's driver does not have the ability to re-assign the "guide" button to return home. this is what really reduces my ability to enjoy alan's driver in this case. i'm sure he will update the driver to accommodate this in the future, though. 
- videostorm driver has the ability to map the color buttons to specific apps in the main driver page instead of custom programming, this is cool, but of course you're limited to the apps they've considered, which may not work perfectly for certain countries/users
- alan's driver supports kodi full but does not yet support plex full (he's working on it IIRC). if you're using kodi then alan's driver is the winner as videostorm mentioned above
 
just my 0.02 and i appreciate not only alan's dedication to building a bad ass driver (yet again), but also videostorm's awesome community support that went from "hey will anyone use this if we build it" (referring to the IRUSB) all the way to shipping the product and providing a solid driver set with it. thanks to you both

Actually our Kodi driver only has the following
IR control of any external device Fast and responsive IP control for menu navigation / all button support in any app SMS Style Text Entry Kodi App launching We decided to not implement mini app launching into Kodi as the driver is bloated enough already.
Our own IRUSB driver however does have mini apps (along with IR control, fast control, SMS style text entry).  With the method we used to develop the driver adding new mini apps does not involve updating the IRUSB driver.  We just create a new mini app driver with the new parameters entered into the driver's properties.  In fact no lua modification is required.  Anyone can create their own mini app using our architecture.  Just replace the default in the property and change the name and icon to suit and you're done.
If however you don't want to make your own we do have a version you can use as a favourite (just a star as an icon).  You can add as many instances of these as you want and just change the property.  It will persist across reboots.

fwiw, here's my assessment: 
- both drivers are awesome ,and provide super fast control over IP and direct app launching.
- videostorm driver is less "sexy" with the shield icon. my guess is that it's designed for all android tv devices whereas alan's driver has individual drivers for 4 or 5 separate units such as the foxtel box, xiaomi box, etc. 
- videostorm driver requires IP address to be placed in the connections field instead of the main driver "page" . not a huge deal, just a bit different
- [disclaimer: i use tons of alan's drivers and they're all pretty f'n amazing] alan's driver does not have the ability to re-assign the "guide" button to return home. this is what really reduces my ability to enjoy alan's driver in this case. i'm sure he will update the driver to accommodate this in the future, though. 
- videostorm driver has the ability to map the color buttons to specific apps in the main driver page instead of custom programming, this is cool, but of course you're limited to the apps they've considered, which may not work perfectly for certain countries/users
- alan's driver supports kodi full but does not yet support plex full (he's working on it IIRC). if you're using kodi then alan's driver is the winner as videostorm mentioned above
 
just my 0.02 and i appreciate not only alan's dedication to building a bad ass driver (yet again), but also videostorm's awesome community support that went from "hey will anyone use this if we build it" (referring to the IRUSB) all the way to shipping the product and providing a solid driver set with it. thanks to you both

btw - confirmed that "select" within the Amazon app in your updated driver works.
thanks!

@alanchowMight be the HID key used for select.  
hidkey["ENTER"] = "QHIDCODE2000065\r"        -- KEY_SELECT
is what we are using on our driver right now and it seems to be universal.

Well spotted.  I did do plex but wasn't on the list (its on the screenshot though).
I am trying to update plex full to support it as well however am having difficulties as the Plex app for android has this weird function where you can keep clicking back and it will eventually exit plex but not close it.

What is this ir peace device? Does it stop ir signals from fighting with each other?

Sent from my Pixel XL using Tapatalk