-
Notifications
You must be signed in to change notification settings - Fork 1
Compatibility Limits
This page lists the reference hardware, capacity limits, verified scope, and known limitations of the current public NAMO firmware. Review it before buying or substituting parts.
| Item | Current reference |
|---|---|
| Board | Seeed Studio XIAO ESP32S3 |
| Flash | 8MB |
| PSRAM | 8MB, Octal |
| Framework | ESPHome on ESP-IDF |
| Partitions | NAMO-specific 8MB partition layout |
The current firmware budgets memory, the embedded dashboard, and OTA partitions for 8MB Flash and 8MB PSRAM. A board with less Flash, no PSRAM, or a different ESP32 variant is not a drop-in replacement even when some pins match.
| Part | Status | Current purpose and limitation |
|---|---|---|
| LD2450 | Reference primary radar | Provides coordinates, motion, up to three targets, and spatial fusion observations. |
| LD2454 | Conditional compatibility | Supports the periodic coordinate frame shared with LD2450 and a bounded startup path. Physical testing found sensitivity to wrong-baud UART traffic during power-on, so it is not treated as equivalent to the reference radar. Verify repeated boots before permanent installation. |
| LD2410C | Optional | Assists an already established presence session. It does not create coordinates, motion, target count, or room state. |
| Panasonic EKMC1603111 PIR | Optional reference part | Provides additional motion evidence. Other PIR modules require separate voltage, output, and pin-stability verification. |
| BH1750 | Optional | Measures ambient light. |
| SHT4x | Optional | Measures temperature and humidity. |
For LD2454, a valid incoming coordinate frame is used without sending speculative commands. If no frame arrives after boot, the firmware performs one bounded recovery sequence rather than repeatedly restarting or commanding the module. A module that becomes stuck during power-on may require a clean power cycle.
| Scope | Limit |
|---|---|
| NAMO devices in one Fusion Group | 7, including the current device |
| Remote NAMO devices added from one device | 6 |
| Local or fused targets | 3 |
| Fusion Groups coordinated by the current device | 1 |
These are product contracts that keep embedded memory and network usage predictable. Configurations that bypass the UI or storage checks to exceed them are unsupported.
- NAMO coordinate fusion uses a two-dimensional plane.
- Mounting height and vertical tilt are not corrected as a 3D pose.
- Floorplan walls and doors provide shared structure and visual occlusion; they do not change physical radar penetration.
- Standalone detection can work without a floorplan.
- Room display, shared coordinates, and multi-device fusion require a floorplan.
- Active devices in one Fusion Group must use the same shared floorplan and geometry version.
- NAMO uses password-protected 2.4GHz Wi-Fi and rejects open Wi-Fi.
- The dashboard, pairing, and fusion assume a trusted local network.
-
.localmay fail depending on mDNS support, so an IP address must remain available. - Guest Wi-Fi, AP isolation, VLANs, and VPNs can block discovery or device-to-device communication.
- Chrome or Edge is recommended for the ESPHome Web Serial path used during first USB installation.
- Exposing a NAMO device to the public internet is unsupported.
See Network and security for the complete policy.
- Standalone sensing, floorplans, zones, pairing, position alignment, and coordinate fusion are implemented.
- Five-device physical setups have verified pairing and single or combined Configuration Owner, Site Leader, and Group Leader failure handover.
- Fixed-capacity code and host tests target up to seven devices in one Fusion Group.
- A complete physical matrix for every six- and seven-device placement, router, duration, and failure combination remains ongoing.
- The full rolling-upgrade matrix with mixed firmware versions has not completed release verification.
- The NAMO Home Assistant custom integration is a development preview and needs broader verification across real Home Assistant deployments.
NAMO is designed to retain presence more reliably than motion-only sensing, but it cannot guarantee a completely motionless person in every room and posture. Distance, orientation, furniture, glass, and partial body occlusion matter.
The primary radar may detect people or adjacent spaces through glass and some thin walls. Drawing a floorplan outline or wall does not block raw radar detection.
Radar and fusion outputs handle up to three targets. People may briefly merge or split when they stand close together or cross a view boundary.
The LD2410C is a presence-retention aid, not a second spatial radar. Its distance report cannot provide an accurate 2D position or multiple people.
The published top.3mf and bottom.3mf belong to the earlier single-radar generation. They must not be assumed to fit the current dual-radar PCB.
The embedded HTTP dashboard and API are not internet-facing services. Direct publication through HTTPS, a proxy, or a tunnel is unsupported.
- Confirm the board, Flash, and PSRAM match the reference.
- Verify the radar model, supply voltage, UART logic voltage, and pin order.
- Add non-reference sensors one at a time and test them independently.
- Test empty, seated, walking, and multi-person conditions before permanent installation.
- Add multi-device members one at a time and complete alignment before adding the next.
- Protect important automations from treating
unavailableas an empty room.