Level and Eve solve different parts of Apple Home security. Level’s current lineup centers on smart-lock access. Eve’s current security-relevant products include contact and motion sensing through Thread and Matter paths. In many homes they are complementary: the lock controls the door, while the sensor reports a door or motion event.
This 2026 comparison does not crown one universal winner. It shows what each brand can and cannot prove, which hubs and accounts are involved, how to test local and remote behavior, and where a real alarm or monitoring system remains separate.
Level vs Eve at a glance
| Need | Level path | Eve path | Missing layer |
|---|---|---|---|
| Lock or unlock a compatible door | Primary fit | Not a door-lock product path | Physical door fit, egress, and credential plan |
| Know a door or window changed state | Some exact locks expose door status; verify model and setup | Eve Door & Window is the focused contact path | State does not automatically equal an alarm zone |
| Detect movement | Not the main product role | Eve Motion is the focused path | Motion is not identity or camera evidence |
| Apple Home control | Exact model, Matter, home-key, and hub path must be checked | Exact Matter/Thread generation and controller must be checked | Remote access and automations add hub dependencies |
| Professional monitoring | Not a complete monitored alarm system | Not a complete monitored alarm system | Separate alarm panel, zones, communicator, and service |
Current Level smart-lock path
Level’s current Level Lock Pro page presents Matter-over-Thread, Apple home keys, touch-to-lock, and NFC-fob paths with a compatible hub requirement. The current Level Lock page lists door-fit measurements and notes that some features require internet access. Product names and generations have changed, so verify the exact box, product page, firmware, included accessories, and supported feature before purchase.
Level’s strength is access without a large interior housing. That design does not remove mechanical fit. Measure backset, door thickness, bore, handing, strike alignment, edge clearance, and the effort required to throw the deadbolt. A motor that must force a misaligned bolt will be less dependable.
Current Eve sensor path
The current Eve Door & Window page presents a Matter-enabled contact sensor that requires a compatible hub supporting Thread and Matter. Eve’s current Eve Motion path adds motion and light sensing. Check the exact sold generation, controller, border-router requirement, firmware, mount, environmental limits, battery, and platform-exposed features.
Eve sensors can report state and support automations. They do not physically secure a weak door, identify a person, record video, sound a monitored burglary alarm by themselves, or guarantee a dispatch response.
Matter, Thread, and Apple Home
Apple’s current Matter accessory guide and home-hub guide are the platform references. Record the exact Matter controller, Thread border routers, active home hub, Apple Home owner, shared residents, vendor apps, and recovery contacts.
Do not assume “Matter” makes all features identical across platforms. A device can expose core lock, contact, motion, or battery state while a vendor-specific feature remains in its own app. Apple home keys are also a distinct feature that should be verified for the exact lock and household devices.
Door fit and contact fit are separate jobs
A Level lock fits inside the door and replaces deadbolt components. An Eve contact sensor mounts on the door or frame with a magnet. Test both without letting one interfere with the other.
- Correct sag, rubbing, weather-seal pressure, and strike misalignment first.
- Measure the lock opening and compare it with the exact Level fit requirements.
- Close the door naturally and prove the deadbolt extends without pulling or pushing the door.
- Choose an Eve sensor position that stays within the maker’s gap and orientation.
- Open slowly and quickly; confirm state changes before the opening permits entry.
- Repeat after temperature or humidity changes that affect the door.
Credentials and household access
For each resident, guest, cleaner, contractor, or caregiver, document the exact access method: key, home key, fob, app invitation, keypad if supported by the chosen configuration, or another approved credential. Use named credentials where the platform supports them. Avoid one permanent shared code or account.
Test creation, first use, normal use, expiration, revocation, lost-phone recovery, and event history. A contact sensor can confirm the door opened, but it does not necessarily identify which credential unlocked it.
Automations: useful boundaries
Good automations preserve the primary event and avoid creating a new access risk:
- turn on an entry light when the door opens after dark;
- send a reminder when a door remains open;
- start a supported camera path after a direct contact event;
- alert a backup resident when a vulnerable opening changes state.
Do not automatically unlock or disarm from motion, presence, a broad geofence, or a camera classification. Do not auto-lock a door until the household has tested egress, pets, children, deliveries, and the physical door state.
Notifications and evidence
Define what each event proves:
| Event | What it proves | What it does not prove |
|---|---|---|
| Lock reports locked | The lock mechanism reported a state | The door is fully closed, latched, or impossible to force |
| Contact reports closed | Sensor and magnet are within the closed threshold | The deadbolt is extended |
| Motion reports activity | Motion met the sensor’s trigger rule | Who moved or whether entry was authorized |
| Apple Home notification | The platform delivered an event to that device | A siren, monitoring record, or dispatch occurred |
If visual evidence matters, add a camera selected by view, power, recording, storage, retention, privacy, export, and outage behavior. Neither a smart lock nor a motion/contact sensor is a substitute for video evidence.
Privacy and account control
Inventory the Apple Home owner, Level account, Eve app access if used, Matter fabrics, shared residents, home keys, fobs, automations, and any voice assistants. Remove former residents and test that removal from every layer.
Keep setup codes and recovery material offline in a controlled record. Do not place pairing codes where a visitor can photograph them. Before selling, moving, or replacing a device, remove it from the relevant home and vendor account, reset it using current instructions, and verify that old credentials no longer work.
Power, internet, and hub failures
Battery devices, phones, home hubs, border routers, Wi-Fi, broadband, and vendor services can fail independently. Run controlled tests:
- Disconnect internet while local power remains on; test local lock control, sensor state, automations, and remote alerts.
- Turn off the nearest Thread border router or active home hub; record rerouting and recovery time.
- Turn off the primary phone and prove another resident’s required access.
- Remove a test resident and confirm home keys, invitations, and app access are revoked.
- Simulate a low-battery workflow without exhausting the device; prove alert ownership and replacement steps.
- Restore dependencies and verify lock, door, motion, and battery states are not stale.
Alarm and monitoring fit
Level and Eve are not complete monitored alarm systems. If an opening must trigger an entry delay, local siren, cellular backup, monitoring-center workflow, or dispatch record, use a compatible alarm platform with direct enrolled zones and test it separately.
The current HomeKit security-device guide can help separate locks, cameras, sensors, and alarm roles. The smart-home security device guide provides a wider device and failure-path comparison.
Three-year written cost
Compare complete working paths rather than one device:
Three-year cost = lock or sensors + required hub/controller + optional keypad or credentials + batteries + camera or alarm layer + subscriptions + expected replacements.
Price one Level lock plus required controls against the number of Eve contacts and motion sensors needed for the same property. They are not direct substitutes, so the most useful worksheet often includes both. Add a monitored alarm or camera path only where the response requirement calls for it.
60-minute Level vs Eve acceptance test
- Record exact models, generations, firmware, batteries, Matter codes, controller, border routers, home hub, accounts, owners, and shared residents.
- Lock and unlock the Level device ten times from the inside and outside using every required credential.
- Open and close every Eve-protected opening ten times slowly and normally; verify state and reset.
- Walk-test Eve Motion from expected and unwanted paths while checking pets, heat, sunlight, and room layout.
- Confirm the contact reports closed only when the door is properly positioned, and the lock extends without forcing alignment.
- Trigger each alert with the primary phone locked, on mobile data, in Focus mode, and turned off; prove the backup resident.
- Disconnect internet, then one border router or home hub, and record local control, events, automations, remote access, and recovery.
- Create and remove one temporary resident or test credential; confirm all relevant access disappears.
- Test physical-key and inside-egress behavior with phones, voice, and internet unavailable.
- If an alarm platform is present, use approved test mode to prove the direct zone, delay, siren, communication, and monitoring record.
Verdict
Choose Level when the primary job is discreet smart-lock access on a physically compatible door. Choose Eve when the primary job is Matter-over-Thread contact or motion sensing. For a complete entry-security path, the two can work together—but only after testing door mechanics, controllers, credentials, alerts, outages, privacy, and the separate alarm or monitoring layer.
Frequently asked questions
Is Level better than Eve for home security?
They solve different jobs. Level controls compatible deadbolts; Eve’s relevant products report contact or motion events. Decide whether you need access, sensing, or both.
Do Level and Eve require a Thread border router?
Current Matter-over-Thread configurations require compatible controller and border-router paths. Verify the exact device generation, platform, and feature before buying.
Can an Eve sensor confirm a Level lock is locked?
A contact sensor can report door or window position. It does not prove the deadbolt is extended. Test lock state and door state as separate signals.
Can Level or Eve call professional monitoring?
Not as complete monitored alarm systems by themselves. Use a compatible alarm platform with direct zones, communication, and a tested monitoring service when professional response is required.
With over 20 years of experience evaluating home security technologies, Andrew is a trusted home security expert. He specializes in DIY home security systems, indoor and outdoor security cameras, doorbell cameras, and safety software such as password managers. Andrew uses in-depth research to provide accurate and actionable insights. His work helps you make better decisions to protect your home.
Leave a Reply