Let owners read their device's data directly

How to do it

Owners want to move to another app, check what the device recorded, or feed a home system. Build the export path into the first firmware and cloud API, since adding it later means a new data model. Use the fields from list every sensor and every field that leaves the device, so the export covers everything you collect. A local API on the device also keeps it useful when the cloud ends. In the EU, the Data Act asks this by design of products placed on the market after 12 September 2026. See give users the data from connected products. The account export itself follows self-service export.

Examples

Python example

def export_problems(export: dict, field_list: set[str]) -> list[str]:
    exported = {field for reading in export["readings"] for field in reading}
    return [f"field {name} is collected but not exported" for name in sorted(field_list - exported)]

Go example

func ExportProblems(readings []map[string]any, fieldList []string) []string {
	exported := map[string]bool{}
	for _, reading := range readings {
		for name := range reading {
			exported[name] = true
		}
	}
	var problems []string
	for _, name := range fieldList {
		if !exported[name] {
			problems = append(problems, "field "+name+" is collected but not exported")
		}
	}
	return problems
}

How to check

A test asks for the export of a test device and parses it against the published schema. Every field in the model's field list appears in it. The request needs no payment and no support ticket.

Sources

• Data Act, Regulation (EU) 2023/2854, Article 3

Related rules

• IOT-31 List every sensor and every field that leaves the device in Connected devices
• IOT-36 Plan what the device does when support or the cloud ends in Connected devices
• CMP-54 Give users the data from connected products in Compliance and governance
• ACC-55 Let people export their data themselves in Accounts and identity