TundraSonic

Both programs are dumpster fires of a legacy system (too harsh?). They work, but are not pretty. The hardest part about programming/configuring C4 is figuring where to go in the layers of enhancements added over time to find stuff. If you use it regularly you'll build up your muscle memory. 

I'm not sure of all the exact differences for an existing setup (if its worth changing out), but the LEAP setup is certainly a huge time saver since it auto imports and sycs all the devices/rooms/keypads rather than having to manually create them and map them all.  takes 5 minutes as opposed to hours for a house full of devices.  And if you add more, you can have the LEAP driver add them, using an action button in Composer (HE as well), and they will even end up in the correct room if you've used the rooms that were auto-created by LEAP in the first place.
I'm not sure if its any faster at runtime, my guess would be that it is, but I haven't done any true comparisons.

Outs or not, I just hope that Josh will be supported by control4 or Snap going forward.  I had this put into my house a year or so ago, and find it really opens the system for use.  My wife was not a huge fan of control4, found it confusing at times.. she loves just being able to tell josh to 'play music in the backyard', or to turn off all the lights in 5 minutes and not have to go to a touchscreen and mess with the hierarchical controls to adjust the 7 thermostats we have in the house.  using alexa or even siri, which we did for a time, is just not the same.

This is exactly why I still prefer the older SR remotes to the Neeo.  I need to be able to use the transport controls without looking for when I watch sports as I ride the FF and SkipFwd buttons constantly when watching sports, which is 90% of my TV watching.

I would NOT count on UI to solve your WiFi problems. Like others we have strange unexplained/insolvable dropouts and slowdowns and too many new bugs introduced with firmware updates that can take months to resolve. And there's no bug tracker so avoiding really bad updates can be difficult.
In the Edge days they were pretty rock solid, that disappeared w/ the UDM world of today. Of the options out there I think UI is one of or the best value but there are a lot of issues that come with those cost savings.  If someone else came along with the UI capabilities but more stability/reliability for 20-50% higher cost I'd be all over it (or same cost but an annual maintenance fee of 5% of the purchase cost or …). 
Definitely keep your Security Spy system. Discreet devices for discreet functions makes for a more robust/reliable system and makes troubleshooting much easier.
 

You could disable chimes at the panel and set up chimes to be announcements in c4. Then manage it with programming.

I cannot recall whether this is possible or just wishful thinking.
If you can control the speaker volume then you can simply set it to zero at certain  times of day.
I’ll try and remember to look later to see if this can be done via programming.

I have several unifi setups.   Including at my house.   After living with my own setup for several years now, it wouldn't be my personal choice anymore.  Unifi is pretty, but has a lot of issues.
 
1) things drop off of wifi for no reason.  Like pump controllers, the Halo remotes, a variety of other iot devices.   This is way more common on my unifi APs than on just about any other network gear I've used
2) it's damn frustrating.  They change the UI all the time for no reason.   There are options on the "legacy" interface they never bothered to put on the new interface. They move basic options all over the place every few months.
3) a lot of the basic features don't work correctly. For several months, the client reporting didn't work at all.  You would type it an IP address, that unify had clearly given a DHCP address to, and should know about, and it wouldn't show up as a device in the network.  The network topology map looks pretty, but often is just simply wrong.  Spanning tree doesn't seem to work at all sometimes.
4) they release half baked updates. The dream machine was a nightmare for the first two years, with basic features that didn't work at all.  Like DHCP....
 
There are a lot of other things too that just bother me. My point here is that it looks really really nice, but is not exactly reliable.  This is based on a lot of installs.....

Ditto.  I really like SecuritySpy.  My comments about not being a fan of Ubiquiti NVR were in reference to SS versus Ubiquiti.  Although this was a couple of years ago that I tried it, so maybe it's a lot better now.   The Apple Silicon Macs with HW Codec acceleration can deal with A LOT of cameras at 4K without complaining.   I don't know how much juice the Dream Machines have in that regard, so you might want to confirm that your cameras (at resolution / settings / features you want) won't put too much strain on the Dream Machine.   One thing that would be hard for me to give up is the AppleTV client for SS.  I use this often.
As I have noted elsewhere, I use the SS Homekit integration to throw alerts (e.g., if a vehicle (but not other motion) appears on driveway, flip a switch in Homekit).  Then I use a C4/Homekit driver to pick up that alert on the Homekit side and I fire off an "open gate" command.  Not sure how this would work with UniFi. 

It's just a janky product. I know that's not technical, but it's a good description of how we'd describe them after years of second, third, and fourth chances. They just have too many problems, and unlike enterprise systems have very little recourse to fix them. 

One thing about UniFi switches is they have lower PoE budgets than Araknis so be mindful if you have a lot of PoE needs outside of the UniFi system itself. They're usually adequate for their own APs and some cameras, but it could mean the difference in choosing between the regular switch and the pro version (where there's no 16 port available).
The Dream Machine Pro is beyond adequate for home use and if you're at all savvy you'll be able to appreciate the "single pane of glass" view of your network. I'm able to get to the bottom of network issues very quickly because I don't have to log in and out of half a dozen boxes to figure out what's going on.

In my case used in combination with motion sensors, my backyard doesn’t start with motion detected

I would not look at a device by device replacement but rather start with your requirements and build a new system from there. Some good advice from @cnicholson.  
Wattbox s/b fine. I've used them w/ UI systems.
I would not use the UI NVR capability. Separate dedicated boxes for each function increases reliability (and UI capabilities are limited). UI cameras were once proprietary as well which is not good, are they still? Our go to is Security Spy on a Mac mini (or Studio) with Dahau cameras.
Note that UI SW/FW updates can be very buggy. Shouldn't be a problem for a smaller simply system but if you do a lot of LAGs, special routing or rely on Radius then something to watch out for. And sadly there is no bug/issue tracker so you have to wade through gobs of posts to guesstimate if you'll be affected or not.  UI is a good value for what you get but this can require some extra time and frustration.
 
 

I love SecutitySpy.  I thought I was the only one using it with C4!    I have all my DS2s and Chimes added to NVR.  I have 32 total cameras (mostly 4K) and it works great with AI tagging of human/animal/vehicle (and you can fire off actions based on object type.  Would be cool if they someday add more sophisticated AI (like Face ID and/or License Plate reading).   But pretty seamless.  And they have simple, but good enough Apple TV app for viewing live or achieve footage using Halo (so seems kinda intergated--- or at least "single control device").  I use some workarounds to send NVR triggers to C4 for various automations.   A M1/M2 Mac Mini (with hardware transcode) has plenty of power for most installs, although I did upgrade to a Mac Studio for my 32 cameras (which does not stress the CPU/GPU at all, so might be overkill)

I'm not a fan of all-in-one systems nor of anything proprietary. I've also found the features of Unifi, Synology and C4 surveillance to be lacking.  Our go to is Security Spy on MacOS. Second is Blue Iris but Windows isn't as stable as MacOS. Blue Iris has some better capability for directing a PTZ based on info from other cameras but otherwise Security Spy is the winner.

I get phone updates OTA (at no charge). I can buy oil and a filter from the dealership. I upgrade all of my windows and linux machines for security pathches routinely. But I need to hire someone to install an update for C4. Not sure if its still the case but if you change out a peripheral or change your network addressing you need to pay someone. There should be options to DIY with C4 for some things and yes, if you screw up the config, hire someone and pay them to dig you out. 
 
 
 
 
 

I looked at Savant prior to installing Control4 for 2 different dealers.  Both said even if I wanted a simple change, far less then what can be done in HE, there was a charge.  They both told me I could not change a single thing without them.  I am very happy I went with Control4 and have talk to some great very helpful people on this forum.  

That's very good news. Thank you.

No worries, that's actually a pretty common one even for dealers to do mistakenly. 

If you are using the os 3.3.0 version of the driver you can add new devices on your own. 
 
 

If you have Composer HE the Documentation is in the Documentation tab.  Not sure there is anything else outside of that documentation

Put it all on the lock - cannot speak to Yale
Kwisket has time restrictions on users.  So the alarm will disarm if the code is approved on my door lock.
When user 4 puts in their code and door is unlocked > disarm the alarm
They do not need their own alarm code, or you can enter their unique code in the panel and have C4 execute it - I can do that with the older IT-100 / DSC combo.

Just letting you know, this made it into our latest beta (installers can now retry the command a few times before giving up), as well as a lot of new enhancements. The code also allowed us to add some additional optimisations 

Yup! 

1. Yes.. The driver protocols and handling are significantly different. I considered reusing the existing drivers, but the reality is, I believe long term maintenance will suffer, and it makes it a lot more prone to bugs. Overall, the complete rewrite was more work, but better for everyone. Also, our UDP driver already has more capabilities (like a command for infrared, and reboot command)
2. The issues with the cloud driver weren't really ACK related (the flag in the Master driver can trigger that on and off as required). The problem more was simply the whole protocol at time operated unpredictably it seems. Some of it was due to the way the light reports back. The UDP has support for the same silly issue (but we keep that flag off)
ACK handling and resending is not implemented in the first beta, but will likely be fully added in the near future because I need it for some of my optimisations I'll be adding (the way I've designed the connections is with the expectation I'll be adding it soon).
That being said, as an example, if I ping a lifx light (I'm using a UAP-AC-LR), its very doable to sustain an almost perfect connection to the light on many networks. So if commands aren't being sent properly, it would be worthwhile checking the network.  Also, we're using Unicast in this case, so you shouldn't be affected by network Multicast / broadcast restrictions 
Ping statistics for 192.168.1.224: Packets: Sent = 324, Received = 324, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 72ms, Average = 7ms Control-C 3. The Agent has built in Auto-Detection, and Auto-setup of C4 drivers. But due to limitations in Composer HE, not sure if there are any restrictions on whether endusers can perform these actions.  
 
Hope that helps, 
Andy