@coffeerunhobby/mcp-ha-connect 2.2.1 → 2.4.0

package/tests/config.test.ts

@@ -1,355 +0,0 @@
-/**
- * Configuration tests
- */
-
-import { describe, it, expect, beforeEach, vi } from 'vitest';
-import { loadConfig, validateConfig } from '../src/config.js';
-import type { EnvironmentConfig } from '../src/config.js';
-
-describe('loadConfig', () => {
-  let originalEnv: NodeJS.ProcessEnv;
-
-  beforeEach(() => {
-    originalEnv = { ...process.env };
-  });
-
-  it('should load valid configuration from environment', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      HA_STRICT_SSL: 'false',
-      HA_TIMEOUT: '30000',
-      MCP_SERVER_LOG_LEVEL: 'info',
-      MCP_SERVER_LOG_FORMAT: 'plain',
-      MCP_SERVER_USE_HTTP: 'false',
-      MCP_SERVER_STATEFUL: 'false',
-    };
-
-    const config = loadConfig(env);
-
-    expect(config.baseUrl).toBe('http://homeassistant.10.0.0.19.nip.io:8123');
-    expect(config.token).toBe('test-token-12345');
-    expect(config.strictSsl).toBe(false);
-    expect(config.timeout).toBe(30000);
-    expect(config.logLevel).toBe('info');
-    expect(config.logFormat).toBe('plain');
-    expect(config.useHttp).toBe(false);
-    expect(config.stateful).toBe(false);
-  });
-
-  it('parses owner question settings (enabled by default; HA users as a trimmed list)', () => {
-    const base = { HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123', HA_TOKEN: 't' };
-
-    const defaults = loadConfig(base);
-    expect(defaults.ownerQuestionsEnabled).toBe(true);
-    expect(defaults.ownerQuestionsHaUsers).toEqual([]);
-
-    const set = loadConfig({ ...base, MCP_OWNER_QUESTIONS_ENABLED: 'false', MCP_OWNER_QUESTIONS_HA_USERS: ' a1b2 , c3d4 ,' });
-    expect(set.ownerQuestionsEnabled).toBe(false);
-    expect(set.ownerQuestionsHaUsers).toEqual(['a1b2', 'c3d4']);
-  });
-
-  it('should apply default values for optional fields', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-    };
-
-    const config = loadConfig(env);
-
-    expect(config.strictSsl).toBe(true); // default
-    expect(config.timeout).toBe(30000); // default
-    expect(config.logLevel).toBe('info'); // default
-    expect(config.logFormat).toBe('plain'); // default
-    expect(config.useHttp).toBe(false); // default
-    expect(config.stateful).toBe(false); // default
-    expect(config.toolRegistrationMode).toBe('eager'); // default
-    expect(config.httpEnableHealthcheck).toBe(true); // default
-    expect(config.httpAllowCors).toBe(true); // default
-  });
-
-  describe('toolRegistrationMode (MCP_TOOL_REGISTRATION_MODE)', () => {
-    it('defaults to "eager" when unset', () => {
-      const config = loadConfig({
-        HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-        HA_TOKEN: 'test-token-12345',
-      });
-      expect(config.toolRegistrationMode).toBe('eager');
-    });
-
-    it('parses "graph"', () => {
-      const config = loadConfig({
-        HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-        HA_TOKEN: 'test-token-12345',
-        MCP_TOOL_REGISTRATION_MODE: 'graph',
-      });
-      expect(config.toolRegistrationMode).toBe('graph');
-    });
-
-    it('rejects an unknown mode', () => {
-      expect(() =>
-        loadConfig({
-          HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-          HA_TOKEN: 'test-token-12345',
-          MCP_TOOL_REGISTRATION_MODE: 'lazy',
-        })
-      ).toThrow('Invalid environment configuration');
-    });
-  });
-
-  it('should remove trailing slash from baseUrl', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123/',
-      HA_TOKEN: 'test-token-12345',
-    };
-
-    const config = loadConfig(env);
-
-    expect(config.baseUrl).toBe('http://homeassistant.10.0.0.19.nip.io:8123');
-  });
-
-  it('should allow missing HA_URL (Omada-only mode)', () => {
-    const env = {
-      HA_TOKEN: 'test-token-12345',
-    };
-
-    const config = loadConfig(env);
-    expect(config.baseUrl).toBeUndefined();
-    expect(config.token).toBe('test-token-12345');
-  });
-
-  it('should allow missing HA_TOKEN (Omada-only mode)', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-    };
-
-    const config = loadConfig(env);
-    expect(config.baseUrl).toBe('http://homeassistant.10.0.0.19.nip.io:8123');
-    expect(config.token).toBeUndefined();
-  });
-
-  it('should throw error for invalid HA_URL', () => {
-    const env = {
-      HA_URL: 'not-a-url',
-      HA_TOKEN: 'test-token-12345',
-    };
-
-    expect(() => loadConfig(env)).toThrow('Invalid environment configuration');
-  });
-
-  it('should parse HTTP configuration when USE_HTTP is true', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      MCP_SERVER_USE_HTTP: 'true',
-      MCP_HTTP_PORT: '3000',
-      MCP_HTTP_BIND_ADDR: '127.0.0.1',
-      MCP_HTTP_PATH: '/mcp',
-      MCP_HTTP_ENABLE_HEALTHCHECK: 'true',
-      MCP_HTTP_HEALTHCHECK_PATH: '/health',
-      MCP_HTTP_ALLOW_CORS: 'true',
-      MCP_HTTP_ALLOWED_ORIGINS: '127.0.0.1,localhost',
-    };
-
-    const config = loadConfig(env);
-
-    expect(config.useHttp).toBe(true);
-    expect(config.httpPort).toBe(3000);
-    expect(config.httpBindAddr).toBe('127.0.0.1');
-    expect(config.httpPath).toBe('/mcp');
-    expect(config.httpEnableHealthcheck).toBe(true);
-    expect(config.httpHealthcheckPath).toBe('/health');
-    expect(config.httpAllowCors).toBe(true);
-    expect(config.httpAllowedOrigins).toEqual(['127.0.0.1', 'localhost']);
-  });
-
-  it('should use default httpPath /mcp', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-    };
-
-    const config = loadConfig(env);
-    expect(config.httpPath).toBe('/mcp');
-  });
-
-  it('should handle wildcard in allowed origins', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      MCP_HTTP_ALLOWED_ORIGINS: '*',
-    };
-
-    const config = loadConfig(env);
-
-    // Wildcard should result in empty array to disable SDK validation
-    expect(config.httpAllowedOrigins).toEqual([]);
-  });
-
-  it('should parse comma-separated origins', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      MCP_HTTP_ALLOWED_ORIGINS: 'http://mcpserver.10.0.0.18.nip.io:3000,http://192.168.0.10:8080,localhost',
-    };
-
-    const config = loadConfig(env);
-
-    expect(config.httpAllowedOrigins).toEqual([
-      'http://mcpserver.10.0.0.18.nip.io:3000',
-      'http://192.168.0.10:8080',
-      'localhost',
-    ]);
-  });
-
-  it('should throw error for invalid bind address', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      MCP_HTTP_BIND_ADDR: 'invalid-ip',
-    };
-
-    expect(() => loadConfig(env)).toThrow('MCP_HTTP_BIND_ADDR must be a valid IPv4 or IPv6 address');
-  });
-
-  it('should accept valid IPv4 bind address', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      MCP_HTTP_BIND_ADDR: '192.168.1.100',
-      // H5: a non-loopback bind requires authentication.
-      MCP_AUTH_METHOD: 'bearer',
-      MCP_AUTH_SECRET: 'test-secret-key-32chars-minimum!',
-    };
-
-    const config = loadConfig(env);
-    expect(config.httpBindAddr).toBe('192.168.1.100');
-  });
-
-  it('should accept valid IPv6 bind address', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      MCP_HTTP_BIND_ADDR: '::1',
-    };
-
-    const config = loadConfig(env);
-    expect(config.httpBindAddr).toBe('::1');
-  });
-
-  it('should parse numeric timeout', () => {
-    const env = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      HA_TIMEOUT: '45000',
-    };
-
-    const config = loadConfig(env);
-    expect(config.timeout).toBe(45000);
-  });
-
-  it('should support all log levels', () => {
-    const levels = ['debug', 'info', 'warn', 'error'] as const;
-
-    for (const level of levels) {
-      const env = {
-        HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-        HA_TOKEN: 'test-token-12345',
-        MCP_SERVER_LOG_LEVEL: level,
-      };
-
-      const config = loadConfig(env);
-      expect(config.logLevel).toBe(level);
-    }
-  });
-
-  it('should support all log formats', () => {
-    const formats = ['plain', 'json', 'gcp-json'] as const;
-
-    for (const format of formats) {
-      const env = {
-        HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-        HA_TOKEN: 'test-token-12345',
-        MCP_SERVER_LOG_FORMAT: format,
-      };
-
-      const config = loadConfig(env);
-      expect(config.logFormat).toBe(format);
-    }
-  });
-
-
-  it('should parse boolean strings correctly', () => {
-    const envTrue = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      HA_STRICT_SSL: 'true',
-      MCP_SERVER_USE_HTTP: 'true',
-      MCP_SERVER_STATEFUL: 'true',
-    };
-
-    const configTrue = loadConfig(envTrue);
-    expect(configTrue.strictSsl).toBe(true);
-    expect(configTrue.useHttp).toBe(true);
-    expect(configTrue.stateful).toBe(true);
-
-    const envFalse = {
-      HA_URL: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      HA_TOKEN: 'test-token-12345',
-      HA_STRICT_SSL: 'false',
-      MCP_SERVER_USE_HTTP: 'false',
-      MCP_SERVER_STATEFUL: 'false',
-    };
-
-    const configFalse = loadConfig(envFalse);
-    expect(configFalse.strictSsl).toBe(false);
-    expect(configFalse.useHttp).toBe(false);
-    expect(configFalse.stateful).toBe(false);
-  });
-});
-
-describe('validateConfig', () => {
-  it('should validate valid configuration', () => {
-    const config: EnvironmentConfig = {
-      baseUrl: 'http://homeassistant.10.0.0.19.nip.io:8123',
-      token: 'test-token-12345',
-      strictSsl: false,
-      timeout: 30000,
-      aiProvider: 'ollama',
-      aiUrl: 'http://ollama.10.0.0.17.nip.io:11434',
-      aiModel: 'qwen3:14b',
-      aiTimeout: 60000,
-      logLevel: 'info',
-      logFormat: 'plain',
-      useHttp: false,
-      stateful: false,
-      
-      httpEnableHealthcheck: true,
-      httpAllowCors: true,
-      sseEventsEnabled: true,
-      sseEventsPath: '/subscribe_events',
-      rateLimitEnabled: true,
-      rateLimitWindowMs: 60000,
-      rateLimitMaxRequests: 100,
-      authMethod: 'none',
-    };
-
-    expect(() => validateConfig(config)).not.toThrow();
-  });
-
-  it('should throw error for missing baseUrl', () => {
-    const config = {
-      token: 'test-token-12345',
-    } as EnvironmentConfig;
-
-    expect(() => validateConfig(config)).toThrow('Invalid configuration');
-  });
-
-  it('should throw error for missing token', () => {
-    const config = {
-      baseUrl: 'http://homeassistant.10.0.0.19.nip.io:8123',
-    } as EnvironmentConfig;
-
-    expect(() => validateConfig(config)).toThrow('Invalid configuration');
-  });
-});

package/tests/features/automation-creation.feature

@@ -1,36 +0,0 @@
-Feature: Automation Creation
-  As a Home Assistant user
-  I want to create automations via the MCP server
-  So that I can automate my smart home devices
-
-  Background:
-    Given a connected Home Assistant client
-
-  Scenario: Create a simple time-based automation
-    Given an automation config with alias "Morning Lights"
-    And a time trigger at "06:00:00"
-    And an action to turn on "light.bedroom"
-    When I create the automation
-    Then the automation should be created successfully
-    And the automation ID should be returned
-
-  Scenario: Create an automation with state trigger
-    Given an automation config with alias "Motion Alert"
-    And a state trigger for "binary_sensor.motion" changing to "on"
-    And an action to send notification "Motion detected!"
-    When I create the automation
-    Then the automation should be created successfully
-
-  Scenario: Reject automation without required fields
-    Given an automation config without alias
-    When I attempt to create the automation
-    Then it should fail with error "alias, trigger, and action are required"
-
-  Scenario: Create automation with multiple actions
-    Given an automation config with alias "Goodnight Routine"
-    And a time trigger at "23:00:00"
-    And an action to turn off "light.living_room"
-    And an action to turn off "light.kitchen"
-    And an action to set "climate.thermostat" to 18 degrees
-    When I create the automation
-    Then the automation should be created successfully

package/tests/features/automation-management.feature

@@ -1,54 +0,0 @@
-Feature: Automation Management
-  As a Home Assistant user
-  I want to manage my automations
-  So that I can control when and how my smart home responds to events
-
-  Scenario: List all automations
-    Given a Home Assistant with automations
-    When I list all automations
-    Then I should get all automation entities
-    And each automation should have id, alias, and state
-
-  Scenario: Get automation details
-    Given an automation "automation.morning_lights" exists
-    When I get the automation details
-    Then I should see the automation alias "Morning Lights"
-    And the state should be "on"
-    And the mode should be "single"
-
-  Scenario: Trigger an automation manually
-    Given an automation "automation.morning_lights" exists
-    When I trigger the automation
-    Then the automation.trigger service should be called
-    And the target should be "automation.morning_lights"
-
-  Scenario: Trigger automation with variables
-    Given an automation "automation.dynamic_scene" exists
-    When I trigger the automation with variables {"brightness": 100}
-    Then the automation.trigger service should be called
-    And the variables should be passed
-
-  Scenario: Enable a disabled automation
-    Given a disabled automation "automation.night_mode" exists
-    When I enable the automation
-    Then the automation.turn_on service should be called
-
-  Scenario: Disable an enabled automation
-    Given an enabled automation "automation.morning_lights" exists
-    When I disable the automation
-    Then the automation.turn_off service should be called
-
-  Scenario: Toggle automation state
-    Given an automation "automation.morning_lights" exists
-    When I toggle the automation
-    Then the automation.toggle service should be called
-
-  Scenario: Reload automations from configuration
-    Given a Home Assistant with automations
-    When I reload automations
-    Then the automation.reload service should be called
-
-  Scenario: Delete an automation
-    Given an automation with ID "1234567890" exists
-    When I delete the automation
-    Then a DELETE request should be made to the config API

package/tests/features/calendar.feature

@@ -1,37 +0,0 @@
-Feature: Calendar Operations
-  As a Home Assistant user
-  I want to access my calendar events
-  So that I can see upcoming appointments and reminders
-
-  Scenario: List all calendars
-    Given a Home Assistant with calendar entities
-    When I list all calendars
-    Then I should see all calendar entities
-    And each calendar should have entity_id, name, and state
-
-  Scenario: Get events from a specific calendar
-    Given a calendar "calendar.family" with events
-    When I get events from "calendar.family"
-    Then I should receive calendar events
-    And each event should have summary and start date
-
-  Scenario: Get events with custom date range
-    Given a calendar "calendar.work" with events
-    When I get events from January 1 to January 31
-    Then the events should be within the date range
-
-  Scenario: Get events using days parameter
-    Given a calendar "calendar.reminders" with events
-    When I get events for the next 7 days
-    Then the end date should be 7 days from now
-
-  Scenario: Get events from all calendars
-    Given multiple calendars with events
-    When I get events without specifying a calendar
-    Then I should receive events from all calendars
-    And results should be grouped by calendar
-
-  Scenario: Get events from calendar with no events
-    Given a calendar "calendar.empty" with no events
-    When I get events from "calendar.empty"
-    Then I should receive an empty events list

package/tests/features/configuration.feature

@@ -1,70 +0,0 @@
-Feature: Server Configuration
-  As an MCP server administrator
-  I want to configure the server with my Home Assistant details
-  So that I can connect to my smart home
-
-  Scenario: Load valid configuration
-    Given environment variables with HA_URL and HA_TOKEN
-    When I load the configuration
-    Then the configuration should be valid
-    And baseUrl should be set correctly
-    And token should be set correctly
-
-  Scenario: Apply default values for optional settings
-    Given only required environment variables
-    When I load the configuration
-    Then strictSsl should default to true
-    And timeout should default to 30000
-    And logLevel should default to "info"
-    And logFormat should default to "plain"
-
-  Scenario: Remove trailing slash from URL
-    Given HA_URL with trailing slash "http://ha.local:8123/"
-    When I load the configuration
-    Then baseUrl should not have a trailing slash
-
-  Scenario: Allow missing HA_URL for Omada-only mode
-    Given environment variables without HA_URL
-    When I attempt to load the configuration
-    Then it should load successfully with baseUrl undefined
-
-  Scenario: Allow missing HA_TOKEN for Omada-only mode
-    Given environment variables without HA_TOKEN
-    When I attempt to load the configuration
-    Then it should load successfully with token undefined
-
-  Scenario: Reject invalid URL format
-    Given HA_URL with invalid format "not-a-url"
-    When I attempt to load the configuration
-    Then it should throw an error about invalid configuration
-
-  Scenario: Parse HTTP server configuration
-    Given HTTP mode is enabled
-    When I load the configuration
-    Then useHttp should be true
-    And httpPort should be set
-
-  Scenario: Validate bind address format
-    Given an invalid bind address "invalid-ip"
-    When I attempt to load the configuration
-    Then it should throw an error about invalid bind address
-
-  Scenario: Accept valid IPv4 bind address
-    Given a valid IPv4 bind address "192.168.1.100"
-    When I load the configuration
-    Then httpBindAddr should be "192.168.1.100"
-
-  Scenario: Accept valid IPv6 bind address
-    Given a valid IPv6 bind address "::1"
-    When I load the configuration
-    Then httpBindAddr should be "::1"
-
-  Scenario: Handle wildcard in allowed origins
-    Given allowed origins set to "*"
-    When I load the configuration
-    Then httpAllowedOrigins should be an empty array
-
-  Scenario: Parse comma-separated allowed origins
-    Given allowed origins "http://localhost:3000,http://192.168.1.100"
-    When I load the configuration
-    Then httpAllowedOrigins should contain both origins

package/tests/features/device-control.feature

@@ -1,100 +0,0 @@
-Feature: Device Control
-  As a Home Assistant user
-  I want to control my smart home devices through the MCP server
-  So that I can manage my home automation
-
-  # Light Control
-  Scenario: Turn on a light
-    Given a light entity "light.living_room" that is "off"
-    When I turn on the light
-    Then the light service "turn_on" should be called
-    And the target should be "light.living_room"
-
-  Scenario: Turn on a light with brightness
-    Given a light entity "light.bedroom"
-    When I turn on the light with brightness 75%
-    Then the light service "turn_on" should be called
-    And the service data should include brightness_pct 75
-
-  Scenario: Set light color temperature
-    Given a light entity "light.kitchen"
-    When I set the color temperature to 4000K
-    Then the light service "turn_on" should be called
-    And the service data should include color_temp_kelvin 4000
-
-  Scenario: Set light RGB color
-    Given a light entity "light.office"
-    When I set the RGB color to red (255, 0, 0)
-    Then the light service "turn_on" should be called
-    And the service data should include rgb_color [255, 0, 0]
-
-  # Climate Control
-  Scenario: Set thermostat temperature
-    Given a climate entity "climate.living_room"
-    When I set the temperature to 22 degrees
-    Then the climate service "set_temperature" should be called
-    And the service data should include temperature 22
-
-  Scenario: Set HVAC mode to heat
-    Given a climate entity "climate.bedroom"
-    When I set the HVAC mode to "heat"
-    Then the climate service "set_hvac_mode" should be called
-    And the service data should include hvac_mode "heat"
-
-  Scenario: Set climate preset mode
-    Given a climate entity "climate.office"
-    When I set the preset mode to "eco"
-    Then the climate service "set_preset_mode" should be called
-    And the service data should include preset_mode "eco"
-
-  # Media Player Control
-  Scenario: Play media player
-    Given a media player entity "media_player.living_room"
-    When I play the media player
-    Then the media_player service "media_play" should be called
-
-  Scenario: Pause media player
-    Given a media player entity "media_player.bedroom"
-    When I pause the media player
-    Then the media_player service "media_pause" should be called
-
-  Scenario: Set media player volume
-    Given a media player entity "media_player.kitchen"
-    When I set the volume to 50%
-    Then the media_player service "volume_set" should be called
-    And the service data should include volume_level 0.5
-
-  # Cover Control
-  Scenario: Open a cover
-    Given a cover entity "cover.garage_door"
-    When I open the cover
-    Then the cover service "open_cover" should be called
-
-  Scenario: Close a cover
-    Given a cover entity "cover.blinds"
-    When I close the cover
-    Then the cover service "close_cover" should be called
-
-  Scenario: Set cover position
-    Given a cover entity "cover.living_room_blinds"
-    When I set the cover position to 50%
-    Then the cover service "set_cover_position" should be called
-    And the service data should include position 50
-
-  # Fan Control
-  Scenario: Turn on a fan
-    Given a fan entity "fan.bedroom"
-    When I turn on the fan
-    Then the fan service "turn_on" should be called
-
-  Scenario: Set fan speed
-    Given a fan entity "fan.living_room"
-    When I set the fan speed to 75%
-    Then the fan service "set_percentage" should be called
-    And the service data should include percentage 75
-
-  Scenario: Toggle fan oscillation
-    Given a fan entity "fan.office"
-    When I enable oscillation
-    Then the fan service "oscillate" should be called
-    And the service data should include oscillating true