How Halo works
Halo is an ambient diabetes safety app. It watches your glucose and triggers smart-device alerts that escalate safely.
The mental model
Halo does the thinking. Smart-home platforms just deliver the commands.
- BG → Safety classification (hard guardrails first)
- Safety → Intent (what devices should do)
- Intent → Providers (Google Home now, more later)
- Providers → Devices (lights/speakers already in your home)
Where automations live
Halo creates and runs the alert behaviour. You don’t create routines in Google Home. Google Home is a bridge that lets Halo control devices you already linked to Google.
Safety guardrails (non-negotiable)
- Severe lows/highs can’t be fully disabled.
- Calm mode is only allowed in the safe in-range band.
- Your custom thresholds apply after Halo’s hard safety floors.
Translation: you can customize, but not in a way that makes the app unsafe.
What Halo can control (today)
- Lights: brightness, color, flashing/pulsing (depends on device support)
- Speakers: volume + spoken alerts (device/platform dependent)
Halo will eventually support more platforms and vendor APIs directly.
Why Halo shows up as a “device” in Google Home
Because that’s how Google Home Cloud-to-Cloud works: third-party services expose a device model so Google can send commands and show state. Halo uses that bridge to reach your real devices. It’s not a physical bulb — it’s the integration surface.