msgreenf

Don’t change from bindings to programming its less efficient and requires more programming then what a binding can do in 1 click.  

that may be the case with the older Pandora driver but I believe that's fixed in the new Pandora driver.

very like part of the above. if its a constant issue a reboot may only be a temporary solution. lots of great remote deals to choose from here to help if your local dealer is unable. Myself included.
 

there are not useful reasons to use them in most home installs...sorry...most home installs should follow the KISS principle

I 2nd the thought. If you're running 1GE+ at home, I don't see the need for VLANs.

VLANs are layer  2.
FWs are layer 3
ACLs are firewall rules applied to a router or switch and are layer 2 and 3.
Each has a reason to be used and they don't replace each other.

Vlans, acls, firewalls all have their place. I tend to think about vlans more as traffic separation and acls and firewalls as the security constructs

https://drivercentral.io/platforms/control4-drivers/security-systems/greenfield-solutions-mega-camera-driver/

I think I could add that to my driver's... programming trigger for privacy mode 

Nevermind, I just found the "Auto Setup Outlet Light Devices" under actions. 
Chowmain is amazing......

If you are a network guru should you be asking this? 

And you think unifi is going to perform better then ruckus? You wrong about that...

Just offering this perspective from the customer-side...
Unless it's something you know well, can easily re-create (and scale).. please don't do it in a showroom. 

I’m not seeing any need to have 2 separate VLANs at all with the equipment you listed.
Id also agree that you either didn’t setup the correct rules in your firewall or don’t have any static routing setup.

If you are a network guru should you be asking this? 

Buy 4Sight.. Done.
Why have 2 VLAN's though? Is this a large business?

STP Mode, instead of RSTP on Unifi causes lots of issues with C4. It changes the path costs to traditional STP path costs too which seems to mess up the internal routing of C4 devices. If you check Unifi controller, it might show some devices with a 172.X.X.X IP when they go funky.
Turn off STP entirely for the ports of all C4 Controllers, on the Chime, and any snapAV manufactured gear. Not sure if this is an issue with the Chime's, but it definitely affected controllers, C4 lighting and a few other things.
It's actually a Unifi design limitation, because they don't let you override the path costs per port (which is supported by most other enterprise brands). In their defense though, Sonos 2 equipment should have switched to RSTP instead (but haven't checked if it has)
 

yeh - No. that's wrong.
If you go to the link i have above, go register and you can then create a VM.
I couldn't import my parallels (not available for ARM) but just created a brand new VM from the WIN11 ISO.
 
 

The customer that is successful but isn't a fiddler and wants technology to work and be reliable. 

We have heard this every year since 2014 when homekit was released... if you can't make a viable product in nearly a decade at the largest company in the world I don't think you care enough to 

@zaphod,
Thanks for mentioning this, I had the Android development team double check things to make sure everything was setup properly to distribute to all markets since Canada is in the currently supported markets. They discovered that Windows 11 support had been unchecked for the last 2 versions due to a change in the app submission flow with all the updates that Amazon has been making to their developer console. They've fixed the issue and resubmitted the app for review, so you can expect it to be available again within 24-48 hours.

For reference of what countries offer support for the Windows Subsystem for Android and the Amazon App Store you can reference the link below.
https://support.microsoft.com/en-us/windows/countries-and-regions-that-support-amazon-appstore-on-windows-d8dd17c7-5994-4187-9527-ddb076f9493e

@chopedogg88

In my opinion, absolutely a step up. 
Voice control (currently Apple TV and Xfinity but assume more will be added over time) 
Backlit buttons 
More hard buttons
Better wifi chipset
To name a few. 

Control4 is aware of “random” problems and is working on improving it by making backend improvements and working with Ecobee

It's not a known issue. Likely specific to your setup and your network