Integrations: what they are, and turning them on
An integration is an outside source that several widgets draw on — this explains what turning one on and off does, and why Mirra refuses to turn one off while its widgets are still on a scene.
Turning an integration on is never refused because of your plan. The plan sits on the widgets: Home Assistant's and Spotify's widgets need the Home plan, and the Webhook widget needs Pro. Calendar and WLED widgets are on every plan.
What counts as an integration
An integration is a source outside Mirra that several widgets draw on. Both halves of that sentence do work. "Outside Mirra" leaves out photo albums, menus and art collections, which are your own content however much setting up they take. "Several widgets" leaves out the weather widget's forecast, which nothing else reads and nobody connects.
What survives is a short list of things a household hooks up once and then several widgets live off. There are seven.
Everything else is core, and core is not a lesser tier — it is the clock. Core widgets stand behind no integration, have no switch, and cannot be turned off. A household should never be one setting away from having no clock.
- Calendar — events from your calendars, as a list, a week or a whole month. Four widgets.
- Home Assistant — anything from your smart home: readings, controls, cameras and summaries. Fourteen widgets, which is why filtering the palette is worth doing at all.
- WLED — addressable light strips: colour, brightness, effects and your own saved presets. Three widgets.
- Spotify — what's playing on the wall, and music the assistant can start for you. One widget.
- Govee — Govee's own bulbs, strips and light bars, over Govee's cloud. It brings no widgets of its own: your Govee lights turn up in the same light tiles Home Assistant and WLED use.
- Philips Hue — Hue bulbs straight from the bridge on your shelf, with no Hue account. Also brings no widgets of its own. Needs a screen switched on and on the same network as the bridge, because nothing else in the product can reach one.
- Hive — British Gas heating and hot water. Also brings no widgets of its own; a Hive thermostat appears in the Thermostat and State tiles.
- Twinview — a building's own tickets, issues and maintenance jobs. Three widgets: Board numbers, Board list and Board breakdown.
The Integrations page
Integrations lives at /integrations and answers two questions at once, because people arrive with both: what can a screen show, and what has this household turned on.
The switchable half is a card per integration. Below the cards is "Always available" — the core widgets, listed plainly with no toggle and no state, so they can be found rather than managed. Two further links hang off the section rather than off either card: Light rules, for making lights react to a time, to somebody arriving, to the assistant or to an emergency; and Camera alerts, for showing a doorbell or a movement on the mirrors you choose.
A search box sits above the cards. It matches the widgets an integration brings as well as its name, because somebody arrives wanting a thermostat rather than wanting Hive — typing "thermostat" surfaces both cards that can give them one. Each card also says who made the integration and which version you have, and links to its own instructions in this help centre.
An account restricted to menus cannot open this page. It is redirected to Menus rather than shown a refusal — the list of pages a menu-only account may open names Menus, the account page, help and support, and nothing else, and anything not on it goes back to the one page that account is for.
Turning one on
A new household starts with Calendar on and the other three off. That is given once, at registration, and remembered: if you turn everything off, nothing switches back on behind your back the next time the page loads.
Open Integrations
From the portal navigation, or go to /integrations.
Find the card and press Turn on
The pill on the card changes from Off to On.
Look in the scene editor
That integration's widgets are now in the palette. Nothing else about them changes — the way they render and the way a screen fetches them are the same as they ever were. Enablement is a filter on what is offered.
Connect something to it
An integration that is on but has nothing behind it shows empty widgets. The card says which of the two is missing and links straight to the setup page: "Nothing connected yet. Set up Home Assistant."
Both turning on and turning off are recorded in the audit log, with who did it.
What the card says about what is connected
Once something is connected the card counts it and reports its health, with the worst status winning. A household with one healthy calendar and one whose token expired has a problem, and a card reading "connected" because the first row happened to be fine is a card that hides it.
- "connected" — nothing has reported a fault.
- "needs signing in again" — a stored credential was refused and has to be renewed.
- "can't be reached" — the thing itself did not answer.
- "Manage" takes you to the same page as "Set up" — the one place that integration's credentials live.
Not every connector reports its own health. Spotify, WLED and meeting rooms write a status here when something has gone wrong. The four ordinary calendar sources — iCal, CalDAV, Google and Outlook — do not, so a Google sign-in that has been revoked still reads as connected on this page. The wall is where you would notice: the widget says "Calendar unavailable".
Turning one off, and why it may be refused
Turning an integration off is refused rather than destructive. A household whose kitchen scene has three Home Assistant tiles on it cannot turn Home Assistant off — the refusal names the scenes to clear first. The alternative is a wall that silently loses widgets because somebody tidied a settings page, and no amount of confirmation copy makes that an acceptable outcome.
The refusal is worked out before the click, so the button is already disabled with the reason beside it. A button that is enabled, pressed, and then refuses has made you ask a question the page could already answer. The same check runs again on the server at the moment of the write, because somebody else in the household may have dropped a thermostat onto the hall screen since your page loaded.
Press Turn off on the card
If nothing of that integration's is placed anywhere, it goes off and its widgets leave the palette.
If the button is greyed out, read the sentence beside it
It reads like this: "Home Assistant widgets are still on “Kitchen” and “Hall”. Remove them from those scenes first — turning Home Assistant off will never take anything off a wall for you."
Open each named scene and remove those widgets
A scene counts once however many of that integration's widgets it holds — a scene with four thermostats is one scene to clear. Scenes that sit in the library on no screen still count, because they are still somewhere the widget would have to be removed from.
Come back and press Turn off
With nothing placed, the switch frees up.
Turning an integration off leaves its connections alone. Your Home Assistant token and your calendars are still there, and turning it back on returns everything to where it was.
Why a widget disappears when an integration is off
An integration's widgets appear in the scene editor's palette once it is on, and nowhere until then. Home Assistant alone is fourteen of the widgets in the product, and for a household that will never own a smart plug that is fourteen tiles in the way of the clock.
The rule is enforced on the way in as well as in the palette. Saving a scene that holds a widget of an integration you have turned off is refused, with a message you can act on: "Home Assistant isn't turned on for this household, so its widgets can't be placed. Turn it on under Integrations first." A rule enforced only in the interface is not a rule the API has.
There are two exceptions, and both are layouts Mirra supplies rather than ones you drew. The starter layout a newly paired screen is given, and the copy made when you duplicate a scene, have blocked widgets removed instead of being refused. The starter layout ships with an agenda on it, and refusing to pair a screen over a widget nobody asked for would be the worse outcome. Nothing you made is ever trimmed this way.
Plans
Where an integration's widgets need a particular plan, the card carries a small plan pill. Home Assistant and Spotify carry Home. Calendar and WLED carry nothing — a light strip behind a television is not the enthusiast's setup, and gating it would gate the art matching that is the reason to want it.
The gate is on the widget rather than on the switch, so turning an integration on is never refused because of your plan. A widget your plan does not include is marked in the catalogue, with a link to Billing instead of a setup link. Plans and integrations are separate questions on purpose: a widget you pay for but have turned off is not unavailable, it is off, and the card above says so.
Always available
Below the cards is a single panel listing the widgets that stand behind no integration — the clock, the weather, photos, art, tasks and the rest. They are a list rather than cards because a card is a thing you press, and one with nothing to press would teach people that the clock is optional.
Some of them still need something from you, and each says so in its own line. "Needs: …" explains what a widget draws on; a "Set up" link appears where content is missing, such as a photo widget with no album behind it; and "Manage" appears once it is ready. One of them, Webhook, needs the Pro plan, which is why a section headed "Always available" admits the plan caveat before the rows do.
What Mirra deliberately does not do here
Widgets are curated and ship with the app. Mirra does not run third-party widget code on your screens — that would mean untrusted JavaScript with a view of your calendar and your home, on a display you cannot easily inspect.
So this page is a catalogue with plan gating and household switches, not an app store. Adding a new integration is our job, not a download.
Related
- Connecting calendarsEvery calendar source Mirra can read — an iCal link, a CalDAV account, Google, Microsoft 365 — with the steps for each, what actually syncs, and what quietly breaks it.
- Home AssistantHow Mirra reaches Home Assistant through a screen on your own network, what it syncs, what it notices, and what each failure message means.
- Lights, light rules and WLEDOne light model across Home Assistant bulbs, WLED strips, Govee lamps and Hue bulbs: adding a controller, what a rule can do, how a segment becomes a light, and which of the four leave your network at all.
- SpotifyConnect a Spotify account so a mirror can show what is playing, skip a track with a wave, and start music when you ask for it out loud.
- Every widget there isThe complete list of widgets Mirra ships with, grouped the way the scene editor groups them, with what each one shows and what it needs before it will show anything.
- The scene editorThe scene editor is where you arrange a screen's widgets on a twelve-column grid, watch the real widgets render behind them, and push the result to the wall.
- Plans and allowancesWhat each Mirra plan includes — screens, household members and assistant credits — how credits are metered, and what happens when you reach a limit.
- BillingHow to subscribe, change plan, find your invoices and cancel — and what Mirra does on an install where payments were never configured.