RyanE

Yes everything has worked perfectly for almost a month now. It seems that the IP interface driver on C4 cannot handle a large amount of traffic (also there could be a limitation from the Ip interface as well). But the IP Router driver is meant for larger deployments with more data back and forth between C4 and the KNX IP Router. From now on we will only use IP Routers regardless of deployment size and I recommend the same for everyone else.

Talk to your dealer (firmly!) - there is a reduced cost replacement program that ran for awhile, and may still be in place

Still in place. Got one 2 weeks ago. 

I don't believe you can have dynamic commands in a driver.
Commands and actions are only specified via the XML structure, and can't change dynamically.
You could have the commands and actions not perform anything when called, and indicate this with a 'Status' field in the properties, but that's about all you can do at this point in time.
RyanE
 

Ryan: Thanks so much! This totally was the issue.
Once I labeled my buttons, they showed up on the Neeo (nice touch that I didn't have to restart the remote -- it detected that a change had been made and it reloaded the settings automatically).  I now have the ability to run scripts with custom buttons. My power knows no end! 

So first you need to go into the remote's properties, and give the Remote Focused Button a name.
If they're not named, they don't show up on the remote.
Once you've done that, they should be one swipe left of the 'home' screen (which you get to by pressing 'home' on the remote).
RyanE
 

Awesome!
Given that it is Android, you could also run our SplashTiles app / tool to add live sports scores, stocks, or traffic maps.  Probably other ways to do it as well if it supports widgets.
 
 

Another Pic...

Aftermarket with a design to integrate and retain most of the factory oem controls.   And look factory.  They are very car model specific as the factory audio and climate harnesses plug and play with the screen. It’s not just a screen as it has a full radio integrated.

To clarify, the original NEEO remote was a Kickstarter project, and was intended as a standalone remote, which came with it's own hub.  Unfortunately, support for the original NEEO remote was limited to 2 years from when Control4 bought the company, so there's really no ongoing support for this configuration.
The Control4 Neeo remote uses very similar hardware, but was not designed or intended to use as a standalone remote, and will not work as such.
RyanE

Also to add to this the economics of driver development are like any other piece of software.  You have expenses (Employee salaries, computers, software, office space, etc) that need to be paid and as such have a minimum rate to ensure that what you are building is profitable.  Some drivers are cheaper as they are less time / resource intensive and others will require muliple programmers, graphics designers, etc to contribute for the project.  As such one off projects are definately cost prohibited.  We have had customers pay us for custom development and they have justified it as the money they save on not buying an alternative product (eg a blind in the case i am thinking of) is enough to warrant commissioning the project.
Having said all of that the majority of people who contract us nowadays are manufacturers and we are finding that we are doing less of our own IP and more contracted work.  You can find the majority of these contracted (and free drivers) via our website (http://www.chowmainsoft.com) with some others being certified (with SDDP implemented) and available via the online Control4 database.
We do however still invest into passion projects where we see gaps in the solutions and we find a product that will fill that gap.  There are actually a ton of passion projects i want to complete but unfortunately contracts come first.  Hopefully now that we have 3 inhouse Control4 developers we will complete more of these passion projects but regardless you will see more output from us for Control4.

I want to chime in on this.
Control4 asked us to attend a meeting at ISE last year with their senior VPs.  In summary they told us (and also every other major Control4 driver developer) to stop reverse engineering APIs and to provide them with the details of the systems we reverse engineered so that they can assist us with creating a relationship with that particular company to stop the API from breaking in the future.
In short there were a few 3rd party drivers out in the wild that broke and caused Control4 alot of headaches.  Not sure if it was just customers complaining or legal issues but regardless it was enough for them to warn all the major 3rd party developers formally.  In fact we were all reminded about the agreements we signed with Control4.
As such our business practices changed to not develop any driver that contains reverse engineered code or if we do reverse engineer it we would create a partnership with the company to ensure that the APIs do not break and they understood that we were using them.
By partnering with these companies we ensure that there is no disruption to the home owners Control4 experience.
A good example of this is an upcoming driver we are about to release in the next week or so (we partnered with a company to do this).  Here is a sneak peak.

To clarify, the original NEEO remote was a Kickstarter project, and was intended as a standalone remote, which came with it's own hub.  Unfortunately, support for the original NEEO remote was limited to 2 years from when Control4 bought the company, so there's really no ongoing support for this configuration.
The Control4 Neeo remote uses very similar hardware, but was not designed or intended to use as a standalone remote, and will not work as such.
RyanE

Also note that you CAN setup a simple 1 room a/v system with a Neeo plus an EA-1,
Control4 isnt 'just' for full home systems

Do yourself a big favor and find one of the remote dealers on this forum to help you get started remotely. If you are a DIYer than you will want to purchaser composer home edition from the same dealer and have them get you started with that. You will find you can do most things yourself, but you do need dealer support for some critical tasks. Again, dealer support is available remote. Have fun!

+1 for webhooks - i have a webhook on my work computer that will turn off my music quickly if i get a call

For details it's best to talk to specialist directly.
One downside I can think of is that, depending on the quality to a degree, is that tinting will not really block people outside in the dark from seeing inside where it's light.
Weather (especially extreme cold) can affect them, in some rare cases kill them, so again this is something best discussed with a regional specialist carrying them,
There's options for all climates (with or without heating) but as with most things, there's usually a price associated with it. We don't see many here for that very reason.

We were able to implement the IP router and change the c4 driver today for both sites. I noticed that c4 actually responds much faster than the IP interface. So far everything works great. Will monitor it though the weekend. Hopefully this is the right way of setting it up and we wont have any outages.
One observation though, The setup does not work unless we put "transmit all" instead of filter on the IP router. Although usually that setting increases traffic and is not recommended for productions system, but this is what I left it at since it only works on that setting.

Thanks for the reply. I have purchased 2 IP routers and will be testing them out before the end of the week. Thanks again!
 

There is an art mode mini driver that must be installed. 

Are they gen 2? There were color change kits for gen 2 and I believe I still have some. 

The previously-referenced Python code won't work on a 'current' version of Control4, BTW, since it uses C4Soap on port 5020, which is not available off of the controller anymore, for security reasons.
RyanE
 

Oh I see. And if you bought a $5,000 television over 5 years ago would you expect Best Buy to cover it?

Architecturally, the Control4 Neeo remote does not connect to the TV.  It connects to the Control4 controller, which then issues commands for the TV.
I bring this up because if you're having control issues that are Neeo-specific (control of the TV is working fine with the Control4 app and other remotes), it's most likely a wifi networking issue, since the Neeo uses wifi to connect to the Control4 system.
RyanE
 

Finally installed.