RAV

Josh is a luxury product.
(they prefer Boutique, but fact is, it's an item that if you try to justify the cost, you'll struggle)
They're building hundreds of micros, not a hundred thousand alexas.
There is also dealer profit, see top statement. They're not giving it away to mine your data.
So you're going to pay quite a bit more than Amazon or Google products.
Is it better than the other options, by a long shot.
It's also private.
It's also more reliable for integration.
And flexible.
And software designed for the AV market.
As to micro vs nano. See top statement again. Nano is beautiful and discrete and slick. It needs a hub, because the wall part is so little, and no room for a speaker, so need for appropriate playback. Nano doesn't do anything that micro can't, except be sexy.
Control4 has not, at this point, made any concessions in software to accommodate Josh, frankly it's all on the Josh side currently. Josh built it really well to absorb from Control4, who was already done in a way that it makes a great match.
Josh is foremost not positioning itself to be an addon, they would just as well prefer to be totally standalone home integration. The trouble is, there's a very small sandbox of players to make that happen and they need some outside processing to integrate the rest. And they benefit from a distribution partnership and dealer connections that Control4 can provide. It's a good relationship, but not a marriage, and not sure it should ever be more than really good best friends.
 

There's too many things in Control4 named favorites, so it's easy to get confused.

With apple watch - you need to
1. favorite the room itself, so it'll show up in the watch app
2. favorite something from within the rooms navigation so it shows on the rooms main page outside of Watch Listen or Lights, and that item needs to be actionable when it's clicked, ie it does something without further selections.
Music favorites aren't the same thing. Just because you made Classic Rock a favorite music channel within Pandora, it doesn't mean it'll show up in the watch.
You have to then go into Pandora, press and hold the Classic Rock music channel, so that gets favorite all the way out to the room level.
Now it'll show up in Apple watch.
To get volume and or transport, use the less often used older Custom Buttons feature. Which used to put a text in the four corners and a drop down menu.
Now it makes a 'folder' in the GUI. That same folder will show up in Apple Watch once you favorite it to the room.
You get 6 items per custom button sub menu. So Vol +, Mute, Vol -, Off, Pause/Play, Skip gives you fairly simple control over music, once you've favorite a couple of music channels/playlists to the room level.

Somebody's got to pay for it.
1. just those who use it - 4sight
2. everybody - markup the products and figure 10 years of developement/server costs per user
3. sell everybodys data, the popular choice of many IoT companies
If it's "free", "included" then everybody pays.
(History lesson, there was a time when these and more were all added licenses. Processors were cheaper. Intercom, Phone, 4Sight, Major Upgrades were all add on license fees. For example: $500 for intercom, $100 per phone for the app.)
 

Somebody's got to pay for it.
1. just those who use it - 4sight
2. everybody - markup the products and figure 10 years of developement/server costs per user
3. sell everybodys data, the popular choice of many IoT companies
If it's "free", "included" then everybody pays.
(History lesson, there was a time when these and more were all added licenses. Processors were cheaper. Intercom, Phone, 4Sight, Major Upgrades were all add on license fees. For example: $500 for intercom, $100 per phone for the app.)
 

If its just a couple of routine broadcasts, "Dinners Ready", then you can just use the Annouincement Agent built in to play a WAV file.
 

Somebody's got to pay for it.
1. just those who use it - 4sight
2. everybody - markup the products and figure 10 years of developement/server costs per user
3. sell everybodys data, the popular choice of many IoT companies
If it's "free", "included" then everybody pays.
(History lesson, there was a time when these and more were all added licenses. Processors were cheaper. Intercom, Phone, 4Sight, Major Upgrades were all add on license fees. For example: $500 for intercom, $100 per phone for the app.)
 

Best to think of it like a multi page software keypad on your wrist.

Need to touch a "button" from the main room screen and have it execute without any other touching or prompting.
So favorited devices like: lights, scenes, channels, streaming services (Netflix), playlists, and executable experience buttons.

You do get custom button 'folders' which is nice. So you can change surround modes for example in a theater easily without digging down in the remote.

Got 2, swap the screens, then you'll know if it's the screen or somewhere in the backbox or power source.

My bet as well.

It'll just cost you more.
But sounds like your mind is made up to use Lutron. Extra time in programing, hardare a little more with duplication of processors, but you can accomplish what you want, Lutron integration is excellent.
The grey area is keypads. If you want them to control your music system volume and what not, then Control4 keypads are more adept. If it's just a couple buttons for away to turn down heat etc, you could stay with Lutron for keypads.

It'll just cost you more.
But sounds like your mind is made up to use Lutron. Extra time in programing, hardare a little more with duplication of processors, but you can accomplish what you want, Lutron integration is excellent.
The grey area is keypads. If you want them to control your music system volume and what not, then Control4 keypads are more adept. If it's just a couple buttons for away to turn down heat etc, you could stay with Lutron for keypads.

To get on the same page:
Processors run Zserver and Zap.
Zserver is the software router, and Zap the hardware device that actually communicates to the devices.
Each Zserver can handle 70 devices.
Router Nodes are non battery powered units and relay commands to other nodes, old stuff (pre 2013 lighting) was limited to the number of end notes (6) EACH router node can communicate with, and zio can do twice as many as lighting (32 vs 16), which only practically matters when there's few router nodes and lots of end nodes.
End nodes do not relay a signal: remotes, thermostats, locks, shades, other battery things.
There are no "extenders" only "repeaters". (even though the literature and guides still uses the wrong nomenclature)
Zigbee distance in an optimum environment, 30'. Typical 9-15'. Bad 6'
Same frequency as WiFI 2.4. Best channels 15, 20, 25. 25 cleanest but also less power as it's limited by FCC.
Multiple servers VS 1 server and multiple zaps.
Over the years this has changed a lot.
Current recommendation is to setup multiple Zservers, idea being as many devices as possible directly communicating with the Zserver, and fewest hops.
Only practical reason for single mesh is portable zigbee devices that need to work through out a large project with multiple zaps, ie remotes taken from room to room.
(the other case may be lighting popcorn, where very large lighting scenes may not trigger at the same time over different Zservers)
Don't stick them within 15' of a Wap.
Don't stick them in a metal rack.
Don't stick them in the corner.

To get on the same page:
Processors run Zserver and Zap.
Zserver is the software router, and Zap the hardware device that actually communicates to the devices.
Each Zserver can handle 70 devices.
Router Nodes are non battery powered units and relay commands to other nodes, old stuff (pre 2013 lighting) was limited to the number of end notes (6) EACH router node can communicate with, and zio can do twice as many as lighting (32 vs 16), which only practically matters when there's few router nodes and lots of end nodes.
End nodes do not relay a signal: remotes, thermostats, locks, shades, other battery things.
There are no "extenders" only "repeaters". (even though the literature and guides still uses the wrong nomenclature)
Zigbee distance in an optimum environment, 30'. Typical 9-15'. Bad 6'
Same frequency as WiFI 2.4. Best channels 15, 20, 25. 25 cleanest but also less power as it's limited by FCC.
Multiple servers VS 1 server and multiple zaps.
Over the years this has changed a lot.
Current recommendation is to setup multiple Zservers, idea being as many devices as possible directly communicating with the Zserver, and fewest hops.
Only practical reason for single mesh is portable zigbee devices that need to work through out a large project with multiple zaps, ie remotes taken from room to room.
(the other case may be lighting popcorn, where very large lighting scenes may not trigger at the same time over different Zservers)
Don't stick them within 15' of a Wap.
Don't stick them in a metal rack.
Don't stick them in the corner.

To get on the same page:
Processors run Zserver and Zap.
Zserver is the software router, and Zap the hardware device that actually communicates to the devices.
Each Zserver can handle 70 devices.
Router Nodes are non battery powered units and relay commands to other nodes, old stuff (pre 2013 lighting) was limited to the number of end notes (6) EACH router node can communicate with, and zio can do twice as many as lighting (32 vs 16), which only practically matters when there's few router nodes and lots of end nodes.
End nodes do not relay a signal: remotes, thermostats, locks, shades, other battery things.
There are no "extenders" only "repeaters". (even though the literature and guides still uses the wrong nomenclature)
Zigbee distance in an optimum environment, 30'. Typical 9-15'. Bad 6'
Same frequency as WiFI 2.4. Best channels 15, 20, 25. 25 cleanest but also less power as it's limited by FCC.
Multiple servers VS 1 server and multiple zaps.
Over the years this has changed a lot.
Current recommendation is to setup multiple Zservers, idea being as many devices as possible directly communicating with the Zserver, and fewest hops.
Only practical reason for single mesh is portable zigbee devices that need to work through out a large project with multiple zaps, ie remotes taken from room to room.
(the other case may be lighting popcorn, where very large lighting scenes may not trigger at the same time over different Zservers)
Don't stick them within 15' of a Wap.
Don't stick them in a metal rack.
Don't stick them in the corner.

To get on the same page:
Processors run Zserver and Zap.
Zserver is the software router, and Zap the hardware device that actually communicates to the devices.
Each Zserver can handle 70 devices.
Router Nodes are non battery powered units and relay commands to other nodes, old stuff (pre 2013 lighting) was limited to the number of end notes (6) EACH router node can communicate with, and zio can do twice as many as lighting (32 vs 16), which only practically matters when there's few router nodes and lots of end nodes.
End nodes do not relay a signal: remotes, thermostats, locks, shades, other battery things.
There are no "extenders" only "repeaters". (even though the literature and guides still uses the wrong nomenclature)
Zigbee distance in an optimum environment, 30'. Typical 9-15'. Bad 6'
Same frequency as WiFI 2.4. Best channels 15, 20, 25. 25 cleanest but also less power as it's limited by FCC.
Multiple servers VS 1 server and multiple zaps.
Over the years this has changed a lot.
Current recommendation is to setup multiple Zservers, idea being as many devices as possible directly communicating with the Zserver, and fewest hops.
Only practical reason for single mesh is portable zigbee devices that need to work through out a large project with multiple zaps, ie remotes taken from room to room.
(the other case may be lighting popcorn, where very large lighting scenes may not trigger at the same time over different Zservers)
Don't stick them within 15' of a Wap.
Don't stick them in a metal rack.
Don't stick them in the corner.

The issues are in what is going to change over the next 5 years?
Streaming stuff - always in flux.
Phones and OS - a mess and uncontrollable.
Cloud services - daily issues.
Third Party - on a whim.
Network Specs/Security - need touches.
The Internet - if it touches the internet, it's a liability.
Lamp tech - lots of changes coming.
Remove those from any tech home, and you're not left with much.
Can you design a low touch system, that's resilient, sure.
Will it be whizz bang and control everything, nope.
Solid network with remote support.
Don't skimp on controller over build in quality and processing, have redundancies, use touchscreens and native equipment.
Address power.
Limit the 'yeah, I can make it do that'
Make sure as much as possible can exist on it's own, don't hide stuff, no whacky solutions, if aliens steal the processor the home should still function for weeks.

YTTV, left cable and I was a Charter Tivo user. No regrets other than the channel infighting BS that happens occasionally.
Great thing about YTTV, the custom guide. Your channels in your order.
All the networks together, than sports, than movies, than ehh channels. Make it to the news at the bottom, then it's time to go read a book.
Can't say I miss the numbers with that (and you can easily flip to all channels)
Also the great DVR. We seldom watch live other than sports.
And if you decide to add a show to the DVR, odds are it'll add all episodes for immediate access.
Watch it on the tablet, to go, flexible.
Agree, cost savings isn't as much as it used to be. But the added flexibility, no cable boxes, makes it worth it.
 

A hobbyist prefers to spend their TIME doing a task.
There's a very LARGE base, who want it all done for them. Whether that's changing car oil, setting up a printer, or even hanging Christmas lights.
Some people visiting this site want to validate their dealer's recommendation, or know they're making a good choice, or the implications of a choice.
Others may want a full DIY option.
This relates strongly to networking, cameras, and other subsystems relating to Control4.

I picked these up along the way:
Link Expires 1-7-22
https://www.dropbox.com/sh/66mp1a7kgxtd5h7/AAAFQo6zJoybPkWaW0mCK-Ywa?dl=0

Side or down as well, ....avoid dust and debris into jacks.

AnthemAV

https://www.anthemav.com/products-current/series=mdx-series/model=mdx-16/page=overview

I use Kasa for Christmas lighting, works very well, bunch of window candle plugs, tree etc, and outdoor dongles.
You can do all the setup in Kasa yourself, then provide an integrator with a list of MACs and names and such.
When I put them away last year I labeled them, but them back the same, and no reprogramming was necessary in Control4 or Kasa or Alexa this year.
Reminder Kasa has a strip of 6 switched outlets, and the outdoor dongle 2 switched (I know you focus on dimming).
Don't forget Shelly. Use a little project box and cut onto each set of cords, switches and dimmer modules, probably $40 ish per.

"Alexa discover devices" repaired the connection for me the morning after.

Think of it like firing the assistant manager. Control4 was collecting and displaying the information to you in a consolidated manner, and handling a lot of the little stuff. Firing them, means taking it on yourself, you save the overhead costs and accept the time required to manage.
You don't have to fire them all at once. You can scale back to control some parts. Your budget, timeframe and wants.
Pop the doorbell for a Ring, easy enough.
Reconfigure the music to all Sonos, probably a few Ports.
Eccobee already can run in it's own app.
Setup your TVs for local video sources rather than distributed.
That leaves the lighting, which may be cheaper to leave under Control4 depending on quantity. Get a copy of HE to tweak, as a couple of the guys here for remote support.
You would likely need to go with Lutron RA Select or RA2/3. But yes, it can be replaced without invasive work.

To know if on Generator: Have a wired outlet that isn't on generator, plug in a 12v supply to a contact.
Contact opens, you're on generator.