Nexview 0.30.0

Nexview connects to Home Assistant now, and everybody does it for themselves: enter your access key over there and you get your own figures and are notified about your own business. Along with a correction that was long overdue: storage sizes are finally called what they are.

New

Home Assistant, for everybody in the house. Notification targets used to be an operator's business. An application that wanted to connect therefore needed an administrative key, and then received everything happening in the house instead of what concerned its owner. Now the application registers itself, with the key it already has, and receives exactly what its owner also sees in their notification bell: their requests, their tickets, their storage. Anybody in the same household running their own Home Assistant gets their own, and neither sees the other's. Your access keys under Profile → API tokens then show where Nexview notifies, with a button to disconnect.

A read-only key may register one too. It is the single exception to that rule, and it exists so that notifications are not the one reason to reach for the more powerful key. What such a key registers concerns nobody but its own owner: it changes no request, no account, no setting.

Where Nexview notifies. Under Settings → Notifications at the bottom, a list of every application that registered: who is being notified, through which key, at which address, and whether anything failed recently. Whoever runs a server should be able to see where it sends data. Nothing is set up here, because the application does that itself. Disconnecting works.

GiB now says GiB. Nexview has always divided storage sizes by 1024³ and written "GB" next to them. That is the unit which divides by 1000³, and the difference is seven per cent. The name changed, not the arithmetic: anybody who entered 300 still has exactly the same space as before, it now says "300 GiB". The other way round would have taken seven per cent off everyone's allowance without anybody touching a setting.

House stock is shown separately. "Used" on the home page threw together two very different things: what the residents requested, and what was here before Nexview or got taken over later. Only the first half counts against allowances and grows when somebody requests something. Both figures are there now.

The API says what a key may do. GET /api/v1/me tells an integration who is knocking and what this request is allowed to do, as stable identifiers rather than a role. An administrator with a read-only token carries role: admin and may still approve nothing; building against the role builds a button that always fails.

Fixed

The Seerr migration wizard speaks the language you set. Conversions on account rows, gaps per area, preview labels, reasons for skipped rows and the "what stays manual" list arrived as finished German sentences from the server. The server now sends identifiers and figures, and the interface builds the sentence in its own language. This shipped as 0.29.1, which never got a tag of its own.

Also

• GET /api/v1/storage/me now says whether an account gets anything attributed to it at all. For an administrator it does not: what they fetch belongs to the house, so their figures sit at zero as a booking rather than a measurement.
• The statistics carry the last sign-in per account, so "which accounts are asleep" can be answered without opening the user list.
• A webhook payload carries its confirmation code in a field of its own, so a machine no longer has to pick it out of a translated sentence.
• Personal notification targets never appear in the channel settings. They are not something anybody configures there, and from that list an operator could have edited a stranger's address.

For integrators

Everything the callback needs sits under /api/v1, which carries Nexview's stability promise: as long as v1 is in the address, these answers do not change in a way that breaks what is built against them. The Home Assistant integration that uses it is not published yet.