RyanE

It will only hold up programming in the same event.  If the event triggers again, I don't recall what happens, whether all the programming waits on the first delay or if it all executes up to the delay a second time.  I don't particularly want to test it...   
If you do a 15 minute trigger on a particular event (let's say a motion sensor sensed motion), and you have other programming on a different event (say, a custom button triggered by a remote, or a *different* motion sensor sensing motion, etc.), it will execute normally.
RyanE

I also don't think anyone has stated it but delays should not be used for motion automation. They will not achieve the correct results you should use a timer or the appropriate driver. 

There is also the security light driver made to do just what you need. 

Just for clarification, it's not a drawback of the Control4 Roku TV driver, it's a drawback of the Roku API, which Control4 has no control over.
If the API had discrete volume available, the driver would as well.
Maybe you were using a different term for driver, but in Control4-land, that means the driver running in Director.
RyanE

There is almost no possibility of the Halo Touch working with webview drivers.
In order to 'work with' webview drivers, a full web browser would have to be included in the remote's firmware.
That's extremely unlikely.  I don't say impossible, because I'm not on the team that's working on the remote, but it doesn't run Android, and adding a browser to a small OS device is problematic.
RyanE

And you can spend more on the soundbar then the TV. Lol. 

Just for clarification, it's not a drawback of the Control4 Roku TV driver, it's a drawback of the Roku API, which Control4 has no control over.
If the API had discrete volume available, the driver would as well.
Maybe you were using a different term for driver, but in Control4-land, that means the driver running in Director.
RyanE

Just for clarification, it's not a drawback of the Control4 Roku TV driver, it's a drawback of the Roku API, which Control4 has no control over.
If the API had discrete volume available, the driver would as well.
Maybe you were using a different term for driver, but in Control4-land, that means the driver running in Director.
RyanE

Drawback applies to all Roku TVs. They don't have discrete volume API command. Only up or down

Both of the lighting systems are standard lighting connections and can be easily retrofitted with any major lighting system out there. Maybe if you went all wireless lighting it would make you have less mechanical options but plenty of wireless solutions as well. What makes you think its would be hard to retrofit. And also lighting is simple essentially once its installed it nearly infinitely customizable on the consumer end with no dealer intervention needed so even if you got rid of control4 for the rest of the automation the lighting will still continue to work as it was orginally installed.
 
My vote would also be for centralized lighting. its much more versatile and a cleaner look. It does cost but you save in other ways.

Hidden banks of dimmers is a hack that was used before centralized dimmers were available from Control4.
It is not recommended now that there are better alternatives.
RyanE

I don't believe any timeframes have been announced yet.
That said, they should not need to wait for a full OS update, so hopefully sooner rather than later.
RyanE

"unknownmac" issue? Identify them via their IP instead. Well after checking if the mac address in the driver is not the wrong one.

Start with the AppleTV integration.  The Xfinity set-top boxes do not have the voice enabled firmware quite yet.  It shouldn't be too long, but we don't have a firm release date at this point in time.
If you are already controlling your Xfinity via IP, you're about as far as you can go right now.
RyanE

I would also say give things a chance. This is a brand new remote with new technology and new firmware. There's only been one production release and I imagine that further releases will enhance the experience. Don't consider it. A never to be updated product. There will be updates coming out

I think HomeAssistant is a pretty capable automation platform at this point, but as others have mentioned, it has a 'diy' UI.  You can make your UI do anything you want, but it's going to still look like a webpage with components.  That's not a cut on them, but that's what it is.  It's not a native UI.
The other weakness compared to Control4 is that HA doesn't have much AV support, and doesn't have any 'native' remote control options.  If you want to do automation plus a home theater or multi-room audio, and want a nice remote, HA doesn't really cover it.
Open source handling sensors with graphs and DIY, it's pretty nice.
RyanE

Have only had the Halo for 24 hours, but not really seeing the huge battery drain problem that some are seeing. I’m also using a UniFi AP at 2.4GHz. 
 
So far I’m really liking the remote. Solid design and just the right size for my hands. 

Sure, you could do that in Composer programming, using a variable to keep track of which 'mode' you were in.
You would then switch modes by pressing red or green, and then you check which mode you're in on the button press, and send the appropriate dish commands.
RyanE

As posted above, on February 3,  I moved my NEEO to a different AP, one that I figured would be worse in every way, especially since it is further away. And now, eight days later, I have had zero problems. So weird. 

It causes the 2 / 4 / 6 / 8 buttons to backlight with red / green / blue / yellow, and then they are used for those button functions.
Colors are a bit washed out (this is from my desk), but it looks like this: https://imgur.com/XHXyDH3
It saves having 4 more infrequently used buttons on a crowded remote.
RyanE 

Greenfield Solutions drivers will be revamped and available on Driver Central soon!  Exciting changes coming that I think everyone will be excited by.

easily solved by buying a remote for each room

ps, the remote is really cool and I find the weighting in the hand fine.  Nice job on the design!
 

I got it to work Ryan.   I was selecting the Roku App Switcher as the video source for the room and then in a second line, launching the App for Netflix and this would not control the app.  When i used instead, Select "netflix" as the video source in the room, it worked.  thanks again!

LOL.  I only have the outside shell of two HC300's under my feet...
That's equivalent to an HC600!!!
RyanE