ura-presence-fusion-reference

Presence fusion in Home Assistant combines motion, mmWave, BLE, and camera sensors via trust rules to maintain a raw occupancy substrate for accurate detection. It merges distinct sensor inputs into a unified occupancy layer, applying provenance splits and trust vetoes to ensure reliable state inference.

False away states during system restart occur because occupancy sensors need time to stabilize. Boot-settle gates prevent false away-actuation by holding the presence-fusion stack in a transient state until sensor data normalizes, ensuring no incorrect away states are triggered during initialization.

Fan interference in mmWave occupancy detection is mitigated using specific strategies within the presence-fusion stack. The reference details how to configure sensor trust rules and occupancy substrates to filter out false positives caused by moving air currents.

Yes, troubleshooting Home Assistant presence detection through this reference requires Python programming knowledge and familiarity with URA architecture. It covers custom integration development, state inference engines, and debugging techniques for occupancy substrates and trust vetoes.

House-state presence detection aggregates occupancy across the entire home, while zone-level detection focuses on individual areas. The StateInferenceEngine differentiates these two scopes, processing raw occupancy substrates to output both granular room-level and holistic house-level presence states.

You verify occupancy detection using the live-verification checklist, which provides a step-by-step guide for testing the presence system. It covers validating sensor kinds, checking provenance splits, and ensuring trust vetoes for sleep and away states operate correctly.