A Sensor Reading key can open a full page of related readings: press the CPU temperature key and the deck switches to a detail view listing every reading of that CPU sensor, with the key you pressed staying live as the Back tile. This is the drill-down asked for in issue #5.

What it is (and is not)

The detail view is a plugin-managed profile, not a native Stream Deck folder. The Stream Deck SDK does not let a plugin place keys inside a user’s folders or profiles, so the plugin ships one editable, one-page profile per supported deck type (“HWiNFO Details” in the app’s profile list) and switches to it on demand. Pressing Back asks the Stream Deck app to return to the profile you came from.

Practical consequences:

• The first time you open details on a deck, the Stream Deck app asks to install that deck’s detail profile. Accept once; later entries switch silently.
• The page is a normal, editable profile, but it ships with every cell already filled: reading tiles, the Back tile, the title and the pagers. Adding a key of your own means replacing one of those, not filling a gap. The plugin never repairs or overwrites what you change. The shipped page holds no data of yours: every tile asks the plugin what to show at runtime.
• What you change on that page is shared. There is one detail page per deck type, so a key you add, or a tile you replace, appears on every drill-down you open on that deck no matter which key you pressed. What still follows the key you pressed is the live content: the reading tiles, the title, the pager range and, until you pick a sensor for it, the Back tile’s face.
• To get the shipped page back, delete the profile under Preferences, Profiles in the Stream Deck app, then open a drill-down again and accept the install. There is no reset inside the plugin, because a plugin cannot edit or repair a profile you already have installed.
• If what you want is a page you lay out yourself, with your own multi-reading keys on it, make a Stream Deck folder instead: right-click a key in the Stream Deck app and choose Create Folder. That is the app’s own feature, not this plugin’s, and unlike the detail page it belongs to that one key. The trade is that a folder’s opener key shows a static icon, while a drill-down key shows a live reading.
• The Stream Deck app never updates a profile that is already installed. When a plugin update changes the page itself, it ships as a new profile revision under a new internal identity, the next drill-down asks once to install it, and the previously installed copy stays untouched in your profile list. Upgrading from a preview works that way, but the release name is “HWiNFO Details” again: remove the preview’s detail profiles first, or the new one installs alongside them as “HWiNFO Details copy”.
• Back returns you to the profile you came from. After a full Stream Deck app restart the app’s own notion of “previous profile” resets, so where Back lands then (or whether it moves at all) is the app’s restore behavior, not stored state in this plugin; if it does nothing, switch profiles from the Stream Deck app once and re-enter.

Turning it on

In the key’s settings panel, under Press:

• Press does picks the behavior. The default stays exactly as before: cycle current / min / max / avg. Open sensor details switches to the detail view on press. Tap cycles; hold opens details keeps the cycle on a short tap and opens details after holding half a second.
• Detail contains picks the list. All readings from this sensor source (the default) lists every other reading HWiNFO currently publishes for the pressed sensor’s source, in HWiNFO’s order; the pressed reading itself rides on the Back tile and is not repeated in the list or the title’s count. Custom sensor list lists exactly the readings you add, in the order you set (the opener’s own sensor stays on the Back tile). Readings matching a filter lists everything whose source name and label, taken together, match a glob pattern, deck-wide and live: *4090* gathers every reading of an RTX 4090, *gpu*fan* just its fans, and the list re-resolves each poll so readings that appear or vanish in HWiNFO follow along. The pattern doubles as the title unless you set one, the panel shows a live match count under the field, and the grammar gets its own section below.
• Tile shows packs two, three or four readings onto each tile of the view, using the same stacked, row and quad faces regular keys have. One reading per tile stays the default and keeps the page exactly as it was. A dense tile shows one shared stat badge, a press cycles all of its readings together, and a page’s last tile simply carries however many readings remain. In the four-per-tile grid each cell wears a short label built from its reading’s name with the words all four share dropped, so four GPU readings read MEMO, HOT, THER and CORE instead of GPU four times over, and Core 0 to Core 3 VID read 0, 1, 2, 3.
• A Custom sensor list can group its tiles one by one. Each entry in the list grows a small tile control: click the size to cycle a tile through one, two, three or four readings, give any cell its own label, and give a quad tile’s cells their own colors or switch it to bare color-coded values, the same knobs a regular key of that size has. Mixed sizes sit together on one page, readings past your groups keep flowing at the Tile shows setting, and the grouping is positional: readings flow through the tile pattern in list order. The arrows, and a drag within one tile, reorder the readings through a pattern that stays put. Dragging a chip onto a different tile moves the reading there instead, so the tile it left loses a cell and the tile it landed on gains one. Wherever on a tile you let go, the chip lands where the blue caret sits, at the cell edge nearest your pointer; a tile already holding four readings cannot take a fifth, so the caret moves to that tile’s own edge and the chip parks beside it as a tile of its own. A reading’s dressing travels with it every one of those ways. That covers the colors a four-cell tile hands out by default as well as the ones you pick yourself, so moving a reading never repaints the ones it moves past. Two readings can end up the same color that way, since each keeps what it already wore; click either cell’s color well to tell them apart again. Removing a reading shrinks the tile that held it instead of pulling the next reading up into it, whether you grouped that tile by hand or the Tile shows fill built it, so the tiles below keep their readings and the freed cell refills from the tile’s plus; a fill tile shrunk this way joins your groups at its new size, the same freeze touching its size control applies. Source and filter lists re-resolve live against HWiNFO and cannot pin tiles positionally, so grouping is a custom-list feature by design.
• Detail title names the view’s title tile in any mode, replacing the default (the source name, the filter pattern, or Custom set).
• Repeat Back under this key’s own cell adds the optional second Back tile described below; leave it off and the movable top-left Back is the one way out.

Existing keys are untouched: a key without a Press setting behaves exactly as it always has.

The detail page

Every detail page has the same furniture:

• Back (always top left, where the native folder back key lives): a real Sensor Reading key whose press is fixed to leaving the view; a small return arrow in the tile’s lower-left corner marks it. Fresh from install it shows the sensor you drilled down from, live, with that key’s theme, text, units, decimals and thresholds. It stays pressable when HWiNFO is down, when the sensor is missing, and even right after a plugin restart.
• A second Back under your finger, if you ask for it. Tick Repeat Back under this key’s own cell on the opener and, when that key’s cell maps onto a reading cell of the page, the cell becomes a second Back tile showing the same opener face with the return arrow: tap in, tap out, without moving your hand. The readings flow around it (none are hidden). Off by default (issue #5 testing settled on one movable Back over two fixed ones), and the top-left Back always works regardless.
• Title (all decks except the Mini): the source or custom title over the visible range, like CPU Enhanced over 1-11 / 46.
• Previous / Next: page through long lists. The chevron dims at either end. Paging happens inside the one profile page; nothing stacks.
• Reading tiles: live readings, themed like the opener. At the default one reading per tile, each tile carries the type accent of its own reading; a denser tile (Tile shows) carries its first reading’s accent, the same rule the regular stacked, row and quad layouts follow for their first sensor. Pressing a tile cycles current / min / max / avg for everything on it, for this visit; leaving the view resets those. Reading tiles deliberately do not inherit the opener’s thresholds: an 80 °C warn level means nothing on a wattage or clock tile. The Back tile keeps its own.
• No sparklines on reading tiles, by design. A sparkline needs a history buffer that fills over a minute or more, and a detail page shows dozens of arbitrary readings (up to 128 on a + XL at four per tile) that change with every page turn and every filter, so the lines would draw mostly empty while costing buffer churn on every visit. The tiles stay instant and scannable; your opener key keeps its own sparkline back on your page.

If HWiNFO stops publishing while the view is open, the tiles show the same status screens as ordinary keys and recover on their own; Back keeps working throughout. If a listed reading disappears (custom mode), its tile shows Sensor missing in place, and the others do not shift.

Configuring the Back tile

The Back tile is an ordinary Sensor Reading key with one fixed job. Select it in the Stream Deck app and its settings panel opens with everything a normal key has: the sensor picker, label, Show stat, decimals, units, theme, custom text, warn and critical thresholds, the Display strip, and the single, dual, triple and quad layouts. Two things differ, both stated in the panel:

• Pressing it always returns to the previous profile. There is no Press section on this tile, and the return arrow stays visible on every layout (it sits in a small gap on the divider in the dual, triple and quad layouts).
• Until you pick a sensor, the tile shows the sensor you drilled down from, so a fresh page needs no setup. Once you pick one, the tile shows your pick, and a missing pick shows Sensor missing like any key would.

Copying the Back tile elsewhere copies the fixed role with it: a pasted copy still returns to the previous profile when pressed. For an ordinary key, add a fresh Sensor Reading from the actions list instead.

Filter patterns

The filter is a glob, not a regex: * spans anything, ? matches exactly one character, everything else is literal, and case never matters. Every reading is tested against one string: the source name, a single space, then the label. For the 4090’s first fan that text is dGPU [#0]: NVIDIA GeForce RTX 4090 GPU Fan1 (the middle of the source name is shortened here), which is why one pattern can select by card, by quantity, or across every source at once, and why anchored patterns must account for the source name at the front. Three rules cover all of it:

1. Plain text matches anywhere. A pattern with no wildcard behaves as if wrapped in *...*, so 4090 and *4090* are the same filter.
2. One wildcard anchors the whole pattern. The moment a pattern contains * or ?, the automatic wrapping is off and the pattern must cover the entire combined text. core*clock matches nothing, because the text starts with the source name, not with “core”; *core*clock* is the form you want.
3. Spaces are literal. Multi-word plain text works only when the words sit adjacent in the name: gpu fan finds the GPU fans, but core clock finds nothing because the cores are named Core 0 Clock. Span the gap with a star: *core*clock*.

Patterns I run on my own bench (512 readings across 21 sources), with their live match counts:

Pattern	Matches	What it gathers
4090	79	the whole RTX 4090, selected by its source name
gpu fan	4	the card’s fan readings (adjacent words, no wildcard needed)
*core*clock*	48	every per-core clock on the CPU
*hot*spot*	2	the CPU IOD hotspot and the GPU hot spot, across sources
tdie	3	the Tdie temperatures, case-insensitive
*12v*	8	every 12 V rail on the board and the PSU
*temperature*	18	everything HWiNFO literally labels a temperature
?PU*	270	sources whose name starts with any one character plus “PU” (anchored start)
*	everything	the full deck-wide firehose, paginated

Two edges worth knowing: an empty pattern refuses entry with the alert cue (there is nothing to list), and a pattern that matches nothing opens an honest empty view reading 0 / 0. Two more: leading and trailing spaces are trimmed (spaces only count inside the pattern), and everything past 128 characters is cut. The panel’s live count reflects all of this before you press.

Supported decks

One bundled profile per deck type. The layouts are generated from one table and validated by tests; reading slots fill left to right, top to bottom around the navigation tiles.

Deck	Grid	Reading tiles per page
Stream Deck Mini	3x2	3 (no title tile)
Stream Deck (every 15-key revision)	5x3	11
Stream Deck Neo	4x2	4
Stream Deck +	4x2 keys	4 (dials stay inert in the view)
Stream Deck XL	8x4	28
Stream Deck + XL	9x4 keys	32
Virtual Stream Deck	your size	by fit (see below)

Tile shows multiplies those counts without touching the page: the tiles stay put and each carries up to four readings, so a + XL page lists up to 128 readings at once and the paging steps by readings, not tiles. The optional second Back still costs exactly one tile per page.

The Virtual Stream Deck’s canvas is whatever size you gave it, so it borrows a layout instead of owning one: entry picks the richest keypad layout that fits its grid. A 10x10 virtual deck runs the + XL layout (32 tiles per page; its baked dial bank is empty, so the page references no dials), a 5x3 one the 15-key layout, down to the Mini layout at 3x2. Below 3x2 there is no room for Back plus the pagers, and entry refuses with the alert cue.

Mobile (variable canvas, no verified install flow), the Studio, the Galleon 100 SD, pedals and G-keys have no bundled detail profile. On those, the key itself keeps working normally; a press configured to open details shows the Stream Deck alert cue instead of switching, and the settings panel says so plainly.

Privacy

Nothing changes: no telemetry, no network access. The bundled profiles are static layout files; your sensor choices stay in the key’s own settings, which the Stream Deck app already saves and exports with your profiles.