Nexview in Home Assistant

Somebody requests a film. The phone buzzes, two buttons, done. Nexview never gets opened.

That is the heart of the integration, and it is out now. Everything else is a bonus, but there is quite a lot of bonus.

Everybody connects for themselves

The unusual part first, because most integrations do it the other way round: there is no house-wide connection everybody looks into. Each person enters their own key in their own Home Assistant and gets their own figures: their requests, their tickets, their storage. Somebody else in the same household running their own Home Assistant gets theirs, and neither sees the other's.

A key marked read only is enough for all of it, notifications included. That was deliberate: otherwise notifications would be the one reason to reach for the more powerful key.

What arrives in Home Assistant

The house at a glance. Waiting requests, downloads in progress, failures over the last week, findings by severity, open tickets, how full the library is. Separately from that, how much of it belongs to the house and how much to the people. All of them keep history, so a graph over a month costs nothing.

Every Radarr and Sonarr as its own device, hanging off Nexview: whether it answers, what it is complaining about, which version it runs, how much is queued and how much of that is stuck, and a button to make Nexview talk to it right now.

Every media server as its own device. Plex, Jellyfin and Emby each get one: how many titles are on them, how many streams are running, and how many of those the server is converting. Who is watching what comes from an action rather than a sensor. That belongs to the moment somebody asks, not in a database that keeps everything for years.

Allowances per account, for the accounts you pick. Nexview applies a number of titles and an amount of storage at the same time, either one being full stopping a request, so both are shown and one sensor says plainly when requesting is over for now, naming which of the two limits it is. Nobody gets entities without being picked: an installation with thirty accounts should not be handed two hundred values.

A calendar of what is coming out, sitting beside the bin collection rather than in an app of its own.

Nexview itself in the update list, so it does not sit at an old version for months because nobody happened to look.

Three triggers by subject: requests, storage, operations. Waiting for a request will not wake you for a storage message.

What this integration does differently

It only shows what the key may do. Nexview hands out named access keys whose rights follow the account. The integration asks first what a key is allowed to do and creates only what fits. A personal key yields a handful of entities, an operator's key the lot. Nothing sits there greyed out, nothing answers a press with "forbidden".

It sets up the way back itself. Nexview refuses to save a notification target that has not proven itself: it sends a test message carrying a four digit code, and only a caller who reads that code back may save. A good rule, because an HTTP 200 means "accepted", not "arrived". The integration catches that code itself and hands it back. Nobody copies anything between two windows.

And when that fails, it says so. If Nexview cannot reach Home Assistant, everything keeps working, only slower, and a repair notice names the reason. The comparable integration for Seerr simply goes quiet in that case.

What is deliberately missing

Child accounts do not appear. In Nexview they are sub-profiles of their parents, and their names and wishes do not belong in a database that records everything forever.

Nothing can be configured. No switches for accounts, none for allowances, no resetting. Everything is read, requests are decided, and a few operator errands exist as buttons, no more. An automation that misfires at three in the morning should not be able to reach any of it.

What it needs

Nexview 0.30 and Home Assistant 2026.3. Older Nexview versions are turned away with a sentence explaining why.

It installs through HACS as a project of its own beside Nexview, at DerKezorm/nexview-homeassistant, under the MIT licence.