Research-led • browser-only • toolkit v1.1
Compatibility, ownership-cost and local-control tools
Use the exact model and route—not the logo on the box. These tools surface documented incompatibilities, conditions and unknowns. They never issue a universal compatible verdict and do not replace manufacturer checks or site-specific installation advice.
6 September correction: the G350 model suffix below is corrected from its official manual. Other matrix evidence retains its 30 August date. See the camera shopping update for current price and card evidence.
JavaScript is required for these interactive lookups. The method and change log remain readable.
Continue with the UK evidence guides
The checker gives a bounded result. Use the cluster hub for the buying method, then the relevant spoke for the exact system or route.
UK heating and boiler compatibility
Subscription-free security
Matter, Thread and local control
UK heating compatibility triage
Search 18 dated product/system configurations and 12 manufacturer exclusions. Only an exact exclusion can return documented incompatible. Product-family routes remain conditional until the boiler, existing controls, interface, hot-water circuit, zones and call-for-heat path are recorded.
Choose a record to see its interface, hot-water, zoning, receiver and call-for-heat boundary.
Free/core versus paid/comparable cost over 36 months
Enter all five components for both scenarios. A blank means Unknown; enter 0 only when evidence confirms that component is unnecessary. Trials and temporary discounts should not form the main comparison basis.
Totals appear only when every component has a numeric value. Unknown is never converted to £0.
Privacy boundary: cost results are intentionally not put into share links because this form accepts free text, a source URL and user-entered price assumptions.
Matter, controller and Thread-role lookup
A Matter end device is not automatically a controller, bridge or Thread border router. Choose one of 13 controller/hub or 13 end-device records to see the documented roles, native-versus-bridged path, implementation version and dependencies.
Choose an exact record to distinguish controller, bridge, Thread border router and end-device roles.
Subscription-free security and outage lookup
Compare storage, free/core versus paid features, and documented broadband, router and power boundaries for six priority products. These are manufacturer-source boundaries, not SHUK outage or latency tests.
Choose G410, G400, D235, G350, C520WS or C660 KIT.
Download and reuse the compatibility evidence
SHUK Compatibility Commons v1.0.0 publishes the five dated matrices as 62 compatibility rows reconciled to 141 source records. Every row keeps its checked date, source, version and visible conflict or limit. It is desk research—not an installation, latency, outage or professional-sign-off claim.
Open the data catalogue · Download all rows as JSON · Download the source ledger · Follow the change feed
The SHUK-authored selection, structure and annotations are reusable under CC BY 4.0. Referenced manufacturers, standards bodies, manuals and trademarks retain their own rights.
Public change log
- 30 August 2026 — toolkit v1.1: added three static cluster routes, fragment-only bookmarks for exact public matrix records and links to Compatibility Commons v1.0.0. Cost/free-text inputs remain tab-only; the canonical path remains /checker/.
- 30 August 2026 — toolkit v1.0: added fail-closed heating triage from 18 product configurations and 12 manufacturer exclusions; no family-level row returns universal compatibility.
- 30 August 2026 — cost method v1.0: standardised hardware + required hub/base/storage + installation + 36-month subscription + mandatory consumables; blanks remain Unknown.
- 30 August 2026 — Matter data v1.0: separated controller, bridge, Thread border router and end-device roles and kept software, certification and device versions distinct.
- 30 August 2026 — security data v1.0: added G410, G400, D235, G350, C520WS and C660 KIT storage, plan, outage and cost boundaries.
- 30 August 2026 — security cost correction v1.0.1: removed the unsourced fixed microSD allowance. Local-recording card cost is now the unresolved variable C_SD, and known subtotals exclude it.
Recheck active rows after a material product, plan, firmware, certification or support change—and at least quarterly. A correction should identify the exact model, region, version, date and official source. Corrections update evidence; they do not create a hands-on test claim.