Aqara U100 Smart Lock
From Wiki-IoT
Revision as of 16:35, 27 September 2025 by Zmt20030508 (talk | contribs)
Classification
| Aqara U100 Smart Lock | |
|---|---|
| Classification | |
| Grade | A- |
| Calculator version | 1 |
| Classification date | 2025-09-24 |
| Information | |
| Name | Aqara U100 Smart Lock |
| Brand by Parent | Aqara by Lumi United |
| Generation | u |
| Model(s) | U100 |
| Release date | 2023-05-23 |
| Type/Category | Lock |
| Website | [1] |
| Status | In sale |
| More | |
| Dimensions | |
| Mass | |
| Operating system | Embedded RTOS |
| Companion App | Aqara Home App |
| CPU | High-performance ARM Cortex-M series MCU |
| GPU | |
| Memory | |
| Storage | Store fingerprints, passwords, and unlock logs locally |
| Battery | Rechargeable lithium battery |
| Power | Battery-powered, supports Type-C emergency power supply |
| Charging | May support (e.g. for lithium batteries) |
| Display | Touch the numeric keypad, LED status light |
| Camera | |
| Sound | Voice prompt, warning buzzer |
| Connectivity | Zigbee 3.0 (core connection, requires Aqara gateway), Bluetooth (direct connection to mobile phone), NFC |
| Device | |||
|---|---|---|---|
| Criterion | Value | Proof(s) | Comment |
| Known hardware tampering | Rare | [Link to Physical Security Test] | It is equipped with tamper detection and brute-force attack alarms. Physical attacks will trigger an alarm. |
| Known vulnerabilities | None | [Link to Security Research Platform] | As a relatively new product, there are no widely disclosed critical vulnerabilities yet. However, its complex multi-authentication system expands the potential attack surface. |
| Prior attacks | None | [] | No reports of large-scale real-world attacks have been found so far. |
| Updatability | Very common | [Aqara Home App OTA Update] | Key Advantage: Supports wireless firmware updates via a gateway, which is crucial for maintaining long-term security. |
| Category score | 2 | ||
| System | |||
|---|---|---|---|
| Criterion | Value | Proof(s) | Comment |
| Authentication with other systems | Partial | [August Cloud Service] | Authentication with cloud servers must be extremely strict to control lock access permissions. |
| Communications | Encrypted with up-to-date encryption | [TLS 1.2/1.3] | Baseline Requirement: All communications between the mobile phone, lock, and cloud must use strong encryption. BLE pairing should also use strong encryption. |
| Storage | Encrypted with up-to-date encryption | [] | Baseline Requirement: Electronically stored keys and user credentials (stored locally) must be encrypted. |
| Category score | 2 | ||
| User Authentication | |||
|---|---|---|---|
| Criterion | Value | Proof(s) | Comment |
| Account management | Full | [Aqara App] | Supports creating up to 50 users, and manages temporary passwords, fingerprints, and NFC cards by time period and permission level. |
| Authentication | Secure | [Multi-factor Authentication Fingerprint (biometrics) + Password (knowledge) + NFC card (possession).] | Provides multiple strong authentication methods. Whether biometric data is processed locally is crucial. |
| Brute-force protection | Exist | [] | Locks and sends an alert after multiple incorrect password entries. |
| Event logging | Access event logged | [Detailed Logs in App] | Records the unlocking method, user, and time for each unlock in detail, and allows setting alerts for abnormal behaviors. |
| Passwords | Require change after setup with complexity requirements | [] | Administrator passwords should be forced to meet complexity requirements. Temporary passwords can be set with an expiration period. |
| Category score | 1 | ||
| Grade | A- |
|---|
