RAV

When alarm triggers start timer dontmissthetrain.
when bath light is turned on stop timer.
when timer expires play damnit.mp3

When alarm triggers start timer dontmissthetrain.
when bath light is turned on stop timer.
when timer expires play damnit.mp3

Included and Free are nice for the budget, but we're much better off with the the current partnerships.
The ability for others to add key function to a system is huge. We're not tied to the corporate development path.
When Extra Vegetables got absorbed, there was a lot less ability to push the envelope, for a time.
The second wave of 3rd Party Developers have enhanced the platform so much, and strengthened it.
They get hired by vendors to develop free drivers, they add other platforms which Control4 would not bother to address (or are competition) and which the vendor wouldn't expense a driver or see the need to. They listen to dealers needs and create enhancements to the programming ability, saving time and adding more abilities quicker than Control4 could react. And Control4 appears to respect the work the developers do by not incorporating their solutions and cutting off their revenue and stifling creativity.
I don't feel Control4 is relying on them, rather sees them for what they are, an asset to work with, which was evident when the color 'module' was added to Control4 and the developers stepped right up for an almost day of update across multiple developers.
 

SnapOne.
There's money, smart people, designed to be integrated products, manufacturing contacts, distribution, dealer base, exposure, marketing, training, support, peer brands support, and brand pressure to be part of the ecosystem.
Again, not every product is great, but there's a lot to work with there.

Included and Free are nice for the budget, but we're much better off with the the current partnerships.
The ability for others to add key function to a system is huge. We're not tied to the corporate development path.
When Extra Vegetables got absorbed, there was a lot less ability to push the envelope, for a time.
The second wave of 3rd Party Developers have enhanced the platform so much, and strengthened it.
They get hired by vendors to develop free drivers, they add other platforms which Control4 would not bother to address (or are competition) and which the vendor wouldn't expense a driver or see the need to. They listen to dealers needs and create enhancements to the programming ability, saving time and adding more abilities quicker than Control4 could react. And Control4 appears to respect the work the developers do by not incorporating their solutions and cutting off their revenue and stifling creativity.
I don't feel Control4 is relying on them, rather sees them for what they are, an asset to work with, which was evident when the color 'module' was added to Control4 and the developers stepped right up for an almost day of update across multiple developers.
 

This right here. Same for both brands, and most all brands.
Lesson #1 Don't be an early adopter.
Lesson #2 Covid reinforces lesson #1.
Lesson #3 Don't reinvent the wheel, learn the ins and outs what works and doesn't and focus on that.
Just like restaurants, each has their own great dish, but not everything each offers is great.

@RAV Your suggestion makes sense to help dealers better understand  the driver which is indeed complex (because it can do so many things).  However adding a second pared down driver would make things more difficult to synchronize in the future. I have therefore decided to take your example and add a QUICK START section at the very beginning of the documentation.  Can't be missed!
-----------------------------------------------------------
QUICK START – A SIMPLE EXAMPLE
Ask: the client wants to use one keypad button to activate/deactivate a Lighting Scene during the day and a different Lighting Scene at night.  The keypad button LED must show the state of the Scene.
Solution: 
⦁    Install the driver.  Do not modify any properties other than the ones outlined below.
⦁    In Agents/Advanced Lighting, create the Daytime and the Nighttime Lighting Scenes to turn on the required light(s) at the required level(s).  Also create the Default Toggle Scene for each.  As you have modified the Scenes setup, run the driver’s Action ‘Refresh Advanced Lighting Scenes’.
⦁    Use the properties Select Advanced Lighting Scene A to point to your Daytime Scene and Select Advanced Lighting Scene B to point to your Nighttime Scene.
⦁    Set the Control Logic When Activating/ON property to: d = A ; n = B   This means that the first program will activate Scene A during daytime (lowercase d) and the second program will activate Scene B during nighttime (lowercase n).
⦁    Connect the driver’s Toggle Button Link L to the desired keypad button.  You may modify the properties for Keypad LED Active/ON Color and Keypad LED Inactive/OFF Color if you wish.
You are done!  Now, read on…
-----------------------------------------------------------
I hope this will be helpful and point dealers in the right direction.
Paul
P.S. to ALL: Do have a look at the driver's Action to '** Print ALS Reports', especially the Cross Reference report which was asked for in these forums just a few weeks ago.

2-9 Switches
10-19 Power
20-29 Surveillance (most often a VLAN)
30-39 Audio Ends
40-49  Audio Source
50-59 Video Ends
60-69 Video Source
70-79 UI
80-89 C4
90-99 Nas/Matrix/Server types
100-199 DHCP Range
200-219 Client Stuff (printers etc)
220-229 Holding (items we think are or could be a problem or have something odd about them)
230-239 Other Contractor's Stuff (generators, alarm, water, etc)
240-254 APs

Rooms get assigned a number. Rack gets 0
Thus 12, 32, 52, 62, 72, 82, 242 Would be Bedroom Watt, Bedroom Amp, Bedroom TV, Bedroom Apple, Bedroom Touch, Bedroom Processor, Bedroom AP
and 38, 58, 68 are Guest SoundBar, TV, Apple

Maybe not the layout I'd do today, but it's what we've done since forever.

 

More things that can go wrong. Power supply, stickers, aiming, WiFi.... and you still need MyQ 2.0 interfaces per door.
Not knocking their product by any means, but hardwired will always be more reliable whenever possible.
And a quarter the cost.

Use a multi meter, set to continuity, put on two out of the four legs of the button, press button, when meter reads continuity when pressed and open when not, then you have your pair of legs.
Solder leads to those two legs, and wire to a relay closure pair on your controller.

(this remote will show as two pair of legs each function as desired, they double soldered for strength)
We typically save the little RJ45->jack flat flexy adapter cables that come with some access points, and solder those to the buttons and trim the case for a neat finish.

When opens - turn on lights, send notifications, if his/hers customize music etc.
When left open - send reminder, garage heater off
Ability to open - allow access, if detached garage run into in the rain from the house without waiting for the door, forgot keys, if detached warm up car (don't sell this feature)
Ability to close - security, good night, lock up, insulation from temperatures, detached close easily when you forget
Control the power to the opener - lockout when away, classic car, etc.
 

Officially it's called the "Fly Out Menu"

Notes posted.
Over 75 bug fixes, plus Fly Out Menu addition.

Can't speak to the alarm questions.
But run a Fiber for everything network.
Put in a network switch: attach cameras, wifi, control4 processor, Touchpanel (intercom if practical), Tirad One for music, Roku for TV streaming, etc.

So everyone understands.
Nest thermostats and Smokes were originally setup to integrate through a NEST account, and called Works with Nest.
Google buys Nest.
2019 Google presses but doesn't force NEST accounts to move to Google Accounts.
As long as you didn't add to your Nest system, works with nest continued to integrate, so if you had smokes you want'ed through Control4, you stayed with Works With Nest.
Anybody setting up a new Nest Thermostat for Control4 integration since 2019 has used a Google account, and NOTHING changes about this or that, so if you've done it since 2019, ignore, it'll all stay functioning, and you're good.
If your Nest was setup through Works with Nest, you now will need to move it to Google by September, which means smokes no longer will integrate (no API).

So everyone understands.
Nest thermostats and Smokes were originally setup to integrate through a NEST account, and called Works with Nest.
Google buys Nest.
2019 Google presses but doesn't force NEST accounts to move to Google Accounts.
As long as you didn't add to your Nest system, works with nest continued to integrate, so if you had smokes you want'ed through Control4, you stayed with Works With Nest.
Anybody setting up a new Nest Thermostat for Control4 integration since 2019 has used a Google account, and NOTHING changes about this or that, so if you've done it since 2019, ignore, it'll all stay functioning, and you're good.
If your Nest was setup through Works with Nest, you now will need to move it to Google by September, which means smokes no longer will integrate (no API).

So everyone understands.
Nest thermostats and Smokes were originally setup to integrate through a NEST account, and called Works with Nest.
Google buys Nest.
2019 Google presses but doesn't force NEST accounts to move to Google Accounts.
As long as you didn't add to your Nest system, works with nest continued to integrate, so if you had smokes you want'ed through Control4, you stayed with Works With Nest.
Anybody setting up a new Nest Thermostat for Control4 integration since 2019 has used a Google account, and NOTHING changes about this or that, so if you've done it since 2019, ignore, it'll all stay functioning, and you're good.
If your Nest was setup through Works with Nest, you now will need to move it to Google by September, which means smokes no longer will integrate (no API).

Can you supply and maintain your own network, sure.
That's a conversation to be had with your dealer, as mentioned, dealers typically pick a brand rather than trying to learn a dozen.
There are some requirements, and things to watch out for. Networks at that level aren't as plug and play, and many home owners want one person to call to make it right, so that's a decision and a conversation to be had.
As to the rack, maybe hire a 3rd party to review the proposal, there (hopefully) may be more in that line item than just a rack.

Highend vendors remotes are typically afterthoughts, expect nothing.
The HEX codes for that unit can be found on Remote Central, and do not include power on or off or toggle, so those likely don't exist.
Use power controlled outlets for the preamp and amp (turning amp off first, and preamp on first), if the preamp doesn't power on when unplug when on, you'll have to leave it on all the time, or mod the unit by soldering to the standby button itself and using a relay from Control4.

Suggest the Liftmaster 893 universal wireless remote. Works with all color buttons, and can do three doors.
Solder to it's buttons to a dry contact.
https://www.liftmaster.com/893max-universal-gate-and-garage-door-opener-remote/p/G893MAXMC

Condensed from Knowledgebase.
Streaming Services and Limits.pdf

Use an IR driver for AppleTV. One in the database, and better one here:
 

Less focus on A vs U brand. (I'm not using names to make the point)
It's more do you want to manage the network, or pay someone else to do it.
If there's a issue with something not staying connected to the network, or needing tweaks, or updates, are you willing to put in the time.
And be sure the dealer will point the finger at the network first. "We don't have that issue on other projects...." right or wrong, it's a likely outcome.

I sell the A. I prefer to have a company that I can call and get support, and warranty replacements, and updates, and tech training, and what not to support my clients.
Most of my clients can't tell a router from a switch and an AP is a website to get news articles.
U is a viable product, but it's not the business plan I wish to work with. It's good gear, but no backside dealer support.

Using an indoor listed TV outside is asking for trouble. Any installer who does so is exposing themselves to huge liabilities.

https://www.blackwiredesigns.com/3rd-party-driver-sales-discontinued/
Contact info for each and where moving in link.
Many to Drivercentral, and some to HTIcustoms.com, a couple will be discontinued (mostly those obsoleted by newer/other drivers)

Vivint claims they integrate with Control4 and have instructions and driver, I have not tested, but have an upcoming project, so we'll see.
https://support.vivint.com/s/article/Control4-Vivint-Integration-Process