fibaro_stop_scene
Stop a running scene on Fibaro HC3 by specifying its scene ID. Manage smart home automation efficiently with precise scene control through the MCP server.
Instructions
Stop a running scene
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Scene ID to stop |
Implementation Reference
- src/fibaro-client.ts:174-182 (handler)Core implementation of the fibaro_stop_scene tool: sends a POST request to the Fibaro HC3 API endpoint /api/scenes/{id}/action/stop to stop the specified scene.async stopScene(id: number): Promise<void> { try { await this.client.post(`/api/scenes/${id}/action/stop`, { args: [] }); } catch (error) { throw new Error(`Failed to stop scene ${id}: ${error}`); } }
- src/index.ts:565-579 (handler)MCP CallToolRequest handler for fibaro_stop_scene: checks connection, extracts scene ID from arguments, calls FibaroClient.stopScene, and returns success response.case 'fibaro_stop_scene': { if (!this.fibaroClient) { throw new Error('Not connected to Fibaro HC3. Please check your configuration and restart the MCP server.'); } const sceneId = args?.id as number; await this.fibaroClient.stopScene(sceneId); return { content: [ { type: 'text', text: `Successfully stopped scene ${sceneId}`, }, ], }; }
- src/index.ts:315-328 (registration)Tool registration in the ListTools response: defines name, description, and input schema (object with required numeric 'id' property). Also serves as schema definition.{ name: 'fibaro_stop_scene', description: 'Stop a running scene', inputSchema: { type: 'object', properties: { id: { type: 'number', description: 'Scene ID to stop', }, }, required: ['id'], }, },