Companion pendant, hardware concept
About the size of a car key fob. Silicone shell, breakaway lanyard, no screen. Charges on a pad overnight next to the phone.
The voice stays with the person, not the phone
The phone runs Omi and holds the schedule. The pendant is a speaker, a microphone and one button over Bluetooth, so the prompt is heard in the bathroom while the phone is on the kitchen counter, and a lost phone does not mean a lost companion.
ListeningSoft teal glow for 8 seconds after Omi speaks. This is the only time the mic is open.
Step open, waitingSteady amber. Mic closed. Omi will repeat on the caregiver's cadence, never louder.
ClearedGreen pulse and a short chime after a press or an addressed reply. Then it goes quiet.
IdleNo light between routines. Nothing is recorded or listened to.
The one button
Single press: done, clears the current step.
Long press: I need more time, pauses reminders for 5 minutes.
Double press: say it again, Omi repeats the prompt once.
What is inside
Small speaker tuned for voice, not alarms. Volume is set by the caregiver and fixed.
Single mic with wake-window gating. Audio is processed on the phone and not stored.
Bluetooth LE to the phone. Out of range: the pendant plays the last prompt and buffers the press.
What the firmware talks toThe pendant is a client of the same API as everything else. Its whole protocol is three calls with a device token it receives during pairing.
POST /api/v1/devices?action=button {"press": "single" | "long" | "double"}
POST /api/v1/devices?action=heartbeat {"battery_pct": 82}
GET /api/v1/devices?me=1 -> device + current run (omi_line to speak, listening)