Aqara and Eve can both put entry, motion, and other smart-home signals into Apple Home, but they are not interchangeable security systems. Aqara offers a wider device family that includes hubs, cameras, locks, and sensors. Eve centers its current security-relevant range on Matter-over-Thread sensors and Apple Home cameras. Neither buying path should be mistaken for a complete professionally monitored burglar alarm without a separate alarm and response layer.
This 2026 comparison uses exact jobs instead of a brand-wide winner. It covers door state, motion, presence, video, hubs, Matter and Thread, Apple Home, privacy, remote access, outages, cost, and acceptance testing.
Aqara vs Eve: quick navigation
Short verdict
- Choose Aqara for a broader first-party device path when you want to evaluate hubs, contact sensors, presence sensors, cameras, and locks under one maker account. Confirm the protocol and hub requirement of every exact model before buying.
- Choose Eve for a smaller Apple Home/Matter sensor plan when the required jobs match Eve Door & Window, Eve Motion, or an Apple Home camera and you already have the needed Apple home hub and Thread border-router path.
- Choose a dedicated alarm as the response layer when local siren behavior, cellular backup, professional monitoring, dispatch workflow, or written alarm-state control is required.
A sensor that appears in Apple Home can drive an alert or automation. That does not automatically make it a listed alarm zone, connect it to a monitoring center, or produce police dispatch. Write those jobs separately.
Current product and platform matrix
| Decision | Aqara path | Eve path | What to verify |
|---|---|---|---|
| Door/window state | Door and Window Sensor P2 uses Matter over Thread | Eve Door & Window uses Matter over Thread | Controller, Thread border router, mounting gap, battery, alert route |
| Motion | Choose the exact Aqara motion or presence model and note its protocol | Eve Motion uses Matter over Thread | Motion versus presence job, field of view, retrigger behavior |
| Presence | Presence Sensor FP2 is a dedicated presence product | Eve’s cited comparison path is motion, not room-zone presence mapping | Required zones, occupancy logic, privacy, false states |
| Cameras | Camera Hub G5 Pro combines camera and Aqara hub roles | Eve Outdoor Cam is an Apple HomeKit Secure Video camera | Power, location, recording requirements, event export, owner access |
| Broader first-party range | Hubs, sensors, cameras, locks, and other automation devices | Smaller security-relevant range centered on sensors and cameras | Exact jobs, not catalogue size |
| Professional monitoring | Do not infer it from the device or Apple Home listing | Do not infer it from the device or Apple Home listing | Named provider, plan, communicator, dispatch path, contract |
Official product references checked for this comparison:
- Aqara Door and Window Sensor P2
- Aqara Presence Sensor FP2
- Aqara Camera Hub G5 Pro
- Eve Door & Window
- Eve Motion
- Eve Outdoor Cam
- Eve Matter overview
Doors, motion, and presence
Door and window contacts
Aqara Door and Window Sensor P2 and Eve Door & Window are the closest direct comparison. Both current pages describe Matter-over-Thread products. That puts the buying decision on installation, controller ownership, border-router coverage, battery service, event timing, app workflow, and the way each household handles failures.
Test the actual door before standardizing. Metal frames, recessed trim, a wide magnet gap, a moving door, or weak Thread coverage can matter more than the logo. Mount one sensor, close the door gently and firmly, leave it slightly ajar, and test from the far edge of the property.
Motion is not the same as presence
Motion sensors are good for movement events. Presence products may be designed to maintain a room-occupancy state or distinguish zones, depending on the exact product. Do not use a presence label as proof of alarm-grade detection, and do not use a motion event as proof that a room is empty after movement stops.
For security planning, give each signal one job:
- contact sensor: prove an opening changed state;
- motion sensor: report movement in a defined coverage area;
- presence sensor: support room or zone occupancy logic;
- camera: add visual context and evidence;
- alarm zone: produce the system’s documented alarm behavior;
- monitoring plan: define human response and dispatch.
Cameras and evidence
The camera comparison is not one-to-one. Aqara Camera Hub G5 Pro is part of Aqara’s hub and camera path. Eve Outdoor Cam is a wired outdoor camera designed around Apple HomeKit Secure Video. Confirm location, wiring, recording requirements, Apple home hub, iCloud plan, field of view, and night image on the exact product page before purchase.
Test the evidence chain
- Close the app and lock the test phone.
- Open the target door and cross the camera zone.
- Record the contact-event time, notification time, and recording start.
- Confirm that the clip shows the entry, not only the person’s exit.
- Open live view over cellular data.
- Export a test clip and confirm playback, timestamp, and owner access.
- Repeat after restarting the camera, home hub, and router.
Camera access should be checked in both Apple Home and the maker’s app where one is used. Removing a Home resident does not prove that a separate maker account, exported clip, or shared credential has also been removed.
For the wider distinction between an Apple Home layer and a dedicated security panel, read 2GIG vs Apple Home. For a camera-first local recording comparison, see Apple Home vs Ubiquiti.
Matter, Thread, hubs, and Apple Home
Matter is an application-layer standard. Thread is an IP-based low-power mesh transport. A Matter-over-Thread accessory still needs a compatible Matter controller and a Thread border router. Apple Home users may get those roles from a supported Apple TV or HomePod model, but the exact home-hub and Thread state should be checked rather than assumed.
Aqara planning rule
Aqara sells products across more than one protocol and generation. Some products need an Aqara hub, while a Matter-over-Thread product has a different controller and border-router path. Build the inventory at model level. Do not write “Aqara sensor” on a plan without the model number, protocol, app, hub, controller, and firmware owner.
Eve planning rule
Eve’s cited Door & Window and Motion pages identify Matter-over-Thread products. The household still needs to document the controller, border router, Apple Home owner, residents, remote-control path, and what happens if the hub or internet connection is unavailable.
Mixed-home rule
A mixed Aqara-and-Eve home can work if every job and dependency is recorded. The risk is not simply that brands differ. It is that ownership becomes unclear: one resident owns Apple Home, another owns an Aqara account, a third knows lock codes, and nobody owns the failure test. Keep one worksheet with:
- room and security job;
- manufacturer and exact model;
- protocol and power source;
- hub, controller, and border router;
- owner account and approved residents;
- alert and recording destination;
- battery or service interval;
- offline behavior and rollback.
Accounts, residents, and privacy
Apple Home can centralize control, but account boundaries remain. Review Apple Home residents, who may add or edit accessories, camera permissions, Aqara account users, any Eve app permissions, Apple Account devices, and exported camera footage.
Use a named account for each person when the product supports it. Avoid sharing the owner’s password. Remove temporary residents and codes after installers, guests, pet sitters, or contractors leave. If the household changes, test that removed access fails instead of stopping when a name disappears from a list.
| Privacy check | Question | Evidence |
|---|---|---|
| Home membership | Who can control accessories remotely? | Current resident and permission list |
| Camera view | Who can stream and view recordings? | Camera permission screen and approved test |
| Maker account | Who owns the Aqara or related service account? | Owner email, MFA state, user list |
| Location logic | Whose phone changes home/away behavior? | Named automation and tested trigger |
| Exports | Where do saved clips go? | Approved storage and deletion rule |
Alarm, siren, monitoring, and dispatch gap
Neither a Matter badge nor an Apple Home tile proves that a sensor is part of a monitored burglar alarm. If the required outcome is a loud local alarm, battery-backed panel, cellular path, monitoring-center response, or dispatch, name the product and service that supplies it.
A dedicated alarm can sit beside Aqara or Eve devices. For example, an owner might use Apple Home sensors for convenience and automation while a separate Abode system handles alarm state, direct security sensors, optional monitoring, and the response path. Current Abode references:
Do not promise that a third-party Matter sensor becomes an alarm zone unless the alarm maker documents that exact behavior. Buy and test the alarm layer on its own terms.
Three-year cost worksheet
Published prices, bundles, and subscriptions change. Capture the checkout price and plan terms on the same day for both designs.
| Cost line | Aqara design | Eve design |
|---|---|---|
| Door/window sensors | Quantity × current price | Quantity × current price |
| Motion/presence devices | Exact model and quantity | Exact model and quantity |
| Camera and wiring | Camera, mount, power, network work | Camera, mount, wiring, electrical work |
| Hub/controller/border router | Only missing roles | Only missing roles |
| Cloud or recording plan | 36 × required monthly fee | 36 × required monthly fee |
| Alarm and monitoring layer | Equipment + 36 months if required | Equipment + 36 months if required |
| Batteries and replacements | Three-year service estimate | Three-year service estimate |
| Exit cost | Re-pairing, replacement, electrician, lost service | Re-pairing, replacement, electrician, lost service |
Three-year total = equipment + hubs/controllers + installation + 36 months of required services + batteries + expected replacement work. Keep optional monitoring separate so a self-monitoring design is not compared with a monitored one as if they perform the same job.
60-minute Aqara vs Eve acceptance test
| Minutes | Test | Pass condition |
|---|---|---|
| 0–8 | Inventory exact models, protocols, power, hubs, and owners | No generic brand-only rows remain |
| 8–15 | Open and close each test contact slowly and firmly | State matches the physical opening every time |
| 15–22 | Walk expected and nuisance motion paths | Intended movement is detected without unsafe automation |
| 22–30 | Trigger one camera event and export it | Entry, timestamp, playback, and owner access are usable |
| 30–38 | Test remote control over cellular data | Approved resident gets the intended result |
| 38–45 | Restart the home hub or border-router path | Devices recover and report current state |
| 45–52 | Disable internet access | Local behavior matches the written design; remote limits are known |
| 52–57 | Remove a temporary resident or test permission | Removed access fails and approved access remains |
| 57–60 | Restore service and record results | Normal state returns with a dated rollback note |
Run the test again after changing the router, home hub, Thread border router, Apple Home owner, camera recording plan, or alarm service. A design that cannot be tested after change is hard to operate safely.
Final recommendation
Aqara is the better shortlist when the project needs a broad maker-owned set of hubs, sensors, cameras, and locks. Eve is the cleaner shortlist when a smaller Matter-over-Thread sensor plan and Apple Home camera path cover the required jobs. For either brand, make a separate decision about alarms, local warning, backup communication, monitoring, and dispatch.
Buy one contact sensor first. Test its physical fit, Thread path, remote alert, account ownership, hub recovery, and offline behavior. Add cameras or presence devices only after the basic event chain passes.
Frequently asked questions
Is Aqara better than Eve for Apple Home?
Aqara has a broader first-party device range, while Eve offers a smaller set of Apple Home and Matter-focused products. The better fit depends on the exact door, motion, presence, camera, hub, privacy, and response jobs.
Do Aqara and Eve sensors need a hub?
Matter-over-Thread models need a compatible Matter controller and Thread border router. Other Aqara models may have different hub and protocol requirements. Check the exact model page before buying.
Can Aqara and Eve devices work in the same Apple Home?
Compatible models can be added to the same Apple Home when the required controller, border router, software, and owner permissions are in place. Test every model and keep the maker-account path documented.
Are Aqara or Eve complete home alarm systems?
Do not infer professional monitoring, cellular backup, or dispatch from a Matter or Apple Home listing. Add a dedicated alarm and monitoring service when those outcomes are required.
Which brand is better for security cameras?
Compare exact camera models rather than the brands alone. Check location, power, field of view, recording requirements, event timing, storage, export, permissions, offline behavior, and the separate alarm-response layer.
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