-
Notifications
You must be signed in to change notification settings - Fork 1
Status Glossary
The NAMO dashboard reports local sensing, multi-device membership, coordinate fusion, and shared configuration separately. This guide explains the most common states and the action a user should take.
| Display | General meaning | Recommended action |
|---|---|---|
Healthy / healthy
|
Required devices and shared state have converged normally. | Use the system normally. |
Degraded / degraded
|
A device is offline or role handover or synchronization is in progress. | Check local sensing and wait briefly. Check power and Wi-Fi if it persists. |
Unavailable / unavailable
|
Current shared state or authoritative fusion output cannot be trusted. | Do not treat it as an empty room. Check membership and role state. |
Recovering / recovering
|
The last complete state is retained while a new authority or route is prepared. | Avoid shared configuration changes and wait for completion. |
Standalone / standalone
|
The current device is sensing locally without fusion peers. | Normal for a single device; inspect membership if peers are expected. |
The Connected indicator at the top of the dashboard describes only the browser-to-current-device connection. It does not prove that peer devices, the shared floorplan, and fusion are all healthy.
Every NAMO calculates local targets and presence from its primary radar. A powered device continues local sensing where possible even when another device or coordination role is unavailable.
The current Group Leader is receiving observations from active members and producing authoritative fused output. Only devices with a completed floorplan, alignment, and In use membership participate.
This may appear while a member is offline or a new Group Leader, credential set, or observation route converges. Local targets may remain visible, but shared coordinates and automations can be temporarily limited.
No authoritative fused output is currently available. Home Assistant and important automations must not interpret this as no presence.
| Dashboard display | Internal meaning | Participates in fusion |
|---|---|---|
| Connected · setup needed | Secure connection is complete, but floorplan selection, alignment, or activation remains. | No |
| In use | Connection, shared floorplan, alignment, and activation are complete. | Yes |
| No response | The registered device cannot currently be reached. | Its current observations may be excluded |
| Removal needs completion | Only part of the bilateral removal has completed. | No |
| Blocked or revoked | The connection is no longer authorized. | No |
In internal logs or API data, quarantined corresponds to Connected · setup needed, and active corresponds to In use. A normal setup-pending member is not necessarily a security failure.
A value such as 5/5 means currently online devices / configured devices.
-
5/5: all five configured devices are online. -
4/5: four of five configured devices are online. -
1/5: the current device may not be communicating with its peers. -
0/1: this may appear briefly during standalone reconciliation; inspect device state if it persists.
If the denominator is unexpected, check whether recent pairing, removal, floorplan replacement, or reset work has finished.
NAMO separates shared configuration and live fusion so that one device does not need to perform every task. Users normally do not select these roles manually.
The reference device for shared floorplans, membership, and automatic fallback settings. A dashboard opened on another device may direct the user to the configuration source for a shared change.
Maintains the low-frequency Site directory and Group routes. It does not fuse raw radar observations.
Receives high-frequency radar observations from active devices and calculates coordinate fusion and Group state.
With few devices or during a failure, one physical device may temporarily hold more than one role. Roles can spread out again when eligible devices become ready. A role change alone is not an error; inspect the final health and fusion authority.
When automatic fallback is allowed, another eligible device can take over a role whose current device is powered off or unreachable.
- Each role can hand over independently.
-
degradedorrecoveringcan appear briefly during handover. - A former role holder that returns must follow the newer healthy Site state.
- Automatic fallback does not repair unstable Wi-Fi, inadequate power, or an incorrect floorplan.
After enabling or disabling fallback, wait for the state to settle before making more shared configuration changes.
- A device has just booted or restarted after a firmware update.
- Pairing, alignment, or automatic fallback settings just changed.
- One role device was powered off and another device is taking over.
- A former role holder has returned and is following the current Site state.
-
degraded,recovering, orunavailablepersists. - Devices in the same Site report different configuration sources or member counts.
-
configuration_conflict,owner_mismatch, or continuity errors repeat. - An online device repeatedly disconnects or reboots.
- Local sensing is healthy but fusion remains unavailable.
Do not start with a full reset. Follow Troubleshooting and FAQ to collect power, Wi-Fi, role, and membership state first.
- Use
healthyand authoritative active state as the normal condition for important automations. - Treat available results conservatively while health is
degraded. - Never convert
unavailableinto an empty room or cleared presence. - Add a clear-duration delay and manual override to lighting or HVAC shutdowns.
- Use stable Site and Space entities rather than a physical role-device address.