WhyPhy

Yes, obstruction sensor (and motion sensor) integration is a great feature. I especially like how they enable automation of the main ceiling lights. 

Yes, obstruction sensor (and motion sensor) integration is a great feature. I especially like how they enable automation of the main ceiling lights. 

This latest update with the closing delay is working perfectly. It addressed my safety/car damage concerns. Thank you Alan!

Yes, obstruction sensor (and motion sensor) integration is a great feature. I especially like how they enable automation of the main ceiling lights. 

This latest update with the closing delay is working perfectly. It addressed my safety/car damage concerns. Thank you Alan!

Ok. Beta test went well.  Update has now been released.
There is now an option to enable a pre movement event in the driver.  You just need to enable it, set the time you want and if you have speakers in the area connected to Control4 select the announcement you want.  A event is also fired if you do not have speakers and want to trigger the audible alarm in some other fashion.

Actually there is a way i can do it if it is fully closed since we get state / position.  A toggle command when it is fully closed will always perform an open.
This means that opening will not be effected.  Only when it is partially or fully open will the delay happen.
 

This actually isn't that hard to implement.  In fact i've just done it.
I'll run it in beta for a few days and if it works well will release.  Delays any movement by x seconds.  Flashes the built in garage door light and automates firing of an announcement before any movement (pulls in the annoucements and allows you to select the announcement).  Also has an event if someone wants to do something custom like hook up a buzzer or something via a relay.

I have heard some feedback from a few users.  It may be due to rebooting of controllers but hard to say as i haven't experienced it myself.  I've made some improvements to the way i'm handling controller reboots and the way we are sending feedback so the next version should resolve this problem.

Ratgdo == Rage Against the Garage Door Opener.
Pretty funny, but true...
RyanE

Yeah think the inside baseball is a good analogy.  Assume that'll get worked out since nearly all other major control platforms (Crestron, Lutron, ELAN) in addition to point solutions (Tidal, Nest, Google, Sonos, etc) are supported on that remote control platform as was just mentioned.  I don't see C4 putting development cost into voice as by many (not myself personally) as a niche market and just leverage the Alexa, Google, and Josh plaforms instead.  
I know there will be different perspectives but glad that the touchscreen does not have a far-field microphone for my specific use case.  I already have Nano and Micro devices in every zone of the home and just want to add a few touchscreens for a few spots for guest to have easy access for scenes they would not know otherwise when visiting (i.e. Great Room, Kitchen, etc.).  If they decided in a V2 to add a far field microphone with the option to disable to far-field microphone I'd be good with that similar to disabling the mic on the current hardware.
Pre-ordered the Cinema remote last week with anticipated delivery in early March to see how that goes.  Have 3 of the current models in guest rooms and based upon visitors in those rooms they loved them since they are phone app folks with their devices back at their homes.  Having the ability to have scenes in a visual format I can do without needing a dealer or effort of Composer style HE work is great and easy to swap and test within seconds.  Will see if battery life is better compared to Halo as definitely disappointed with some of the lack of functionality in Halo without doing button programming that I can already do on the Josh/Ava remote (locks, shades, fireplaces, heaters) from day 1 of receiving unit.
Biggest differentiator for our case is the UI is an order of magnitude better and the OTA updates both are detailed and frequent.  Along with that the end user customer like myself can go to a Medium Blog by the company or to their YouTube channel and review the changes and updates made. In the case of C4 I have to rely on a forum where the release notes are not published often or a change happens (like the photo icons in the iOS) with no accompanied detailed blog, video or detailed information on what updated and why.  That's a gripe but a reason for only using C4 now as a 'backbone/back office' element and not the front end UI we used to use it for those in the household and visitors.

This is where that VideoStorm switch shines as it does the ramp down of audio, plays announcement, then ramps back up.  I never had to add any additional silent audio to the announcements for the signal sensing amps.
Which also doesn’t require using the snapshot driver to capture each room.

In my experience, with 20 zones across 3 AudioControl matrix amps, it’s better to just let C4 handle the announcement and not do custom programming. C4 does numerous pause/save/adjust/announce/resume steps that are not apparent and don’t necessarily behave consistently. The announcements Agent is basically a “black box” that’s supposed to just work.
 
Additionally, I have to add delays before each announcement so the first few seconds aren’t cut-off (the more zones, the longer the required delay.) In the end, announcements mostly works, but would be much better if implemented by the matrix itself as an “announcement input” vs C4 doing save/announce/restore for each zone individually. 

In my experience, with 20 zones across 3 AudioControl matrix amps, it’s better to just let C4 handle the announcement and not do custom programming. C4 does numerous pause/save/adjust/announce/resume steps that are not apparent and don’t necessarily behave consistently. The announcements Agent is basically a “black box” that’s supposed to just work.
 
Additionally, I have to add delays before each announcement so the first few seconds aren’t cut-off (the more zones, the longer the required delay.) In the end, announcements mostly works, but would be much better if implemented by the matrix itself as an “announcement input” vs C4 doing save/announce/restore for each zone individually. 

In my experience, with 20 zones across 3 AudioControl matrix amps, it’s better to just let C4 handle the announcement and not do custom programming. C4 does numerous pause/save/adjust/announce/resume steps that are not apparent and don’t necessarily behave consistently. The announcements Agent is basically a “black box” that’s supposed to just work.
 
Additionally, I have to add delays before each announcement so the first few seconds aren’t cut-off (the more zones, the longer the required delay.) In the end, announcements mostly works, but would be much better if implemented by the matrix itself as an “announcement input” vs C4 doing save/announce/restore for each zone individually. 

HI.  We have not seen this. Have you submitted a help desk ticket for us to look your system?  The email system should allow up to 50 emails (from all our drivers combined) per day.  This has been the same for years.
 
Please put a support ticket in @ https://help.drivercentral.io and we can help you out.
 
Thanks!

Yes, I agree. Assuming it’s a dark room. 

The highest a screen should be is this: measure 1/3 up the screen from the bottom - that imaginary horizontal line should be at or below seated eye level. This results in the bottom of the screen being pretty close to the floor.
If you’re ever going to watch TV shows, and probably even if you are not, you should go with a screen aspect ratio to match the projector aspect ratio. So unless you’re using an amorphic lens on the projector, you should use a 16:9 screen. Otherwise, you’re losing 1/3 the pixels and 1/3 the brightness and will have light spillover above/below the screen. 
 
For the price, you cannot beat a Silver Ticket screen from Amazon. Their woven acoustically transparent screen is a great performer, as proven in testing. If you want integrated boarder lighting or light rejection do SI; for absolutely reference color reproduction do Stewart StudioTek 130. 

The highest a screen should be is this: measure 1/3 up the screen from the bottom - that imaginary horizontal line should be at or below seated eye level. This results in the bottom of the screen being pretty close to the floor.
If you’re ever going to watch TV shows, and probably even if you are not, you should go with a screen aspect ratio to match the projector aspect ratio. So unless you’re using an amorphic lens on the projector, you should use a 16:9 screen. Otherwise, you’re losing 1/3 the pixels and 1/3 the brightness and will have light spillover above/below the screen. 
 
For the price, you cannot beat a Silver Ticket screen from Amazon. Their woven acoustically transparent screen is a great performer, as proven in testing. If you want integrated boarder lighting or light rejection do SI; for absolutely reference color reproduction do Stewart StudioTek 130. 

The highest a screen should be is this: measure 1/3 up the screen from the bottom - that imaginary horizontal line should be at or below seated eye level. This results in the bottom of the screen being pretty close to the floor.
If you’re ever going to watch TV shows, and probably even if you are not, you should go with a screen aspect ratio to match the projector aspect ratio. So unless you’re using an amorphic lens on the projector, you should use a 16:9 screen. Otherwise, you’re losing 1/3 the pixels and 1/3 the brightness and will have light spillover above/below the screen. 
 
For the price, you cannot beat a Silver Ticket screen from Amazon. Their woven acoustically transparent screen is a great performer, as proven in testing. If you want integrated boarder lighting or light rejection do SI; for absolutely reference color reproduction do Stewart StudioTek 130. 

I had this problem two different times. I don’t have a backup generator. A quick power “flicker” on the grid caused it. 

I think the best way to do this is with the Media Scene Agent. You’ll need to create a media scene for each scenario (group of rooms, primary starting room) you want.
 
If your matrix doesn’t have enough ports and C4 sees these as 2 separate/independent sources, you’ll then need to create custom programming to manually switch the second room to the required physical input / source device. Not the media stream, but the source device.
Getting a bigger matrix will ultimately be a more consistent and flexible solution.
 
 

The problem is that the power cycles extremely quickly when switching to/from the backup generator. Because of this, the keypad does not completely lose power before powering back on. It gets stuck in a weird “half awake” state. I had this happen to every keypad in my house. I don’t have a backup generator; it was due to a power flicker from the electrical grid. 
 
The good news is that it’s very easy to fix. At the breaker box, turn off the breakers for about 10 seconds, then turn them back on, without activating backup power. The switches will resume normal behavior. 

Part of this week's Apple announcements are rumored to include new "U2" wideband chips.   I have assumed for a while that Apple would turn your Apple Watch into a precise indoor tracker, using HomePods and Apple TVs (etc.) as triangulation beacons to track what room you're in (and not just that you're home).   Maybe that is finally coming.   With existing 3rd party Homebridge drivers, that stuff could be easily tracked via C4 dummy devices.

Too much marketing smoke in the CEPro article. "Savant’s AI technology can be triggered through Siri Shortcuts allowing for additional hands-free automations" is not a full integration. C4 can do that with 3rd party drivers as can lots of other DIY systems. Full integration would be passing the voice to Savant for Savant to do its thing. "Or ask Siri on an Apple HomePod to dim the living room lights, turn on the Apple TV and launch Disney+." requires zero Savant or other control system to work.