Testing
Manual triggers, webhook tests, and adapter diagnostics.Not signed in
Selected devices
Pulled from Settings → Devices. This auto-loads when you open Testing.
Lighting: 0
Audio: 0
No devices selected yet. Go to Settings → Devices and pick at least one.
Engine → adapter (end-to-end)
Runs the real engine intent and dispatches adapter actions to your selected devices (web dev uses the Noop controller).
Uses the same Mode + night gating inputs above, and the selected devices shown at the top of this page.
Optional BG override
Leave blank to let Halo use the current simulated/real data path. If provided, we’ll include it in the test payload.
Mode + night gating (testing)
Simulation-only inputs. They do not affect the dashboard CGM feed. Use them to test night gating rules and “out of range for N minutes” behavior.
Out of range
min
Delay
min
Sleep window
to
Tip: set Night mode + out of range ≥ delay to allow the wake sequence. If it still doesn’t fire, check the intent’s
night.reason in Recent results.Manual Halo triggers (simulation preview)
Simulation preview only. We ask the server what Halo would do and show the resulting dispatch payload below. This does not change the dashboard CGM state.
Webhook URLs (testing)
Paste public HTTPS endpoints here (Webhook.site is fine). These are saved to your account and used by the “Webhook” test buttons.
Low webhook
High webhook
Day/Night webhook
Device controller (adapter)
Tests the platform-agnostic device controller interface. In web-only dev this uses the Noop controller.
When we move to iOS (Capacitor), this same test will hit the real Google Home APIs implementation.
Recent results
Newest first. This is local-only and clears on refresh.
No tests run yet.
If a test fails: check Vercel logs first. If Halo dispatch fails: it’s usually an env var or a Supabase permission/schema mismatch.