RyanE

It wasn't me, but it was my boss and PMs.
I'm in all the chats about the vuln though. It's been a wild scramble talking with all the teams to review everything we include in our products and services.

FYI - I found this statement on the Control4 web site.
LOG4J VULNERABILITY RESPONSE
Dear Partner,
On Friday, Dec 10, a vulnerability in the “Log4j” Java library was announced (CVE-2021-44228).
An initial audit of our systems and applications indicates that the vulnerability is not present in
any Snap One mobile application or product.
Snap One’s usage of the affected “Log4j” library is limited to internal, backend services. Based
on available information, we have no indication that the vulnerability has been exploited within
our organization and are confident that there is no impact to customer data.
The security of our products is a top priority and critical to our ongoing commitment to foster
trust and transparency for our customers.
Snap One continues to monitor our systems and applications, as well as information provided
by CISA (Cybersecurity and Infrastructure Security Agency), threat intelligence and other
vendors for new information, and we will continue to take prompt action as necessary.
Snap One Cybersecurity Team

As the hardware has not been announced or released, it's certainly possible that it could use the same Dish API and would not need a new driver.
Why would I commit to something when I have no idea what's going to happen?
On top of that, we typically don't pre-announce new drivers, etc.
Sorry.
RyanE
 

very fair clarification, thanks.  Removing the implicit blame from my post, then - this illustrates the problem very well with these efforts to get everyone on a single standard.

LOL.  I assume you're talking about Control4.
Control4 *proposed* their large network extensions to Zigbee (which are necessary for the large Zigbee networks in Control4 installations to not get bogged down with excessive messaging) to the Zigbee board, to become part of the standard.  It could have been part of the HA standard (which is only one of many Zigbee standards, most of which are not compatible with each other, due to varying security requirements, etc)...
It was sadly not accepted.
RyanE

The PLAY, PAUSE and STOP buttons on remotes are mapped to keypress/Play on the Roku API.
There are no Pause and Stop commands available in the Roku API, which makes sense, since there is also no STOP button on the Roku Remote, and the play button is combined with the pause button.
You are welcome to look at your Roku remote, and confirm with the Roku API, which is publicly available:
https://developer.roku.com/docs/developer-program/debugging/external-control-api.md
You can also see what is being sent to the RokuTV in the driver's Lua output.  When Play, Pause, or Stop are pressed on the Control4 remote, you should see this:
12/09/21 09:11:31 : ----- > 'http://192.168.29.63:8060/keypress/Play' []
If those keys are not working for you on particular apps, it's likely an issue with the app itself, not with Control4's RokuTV driver.
RyanE

Thanks Mitch and Ryan!

I'm sure they do have redundancy ... within the AWS cloud.
Keep in mind that a large scale outage like this is uncommon for AWS. While I agree that its very inconvenient to have all of their cloud services offline for a day, lets not pretend as though AWS does this often, or that C4 is the only major company who experienced outages as a result.
Having an in-house server for redundancy negates a lot of the incentives of using a 3rd party cloud provider in the first place. Maintaining both increases both the cost and work required to keep everything online, where the main benefit of a hosted solution is to decrease both cost and effort. If AWS was dropping off like this every week, every month, or even once every couple of months then, yes, it would be reasonable to suggest that they move away from hosting there or that they have redundancy someplace else. That's simply not the case though.
 
Here I would tend to agree with you. I can see why authentication is best done through their servers, but it seems like there should have been some fail-over process which would have allowed the controllers to authenticate locally. I'm not familiar with the details of Control4's authentication process, and it's possible that something like this is in place but was not triggered due to the fact that AWS was not totally offline. Again, that's just speculation and if someone from C4 would like to correct me, I'd be glad to know.

I was using the third party HTI one - I didn't know that there was a Control4 Roku TV driver.  Is this new?
The appears to work - at least to power on and off.    I was having problems with the 3rd party driver.
Thanks!

Are you using Control4's Roku TV driver, or a 3rd-party one?
You could add Control4's Roku TV driver, and use it to send the PowerOn command.  The 'On' command of the TV proxy will send PowerOn.
RyanE

Today Control4 released mobile webview which is a major feature release for customers running Control4 OS 3.1.3 (or later) with mobile app versions 321.46 (or later). We are proud to announce that we have launched the first 3rd party mobile webview driver for Control4 which is designed to assist integrators to keep in contact with their customerbase through our Contact Us driver for Control4.

The Contact Us driver for Control4 allows integrators to provide an elegrant contact us page on the Control4 T3 touchscreen, Control4 T4 touchscreen, iPhone, iPad and Android devices with the ability to provide their own logo, address, phone and email contact details along with a text field that they can use for whatever they want (eg a short company description or details specific to that project).

The URL is clickable which allows the user to visit the integrator's website on the T3, T4 or mobile device.

On iOS devices a force touch on the phone number will allow them to call the number and force touch on the email will allow them to email the email address.

This provides integrators with the ability to market their business to the people utilising the Control4 system they installed.

We have priced this driver at an extremely low price so that integrators can utilise it in every project.
 

This functionality is now available for all OS 3 customers.  

I currently have 4” cans with standard A19 led bulbs (some philips hue). I just got a couple 4” led retrofit bulbs that have the trim ring built in; I’m probably going to change most of them to the retrofit led because they’re much cleaner looking then the standard A19 bulb with separate trim ring. I can post some pics if it would help. If I were in the build stage I would definitely be going with a clean recessed led and not the screw in bulb cans. I don’t know if that helps at all.

I need Linux Subsystem for Windows, the opposite...
I'd love to get rid of my Windows VM, but my desktop will remain Linux.

RyanE

If this is on a wall that backs into a closet or otherwise 'less finished' area, a panel box would allow you to safely do this, and would likely be allowed by code.
Otherwise, there's no way I'd do this.
I'd wait for the line voltage T4.
RyanE

If this is on a wall that backs into a closet or otherwise 'less finished' area, a panel box would allow you to safely do this, and would likely be allowed by code.
Otherwise, there's no way I'd do this.
I'd wait for the line voltage T4.
RyanE

I’m not an electrician but I’m almost certain you can’t put a POE injector in a wall. Likely a big code violation.  You’ve got line voltage going into it. 

I am not an electrician either, but I am 100% sure this does not pass code. I would definitely make sure this is removed before attempting to sell the home. And I would pray there is never a fire behind the wall that exposes this hidden PoE injector. That said, I might do the same thing temporarily as I waited for C4 to launch a line voltage backing box for the T4.
If this was a permanent solution in my house, I would install a small OnQ panel box or similar to house the PoE injector near the T4, and hang a picture over the panel to hide it.

Im assuming you are going to put the poe injector in an accessible junction box. Maybe use an industrial UL rated version?

*Very* easily.

The Control4 Neeo remote has an STM32F429 as it's main processor.  Single core.  Very low energy.
RyanE

Not that my opinion holds much water here, but in my dealings with Blackwire, Kevin, and their team, I was always highly impressed.  These guys helped me on weekends, odd hours, and with difficult clients.  I'd say one of the best experiences I had while I was in the business, both on software (numerous drivers), and hardware (Just Add Power).  

The Roku API is public, so there's not really much more a paid driver *could* do vs. the Control4 driver.
RyanE

The Roku API is public, so there's not really much more a paid driver *could* do vs. the Control4 driver.
RyanE

On Friday Control4 released their own RokuTV driver

Given your investment and dissatisfaction / non-resolution with the original install/upgrade dealer, I agree.
Customer Advocacy isn't a miracle, and I'm sure they can't solve every problem, but yours sounds like the kind of thing they do.
RyanE