Matter

localby ALYT

What it adds to a house

adds lights, switches, blinds, locks and sensors.

How a person connects it

Method: discover. Use Add a device → A Matter device. Setup checks your hub’s reported readiness before continuing.

What it can look for

Yes: “Set up a Matter device”.

What stops working when it is disconnected

Remove each device from this home first. Other Matter administrators keep their access.

The descriptor

Connection fields are served for a program at /connectors/matter.json.

{
  "source": "built-in",
  "visibility": "public",
  "listed": true,
  "version": "1.0.0",
  "docsUrl": "https://developers.alyt.com/connectors/matter",
  "kind": "MATTER",
  "logo": {
    "url": "/integrations/logos/matter.png",
    "color": "#121925",
    "ratio": 1,
    "background": "#FFFFFF",
    "inset": 0.12,
    "scale": 1
  },
  "name": "Matter",
  "icon": "radio",
  "builtIn": {
    "reason": "Matter through a compatible ALYT home hub"
  },
  "connectivity": "local",
  "brings": [
    "light",
    "switch",
    "cover",
    "lock",
    "sensor"
  ],
  "connect": {
    "method": "discover",
    "fields": [],
    "help": "Use Add a device → A Matter device. Setup checks your hub’s reported readiness before continuing."
  },
  "discovery": {
    "verb": "Set up a Matter device",
    "flow": "hub-matter"
  },
  "disconnect": {
    "consequence": "Remove each device from this home first. Other Matter administrators keep their access."
  },
  "author": {
    "kind": "alyt",
    "name": "ALYT",
    "url": "https://alyt.com"
  }
}

The guide

Matter connects through a compatible ALYT home hub and uses the home’s local network path. Setup starts only when the selected hub has a fresh ready report. The hub is the Matter controller for the home: it handles commissioning, subscriptions, commands, and local routine execution, while ALYT presents the devices as room endpoints after setup completes.

Connect and pair devices

To add a device, open Add a device → A Matter device. Then select a ready home hub, choose the device name and room, choose the device’s network, and either scan the Matter QR code or enter the setup code manually.

QR scanning is optional. If camera permission is denied, or the browser does not provide scanning, manual code entry is available instead.

Setup checks your hub’s reported readiness before continuing. An unfinished setup can be reopened, and reviewing saved progress does not restart commissioning. If setup is cancelled, ALYT waits for the hub to confirm cleanup before ending it.

If the device is already paired in another Matter fabric, you need a fresh sharing window and code from that other administrator. ALYT does not import another fabric’s private keys and does not reset the device as part of setup.

Setup credentials, including Wi-Fi credentials used during commissioning, are transient.

Network and prerequisites

Matter is a local connector. Local functions can keep working during a cloud outage.

The required network path depends on the device:

• Matter over Thread requires the hub’s attached Thread network.
• Matter over Wi-Fi requires the appropriate Wi-Fi network path.

If that local path is unavailable, the device cannot be commissioned or controlled through this connector.

Only a compatible owning hub’s fresh readiness report can enable setup. The built-in label means ALYT supports Matter through a compatible ALYT home hub; it does not mean ALYT runs a separate online Matter controller.

What devices expose

A device appears in ALYT only after a complete, validated interview. It then appears as ordinary room endpoints.

Exposed state and controls follow the device’s reported capabilities. Supported capabilities include:

• lights and switches
• covers
• locks
• sensor readings

Generic occupancy is not called vibration.

Unsupported endpoint families can still appear, but ALYT does not invent controls that the device did not report. TV devices use normal controls and state once present, but setup and repair are handled in the web and phone flows.

A quiet battery sensor is not treated as offline only because it has not sent an unsolicited update. Monitoring follows Matter’s negotiated liveness instead.

Control and recovery behavior

Commands are confirmed through the hub’s Matter flow. If a requested change has not yet been confirmed, ALYT can return an uncertain result instead of claiming success. In that case, do not repeat the operation immediately; the hub owns completion.

Fix connection retries monitoring and reads the same physical device again. Its identity, name, room, and routine references stay unchanged.

Existing Matter fabrics and datasets are retained across hub restart.

Removal and disconnect

To disconnect Matter from a home, remove each device from this home first. Other Matter administrators keep their access.

Remove device removes the whole physical node, including any child endpoints. While removal is pending, those endpoints are disabled. Final deletion requires the hub to confirm removal from its own fabric and complete local cleanup. A command acknowledgement or timeout on its own is not treated as successful removal.

Retrying or reopening the same removal request reuses the saved result instead of authorizing duplicate removal. If the outcome is rejected or remains unknown, the device stays visible but disabled. After removal, review any routines that referenced that device.

If something fails

Check these points first:

• the selected hub is currently ready
• the hub is linked to the home
• the device still has the required local Thread or Wi-Fi path
• for shared devices, the other administrator provided a fresh sharing window and code

If setup was interrupted, reopen it rather than starting over. If monitoring stops or state looks stale, use Fix connection before removing and re-adding the device. If removal does not complete, wait for the hub’s confirmed cleanup result rather than assuming a timeout means success.