Room and floor presence with mmWave nodes
See which rooms and floors are occupied using configurable radar nodes, with presence and device health kept distinct.
HOMESENSE / CONNECTED HOME MONITORING
See your home as one connected system.
Bring room presence, security modes, cameras, weather, and home energy into a calm dashboard built around your installation.
Private application. Demonstrations by arrangement.
Built around your workflow
Configurable connected homesRoom presence and camera contextSolar and backup monitoring
Inside HomeSense
Start with presence. Add context as you need it.
Home, Night and Away modes with schedules
Choose which areas are watched in each mode and keep automatic schedules in the same configuration.
Deliberate siren approval and Telegram controls
Keep urgent controls visible, with outdoor alarm escalation requiring a person's approval.
Optional cameras and doorbell/event evidence
Open a linked camera when context matters, review captured event evidence, and keep camera viewing separate from presence sensing.
Weather context and read-only home energy
Keep outside conditions, solar flow, battery state, and backup context beside the home overview when those integrations are enabled.
Browser setup and recoverable modular configuration
Configure supported nodes from the browser, enable only the modules you need, and keep installation choices recoverable across upgrades.
Native Android TV companion
Bring the home overview and live camera viewer to a TV using the same configured server.
Inside the system
Fresh observations become useful home context.
HomeSense / system flow01 → 06
- 01
Sense
LD2420 presence + range over UART
- 02
Publish
ESP node sends fresh MQTT observations
- 03
Validate
Boot, sequence, source samples and age
- 04
Interpret
Occupancy hold + separate health state
- 05
Decide
Profiles, confirmation and approval gate
- 06
Context
Dashboard, evidence and read-only energy
01 / MECHANISM
Start with evidence from the physical sensor
Supported firmware parses LD2420 UART presence and range lines. Non-retained MQTT snapshots carry boot identity, sequence, actual source-sample count and source age, so a repeated transport message does not become a new physical observation.
02 / MECHANISM
Keep occupancy, health and alarm evidence separate
The ingest path distinguishes fresh readings, retained state and connection uncertainty. Server occupancy holds smooth the room view, while configurable confirmation examines coherent movement or sustained fresh presence. Sensor health remains visible independently.
03 / MECHANISM
An explicit gate before outdoor escalation
Indoor warning and outdoor approval use distinct state. A persisted nonce and current-mode checks fence decisions; late approval needs additional confirmation. The dashboard and supported Telegram controls answer the same request, with no automatic timeout approval.
04 / MECHANISM
Link context without inventing history
Camera jobs retain event and actual capture times, deduplicate work and bound retained media. Optional energy and weather modules add timestamped context. Energy integration monitors readings; it does not issue inverter control commands.
Implementation parameters · not benchmarks
- Radar UART
- 115200 baud
- protocol setting
- Radar hold
- 2 seconds
- firmware setting
- Active snapshot
- ~1 second
- publish interval
Source timing parameters describe the sensor pipeline. Occupancy and confirmation settings remain installation-specific; they are not detection-accuracy or alert-latency benchmarks. Optional external integrations require connectivity.
Read the full engineering storyHow it works
A clear path from
setup to useful work.
- 01Configure supported sensor nodes
- 02Map rooms and enable modules
- 03Follow presence and inspect context
A closer look
One home. More than one way to see it.
Room state, optional floor views and linked cameras share the same installation context. A native Android TV companion brings the overview to a larger screen.
/ workflow
Presence → Context → Deliberate action
Conceptual workflow · configured for your environment
Practical questions
Know what
fits your setup.
Is presence the same as identifying a person?
No. Configurable mmWave nodes report room presence, separately from device health. Calibration and hold settings matter; this does not establish identity or guarantee zero missed or false alarms.
Will an outdoor siren start automatically?
Outdoor escalation requires explicit human approval. Home, Night and Away profiles and schedules determine monitoring context. HomeSense is a configurable monitoring application, not a certified professionally monitored safety system.
Does local-first mean entirely offline?
Core installation workflows are local-first. Optional weather, Telegram and energy integrations can depend on external services. Energy integration is monitoring-only and does not control the inverter.
What does setup require?
Supported sensor hardware, reachable services and installation-specific configuration. A configuration export excludes credentials, accounts and history; it is not a full private-data backup. Contact us to discuss a demonstration.
Make it work for you