A dashboard you can actually do something on
A number turning red is only half the job. The two or three moves you make afterwards sit on the card the number is on. Anything that cannot be undone asks once. Everything is logged.
On the card, not in another window
The moves you would otherwise open three interfaces for sit where the number that prompted them is.
Containers
Restart, stop, start again. And follow the log while it is being written, without a detour through a terminal.
Machines
Start virtual machines in Proxmox. Wake a powered-down host with a magic packet and then watch for it to start answering.
Downloads
Pause and resume, on SABnzbd, NZBGet, qBittorrent, Transmission and Deluge. The queue stands right next to the button.
Requests
Approve open requests from Seerr or Nexview without opening their interface.
The house
Toggle Home Assistant entities. A light, a socket, a scene, straight from the card.
With a question first
Anything that cannot be taken back asks once. And every action that ran is in the log afterwards, with the account and the time.
Who may trigger an action depends on the role and on what was agreed when a board was shared. A wall display may do nothing at all out of the box, because otherwise anyone standing in front of it could restart a container. That is under Running it.
Is it still answering?
Every app tile can carry a check. It knocks on the service's address and puts the result under the tile as a row of bars: you see not only that something is gone right now, but also that it was gone three times yesterday.
If a service stays away longer than the threshold you set, a message goes out. Not on the first blip, but when it holds. When it comes back, nexdeck says that too.
One integration with an unreadable secret no longer stops anything else. A single broken credential used to be able to bring down every check in the installation. Now the card in question puts a readable message on itself and tries again later.
Eight roads out
Telegram, e-mail, Web Push, ntfy, Gotify, Discord, Slack and Apprise. One service may hold as many ways as you like.
- A row of services with their logos, the ways you have set up as tiles below them, and the one you are working on opened underneath with a step-by-step guide beside the fields.
- Saving and sending a test are one button. A test says nothing about fields nobody kept.
- A mail server for the installation sits next to it, for what has to leave the house before anyone can sign in. A forgotten password first of all.
- Every account has an address, unique across accounts, so a password reset ends at exactly one of them.
What gets reported
A service that has not answered for too long, and the same service when it comes back. Everything else nexdeck could say, it says on the card, because a message for every small thing ends with nobody reading any of them.
The mail server's password is stored encrypted and never travels back to the browser. The same goes for every credential of a connected service.