GridFit

How we get the data, and what we do not guarantee

Sources

  • Home Assistant core — integrations.jsonand each integration's manifest.json (Apache-2.0): the name, its iot_class (local_polling / local_push = local; cloud_* = cloud) and whether it has settable entity platforms (number, select, switch, button). Core models are not listed: the Open Home Foundation Device Database does that from real installations, and we link to it.
  • HACS custom integrations — picked by hand from the HACS default store (energy devices only; generic protocol bridges such as OCPP or SunSpec and automation helpers are left out). Stars and last update come from the HACS store data, iot_classfrom the repo's manifest, the platforms from the repo itself. What a repo covers is written from its README, in its own words.
  • evcc — the device templates in templates/definition (MIT): brand, product, connection parameters and capabilities. Templates that need an evcc sponsor tokenare marked; no template content is copied, only the fact of support.
  • Grid registers — the published type-approval lists of 6 registers (see Grid lists). Device pages show every list row for the matched models. The grid lists view also shows each row's status word, firmware, row or document number and dates — the registers' facts, not GridFit's work, and not under GridFit's CC BY. None of the lists states reuse terms; every row links back, and the register is the authority. Belgium's Synergrid list allows personal use only, so the cross-view shows just “listed” / “expired” with a link, and family pages do not use it.

What the marks mean

  • local the integration or template talks to the device (or its logger) on your network. It says nothing about whether the device also needs the internet for setup or updates.cloud it goes through the vendor's cloud. not found no integration found — not “does not work”.
  • control Home Assistant: the integration has entities you can set — anything from a battery charge limit to a restart button; read its docs for what exactly. evcc: chargers are controlled by definition; meters only when the template has battery-control. read only sensors only.
  • Listed in — a register lists a model whose code matches this family's pattern. The match is a pattern, not a confirmation; each model shows how its brand name was matched (exact / alias).
  • No listing for this class (dotted green cell) — the country has no list for this kind of device: a wallbox is a load, not a generating unit, and only Austria lists chargers; a meter or energy manager is not a grid-connection unit anywhere. Nothing to check, which is different from “no model found”. A dotted amber cell means there is no list but a rule applies — a DSO notification, a registration, or a ban (plug-in solar in Sweden) — and the family page says which. A ? cell means we have not yet confirmed whether the country lists or otherwise gates the class. Source of all three: the EU+ grid-connection table of 2026-10-29.

What we do not guarantee

  • An empty cell is not a “no”. We never say a device does not work or is not approved — only what a source says.
  • Firmware changes things. Vendors have closed local APIs with an update before. Every row shows the date we last saw it.
  • Grid rules are yours to check. Changing export limits or charging a battery from the grid can break your connection agreement. Ask your installer or grid operator.
  • Nothing here is a purchase recommendation, and no manufacturer pays for a listing.

Corrections

The dataset lives in a public GitHub repository (data CC BY 4.0, code MIT). Open an issue or a pull request — “my Deye does Modbus TCP from firmware X” is exactly what we need. The site rebuilds from the sources weekly; Changes lists what moved.

Trademarks

Home Assistant is a trademark of the Open Home Foundation; evcc, HACS and all product and company names are trademarks of their owners, used here only to say what works with what. This site is not affiliated with any of them.