RyanE

This is factually incorrect.
The Harmony remote's hardware and software would not be terribly useful for Control4.
Harmony's remote hardware capabilities are terribly dated, and their software would not be even as easy to turn into a Control4 remote as the Neeo was.
That would be a downgrade over the Halo remotes.
RyanE

As others have said, Neeo has always been able to be able to be set up by end users (installers can lock the system however to prevent end users adding them, but nobody does)
It could be compared to allowing end users to add their own mobile phones to the system. As Mitch mentioned too, Sr260 is a bit different and needed Zigbee.
It's a bit more complicated than being able to simply add drivers too.
Lets say a user adds a driver which causes the controller to crash? Suddenly, they also need the ability to remove drivers too and to access lower level parts of the controller.. Which also means they could remove drivers which are critical accidentally. It also means that if the driver is doing dodgy things (like the ping driver), who supports users who install their own drivers? Does SnapAV take responsibility? Or is it the dealer? What if they don't have a dealer? An installer maintaining the system has no way of relying on the setup of the system being reliable. Which means even minor issues may require a call-out. Technical support for 3rd party drivers also becomes less efficient, so costs of drivers will likely skyrocket, and support for certified installers would also suffer. Installers are given proper training which helps bypass a lot of support issues (and ensures bug reports are fairly succinct).  
Systems like Control4 are designed to be both powerful, and quick to deploy by trained installers. Dealer managed systems aren't for everyone, but in my opinion, work well for the jobs they're designed for. There's a lot of possible flow on effects though with opening any part of the system, which would completely change the audience it is suitable for (for better and worse). Opening things up as an example could open it up to a range of new users, but it could also lose the existing ones because of other side effects. In my opinion, its not really designed as a DIY system

This is factually incorrect.
The Harmony remote's hardware and software would not be terribly useful for Control4.
Harmony's remote hardware capabilities are terribly dated, and their software would not be even as easy to turn into a Control4 remote as the Neeo was.
That would be a downgrade over the Halo remotes.
RyanE

Not an official company response, but I'd say in general, this is most likely not a change in policy.
As others have mentioned, the Neeo could also be added without the participation of a Control4 partner.
RyanE

This is factually incorrect.
The Harmony remote's hardware and software would not be terribly useful for Control4.
Harmony's remote hardware capabilities are terribly dated, and their software would not be even as easy to turn into a Control4 remote as the Neeo was.
That would be a downgrade over the Halo remotes.
RyanE

LOL no.
RyanE

He specifically says in the beginning of the article that he got one "ahead of the official launch".
The story was probably written days ago, and embargoed until the launch date.
RyanE

Ah yeah - sorry, I had it backwards.
$900 MSRP on the Halo Touch, $500 MSRP on the Halo.

Yes, but how it would do it is to have the Core 5 literally decoding the audio one time per output, and sending the 'sync' info between internal players.
It's very inefficient, CPU-wise, vs. just having an actual switcher.
Also, if you're using the controller's audio inputs for a source, that source is delayed for enough time for the outputs to be 'in sync', which is usually a couple of seconds.
An audio switch is the right solution for multiple zones.  Hacking it without one is never recommended.
RyanE
 

It certainly has issues for some people.
That said, person who responds to the thread a year later: I have absolutely no issue with the half dozen I have around my house.
They are locked to their own 2.4 GHz SSID, can't roam, etc., and never fall off the network.
RyanE

As I've mentioned a number of times on here, I do not speak for Control4 on these forums.
My issue is really that there are plenty of other more recent discussions of the Neeo that address the Wifi performance, that would be a more appropriate place to vent.
It is not an 'awful remote' by any stretch.  Most installations are not having constant wifi issues, even with the limitations of the TI chip used in the Neeo.
And yeah, I can be obnoxious.  At the end of the day, hopefully the value of my contributions here will be found useful enough to overcome that.
RyanE

As I've mentioned a number of times on here, I do not speak for Control4 on these forums.
My issue is really that there are plenty of other more recent discussions of the Neeo that address the Wifi performance, that would be a more appropriate place to vent.
It is not an 'awful remote' by any stretch.  Most installations are not having constant wifi issues, even with the limitations of the TI chip used in the Neeo.
And yeah, I can be obnoxious.  At the end of the day, hopefully the value of my contributions here will be found useful enough to overcome that.
RyanE

I don't know any specifics of this particular integration, but sometimes features like this don't happen in controllers due to per-unit licensing costs.
Expensive to license for every controller when it's not going to be used but in a relatively small number of them.
RyanE

https://annex4.link/drivers/samsung-mdc
 

There’s a 3rd party driver for Samsung commercial displays. Forget which marketplace has it though. 

Not true - but sure spin it how you want.  The Control4 implementation was based on security and improvements for mesh size and scalability.

but with the yale August card you have 1) cloud dependency 2) another app to configure and use and 3) the BT wifi bridge.  Just buy the right card and it's much cleaner

because that on the garage door open.  It won't actually fire when the timer expires.  You need to send the push notification on timer expired.

Or you could use the 'relay garage door' driver, freely available in Control4's online database.  It provides a nicer Experience Button interface as well.
It has an configurable 'open time' after which it will fire an event.
If you have multiple contacts (door fully open and door fully closed), it can also alert you if the door takes too long to open or close.
RyanE

Or you could use the 'relay garage door' driver, freely available in Control4's online database.  It provides a nicer Experience Button interface as well.
It has an configurable 'open time' after which it will fire an event.
If you have multiple contacts (door fully open and door fully closed), it can also alert you if the door takes too long to open or close.
RyanE

Or you could use the 'relay garage door' driver, freely available in Control4's online database.  It provides a nicer Experience Button interface as well.
It has an configurable 'open time' after which it will fire an event.
If you have multiple contacts (door fully open and door fully closed), it can also alert you if the door takes too long to open or close.
RyanE

Note that the recommendation would be to make sure the SSID the Neeo is on is a 2.4Ghz ONLY channel - as in not use a mixed channel SSID for them

In theory if the amp is always on, the (numbers should always be lit up), there shouldn't be any delays even the first time that something is played.  It *sounds* like he has it set to Audio sense, but he's saying its set to ON...

The Timer Agent is just a C++ driver.
All agents are drivers, but are limited to a single instance, and they show up in the Agents tab instead of System Design, and have a different type of UI.  They don't require any more resources than any other driver, and as the Timer Agent is a native C++ agent, it likely requires fewer resources than the DriverWorks Lua drivers.
RyanE

The Timer Agent is just a C++ driver.
All agents are drivers, but are limited to a single instance, and they show up in the Agents tab instead of System Design, and have a different type of UI.  They don't require any more resources than any other driver, and as the Timer Agent is a native C++ agent, it likely requires fewer resources than the DriverWorks Lua drivers.
RyanE