Skip to content

Analytics

In 1Home Server and it's variants you can optionally share basic anonymous data to help us prioritize our future development efforts.

Table of contents

Why collecting analytics?

As a privacy-first product, we still need to make the correct decisions on what to build next.

Without real insights into how our products are being used, we are left guessing about where to focus our efforts.

Our analytics principles

All data in your smart home is yours and yours only. We want to treat it with respect.

Thus 1Home Server analytics are:

  • Opt-in - you have to explicitly enable it
  • Anonymous - we don't send personal data, and only send what we really need for decision making
  • Transparent - see below exactly what is being shared
  • Not shared with any 3rd parties - we solely use the data to help us improve the products that you use

See exactly what is being shared

Below is a complete list of data that is shared with 1Home if analytics are enabled (via opt-in).

  • General
    • Analytics ID - an anonymous id
    • Details about your device - software version, product variant, timezone, uptime
  • Quality of service
    • Error rate monitoring - number of warning and error logs in the past 24 hours to monitor new releases for any unforeseen issues
  • Installation
    • Number of rooms - to understand the average size of the project
    • Devices - To understand what devices are most used we collect device type, online state and if they are bridged to Matter
  • Integrations
    • Matter bridge - to understand how many people use Apple Home, Google Home and others we collect whether any of these services are connected
    • Matter controller - in order to better support certain Matter devices that are popular we collect models of Matter devices that are used in the system (e.g. Philips Hue Bridge) and whether the connection to them is working
    • Graphs - number of custom graphs and last view of the graphs page in order to understand if this feature is being used
    • Crestron Home - whether the integration is configured, what is the driver version and how long is it online
  • Automations
    • Number of errors - number of errors compared to number of runs in the past 24 hours
    • Automomation - if it has issues, if it is enabled, lastRun, type and count of different block types (condition, action, ...)
  • Mobile app
    • To understand how important 1Home mobile app is, we collect how often it is used. We also collect whether the users use iOS or Android
  • Remote connections
    • Remote access - if the remote access is enabled and how often it is used
    • Remote ETS programming - if remote ETS programming is enabled and how often it is used

We keep the data we collect to minimal and gather only what we need to make future product decisions.

Thank you for helping us make your product better!