RyanE

Please tell me what professionally installed automation system has more end user control than control4 between the OS3 app, Composer Home Edition and When / Then?
Not Savant, Crestron, AMX, Elan, RTI..... Please tell me what I'm missing here?

This really shows how little you know about the other systems... 

Same wife has her own but honestly never remembers her info and asks me for mine smh

While I agree with some of your other statements re: the DS2, this one is outright wrong.
Control4 has released a DS2 driver update since the Chime release, and is likely to continue to update the driver with bugfixes.
Some of the limitations / issues are hardware issues (lower res camera, worse low light sensitivity, etc.), that obviously can't be fixed with a driver update, but driver bugs are still 'fair game'.
RyanE

I use the backlights to indicate when the power's out.

RyanE

Thanks Ryan! Much appreciated!

There's a driver specifically made to manage that for you.
You set the lock time (up to 3600 seconds), you connect your lock proxy and your door contact input, and you're good to go.
You of course turn off the auto lock on the door lock itself.
You can enable/disable it through ComposerPro programming (which I do for all locks when we have guests over, for example), and there is a UIButton that shows the door's status, whether it's open unlocked / open locked / closed unlocked / closed locked, and can be allowed to either only lock, or can be allowed to lock and unlock the lock.
You can even choose the color of the lock icon set (black/black, red/green, green/red, etc.).
It's available in the online database, and it's called "Door Auto-Lock (OS 2.9+)"
RyanE

There's a driver specifically made to manage that for you.
You set the lock time (up to 3600 seconds), you connect your lock proxy and your door contact input, and you're good to go.
You of course turn off the auto lock on the door lock itself.
You can enable/disable it through ComposerPro programming (which I do for all locks when we have guests over, for example), and there is a UIButton that shows the door's status, whether it's open unlocked / open locked / closed unlocked / closed locked, and can be allowed to either only lock, or can be allowed to lock and unlock the lock.
You can even choose the color of the lock icon set (black/black, red/green, green/red, etc.).
It's available in the online database, and it's called "Door Auto-Lock (OS 2.9+)"
RyanE

This is an opinion.
RyanE

Even your forum handle is an *opinion*.
RyanE

I think you misspelled opinions.
RyanE

Call me crazy but the nicest keypad (aesthetically) of the 3 pictures you posted is without a doubt the black C4 Keypad at the bottom. The white Control4 keypad with the god awful glass plate looks terrible. Hate the way those engravings look too. The C4 faceplates really make the keypad look great. Don't use other brands of face plates.
And dont get me wrong I understand that glass is a premium product and plastic is a cheap product but that palladium keypad is a total gimmick. The glass wall plate looks so small and crappy. The engravings aren't centered. That thing will look super outdated fast. I dunno, I'm not a fan at all. I certainly wouldn't pay extra for that finish. The pricing is out to lunch on Palladium. The only room where that would even make make sense is in a bathroom... but even then. To each their own though.
 
Depending on the finish of the house go with Snow white (WAY better than regular white) and if you can go with Midnight black (way better than regular black) with a stainless C4 plate.

Comparatively I would say it is. Compared to EAs, CAs, or other smart home control hubs. 

Oh my, yes I'm assuming it's all 'power at light' wiring, hence no neutral at the switch location.
If it's full no neutral in the house...move out.

As there is no 'flash' mode on keypad button LEDs by design, as flash is annoying, the only way to do this is to send on / off commands to the keypads for every flash on / flash off.
This causes a large number of Zigbee packets on the network, and *really* is not recommended.
That said, if you wanted to do it, the best way would be to create a repeating timer in the Timer agent, put programming to toggle the LED when the timer goes off (if needed, use a separate variable to track state), start the timer when the door is opened, and stop the timer (and set the LEDs to the 'off color') when the door is closed.
RyanE

As there is no 'flash' mode on keypad button LEDs by design, as flash is annoying, the only way to do this is to send on / off commands to the keypads for every flash on / flash off.
This causes a large number of Zigbee packets on the network, and *really* is not recommended.
That said, if you wanted to do it, the best way would be to create a repeating timer in the Timer agent, put programming to toggle the LED when the timer goes off (if needed, use a separate variable to track state), start the timer when the door is opened, and stop the timer (and set the LEDs to the 'off color') when the door is closed.
RyanE

I guess Snap should hire you because of course then they'd have zero issues sourcing parts and materials that will absolutely always live 100% up to the supplier's specs and will always fulfill Snap's expectations.
Oh wait, that isn't possible.
Like every manufacturer, Snap/Control4 are going to have issues from time to time (fortunately with Control4, it's been very infrequently), and having it be a variable cost to fix is a good way to go out of business.
With relatively few 8" T4's released, it's not unreasonable for Control4 to set a fixed rate for replacement.
RyanE

I guess Snap should hire you because of course then they'd have zero issues sourcing parts and materials that will absolutely always live 100% up to the supplier's specs and will always fulfill Snap's expectations.
Oh wait, that isn't possible.
Like every manufacturer, Snap/Control4 are going to have issues from time to time (fortunately with Control4, it's been very infrequently), and having it be a variable cost to fix is a good way to go out of business.
With relatively few 8" T4's released, it's not unreasonable for Control4 to set a fixed rate for replacement.
RyanE

Man, if the reimbursement for this isn't covering your (or a junior installer's) time, you need to work faster. All you're doing is replacing a screen (not the back box), with the T4 and it's install method, it should take you as long to log into a system as it does to physically swap it and ID it.
If you're talking about a long drive time, sure.

Ok, so you can do your lua and xml coding in something like visual studio and then use Driver Packager to Zip it together with varoius options like encryption, etc.

Also just wanted to say that this is the first driver that @Andrew luecke has developed at Chowmain Software & Apps.
He has done a fantastic job and it is upto (if not exceeding) the standards we have at our company.
Keep up the good work mate.

Indeed, if there are two areas of my Control4 system I want worry-free reliability it is lighting and distributed audio. Relying on third party integrations for these major pieces is not recommended from my perspective.

+1 for C4 lighting.   Solid value and options.   My only gripe has been durability of toggles/light bars but they do offer replacement parts which helps.

I agree, I’m hoping they add the capability to HE soon. 

By combining I just meant incorporating the XML code, or whatever else is required, for the bindings.