Every widget there is
The 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.
Most widgets are on every plan. Webhook needs Pro. Every Home Assistant widget and the Spotify widget need Home or above. The menu board carries no plan gate of its own — but it needs a menu, and Menus are part of the business plans.
What a widget is
A widget is one thing on a screen — the clock, the agenda, a light switch, a photograph. A scene is an arrangement of them on a twelve-column grid, eight rows tall in landscape and eighteen in portrait, and a screen shows one scene at a time.
Widgets are curated and ship with Mirra. There is no widget store and no way to install somebody else's code, which is a deliberate limit rather than a gap: a third-party widget would be untrusted JavaScript running on a panel that can see your calendar, your cameras and your home. The trade is that the list below is the list, and it grows when we add to it.
There are forty-one widget types. Sixteen of them stand behind no integration at all.
Widgets may overlap. That is what makes a photograph behind a clock possible, and it is why the grid does not push things out of the way when you drag one on top of another.
Adding one to a scene
Every widget is placed the same way, from the screen it is going on.
Open Screens and choose the screen
The scene editor is per-screen. The canvas is drawn in the shape the scene was made in, so a portrait scene stays portrait even when you are looking at it from a landscape screen.
Pick the scene you are editing
A screen can hold several scenes and swap between them on a schedule. Widgets belong to a scene, not to the screen.
Find the widget under Add widget
The palette is grouped by category. Core widgets appear by name — "+ Clock", "+ Photo frame". An integration's widgets are collapsed behind one tile, so Home Assistant's fourteen arrive as a single "+ Home Assistant…" that opens a picker.
Click it to select it, and set it up
The panel underneath is headed with the widget's name — "Photo frame settings", "Dial settings" — and holds three things: Appearance, When to show, and the widget's own fields.
Press Save & push
Nothing reaches the wall until you do. The button is disabled when there is nothing to save, and the header says "Unsaved changes" until then.
An integration that is turned off has no tile in the palette at all. If you have connected Home Assistant and cannot find its widgets, the palette says so at the bottom and links to Integrations.
What decides whether you can place it
Four separate things gate a widget, and they are separate on purpose — a widget you have turned off is not the same as one your plan does not include, and neither is the same as one that has nothing to show yet.
The Integrations page and the scene editor's palette both work from the same answer, so they cannot disagree with each other about whether your photo frame is ready.
- Your plan. Webhook needs Pro. Every Home Assistant widget and the Spotify widget need Home. Everything else is on every plan.
- The integration being on. Turn Home Assistant off and its fourteen widgets leave the palette. Core widgets are never gated this way — a household one setting away from having no clock is not a household anybody should be able to create by tidying a page.
- Something to show. The photo frame needs an album, the agenda a connected calendar, the art frame a collection, the light widgets a light. The catalogue says which is missing rather than leaving you to work it out from a blank rectangle on a wall.
- Your kind of account. The menu board widget itself carries no plan gate, but the menus it draws on are part of the business plans, because a household has no use for one.
Time
Three widgets, none of which needs anything connected. The size after each name is the size it arrives at, in grid cells — you can resize any of them afterwards.
The clock and the date are bare by default, with no card behind them, because they are usually the first thing laid over a photograph.
Calendar
Four widgets, all reading the same merged set of events. They need the Calendar integration on and at least one calendar connected — an iCal link, CalDAV, Google or Outlook.
Each of them carries the same Calendar field, which chooses between all your calendars, one named calendar, or this screen's own room. That last option is what lets one scene serve forty identical door panels outside forty different meeting rooms.
Photos, art and music
The portal calls this group "Photos & art". Two of the three are core; the third needs Spotify.
Art and the photo frame look similar and are pointed at different things. The photo frame shows an album you uploaded. The art frame shows a collection — one you assembled, or one we curate, which is why it is ready to use before you have uploaded anything.
The building
One widget, and nothing has to be connected for it — the plans are your own drawings and the screens on them are your own fleet. In the palette it sits under Smart home.
The setting that matters is Plan, whose default is "the plan this screen is on". A screen works that out for itself, so one scene holding one Floor plan tile can go to every panel in a building and each will draw its own storey with itself ringed. A screen that has not been placed on any plan says so on the tile rather than drawing a floor it is not on.
Three more widgets draw on Twinview — Board numbers, Board list and Board breakdown — and they are covered in the Twinview article rather than here, because what they show depends entirely on how your project is set up.
Information and household
Everything here is core — no integration stands behind any of it — though several read something from outside. Weather reads Open-Meteo, News reads whatever feed you point it at, and Webhook shows whatever another service sends it.
Lights, whichever system they are on
Two of these are core rather than filed under an integration, and that is deliberate. A light is not an integration — it is a thing on a wall, and there are four ways of getting one into Mirra: Home Assistant, WLED, Govee and Hue. Filing the only widgets that can set a colour under any one of them would mean the households on the other three could not reach them.
The three WLED widgets are the opposite case: they hold things the general vocabulary cannot express — a controller's own saved presets, its effect and palette catalogues, and a strip that has a physical shape. WLED carries no plan gate, because a strip behind a television should not cost more than a strip.
Home Assistant
Thirteen widgets, all needing Home Assistant connected and the Home plan. In the palette they sit behind one tile, and the picker offers them under four headings grouped by what you are trying to do rather than by how they are built — "I want to see a number" and "I want to press something" is how people arrive at this.
The Thermostat used to be the fourteenth and is now core, listed under Information and household above, because Hive households have thermostats too and filing it here put it out of their reach.
Every entity picker filters to what the widget can actually use, and every one of them keeps a way to see the full list. Home Assistant lets people put anything in any domain, and a filter that is too clever locks somebody out of their own setup.
What the catalogue will not do
It will not run code we did not write. There is no way to add a widget type yourself, no embedded web page widget, and no scripting surface on a screen. If a widget you want is not here, it is not here yet.
It also will not hide a widget that your household pays for and has merely turned off. Those two states read differently everywhere — the palette drops a turned-off integration entirely and tells you where the switch is, while a widget your plan does not include stays visible with an upgrade note on it. A feature nobody can see is a feature nobody upgrades for.
Turning an integration off never takes anything off a wall. While its widgets are sitting on a scene, the Integrations page names the scene and the switch stays put.
Related
- The photo frameHow to build an album, point a screen's photo frame at it, control how photos are cropped and dimmed, and turn one into a full-bleed background for the rest of a scene.
- The agenda widgetWhat the agenda draws from, how far ahead it looks, how it picks between your calendars and a meeting room's, and why an empty agenda is not the same as a broken one.
- The tasks widgetOne household task list, kept in the portal or by talking to the assistant, shown on any screen with the tasks widget.
- 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.
- Integrations: what they are, and turning them onAn 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.
- 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.