-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
Start with the least destructive check. Most temporary network, pairing, or role-handover states should not be handled by resetting every device.
- Note the exact local time and action that caused the problem.
- Keep the affected devices powered.
- Wait for an ongoing save, update, pairing, calibration, or handover to finish.
- Reload the dashboard once.
- Open the device by IP address if its
.localname fails. - Check Management/Backup > System information.
- Restart only the affected device if needed.
Create a backup before deleting settings. A factory reset should be the final recovery step, not the first diagnostic step.
When reporting a reproducible problem, include:
- firmware and dashboard versions;
- device model and connected radar modules;
- IP addresses or short device names, with private network details redacted if needed;
- exact time and time zone;
- the user action immediately before the problem;
- the complete user-facing error message and HTTP status if visible;
- device logs covering before and after the event;
- which device was the configuration source and which device was the target;
- whether power or Wi-Fi changed during the operation.
Do not include Wi-Fi passwords, Home Assistant API keys, firmware signing keys, or private device credentials.
- Confirm that the phone or computer is on the same LAN as NAMO.
- Try
http://<device-ip>/instead of the.localaddress. - Check that client isolation or a guest Wi-Fi network is not blocking local devices.
- Wait if the device has just rebooted after setup or an update.
- Try another data-capable USB power supply if the device repeatedly disappears.
.local depends on mDNS support and multicast traffic. It generally works most consistently on macOS and iOS, but may fail depending on the Windows or Android device, browser, and network. Routers, VLANs, VPNs, guest Wi-Fi, and client isolation can also block mDNS. If resolution is unreliable, create a DHCP reservation and use the device IP address.
Reload once after the operation has finished. Avoid repeated refreshes during a floorplan save, firmware update, pairing commit, or calibration activation.
- Wait for the device to finish booting.
- Confirm that the correct factory image was installed.
- Disconnect optional modules that may affect a strapping pin, then reboot.
- Check USB power and cable quality.
- Re-enter the SSID and password exactly.
- Confirm that the selected network is reachable from the installation location.
- Avoid captive portals and networks that isolate wireless clients.
- Use the IP address assigned by the router after setup.
The first ESPHome Native API check can take about one minute. The NAMO dashboard can be ready before Home Assistant confirms the connection.
- Check that the primary LD2450-series radar is available.
- Verify crossed UART wiring: XIAO TX to radar RX and XIAO RX to radar TX.
- Confirm common ground and the correct supply voltage.
- Check whether a disabled or excluded area covers the target.
- Inspect the radar direction on the floorplan.
The firmware may boot without valid primary-radar frames, but spatial detection cannot work normally.
First determine whether the raw radar coordinates move or only the fused result moves.
- Glass, thin walls, reflective surfaces, partial body visibility, and mounting angle can disturb the radar itself.
- Confirm the radar origin, rotation, and floorplan scale before adding correction areas.
- Compare one radar at a time before blaming fusion.
- Use false-positive correction only after the physical placement is credible.
A short duplicate can occur at the edge of a radar view or while observations associate across devices. Persistent duplicates require checking local raw targets, pair calibration, overlap geometry, and whether two real targets are present.
This is expected. LD2410C can maintain an already established presence session but does not create coordinates, target count, room state, or zone occupancy by itself.
An isolated warning lasting tens of milliseconds does not by itself mean that the device crashed. Investigate when warnings become frequent, occur in bursts, coincide with unavailable state, low-memory warnings, watchdog resets, or visible detection gaps.
Correct the radar origin and rotation. Do not move every zone to compensate for an incorrect radar placement.
Check the full floorplan scale, outline, physical wall segments, door placement, and radar position. A floorplan outline is not a substitute for fixing a grossly incorrect radar transform.
Open Floorplan > Edit > Change radar position > Advanced options. Verify the stored physical walls and use an occlusion exception only for a real wall that the radar can genuinely see through.
Open the configuration source device shown by the dashboard. If a connected device has just restarted, wait for the latest shared floorplan and connection records to converge.
- Enable Allow connection for 3 minutes on the target.
- Refresh the nearby list.
- Enter the target IP address manually.
- Confirm that the target is not still responsible for another Site.
Refresh the connected-device list and continue from the current configuration source. Do not keep submitting the operation to the old source device.
Messages such as site_configuration_continuity_unavailable or site_configuration_sync_timeout mean the devices have not finished agreeing on their shared connection records or floorplan within the UI wait period.
Keep both devices online, stop making additional changes, wait for the state to settle, then use Continue connection setup. If the same state persists after a restart, collect logs from both devices before resetting connections.
The devices report conflicting shared connection records. Review the existing connected-device lists on both sides. Finish a pending removal or reset stale device-to-device connections on the isolated target before pairing again.
Automatic alignment accepts only bounded corrections:
- at least 0.8 m between the two calibration positions;
- no more than 750 mm position correction;
- no more than 12 degrees rotation correction;
- no more than 350 mm residual error.
If the correction exceeds these limits, fix the saved radar position or floorplan scale instead of repeatedly accepting a large automatic correction. Use one person and choose two clearly separated positions visible to both radars.
A short degraded state can occur while a device restarts, an eligible replacement takes over, or shared credentials converge. Local sensing continues on powered devices. If the state does not recover, check online/configured device counts and each device's connection status.
Keep both devices online and finish the pending removal. Use force removal only when the target cannot be recovered; afterward reset stale device-to-device security connections on the target before pairing it again.
Wait for reboot, reopen the dashboard by IP address, and check the installed version. The final response can be lost even after a successful flash.
- Use an unedited backup created by NAMO.
- Review checksum and format-version errors.
- Import only sections present in the file.
- Restore a shared floorplan from the configuration source.
Wait until the device finishes booting and storage operations are idle. In a connected Site, finish member removal or use the configuration source before resetting shared connection or space data.
Open Management/Backup > Show API key and compare it. If the key was reissued, update or recreate the ESPHome integration with the new key.
This is intentional. NAMO does not report an unreachable source as an empty room. Check network reachability and Site health.
The custom integration should be added once per Site, not once per physical node. ESPHome entries remain per physical device and are separate.
If you have the matching local ESPHome YAML and Python environment, run:
esphome logs namo.yaml --device 192.168.1.50Replace the YAML and IP address with your device values. Keep the terminal open before reproducing the problem so the log includes the event itself.
Repeatedly opening log sessions can exhaust the ESPHome API connection limit. Close unused esphome logs processes before opening another session.
No. Sensing, the embedded dashboard, pairing, and coordinate fusion are designed for local-network operation.
No. Never expose a NAMO device directly to the public internet. Do not publish its dashboard or API through router port forwarding, DMZ, a public IP address, a public reverse proxy, or an internet tunnel. Adding an HTTPS certificate alone does not turn the device into a safe internet-facing service. For remote access, keep NAMO on a trusted LAN and connect to that LAN through a VPN.
No for standalone detection. A floorplan is required for room placement, shared coordinates, and multi-device fusion.
One fusion group supports up to seven NAMO devices including the current device. NAMO tracks up to three targets.
No. Restart device and Reset are separate actions. Reset deletes only the categories selected in its confirmation dialog.
Start with correct wiring, power, radar placement, floorplan scale, and calibration. Use correction zones only for repeatable physical behavior, not as the first response to every noisy sample.