cwilmo

@DLiteNo, you don't specifically need a UDM-Pro; you just need a Controller - the simplest is probably just the cloud key; but you could also host it on a local computer or in the cloud.  Unfortunately the USG does not include a controller.  I would not recommend the original Unifi Cloud key (Gen1) but the newer Cloud Key Gen2 is solid.  Get the Gen2 Plus if you also are interested in running apps other than Network such as Protect, Talk or Access.  Other devices with controller included are : UDM, UDR and UDM-SE.

@anon2828: I wanted to mention some tools you can use to better characterize your network issue (before you just swap pieces out) - as a general tool I recommend PingPlotter - pick a reliable domain on the wider web and leave it graphing, ideally running on a hardwired device - when you get performance issues take a look at the time frames in the graph to see if there are changes in the various hops to better pinpoint the problem.  You can also use this within your network similarly to keep an eye on devices.  
For bandwidth checking I like iPerf for LAN to LAN and Waveform Bufferbloat for WAN testing (or Speedtest.com, Fast.com, Speedof.me etc).  Many routers have excellent speed and bandwidth testers built it - on the Mikrotik for instance there is bTest which can test to public servers.  I also sometimes look at the Speedtest results which are graphed by the OVRC controller now built in to your Control EA controller (mine seem to run about every 7 hours but you can also run on demand).  Keep in mind some test results can be limited by the device they run on.  For OVRC on my EA it seems to have no problem graphing my 500/500 connection but I don't know about gig.

Thank-you for the quick reply.
 
I followed the instructions and deleted the Control4 folder, relaunched the Control4 app.  Initial size of the systems.realm file 131kb.  After clicking in and out of a couple camera views I found that the file seemed to be increasing in size, after 10-15 minutes of clicking various views it was 7.3MB.  I left it running on a snapshot view overnight and its 54.82GB today. I've attached the app.log file. It did also make two other app_xxx.log files if needed.
app.log

Versions: C4 Director 3.3.0, Control4.App 322.25.0, macOS 12.4
Use: Control4.app running on M1 Mac, generally in Camera snapshot view, but occasionally streaming one camera view
Problem: Huge container file generated which ultimately uses all available free space on the computer (this one got up to 92gb) [photo attached]
Solution: Delete the 'systems.realm' file in the affected container file.
Results: App had me sign back in.  'systems.realms' file monitored afterwards and could not reproduce results, remained 16kb in size.
Outcome: Hope this helps anyone who finds all their free space gone with a similar setup and developer possible squash a bug.
PS: I know it is made primarily for iPad.

Blue tint is finally GONE with App 322.25.0 with Director 3.3.0!

ZBforget it and then re-add it again