Chime Device Type

[lboue]

Summary

Adds support for the Matter Chime device type / cluster, allowing plugins to expose devices (e.g. doorbells, alert devices) that can play a selected or requested chime sound.

• Add MatterbridgeChimeServer behavior (packages/core/src/behaviors/chimeServer.ts), extending ChimeServer, which handles the playChimeSound command: resolves the chime ID from the request or falls back to selectedChime, forwards the command to the Matterbridge command handler, logs the action, and emits the chimeStartedPlaying event.
• Add MatterbridgeEndpoint.createDefaultChimeClusterServer(...) helper to create a default Chime cluster server with configurable installedChimeSounds, selectedChime, and enabled state.
• Wire up the chime device type in addClusterServers() so it is created automatically via addRequiredClusterServers().
• Extend MatterbridgeEndpointCommandHandler with the playChimeSound command handler type/entry (Chime.playChimeSound).
• Export MatterbridgeChimeServer from packages/core/src/behaviors/export.ts.
• Add vitest coverage:
  • createDefaultChimeClusterServer default-attributes test in matterbridgeEndpoint-default.test.ts.
  • Chime device creation, registration on the server node, and playChimeSound command invocation in matterbridgeEndpoint-matterjs.test.ts.

Test plan

• npm run build (tsgo) passes with no type errors.
• npm run lint no longer reports the chimeServer.ts warning.
• New vitest cases cover default Chime cluster attributes and the playChimeSound command flow (request with/without chimeId, log output, chimeStartedPlaying event).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!