Kwikset lock

[wappinghigh]

This is something that definitely needs to have the ability to be added and driver re identified using composer HE if there is a problem after a C4 firmware upgrade or the batteries go completely flat.

It is simply not good enough to "lock" this lock down in Composer Pro.

It is a security device therefore needs to be completely independent from a dealer and totally 100% configurable by the home owner

It is also near on impossible to re-identify this device remotely from Composer pro as someone has to be in the house to physically push buttons etc...

It doesn't matter if there are problem with drivers and the dealer forgets to add this or that, if it's a non important item like a TV or whatever..

But a Lock for your house?

Crickey: that is an essential item that simply *has* to work and be identified NO MATTER WHAT

Can someone with contacts around here please pass this onto kwikset or B&D or whoever the manufacturer is and make this lock upgradeable and identifiable using Composer HE.

Thanks

Wap

[RyanE]

If the batteries go completely flat, the identification / mesh info is still kept in the ZigBee module, and is not lost.

The only reason this lock would *ever* need to be re-identified is if some moron caused it to leave the ZigBee mesh.

If that does happen, yes someone has to physically tap a button to get it to identify, that person does not have to be the dealer, if the dealer remotes in and sets it to identify.

If a dealer "forgot" this, they should remedy the situation.

This is not a different argument than saying "Control4 should be DIY", which is as you know not currently the case, and not likely to change anytime soon.

RyanE

[wappinghigh]

I agree with what you say Ryan

And thanks for explaining how the driver works.

What you say is all well and good in theory. Yes in theory there should never be a problem with this lock.

Unfortunately computer<>human interaction and how these sorts of things work outside in the field does not necessarily pan out the way the original software engineers think it will..

In practice..out there in everyday use, all I'm saying is it would be nice to be able to re-identify this lock in HE

Just like in theory there should have never been a problem with the ID of iPhones etc with pro...but it soon become obvious that in practice, this should be put into the domain of users. So a change was made in 2.3. For that we are very grateful

I'd put certain essential devices into a similar category. Such as anything home security related.

[RyanE]

MyHome device registration wasn't "put into the users' hands" due to some issue with Pro or even with the Dealer model of installations...

MyHome registration was changed IMHO because of the site license and the fact that end users change / add MyHome devices *a lot* more often than they change locks, etc.

RyanE

[cashmoney]

This does bring up a question, for me... Are the access codes for the locks encrypted or can they be seen by the dealer? Could a dealer theoretically set his own access code?

I know this sounds far fetched but so did the idea of some porters at a Lamborghini dealer using customer info to break into their homes. It's a somewhat similar situation, sending folks into your homes who we really don't know and trusting them with our security info. A good addition to the locks would be all security info is encrypted and can only be entered by the owner.

[RyanE]

I think you have to consider that if you don't trust your installer, you're in a world of hurt no matter what.

Regardless of whether he knows the codes, he could program the lock to unlock on a schedule, etc.

You also need to consider security in depth. That is, you have a security panel as well as locks, as well as cameras on a DVR.

Your installer shouldn't be able to access / modify all 3. If he can only do the door lock, and doesn't manage your security panel codes, and can't erase images from the DVR, he's unlikely to consider unlocking the doors.

RyanE

[wappinghigh]

Sure.

But with so much security driver integration into C4 these days, you've just supported a solid argument why such drivers should be only seen and controlled within HE. In other words operated the other way around. Setup and visible only within HE. And totally absent and invisible to composer pro.

[RyanE]

No, not really.

Control4's drivers for security panels do *not* know the security code. It's not stored in the driver, it's not stored in the project file, the dealer does not have access to the security code.

Navigators can be used to enter a code, but it is just the same as typing the numbers on the physical security keypad.

End users (and dealers) can do something stupid, and have the project 'type in' that code in programming, but that can be done TODAY in ComposerHE, and is a bad idea whether a dealer does it, or whether the homeowner does.

RyanE