THE KNOWLEDGE GRAPH

Every product we cover — and everything it connects to — as one graph you can question.

Behind the compatibility checker is a source-tracked map of 283 models, their protocols, and the ecosystems they work with. This is what it looks like.

283Product records
1415Compatibility edges
3611Sourced claims
17Categories

WHAT IT IS

A catalog of specs is a list. A knowledge graph is a set of relationships.

Most product sites store a spec sheet per model and stop there. We store two things and the link between them: a product-model record — one durable entry per model, its identity, protocols, subscription reality, and lifecycle — and a compatibility graph that connects each model to the ecosystems and hardware it actually works with.

That link is the asset. It's what lets the checker answer "will these work together in my home" instead of reciting what each box claims on its own. Every product is a node; every "works with Alexa," every "needs a Thread border router," every "cloud link removed" is an edge — and every edge carries a source.

It's built to be read by people and by machines — the same graph powers the human checker and a public feed for AI agents.

Nodes — the models

283 product records across 17 categories, each with a stable identity that survives renames, generations, and supersessions.

Edges — the compatibility

1415 integration cells linking models to 5 ecosystems, plus protocol and hub-dependency edges — the "picks that work together" relationships.

Provenance — the trust

3611 source entries. A claim without a citation isn't in the graph; an unknown we haven't confirmed says so plainly.

THE GRAPH TODAY · LIVE FIGURES

The graph, by the numbers.

Not a marketing snapshot — the actual shape of the catalog right now, including the parts we haven't finished confirming. These numbers are generated from the live data on every build.

Compatibility coverage1415 integration edges
Full — works natively 586
Partial — works, with a catch 251
None — confirmed not supported 248
Unknown — not yet confirmed 330

Why we show the grey. "Unknown" and "confirmed none" are separate states here on purpose. A confident-looking guess is worse than an honest gap — so an edge we haven't verified is never dressed up as a "no."

Depth by category17 live
Smart Lighting32
Cameras & Doorbells30
Hubs & Controllers24
Switches & Dimmers23
Indoor Air & Comfort19
Plugs & Outlets18
Outdoor, Lawn & Irrigation17
Sensors & Detectors15
Robot Vacuums & Mops14
Smart Locks13
Smart Pool13
Water Protection & Plumbing13
Garage & Access12
Thermostats12
Blinds, Shades & Curtains11
Security Systems & Alarms9
Energy, Solar & EV8
16Protocols tracked — from Wi-Fi (195 models) and Matter (88) to Thread, Z-Wave, and Clear Connect
240 / 283Models that need no subscription — 34 optional-but-material, 6 required. Subscription reality is a first-class field
283 / 283Records carrying at least one cited source — 3611 source entries in total across the graph
Facts per record — how many are established, and how many are sourced26 attributes · 7,035 fact cells

Each record has 26 attributes it can hold — protocols, hub requirement, subscription reality, whether it works offline, the security-update window, and so on. Multiply by 283 records and you get 7,035 facts the graph is built to carry. Here is how many it actually does, and how many of those point at a source you could open.

62.4%Established — 4,390 cells hold a real value rather than an honest "not yet confirmed"
67.7%Cited with a URL — 4,765 cells trace to a fetchable source; 70.9% are cited at all, the rest of those with a stated reason no single URL exists
88.3%Source entries with a URL — 2,502 of 2,834 claim-bearing citations name a page a machine can re-fetch
1,091 / 1,143Source URLs under automated watch — re-fetched on a schedule and compared to a stored fingerprint; the watcher last ran 2026-09-08

Where the biggest gaps are right now

  • capabilities.mapping0% established
  • identifiers3.5% established
  • Security-update window10.2% established
  • App platforms19.4% established
  • Hub capability it provides20.5% established

Read the gaps honestly. Some attributes are empty because the fact is rare — most products aren't hubs, and most vendors publish no security-update end date — and some because we haven't researched them yet. Either way the cell says "not established" rather than guessing, and the list above is regenerated from the live data on every build.

PROVENANCE

Why every claim in the graph holds up.

Open any record and each fact traces to where it came from. Here's a real one from the catalog, annotated.

A source, or it doesn't ship

Every edge cites where it came from — a vendor spec, an ecosystem developer doc, a standards registry — not "our research."

Honest unknowns

We distinguish "we checked, it's a no" from "we haven't checked." The graph carries both, labeled.

Negatives are claims too

"Needs the Hue Bridge" or "no HomeKit support" is evidence we record and cite, not silence.

Made for agents

88.3% of our claim-bearing citations now carry a fetchable source URL — so an AI agent, and our own scheduled watcher, can re-check our work. The rest are being converted from prose, and the number above is live.

wyze-cam-v4.json Cameras & Doorbells
protocols["wifi"]
Alexafull works natively
Googlefull works natively
Apple Homenone confirmed not supportedThe Wyze Cam v4 product page lists its integrations as Alexa, Google Assis
SmartThingsnone confirmed not supportedThe Wyze Cam v4 product page lists its integrations as Alexa, Google Assis
Home Assistantpartial works, with a catchNo official RTSP firmware exists for the Cam v4 — Wyze's RTSP article name
subscriptionoptional_but_materialfree 24/7 local microSD · Cam Plus $2.99/mo
provenancewyze.com — vendor product pageverified 2026-07-15 · every cell traces to a cited source

WHAT'S LIVE · WHAT'S COMING

The catalog's promise is shifting from complete to true.

We're honest about what the machinery does today versus what it's built to do next.

LIVE NOW

Working today

  • Source-tracked records — 283 models, every claim cited
  • The compatibility graph — 1415 model-to-ecosystem edges powering the checker
  • Honest unknowns & evidenced negatives — gaps and "no"s are labeled, not hidden
  • Machine-readable feed — the same graph, published for AI agents
  • Source watching — 1,091 cited URLs re-fetched on a schedule and fingerprinted; a change is flagged for a person to re-verify, never written into a record automatically
  • Graph health in the open — the coverage figures above are recomputed from the live data on every build

Straight answer: the graph is kept current by scheduled research and by a watcher that notices when a cited page changes — but every correction is made by a person, the catalog does not maintain itself, and a "verified" date is a record of when we last looked, not a guarantee nothing has changed since. Change detection is our stated direction. The day it goes live, this page will say so.

Put a question to the graph.

Pick what you own, or what you're about to buy, and see whether it all works together — sourced, not guessed.

Want the methodology — what we borrowed from the formal provenance standards, and what we had to add for facts that change? Read how we're building the knowledge graph →