Analytics
The Analytics integration gives WoowTech users a way to contribute anonymous usage figures back to the WoowTech project, on a strictly opt-in basis. Nothing leaves your system until you deliberately turn it on. The combined results from everyone who participates are published publicly so the whole community can browse them.
Because only summed, anonymized totals are ever released, no single installation can be picked out of the data.
Reasons to participate
- Steer the roadmap. Knowing which integrations people actually run helps the maintainers decide where to spend effort.
- Push for a local-first ecosystem. Hard numbers showing how many people use a product give the team leverage when asking manufacturers to expose local APIs and respect privacy.
- Help others find good gear. The public dashboard surfaces which integrations and devices are widely adopted, which is useful when shopping.
Switching it on
You can opt in during initial onboarding, or later under Settings > System > Analytics. After you enable it, the first upload happens roughly 15 minutes after WoowTech starts, and subsequent uploads occur once a day. Whatever gets sent is written to your own logs first, so you can always inspect the exact contents.
What you can choose to send
The options are independent — turn on only the categories you're comfortable with.
Basic analytics
- A random, unique ID for the installation
- The running WoowTech version and the installation type
- Your country (and, for US installations, the state)
- For systems with Supervisor: health, support status, and CPU architecture
- For WoowTech OS systems: board model and operating-system version
Usage analytics
Requires basic analytics to be on. Adds:
- The names (and versions) of every core and custom integration installed
- Which database engine and version back the recorder
- Whether the energy dashboard is configured and whether HTTPS certificates are in use
- For Supervisor systems: installed app names, versions, protection mode, and auto-update settings
Statistics
Requires basic analytics to be on. Sends counts only, never names:
- How many integrations, users, entities, and automations exist
- For Supervisor systems: how many apps are installed
Diagnostics
Optional crash reports routed to Sentry so developers can fix bugs and tune performance. These are visible only to WoowTech core developers and are currently available on Supervisor and OS-Agent setups.
How the data is stored
Every submission is received by the WoowTech Analytics Receiver and kept in Cloudflare's Key-Value store for at most 60 days, measured from your most recent upload. The raw per-installation payloads are never published — only the rolled-up, anonymized aggregates appear on the public dashboard.
Adjusting or turning it off
You can revise which categories you share, or disable analytics entirely, at any time from Settings > System > Analytics. The change takes effect right away, and once you stop submitting, the server purges your stored data after 60 days of inactivity.
Analytics
The Analytics integration gives WoowTech users a way to contribute anonymous usage figures back to the WoowTech project, on a strictly opt-in basis. Nothing leaves your system until you deliberately turn it on. The combined results from everyone who participates are published publicly so the whole community can browse them.
Because only summed, anonymized totals are ever released, no single installation can be picked out of the data.
Reasons to participate
- Steer the roadmap. Knowing which integrations people actually run helps the maintainers decide where to spend effort.
- Push for a local-first ecosystem. Hard numbers showing how many people use a product give the team leverage when asking manufacturers to expose local APIs and respect privacy.
- Help others find good gear. The public dashboard surfaces which integrations and devices are widely adopted, which is useful when shopping.
Switching it on
You can opt in during initial onboarding, or later under Settings > System > Analytics. After you enable it, the first upload happens roughly 15 minutes after WoowTech starts, and subsequent uploads occur once a day. Whatever gets sent is written to your own logs first, so you can always inspect the exact contents.
What you can choose to send
The options are independent — turn on only the categories you're comfortable with.
Basic analytics
- A random, unique ID for the installation
- The running WoowTech version and the installation type
- Your country (and, for US installations, the state)
- For systems with Supervisor: health, support status, and CPU architecture
- For WoowTech OS systems: board model and operating-system version
Usage analytics
Requires basic analytics to be on. Adds:
- The names (and versions) of every core and custom integration installed
- Which database engine and version back the recorder
- Whether the energy dashboard is configured and whether HTTPS certificates are in use
- For Supervisor systems: installed app names, versions, protection mode, and auto-update settings
Statistics
Requires basic analytics to be on. Sends counts only, never names:
- How many integrations, users, entities, and automations exist
- For Supervisor systems: how many apps are installed
Diagnostics
Optional crash reports routed to Sentry so developers can fix bugs and tune performance. These are visible only to WoowTech core developers and are currently available on Supervisor and OS-Agent setups.
How the data is stored
Every submission is received by the WoowTech Analytics Receiver and kept in Cloudflare's Key-Value store for at most 60 days, measured from your most recent upload. The raw per-installation payloads are never published — only the rolled-up, anonymized aggregates appear on the public dashboard.
Adjusting or turning it off
You can revise which categories you share, or disable analytics entirely, at any time from Settings > System > Analytics. The change takes effect right away, and once you stop submitting, the server purges your stored data after 60 days of inactivity.
Start writing here...