mindedc1

Just make sure your channels are not overlapping and also not overlapping with gear from your neighbors. There are also non-wifi 2.4ghz sources like baby monitors, wireless audio products like sonos and the sony HTIB wireless etc... I spent a bunch of time chasing performance issues with my setup until I discovered that both my neighbors had strong transmitters sitting on the same channel which overlapped one of my APs... signal strength was great, signal to noise was terrible.....

The only thing you need the dealer for is to add the driver and make the connections to the display and input(s). All the other programming can be done via HE. A lot of customization can be done in properties and everything else can be done in programming. There are probably two dozen signal attributes to use in conjunction with your display to adjust the video and do whatever you want. The included documentation has a number of examples of integration with other devices like doorbells and your alarm system for notification during viewing as well as more standard things like adjusing lighting based on movie start, associating aspect ratios with buttons and setting up for anamorphic lenses or masking systems.

Just some clarification for anyone reading this:
A mesh system is where the APs backhaul their traffic to a central point over one of the wireless channels. These systems generally have mediocre performance. If all you're doing is surfing the web you may not notice the performance is terrible. They also do not expose any setting to resolve issue or optimize the RF environment. If you run into a problem you may not be able to solve it easily.
You can assemble a wifi setup with either seperate dumb APs or with centrally managed APs. Either way you can have a single network that spans all the APs. If you see someone with a unique SSID per AP they are ignorant and didn't set it up properly. You only have to make the SSID (network name) and authentication match between the APs. 
A centrally managed configuration will have several advantages over dumb APs with the same settings. One obviously is a single point to manage all of the APs. Another is that they can automatically tune channel, power, and pre-cache credentials to speed roaming. They also can have more sophisticated security mechanisms. A large part of what you are paying for with a wireless system is the ability of the system to manage the wireless spectrum and adjust for problems and interference sources. 
The example of having multiple APs and wanting the client to connect to the best one is how it should and does work. The client collects a list of APs and their signal strength. If 802.11k is enabled they get some additional performance information, they then select the "best" AP based on some criterial, signal strength is the primary factor. When signal strength degrades, the AP will start looking for the next best AP, it then will re-initiate authentication to the AP. If 802.11r is enabled some of the cached intermediary cryptography is passed between APs to speed roaming and keep the client from dropping traffic while roaming. You don't need a "mesh" system for any of this.
With networking products, market share counts. There are trillions of combinations of client, operating system, interference sources, firmware etc... the more APs and switches a company has in the market the more bugs they will find and fix. I agree with the comment about these "luxury" wifi products being like an off brand car. I wouldn't build my environment off of them. Ubiquiti is a great product and probably the best price point. I would also take a strong look at Ruckus and Aruba InstantON. My team installs something like 20,000 APs per year ( in a three city geography), mostly Aruba, Mist, and Ruckus. We are only one of thousands of networking companies in north america. I suspect that the luxury brands barely sell that number in totality in a quarter. They just don't have the client exposure that an enterprise product does. 
Don't get hung up on the most fancy APs out there. 8x8 APs are useless when you have an indoor environment with a bunch of 2x2 clients. I would shoot for 4x4 at most.
Long range APs have no business in a home, regardless of manufacturer. Those are for a "coverage only" model. You cause problems with sticky clients and poor signal. There are enough clients (chromebooks) that get stuck on 2.4ghz and won't voluntarily roam to 5ghz. A long range AP will cause the issue you describe with the client on the "wrong" AP.
Your ideal system should have
a physical or virtual controller Use a POE connection for backhaul (I would run cat6a for new locations, shielded is a waste of money for APs) 4x4 5Ghz radio, 2x2 2.4 ghz radio it should do 802.11K and 802.11R It should both do auto power and auto channel Ability to manupulate all wireless parameters manually to solve issues  The manufacturer should have a plan of record for Wifi 6E (6ghz) High install base so other people are getting bugs squashed so you don't have to From a POE perspective, 802.3AF (class 4) will get you 30 watts of power per port. 802.3bt will get you up to 90. Most of the new Wifi 6E radios will require >30 watts to boot. You can decide if you want to pre-purchase the POE ports or wait for 6E to hit fully at the end of the year and replace your switches. The full 90 watts is not nessecarry for the 6E APs, they will typically be using less than 60 watts. The pre-release stuff we've seen is that they will use less than 40, however it still pushes you into .bt power.
You need to look at the total power budget of the switch as well. For example, a 48 port switch will pull 1440 watts for all ports consuming full 802.3 AF power (30 watts). A switch may support 30 watts per port but only be capable of supply 800 watts of power or may require additional power supplies to max out power delivery on all ports. This isn't the huge issue it seems. Often a device will say it needs class 4 (30 watts) but it only pulls 20 watts. A good switch operating system will report actual power consumption and even allow you to tier ports if consumption exceeds supply such that the most vial devices remain powered. Your blinds won't be a constant load so that will aid your power budget. The rest of it will so I would do a power calculation based on the supply requirements and make sure your switches have enough power to deliver it.  I would also recommend going with 48 port switches, the ports are spaced the same as a 24 port and you will use less rack space. Regardless of the port density I would install horizontal cable management. 
If you're linking switches together you can use optics but it's really a waste of money. A 10G DAC cable is generally what one optic costs and you only have to purchase one of them. Most of my installs use 40G and 100G DACs. Performance is the same as the optics, you're buying one part instead of 3. I would also not buy a switch that only has 1G SFP ports, the cost difference is near 0 from a manufacturing perspective. Keep in mind that your WiFi 6 radios with 4x4 can push more than a gig and should use a multirate port (2.4G/5G) to begin with and 1G SFP ports are dumb. A quality switch will "stack" such that all of your switches look like one unit, similar beneifts to centrally managed wifi. The Ubiquiti, Ruckus, and Aruba gear will provide single plane of glass management of the setup.

Samsung ip control with c4 is great...3 in my house. No issues for years.
Had issues very early on but RyanE fixed em!

I've heard the Phantages and one of their other seperates, I own a Maestro X7. The Audio Controls gear I've heard sounds fantastic. 

Keep in mind that your packedge "router' is actually a nat/firewall device. It may have the ability to be an actual "router" but even if it doesn't I'm guessing your "sky" device is also a nat/firewall device and not a real router either. What's the big deal? Well if you want multicast to work between the buildings if you use a nat/firewall device you're probably putting a nat boundary between the two broadcast domains and you would have to configure some fancy multicast routing between the two networks. You would probably break any C4 discovery (phone app, touch pads, SDDP etc).  You would also break all sorts of home level media discovery stuff (airplay, chromecast, sharibridge, etc).
If you don't know enough about how to do this and are thinking two "routers" on a home network is a good setup, I advise you to get some help from someone that understands networking before having to re-do the install because a lot of it is broken.
I would also use MOV based surge suppression on the catX cable between the buildings on BOTH ends and I would earth it to the ground for each building just before or after building penetration. Ubiquiti makes a very nice one, there are many models to choose from L-Comm and other places. You don't want a close strike induced into the gear on each end. 

The driver is up and available for purchase on drivercentral.io now. If you have lumagen driver specific issues I am available via PM here. If you have drivercentral issues please hit them up directly. I may take a day or two to respond as I don't check this forum every day.
https://drivercentral.io/platforms/control4-drivers/audio-video/lumagen/

The two issues are lightning and surges. Lightning is thousands of volts and thousands of amps. Surges are hundreds of volts and hundreds of amps.
The best defense against lightning is proper grounding just like video storm mentioned above. A single ground or properly bonding your grounds with 6awg copper is the way to go. I would engage an electrical engineer to validate your grounding and I would the. Engage an electrician to audit your panel(s)and pop off a few wall plates to verify the house was wired properly. If you have antennas for any reason (tv, wifi, satellite, ham radio etc) those should have a gas passivated lightning arrester with replaceable cartridges. The cartridges are like a neon bulb and will conduct a lightning level strike to ground and destroy the capsule in the process. Please keep in mind that a direct strike will blow apart concrete, blow the Sheetrock off your walls etc... I've seen it blow a vcr out of a rack and embed it in the opposite wall... proper grounding will bleed down charge on your devices and minimize this risk.
The other concern are surges in the form of 200-500+ volts on your AC line. There are several causes but grounding won't help with this. Mov or PTC based arrestors are the best defense here. A good example of this is a quality "surge strip" like a tripplite isobar. Cheap surge strips might have a circuit breaker or just an on/off switch which are both useless for protection purposes. There are whole house versions an electrician would be delighted to install on your panel. These work by having a sacrificial element (I.e. MOV) that starts conducting at a voltage higher than line level and it shorts the over voltage to ground. If the device triggers and protects it will literally be fried and you have to throw it away and replace it. They are very effective and I personally have one but I also made sure I had a properly grounded electrical system in the house first.
if you have high dollar gear it's worth the investment as typical homeowner policies will only cover $2500 in damages from lightning...you can also inexpensively add a rider fir your high dollar gear...

Just an update to everyone, the driver should be up on drivercentral in a few days. There are quite a few hoops to jump through on the signup process. If you have an urgent need you can dm me on here and we can work something out.

HC-800 can run 2.10 and still run current 3.2.x code. It's still quite a fast controller. You will lose gui to any connected TV if you go to 3.x. I would go up to current if you don't have anything weird that will break as the phone/tablet apps are better and performance and stability in the most current releases seems quite good.
You need a dealer to do this for you. @msgreenf is a great dealer that may or may not be interested in doing this. He's very active on the forum here. There are other great remote dealers running around too. Generally upgrades aren't too bad but it would be best to have someone take a peek and look at the system before agreeing to a price because there may be some gotchas about what you're doing.

Yeah agree i use an Audiocontrol XR6 as my head end processor and 2 5 channel ATI power amps.  Had MRX720 prior and 7013, Audiocontrol outperformed them both prior to Dirac actually.  Little quirky from time to time but IP driver works fine, sometimes a bit slow.

I cheat physics every day 😉
Will keep you all posted on what I find. It should be delivered tomorrow. 

Also, the ubnt gear has a watchdog that you can set to ping the far side and reboot itself if the link fails... no external dependencies...

powerline networking will depend on if the Barn is on the same power service or not...

waaaaaaaaaaaaaaaaaaay overkill.
For Ruckus a zone controller is for 10+ APs. Well unless your house is THAT big - but I doubt it.
Think large coorporate buildings, government and (fancy) hotels for zone controller where there is large space but more importantly heavy density of users.

Custom buttons are a pain in 3.x, they're a bit odd in 2.x as well. It's really the only decent way to deal with a customer that wants something like DSP modes or something.
Scenario buttons outside of the given limitations are quite nice, can turn into a pain for you and your dealer (edit/upload/repeat).
The upside and downside of C4 is that the UI is only so configurable. The upside is it's consistent and easy to program. Things always work the same way. Have you ever seen a windows program with weird and non-standard controls? Annoying? Pain to use? that's the opposite side of the coin where someone thought they know UI design better than the OS developers and you get something that could be wonderful but is more often than not annoying. The difference with C4 is it makes people angry when their houses don't work... lesser of the two evils is to make it fit a pattern, make it consistent and easy to program and support. If the dealer that built it gets hit by a truck, that customer can get good support from another dealer with minimal fuss. The downside is accounting for that uncommon 10% of things people want to do can get annoying from a UI perspective. I'll take it never being broken when I'm out of town for the inconvenience of dealing with the UI.
The one big game changer is in 3.x you can favorite Experience buttons to the room, quite nice. I recommend giving it a try. Just hold down on the button you want to favorite, should get a popup allowing you to favorite it to the room. It also works at a higher level. For example in an alcove in my foyer I have a panel and use the garage door buttons a lot as well as security panel and security cameras. I have the doors, and the panel room favorited as well as the overall icon for cameras. No watch/listen sources in that room so it's sort of an entry/exit security control center. I also have home/away/vacation buttons favorited to the room. Very nice! I believe these show on the Neo remotes as well. You have to do the favoriting on a touchpad or app, but the button will appear in the room on the Neo after that.
 

Custom buttons are a pain in 3.x, they're a bit odd in 2.x as well. It's really the only decent way to deal with a customer that wants something like DSP modes or something.
Scenario buttons outside of the given limitations are quite nice, can turn into a pain for you and your dealer (edit/upload/repeat).
The upside and downside of C4 is that the UI is only so configurable. The upside is it's consistent and easy to program. Things always work the same way. Have you ever seen a windows program with weird and non-standard controls? Annoying? Pain to use? that's the opposite side of the coin where someone thought they know UI design better than the OS developers and you get something that could be wonderful but is more often than not annoying. The difference with C4 is it makes people angry when their houses don't work... lesser of the two evils is to make it fit a pattern, make it consistent and easy to program and support. If the dealer that built it gets hit by a truck, that customer can get good support from another dealer with minimal fuss. The downside is accounting for that uncommon 10% of things people want to do can get annoying from a UI perspective. I'll take it never being broken when I'm out of town for the inconvenience of dealing with the UI.
The one big game changer is in 3.x you can favorite Experience buttons to the room, quite nice. I recommend giving it a try. Just hold down on the button you want to favorite, should get a popup allowing you to favorite it to the room. It also works at a higher level. For example in an alcove in my foyer I have a panel and use the garage door buttons a lot as well as security panel and security cameras. I have the doors, and the panel room favorited as well as the overall icon for cameras. No watch/listen sources in that room so it's sort of an entry/exit security control center. I also have home/away/vacation buttons favorited to the room. Very nice! I believe these show on the Neo remotes as well. You have to do the favoriting on a touchpad or app, but the button will appear in the room on the Neo after that.
 

So some clarification and information for you to cut through the clutter. I'm a networking professional and have architected many very large high scale networks (500K user+ type environments). I was CCIE level 20 years ago, tier 3 tac level at a Cisco competitor, have moved on to other products but manage a networking team now. My guys install around 20K access points each year and thousands of switches, lots of large firewalls etc. I also do a little C4 programming as freelance for a dealer on the side, some C4 driver development as well as have a decently large install myself with lots of odd things. I run pro networking gear myself at home in my environment (Ruckus and Juniper switching, have use Mist, Aerohive, and Aruba APs with my current C4 setup as well).
All of the C4 restrictions around networking are because most dealers don't have an in-depth knowledge of networking. Let's discuss:
C4 uses broadcast - not true. Do a wireshark and set the display filter for eth.dst == ff:ff:ff:ff:ff:ff, you'll see lots of ARPs and probably netbios garbage but nothing important for C4 beyond ARP. C4 does rely heavily on multicast (wireshark display filter ip.addr >= 224.0.0.0). Ubiquiti is supposedly on the "no" list because of some UBNT hardware not forwarding multicast, specifically the routers as I recall. It works fine other than that rare case, no reason to change to Cisco or anything else.
Spanning Tree Protocol - Recommended against because it's a pain to configure properly and configured improperly you can have issues, I suppose they consider it better to allow a customer's network to get locked in a hard loop. It works fine, I've used MSTP, RPVST+ and some other flavors with C4 and it's fine if configured properly. Home grade switches may have poor implementations.
Flow Control - Properly implemented flow control is fine, the issue is most network hardware doesn't expose getting pause frames from devices that are overloaded..again instead of identifying the problem it turns into some sort of mystery that's resolved when the overloaded device is replaced randomly. This could be an issue in switch to switch communications or server to server where lots of disk IO is happening. If you're running pro gear and routinely check for pause frames as part of your troubleshooting not an issue.
QoS (Quality of Service) - I've also used switch level QoS with no issues, I would be cautitous about QoS or traffic shaping in home grade routers. Industry standard DiffServe on switches works fine. I would avoid punishing multicast or anything C4 is doing. I would also avoid voice prioritization for wireless unless you have someone who really knows what they're doing set it up. Lots of bugs in those features on most wireless products.
Wireless isolation (QoS setting) - This will cause problems RE C4 discovery works off of multicast.
Privacy Separator - presume this is same as client isolation, same deal
PaGP (Port Aggregation Protocol) - Works fine as well as LACP/802.3AD dynamic and static. If  you don't know how to configure these protocols you can of course create problems. There are special criteria in PIM environments with LAG/PAGP
IGMP Snooping (or any other Multicast Filtration of any kind) - Presuming from the bitching I hear from dealer friends about this, I presume that either the C4 gear doesn't prune/join properly or they've had networking folks not set this feature up. I run IGMP enabled on my Juniper switches but your mileage may vary. They left off storm control, DHCP snooping, Dynamic ARP inspection, etc here but again, I use it and it works fine.
So, the recipe for success, is keep all the C4 gear and all the clients that talk to it on the same VLAN, even over wireless. 
You should be able to have multiple VLANS working with PIM with a phone or touchpad on one side, however if any of the C4 devices don't handle IGMP properly you may still have issues. C4 doesn't really define which devices need which s, g publicly so any PIM troubleshooting would be a guessing game. You may also have RP overload in a home environment with a setup that large. We generally filter out SSDP, MDNS, Bonjour etc in corp environments as I've seen 50 misbehaving clients take down a 1 terabit line rate switch with enough control plane traffic thanks to MDNS. Though technically possible you would be in the minority with this type setup. The exception here would be things that do not need multicast discovery. For example I have all of my IP cameras on a firewall zone on an isolated switch (ethernet connection on the outside of my house, security problem!). The IPs are manually configured in C4 so no need for multicast, works great. If you put things that never need to talk to C4 on different VLANs, that's fine as well.
I saw you ran some pings as a test. 12 pings isn't enough and if you're running 1G or 10G you're not loading enough of the wire to see an issue. I would run 1000 pings and I would also increase the packet size to 1472, after applying the header that's the largest payload you can squeak through a 1500 byte mtu ethernet connection. If you run 100% clean with no loss I would say it's unlikely network is your issue. You will see loss over wireless, I would test from wired. You could still have multicast being blocked but that would be more difficult to test. You can use netcat if you have a unix system or if you have two laptops you can generate a multicast stream with VLC and some video file. Google will explain that process better that I am willing to here. I would also suspect that your issue with controls not working is not a multicast issue. Multicast is used by C4 for discovery. Once the remote device is discovered (Say an EA1) the communications are unicast for which ping is a good test. Anyone that doesn't believe me is free to use the above wireshark filters to find out for themselves.
I think it's unlikely you have a wired network issue.
I would look into the EA that runs director. I've had severe C4 latency issues with an IP driver (Yes, a Control 4 issued driver BTW) eating a lot of CPU and lagging out director. Identifying that driver and fixing an issue with it has completely resolved the issue. I spent a week on the phone with support on that one. Engaging your dealer is the best way to identify if something like that is causing the issue because they're going to have access to deeper troubleshooting tools that you don't.
You could also be having a spectrum issue with zigbee. It's sitting on the 2.4 band. Given that you have 11 APs, hopefully someone has told you or you know to turn off most or all of the 2.4ghz radios. There are only three non-overlapping channels in 2.4, given that there's better reach on 2.4 vs 5ghz, it would be difficult to not have channel overlap 3-4x in that setup. I would only use 5Ghz if possible and potentially only enable 2.4 on three APs at most. If you need more you should do a heatmap of your house and identify which APs have the most RF barrier between them and configure the overlapping channels there, using the attenuation of of your structure to your benefit, adjusting down power as needed. Just the SSID broadcast from two networks (user and guest) could eat something like 40% of the 2.4 ghz bandwidth if replicated on three APs overlapping each other...it would also trash zigbee pretty bad. If someone configured the ubnt gear for 40 or 80 mhz channels on 2.4 you will have similar issues as well. My recomendation would be to disable 2.4 altogether if possible and use strictly non-overlapping channels on 5ghz, I think with 40mhz channels you should be able to just make it.
Speaking of wireless, I would also get someone who is a drop dead expert on the ubiquiti gear or an expert with Airmagnet to look into the wireless, especially if the touchscreens are wireless. 802.11r/k are squirlley in a lot of client and AP chipsets, you may have stability issued on the T3s with roaming given the number of APs you have r/k/v enabled. Band steering can also create issues etc... There are other issues with fast roaming on cheap gear as it generally doesn't generate l2 forwarding table updates on a client roam. Controller based enterprise gear does this, UBNT might, however I don't know. My understanding is that the UBNT controller doesn't really handle traffic so I would expect not. Other solutions like Mist, Aerohive, and Ruckus unleashed have this sorted in a decentralized forwarding plane setup so perhaps UBNT has this as well. I'm also not sure how well autopower/auto channel works on ubnt, generally only Mist, Aruba, and Cisco have this actually working. You should probably use an analyzer to tune down the power on your APs to make a more microcell environment. I would get an expert on UBNT wireless as its very complicated and it's much more about the skeletons in the closet on each platform.
Actually, just looked before submitting and it seems the T3s are 2.4 ghz only. If you're running them on wifi, I would kill all but one of your APs and put a T3 right next to the active AP and see if that stabilizes the T3. If so you probably have channel overlap issues on 2.4ghz.
Good luck, hopefully this helps.
 

https://drivercentral.io/platforms/control4-drivers/security-systems/hikvision/

I added commands for the new sharpening that was exposed in November or December. It's my daily driver scaler so I do keep it up to date when they add new features. They have also added features for me. Two bug fix releases in the last year were thanks to issues I discovered (The Nvidia shield issue and the one after it). I also got them to allow you to change the color of on screen messages. The new remote adds test patterns, saving config, HDR setup, auto aspect enable/disable, and input aspects for some additional formats. Of them the following are supported via serial:
Test patterns, Save config, Enable+reset auto aspect detection.
I refrained from exposing save config as it seems like something you would use infrequently. Same thing for test patterns. The Enable/reset auto aspect detection would be trivial to implement. The following are not exposed via serial at this time:
Auto aspect disable, HDR setup, NEW aspect ratios.
If there is need/demand of those things I can add them pretty quickly. I have a driver I'm trying to get substantially finished this week but will free up a little after that. 
I have no relationship with Lumagen other than being a customer and developing the driver (and calling support perhaps a few too many times) so I can't really comment on the PIP situation. 
 

I wrote it, it works famously
 

Here is a writeup of features. I've been using it for two years, I've had customers for a full year. Since I wrote this I've added the new sharpening commands from the fall firmware release and increased the number of inputs to 10 to account for the additional virtual inputs and the new hardware with 10 inputs.
 
The preferred setup for Lumagen is to have all sources connected directly to the lumagen and then connect the lumagen to your preamp/processor/reciever. This creates an issue that you don't get any volume or mute feedback on your screen because the preamp/receiver is out of path. The driver has property enabled features called  "Auto Volume" and "Auto Mute" that will grab the volume level and mute state from the room the lumagen is located in and use them to trigger a message on the display. No programming required. If that doesn't work in your configuration, there is a mute on/off command available in programming and a message can be written to the display to indicate the volume or mute state via MESSAGE1 and MESSAGE2 variables.

Supports IR power on, set the power method to "IR" and bind an emitter to the driver, this is only needed in some rare condition.

The driver supports all remote commands fired from programming and also exposes almost all of the lumagen video attributes as variables. This allows you to alter Lumagen configuration based on something in your environment such as moving an anamorphic lens in and out or selecting a video game source that needs certain latency (game mode) or video configuration. You can also automate any aspect ratio, zoom etc changes. The state of video being displayed by the lumagen can also be used to trigger outside events. Every time the video changes aspect ratio, resolution, refresh rate, color space etc, the variables are updated and via standard C4 programming any type of automation can be triggered. We have some customers that change color space settings on their Sony projector based on the input color space. I believe they are using the Lumagen for DTM and they are putting the Sony in the proper HDR color space without triggering high lamp or something like that. We have other customers that use the aspect ratio to trigger automatic masking systems and anamorphic lenses. Care must be taken that sources that change aspect ratio frequently do not cause mechanical malfunctions. I prefer to select when my anamorphic lens is in or out of path so I automatically change output aspect ratio via a memory setting when I move the lens in and out.

An arbitrary message can be written to the display to indicate the volume via the QUICK_MESSAGE or MESSAGE1 and MESSAGE2 variables. Message persist is the amount of time any of the onscreen messages from the driver will be displayed, 1-8 seconds. With more recent firmwares, the lumagen supports setting the colors of the messages. This is configured with RGB hex codes similar to HTML. The entire set of "standard" computer colors and hex codes are added as well as the ability to define up to five custom colors. Alpha channel or transparency is also supported. We have a customer whose preamp has a feedback driver but no on screen display and they write a display message when their audio format changes as they like to know what mode it's in.

Commands

The following commands are supported via programming.

Mute On - Display Mute
Mute Off - Clear display of Mute
Select Input 1-8
Select Input Aspect Ratio NLS, 4:3, 4:3NZ, LBOX, LBOXNZ, 16:9, 16:9NZ, 1.85, 1.85NZ, 2.35, 2.35NZ
Select Output Aspect Ratio O16:9, O2.35, O1.33
Select Memory MEMA, MEMB, MEMC, MEMD
Select Resolution 480P, 540P, 600P, 720P, 768P, 840P, 1080P, 1080I
Send Generic Command - Commands not covered by above features
Send Darbee Enable/Disable, Mode, and adjust value up and down in increments of 1,5, and 10.


VARIABLES

All feedback is handled through the device variables. The "Debug Action" will display the state of these variables at any time regardless of the setting of debug on/off in the driver.

Note: These variables are all read-only, and changing the variables' values does not cause the Lumagen to change state I.E. setting the INPUT_PHYSICAL variable to 03 does not cause the Lumagen to change inputs. You must use a command (above) to do this. If you want one variable to change another, for example when a source with two way is powered on manually you want the lumagen to auto switch you can fire the input command from the power state variable on the source.

Variable Value
------------------- -------------------
INPUT_PHYSICAL Selected Physical input 1-8
INPUT_LOGICAL Selected Logical input 1-8
INPUT_CONFIG_NUMBER Selected Input configuration
INPUT_ASPECT Input aspect ratio I.E. 178 is 1.78:1 or 16:9
INPUT_RATE I.E. 23 = 23.9 FPS, 24 = 24FPS, 60 = 60FPS
INPUT_RESOLUTION I.E. 1080 for 1080P HD, 2160 for 4K
INPUT_MODE P/I/n Progressive, interlaced, or no input
INPUT_3D_MODE 2D / Frame-Seq / Frame-Packed / Top-Bottom / Side-by-Side
INPUT_DYNAMIC_RANGE SDR/HDR
HDR_MIN Minimum Luminance of HDR signal
HDR_MAX Maximum Luminance of HDR signal
HDR_CLL Maximum Coherent Light Level of HDR signal
INPUT_STATUS No Source/Active Video/Internal Pattern
NLS Normal or NLS for Non Linear Stretch enabled
MEM A / B / C / D
OUTPUT_STATUS 000e - Binary field, needs better decoding
OUTPUT_3D_MODE 2D / Frame-Seq / Frame-Packed / Top-Bottom / Side-by-Side
OUTPUT_MODE P/I Progressive or interlaced
OUTPUT_CMS_NUMBER 0-7
OUTPUT_STYLE_NUMBER Selected output style 0-8
OUTPUT_COLOR_SPACE REC601 / REC709 / REC2020 / REC2100
OUTPUT_RATE I.E. 23 = 23.9 FPS, 24 = 24FPS, 60 = 60FPS
OUTPUT_RESOLUTION I.E. 1080 for 1080P HD, 2160 for 4K
OUTPUT_ASPECT Input aspect ratio I.E. 178 is 1.78:1 or 16:9
OUTPUT_ADJUSTED_ASPECT Aspect ratio from AR detection I.E. 178 is 1.78:1 or 16:9, Can be overriden by user forcing aspect ratio with sticky.


These variables should be writable. The specified action will occur immediately after updating the variable. The message feature could be used for several things. For example, if the customer has a soundproofed theater you may want to write a message when their doorbell rings or security alarm goes off. You can safely write to the variables at any time, if the lumagen is in an off state the commands are silently discarded (so you can be lazy programming and fire the dorbell message without regard for if the theater is in use for example).

Variable Value
------------------- -------------------
VOLUME_DISPLAY integer will be immediately displayed as volume
QUICK_MESSAGE string will be immediately displayed as a 1 line message
DARBEE_ENHANCE integer value of 0 - 120 for darbee enhancement
MESSAGE1 string will be stored for displayed as line 1 of a 2 line message
MESSAGE2 string will be displayed as line 2 of a message. Writing to this will trigger display of line 1 and line 2

So some clarification and information for you to cut through the clutter. I'm a networking professional and have architected many very large high scale networks (500K user+ type environments). I was CCIE level 20 years ago, tier 3 tac level at a Cisco competitor, have moved on to other products but manage a networking team now. My guys install around 20K access points each year and thousands of switches, lots of large firewalls etc. I also do a little C4 programming as freelance for a dealer on the side, some C4 driver development as well as have a decently large install myself with lots of odd things. I run pro networking gear myself at home in my environment (Ruckus and Juniper switching, have use Mist, Aerohive, and Aruba APs with my current C4 setup as well).
All of the C4 restrictions around networking are because most dealers don't have an in-depth knowledge of networking. Let's discuss:
C4 uses broadcast - not true. Do a wireshark and set the display filter for eth.dst == ff:ff:ff:ff:ff:ff, you'll see lots of ARPs and probably netbios garbage but nothing important for C4 beyond ARP. C4 does rely heavily on multicast (wireshark display filter ip.addr >= 224.0.0.0). Ubiquiti is supposedly on the "no" list because of some UBNT hardware not forwarding multicast, specifically the routers as I recall. It works fine other than that rare case, no reason to change to Cisco or anything else.
Spanning Tree Protocol - Recommended against because it's a pain to configure properly and configured improperly you can have issues, I suppose they consider it better to allow a customer's network to get locked in a hard loop. It works fine, I've used MSTP, RPVST+ and some other flavors with C4 and it's fine if configured properly. Home grade switches may have poor implementations.
Flow Control - Properly implemented flow control is fine, the issue is most network hardware doesn't expose getting pause frames from devices that are overloaded..again instead of identifying the problem it turns into some sort of mystery that's resolved when the overloaded device is replaced randomly. This could be an issue in switch to switch communications or server to server where lots of disk IO is happening. If you're running pro gear and routinely check for pause frames as part of your troubleshooting not an issue.
QoS (Quality of Service) - I've also used switch level QoS with no issues, I would be cautitous about QoS or traffic shaping in home grade routers. Industry standard DiffServe on switches works fine. I would avoid punishing multicast or anything C4 is doing. I would also avoid voice prioritization for wireless unless you have someone who really knows what they're doing set it up. Lots of bugs in those features on most wireless products.
Wireless isolation (QoS setting) - This will cause problems RE C4 discovery works off of multicast.
Privacy Separator - presume this is same as client isolation, same deal
PaGP (Port Aggregation Protocol) - Works fine as well as LACP/802.3AD dynamic and static. If  you don't know how to configure these protocols you can of course create problems. There are special criteria in PIM environments with LAG/PAGP
IGMP Snooping (or any other Multicast Filtration of any kind) - Presuming from the bitching I hear from dealer friends about this, I presume that either the C4 gear doesn't prune/join properly or they've had networking folks not set this feature up. I run IGMP enabled on my Juniper switches but your mileage may vary. They left off storm control, DHCP snooping, Dynamic ARP inspection, etc here but again, I use it and it works fine.
So, the recipe for success, is keep all the C4 gear and all the clients that talk to it on the same VLAN, even over wireless. 
You should be able to have multiple VLANS working with PIM with a phone or touchpad on one side, however if any of the C4 devices don't handle IGMP properly you may still have issues. C4 doesn't really define which devices need which s, g publicly so any PIM troubleshooting would be a guessing game. You may also have RP overload in a home environment with a setup that large. We generally filter out SSDP, MDNS, Bonjour etc in corp environments as I've seen 50 misbehaving clients take down a 1 terabit line rate switch with enough control plane traffic thanks to MDNS. Though technically possible you would be in the minority with this type setup. The exception here would be things that do not need multicast discovery. For example I have all of my IP cameras on a firewall zone on an isolated switch (ethernet connection on the outside of my house, security problem!). The IPs are manually configured in C4 so no need for multicast, works great. If you put things that never need to talk to C4 on different VLANs, that's fine as well.
I saw you ran some pings as a test. 12 pings isn't enough and if you're running 1G or 10G you're not loading enough of the wire to see an issue. I would run 1000 pings and I would also increase the packet size to 1472, after applying the header that's the largest payload you can squeak through a 1500 byte mtu ethernet connection. If you run 100% clean with no loss I would say it's unlikely network is your issue. You will see loss over wireless, I would test from wired. You could still have multicast being blocked but that would be more difficult to test. You can use netcat if you have a unix system or if you have two laptops you can generate a multicast stream with VLC and some video file. Google will explain that process better that I am willing to here. I would also suspect that your issue with controls not working is not a multicast issue. Multicast is used by C4 for discovery. Once the remote device is discovered (Say an EA1) the communications are unicast for which ping is a good test. Anyone that doesn't believe me is free to use the above wireshark filters to find out for themselves.
I think it's unlikely you have a wired network issue.
I would look into the EA that runs director. I've had severe C4 latency issues with an IP driver (Yes, a Control 4 issued driver BTW) eating a lot of CPU and lagging out director. Identifying that driver and fixing an issue with it has completely resolved the issue. I spent a week on the phone with support on that one. Engaging your dealer is the best way to identify if something like that is causing the issue because they're going to have access to deeper troubleshooting tools that you don't.
You could also be having a spectrum issue with zigbee. It's sitting on the 2.4 band. Given that you have 11 APs, hopefully someone has told you or you know to turn off most or all of the 2.4ghz radios. There are only three non-overlapping channels in 2.4, given that there's better reach on 2.4 vs 5ghz, it would be difficult to not have channel overlap 3-4x in that setup. I would only use 5Ghz if possible and potentially only enable 2.4 on three APs at most. If you need more you should do a heatmap of your house and identify which APs have the most RF barrier between them and configure the overlapping channels there, using the attenuation of of your structure to your benefit, adjusting down power as needed. Just the SSID broadcast from two networks (user and guest) could eat something like 40% of the 2.4 ghz bandwidth if replicated on three APs overlapping each other...it would also trash zigbee pretty bad. If someone configured the ubnt gear for 40 or 80 mhz channels on 2.4 you will have similar issues as well. My recomendation would be to disable 2.4 altogether if possible and use strictly non-overlapping channels on 5ghz, I think with 40mhz channels you should be able to just make it.
Speaking of wireless, I would also get someone who is a drop dead expert on the ubiquiti gear or an expert with Airmagnet to look into the wireless, especially if the touchscreens are wireless. 802.11r/k are squirlley in a lot of client and AP chipsets, you may have stability issued on the T3s with roaming given the number of APs you have r/k/v enabled. Band steering can also create issues etc... There are other issues with fast roaming on cheap gear as it generally doesn't generate l2 forwarding table updates on a client roam. Controller based enterprise gear does this, UBNT might, however I don't know. My understanding is that the UBNT controller doesn't really handle traffic so I would expect not. Other solutions like Mist, Aerohive, and Ruckus unleashed have this sorted in a decentralized forwarding plane setup so perhaps UBNT has this as well. I'm also not sure how well autopower/auto channel works on ubnt, generally only Mist, Aruba, and Cisco have this actually working. You should probably use an analyzer to tune down the power on your APs to make a more microcell environment. I would get an expert on UBNT wireless as its very complicated and it's much more about the skeletons in the closet on each platform.
Actually, just looked before submitting and it seems the T3s are 2.4 ghz only. If you're running them on wifi, I would kill all but one of your APs and put a T3 right next to the active AP and see if that stabilizes the T3. If so you probably have channel overlap issues on 2.4ghz.
Good luck, hopefully this helps.
 

What was the last driver you installed?  Generally you can track these back to a memory leak in a driver

Here it is running on a T3... we're looking for some beta testers actually.