Skip to content

Virtual Buttons on customer hubs ​

How household owners configure Alexa home controls — and what operators do not do anymore.

Customer hubs (*.lovely-hub.com) ​

Owners on Lovely Home+ (or Multi Home) set up Virtual Buttons entirely in the hub:

  1. Help → Virtual Buttons and Home Hub controls (alexa-controls in owner help) — UK step-by-step for Alexa routines and linking buttons.
  2. Settings → Controls — add VB01–VB10 rows, labels, optional groups, and the Virtual Buttons access code (stored as a Worker secret, not in the PWA bundle).

The Controls app stays hidden until at least one button is saved. Guest/sitter visibility is controlled from Settings (see owner help — Owner mode vs guests and sitters).

Operators do not edit src/config.js, Wrangler vars, or shared deploy config for customer sites to enable Alexa. Each customer hub reads controls from site profile + secrets after the owner saves Settings → Controls.

Operator / production home hub ​

The platform operator’s own home hub (production home-dashboard Pages deploy) may still ship bundled Virtual Buttons in src/config.js until those buttons are migrated into the site profile. That bundled file is for the operator stack only — it must not leak to customer *.lovely-hub.com deployments (enforced at runtime merge since 3.6.0).

For test/sandbox vanilla hubs, empty bundled config keeps Controls hidden until someone deliberately configures buttons — see cloudflare-test-environment.md.

Support pointers ​

AudienceWhere to send them
OwnerIn-hub Help → Virtual Buttons and Home Hub controls; Settings → Controls
OperatorThis page; cloudflare-worker.md (API and secret rotation); customer hub playbook