Baldwin
Minneapolis 10 Touchscreen Electronic Deadbolt
SKU: 8225
Quickstart
This is a
Initiate the process to add the lock to your system at your smart home controller.When prompted by your smart home system to add the lock, press button A on the lock interior one time. The red LED will illuminate when the lock enters Add Mode.Please allow time for the controller to add the lock to your system.
Important safety information
Please read this manual carefully. Failure to follow the recommendations in this manual may be dangerous or may violate the law. The manufacturer, importer, distributor and seller shall not be liable for any loss or damage resulting from failure to comply with the instructions in this manual or any other material. Use this equipment only for its intended purpose. Follow the disposal instructions. Do not dispose of electronic equipment or batteries in a fire or near open heat sources.What is Z-Wave?
Z-Wave is the international wireless protocol for communication in the Smart Home. This device is suited for use in the region mentioned in the Quickstart section.
Z-Wave ensures a reliable communication by reconfirming every message (two-way communication) and every mains powered node can act as a repeater for other nodes (meshed network) in case the receiver is not in direct wireless range of the transmitter.
This device and every other certified Z-Wave device can be used together with any other certified Z-Wave device regardless of brand and origin as long as both are suited for the same frequency range.
If a device supports secure communication it will communicate with other devices secure as long as this device provides the same or a higher level of security. Otherwise it will automatically turn into a lower level of security to maintain backward compatibility.
For more information about Z-Wave technology, devices, white papers etc. please refer to www.z-wave.info.
Product Description
Kwikset, the leader in residential security, introduces the Baldwin 8225 Touchscreen Electronic Deadbolt with Z-Wave.Capacitive touchscreenSecureScreen: Additional security by preventing fingerprint code detectionOne touch lockingDramatically reduced, all-metal interior30 user codes plus master codeBHMA grade 2 certified20 minute fire rating - UL certifiedFull 128-bit encryption securitySmartKey: Re-key the lock in seconds
Prepare for Installation / Reset
Please read the user manual before installing the product.
In order to include (add) a Z-Wave device to a network it must be in factory default state. Please make sure to reset the device into factory default. You can do this by performing an Exclusion operation as described below in the manual. Every Z-Wave controller is able to perform this operation however it is recommended to use the primary controller of the previous network to make sure the very device is excluded properly from this network.
Reset to factory default
This device also allows to be reset without any involvement of a Z-Wave controller. This procedure should only be used when the primary controller is inoperable.
A factory reset will delete all user codes associated with the lock and will remove itself from your smart home system.Please only perform a factory reset when the primary controller is missing or inoperable.To perform a factory reset, please perform the following:1. Remove the battery pack2. Press and HOLD the Program button while reinserting the battery pack.3. Keep holding the button for 30 seconds until the lock beeps and the status LED flashes red.4. Press the Program button once more.The status LED will flash green and red several times.5. After a few seconds, the lock will initiate the door handing process.
Inclusion/Exclusion
On factory default the device does not belong to any Z-Wave network. The device needs to be added to an existing wireless network to communicate with the devices of this network. This process is called Inclusion.
Devices can also be removed from a network. This process is called Exclusion. Both processes are initiated by the primary controller of the Z-Wave network. This controller is turned into exclusion respective inclusion mode. Inclusion and Exclusion is then performed doing a special manual action right on the device.
Inclusion
Initiate the process to add the lock to your system at your smart home controller.When prompted by your smart home system to add the lock, press button A on the lock interior one time. The red LED will illuminate when the lock enters Add Mode.Please allow time for the controller to add the lock to your system.Exclusion
Follow your smart home systems instructions to remove the lock from the network. When prompted by the system, press button A on the lock interior once.The red LED will illuminate when the lock enters Remove mode.Communication to a Sleeping device (Wakeup)
This device is battery operated and turned into deep sleep state most of the time to save battery life time. Communication with the device is limited. In order to communicate with the device, a static controller C is needed in the network. This controller will maintain a mailbox for the battery operated devices and store commands that can not be received during deep sleep state. Without such a controller, communication may become impossible and/or the battery life time is significantly decreased.
This device will wakeup regularly and announce the wakeup state by sending out a so called Wakeup Notification. The controller can then empty the mailbox. Therefore, the device needs to be configured with the desired wakeup interval and the node ID of the controller. If the device was included by a static controller this controller will usually perform all necessary configurations. The wakeup interval is a tradeoff between maximal battery life time and the desired responses of the device. To wakeup the device please perform the following action: Even though the lock is sleeping, all buttons are active and can be used to initiate any lock activity.For the RF side, it will wake up every 1 second to check if there are any requests from your smart home controller.
Quick trouble shooting
Here are a few hints for network installation if things dont work as expected.
- Make sure a device is in factory reset state before including. In doubt exclude before include.
- If inclusion still fails, check if both devices use the same frequency.
- Remove all dead devices from associations. Otherwise you will see severe delays.
- Never use sleeping battery devices without a central controller.
- Dont poll FLIRS devices.
- Make sure to have enough mains powered device to benefit from the meshing
Association - one device controls an other device
Z-Wave devices control other Z-Wave devices. The relationship between one device controlling another device is called association. In order to control a different device, the controlling device needs to maintain a list of devices that will receive controlling commands. These lists are called association groups and they are always related to certain events (e.g. button pressed, sensor triggers, ...). In case the event happens all devices stored in the respective association group will receive the same wireless command wireless command, typically a 'Basic Set' Command.
Association Groups:
| Group Number | Maximum Nodes | Description |
|---|---|---|
| 1 | 1 | Z-Wave Plus LifelineSupports the following types of unsolicited messages:Battery Report - sends periodic battery reports containing the battery percentage.Door Lock Operation Report - upon power up, this message will be sent to allow the controller to sync up with the current lock status.Notification Report - many notification types will be sent for status and alarms.The following notification types are supported:Access Control (V2), Home Security (V2), and Power Management (V2).Device Reset Locally Notification - this message will be sent to notify the smart home controller that the lock is resetting back to factory defaults and will be leaving the network. |
| 2 | 5 | This group will provide all Notification reports as described for the Lifeline.This group allows other controllers, other than the lifeline, to receive these types of unsolicited messages as well. |
Configuration Parameters
Z-Wave products are supposed to work out of the box after inclusion, however certain configuration can adapt the function better to user needs or unlock further enhanced features.
IMPORTANT: Controllers may only allow configuring signed values. In order to set values in the range 128 ... 255 the value sent in the application shall be the desired value minus 256. For example: To set a parameter to 200 it may be needed to set a value of 200 minus 256 = minus 56. In case of a two byte value the same logic applies: Values greater than 32768 may needed to be given as negative values too.
Parameter 1: User Code Type for User Code 1
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 1.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 10: User Code Type for User Code 10
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 10.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 11: User Code Type for User Code 11
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 11.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 12: User Code Type for User Code 12
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 12.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 13: User Code Type for User Code 13
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 13.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 14: User Code Type for User Code 14
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 14.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 15: User Code Type for User Code 15
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 15.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 16: User Code Type for User Code 16
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 16.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 17: User Code Type for User Code 17
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 17.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 18: User Code Type for User Code 18
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 18.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 19: User Code Type for User Code 19
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 19.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 2: User Code Type for User Code 2
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 2.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 20: User Code Type for User Code 20
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 20.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 21: User Code Type for User Code 21
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 21.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 22: User Code Type for User Code 22
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 22.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 23: User Code Type for User Code 23
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 23.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 24: User Code Type for User Code 24
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 24.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 25: User Code Type for User Code 25
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 25.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 26: User Code Type for User Code 26
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 26.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 27: User Code Type for User Code 27
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 27.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 28: User Code Type for User Code 28
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 28.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 29: User Code Type for User Code 29
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 29.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 3: User Code Type for User Code 3
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 3.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 30: User Code Type for User Code 30
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 30.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 31: Dipswitch settings
This is a one byte read only bit mask that returns the state of the user accessible dipswitches on the rear panel of the door lock.0x01: Lock Status LED (1: enabled, 0: disabled)0x02: Autolock setting (1: enabled, 0: disabled)0x04: Buzzer (1: enabled, 0: disabled)0x08: Secure Screen (1: enabled, 0: disabled) Size: 1 Byte, Default Value: 11
| Setting | Description |
|---|---|
| 0 | All functions are disabled |
| 1 | Lock Status LED enabled |
| 2 | Autolock setting enabled |
| 3 | Lock Status & autolock enabled |
| 4 | Audio Feature enabled |
| 7 | Lock Status, Autolock, and Audio feature enabled |
| 8 | Secure Screen enabled |
| 15 | All features are enabled |
Parameter 33: SKU number, 1st 4 bytes
This configuration parameter provides the first 4 bytes of the SKU number that has been programmed into the lock. Size: 4 Byte, Default Value: 0
| Setting | Description |
|---|---|
| 32 - 126 | All printable characters |
Parameter 34: SKU number, last 4 bytes
This configuration parameter provides the second and last 4 bytes of the SKU number that has been programmed into the lock. Size: 4 Byte, Default Value: 0
| Setting | Description |
|---|---|
| 32 - 126 | All printable characters |
Parameter 4: User Code Type for User Code 4
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 4.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 40: Reset to Default
This configuration parameter allows the smart home controller to force a factory reset of the lock.After receiving this request, the lock will send a Device Reset Locally message back to the lifeline controller.This configuration parameter is a write only parameter where the only possible value to write is a 1.The lock will not accept any other value. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Force Factory Reset |
Parameter 5: User Code Type for User Code 5
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 5.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 6: User Code Type for User Code 6
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 6.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 7: User Code Type for User Code 7
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 7.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 8: User Code Type for User Code 8
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 8.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Parameter 9: User Code Type for User Code 9
This configuration parameter is used to get or set the type of user for their corresponding user code.By default, all user codes are set to the Owner type unless otherwise specified.The parameter type is associated with the user code location 9.Caution must be used when setting these values.Guests and Workers will require schedules attached to them in order for those types to be assigned. Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Owner |
| 3 | Guest |
| 4 | Worker |
Technical Data
| Hardware Platform | ZM5101 |
| Device Type | Door Lock - Keypad |
| Network Operation | Listening Sleeping Slave |
| Firmware Version | HW: 6 FW: 4.10:66.23 |
| Z-Wave Version | 6.51.08 |
| Certification ID | ZC10-19056501 |
| Z-Wave Product Id | 0x0090.0x0009.0x0642 |
| Firmware Updatable | Updatable by Consumer by RF |
| Door Lock Type | Deadbolt |
| Supported Notification Types | Access ControlHome SecurityPower Management |
| Communications Protocol | Z-Wave Serial API |
| Frequency | XXfrequency |
| Maximum transmission power | XXantenna |
Supported Command Classes
- Antitheft V2
- Association Grp Info
- Association V2
- Battery
- Configuration
- Device Reset Locally
- Door Lock Logging
- Door Lock V2
- Firmware Update Md V3
- Manufacturer Specific V2
- Notification V4
- Powerlevel
- Schedule Entry Lock V2
- Security
- Time Parameters
- User Code
- Version V2
- Zwaveplus Info V2
Explanation of Z-Wave specific terms
- Controller — is a Z-Wave device with capabilities to manage the network. Controllers are typically Gateways,Remote Controls or battery operated wall controllers.
- Slave — is a Z-Wave device without capabilities to manage the network. Slaves can be sensors, actuators and even remote controls.
- Primary Controller — is the central organizer of the network. It must be a controller. There can be only one primary controller in a Z-Wave network.
- Inclusion — is the process of adding new Z-Wave devices into a network.
- Exclusion — is the process of removing Z-Wave devices from the network.
- Association — is a control relationship between a controlling device and a controlled device.
- Wakeup Notification — is a special wireless message issued by a Z-Wave device to announces that is able to communicate.
- Node Information Frame — is a special wireless message issued by a Z-Wave device to announce its capabilities and functions.