Hardware partners
We integrate with the devices you already have.
Halo is deliberately device-agnostic. Care providers already have a mix of contactless sensors, wearables, environmental sensors and legacy monitoring kit. Rip-and-replace is a non-starter. We connect to what’s there — via HTTP, MQTT, or webhook — and unify the data behind one clinical view.
Why we don’t lock you to one manufacturer
Most connected-care platforms will only work with the hardware they sell. That means: your homes end up with fragmented estates, contracts you can’t get out of, devices you can’t reuse, and pricing that’s opaque.
Halo’s data model treats devices as pluggable. A device type is defined by its capabilities (pulse, respiration, presence, fall, sound, environmental, etc.), not its manufacturer. Add a new manufacturer, register a new device type with its capability set, and every downstream rule — alerts, baselines, audit — just works.
- Your care home stays the buyer of the hardware, not us. We take no margin on device sales.
- Multi-org support: two organisations sharing a Halo instance can each supply their own credentials for the same device type. Tokens are per-device, not per-manufacturer.
- MQTT, HTTP polling, or inbound webhook — pick what your device supports.
- Adding a new device type is a data change, not a code change.
Featured partners
Two contactless-monitoring partners we deploy most often. Both work under UK GDPR with data processed in the UK.
Vayyar Home — contactless radar
ContactlessFallRadar
Vayyar Home is a wall-mounted 4D radar unit that maps a whole room — no cameras, no wearables required. Detects falls, tracks presence, and provides a respiration proxy — all through the wall, no line-of-sight needed. Ideal for bathrooms and bedrooms where cameras aren’t appropriate.
Why we chose it
- Radar-based — works in the dark, through steam, and doesn’t record images. Massive privacy win over camera-based systems.
- Whole-room coverage — one unit covers a typical bedroom or bathroom.
- Fall detection genuinely low-false-positive vs pendant-based systems.
- Clean MQTT feed — Halo’s MQTT connector reads presence, motion, fall events, and respiration proxy natively.
Nobi — smart lamp with fall detection
Ceiling lampFall AIPresence
Nobi is a ceiling-mounted smart lamp with built-in AI-driven fall detection, presence detection, and ambient lighting. Guides residents at night, detects falls in real-time, and alerts before the resident even calls for help. Deployed successfully in supported-living and dementia settings across Europe.
Why we chose it
- Combines fall detection with ambient function — residents accept it as a lamp, not a monitor.
- AI-based detection, retrained specifically for older-adult movement patterns.
- On-device processing — no images ever leave the unit. Only detected events reach Halo.
- Reliable HTTPS webhook feed with HMAC signatures — Halo verifies every incoming event.
Every integration available today
| Manufacturer / device | Category | Transport | Capabilities |
|---|---|---|---|
| Vayyar Home | Contactless room sensor | MQTT | Presence, fall, respiration proxy |
| Nobi | Smart ceiling lamp | Webhook (HMAC) | Fall AI, presence, ambient |
| Fitbit Charge 6 | Wrist wearable | HTTP (OAuth2) | HR, HRV, sleep, steps |
| Apple Watch (via HealthKit) | Wrist wearable | HTTP (OAuth2) | HR, ECG, fall, sleep, steps |
| Withings ScanWatch | Wrist wearable | HTTP (OAuth2) | HR, SpO2, sleep, AFib screening |
| Withings BPM Core | Bedside BP + ECG | HTTP (OAuth2) | BP, ECG, HR |
| EMFIT QS | Under-mattress sensor | HTTP polling | HR, HRV, respiration, sleep stages, bed-in/out |
| Aqara sensors | Environmental | MQTT | Temperature, humidity, motion, door/window |
| Shelly Plug S | Smart plug | MQTT | Kettle-use proxy for morning routine |
| Netatmo Weather Station | Environmental | HTTP (OAuth2) | Indoor / outdoor temp, humidity, CO2, VOC |
| Careium (SureSafe) pendant | Fall / SOS | HTTP polling | Fall event, SOS, low battery |
| Dexcom G7 | Continuous glucose | HTTP (OAuth2) | Interstitial glucose, trend arrow, hypo alert |
| Freestyle Libre 3 | Continuous glucose | HTTP (OAuth2, LibreView) | Interstitial glucose, trend |
How the three transport types work
HTTP polling
Halo’s connector calls the manufacturer’s API on a schedule (typically every 30–120 seconds for vitals, every 5 minutes for slower-changing data). OAuth2 or API token per device. Suits cloud-first wearables (Fitbit, Withings, Apple Watch).
MQTT subscription
Halo subscribes to a topic per device type. The device (or its bridge) publishes events to the topic. Push-based, low-latency, ideal for room sensors and environmental data. TLS-encrypted, per-device username/password.
Webhook receipt
The device (or its cloud) posts events to a Halo endpoint. Every webhook is HMAC-verified with a per-device secret. Failed verification is logged, response is 401, no data written. Ideal for event-driven devices like Nobi.
Adding a new device type
Adding a new device isn’t a code change — it’s a config change.
- 1. Register the manufacturer — name, contact, support URL, connector code (if any).
- 2. Register the device type — pick its capabilities (pulse, respiration, presence, fall, sound, environmental, glucose, etc.), pick its transport (HTTP / MQTT / webhook).
- 3. Per-device credential — issue an API token, MQTT credentials, or HMAC secret to each physical device. Multi-org providers can supply their own tokens.
- 4. Pair the device — either from the Halo web console (pairing code + QR), or by the manufacturer’s cloud calling our pairing API.
- 5. Verify — the device shows up under its assigned resident within seconds. Events flow immediately.