Diagnostics
Denframe keeps a few local, content-free counters so you can tell whether it is working well, and lets you export a redacted report to share when you ask for help. Nothing leaves your computer unless you send it.
What Denframe counts
Denframe counts events on your own computer, in its local database. It records how often a dashboard was launched to a screen and how often that failed, how long a screen took to show its first dashboard, how many times it recovered a screen after a lost connection, how often a new dashboard started (including playlist advances), how often media was played and presets were run, and how often a dashboard was saved or restored from its history.
It also counts wall panel connections and reconnects, home-control results (done, unconfirmed, not done) and their average time, and a first-dashboard setup funnel. A few figures are read live rather than counted: how many schedules exist, how many blocks are turned off, and how many sources are stale or unavailable.
Counts are kept for 90 days and are then deleted automatically, with a separate row limit for each kind of count, so a frequent one never pushes out a rare one.
What is never recorded
No count can hold a calendar title, a web address, a street address, a device’s state, a source’s settings, a password or key, or anything else your household sees or does. Denframe accepts only a fixed list of count names and plain numbers, and refuses anything else.
Home controls are counted by outcome only, never by which device, control or value. Dashboard history names blocks by kind, never by what they show.
None of this is sent anywhere. Denframe makes no network call with metrics or diagnostics, and nothing is scheduled to.
Review before you export
In Studio, open Screens & rotation, then Review before you export, and choose Preview export. The page shows the counts first: launches, dashboard starts, media casts, preset runs, edits and restores, recoveries, schedules, sources that are stale or unavailable, panel connections, home controls, and which experimental integrations are on. Wall panels are listed with their app and WebView versions.
Preview JSON shows the exact report, the same bytes a download contains. Download report saves it as a JSON file in this browser. There is no send button: the report goes only to the browser that asked for it.
The report also says which version and build of Denframe you run, its release channel, the operating system, how Denframe is installed, the database version, how dashboards reach Cast screens, and the problems logged since Denframe started -- where each happened and its type, never its message.
It always leaves out passwords, keys and tokens, source settings and addresses, the names and ids of devices, sources, people and dashboards, each device’s network address, calendar, task, meal and media content, file paths, and the text of error messages. The page lists exactly what was left out before you download.
Send it to support
On the same page, Report a problem lists what the file holds and what it never does. Save file saves the report, named with your version and the date; Email support opens an email to support@nannertech.com with the version in its subject, and you attach the file yourself. You can also send it through Support. Say what you expected, and what happened instead.
Never add passwords, pairing codes, PINs or keys to a support message: Denframe never asks for them.