{ "server": { "transport": "stdio", "httpPort": 8000, "httpHost": "127.0.0.1" }, "devices": { "refreshIntervalMinutes": 60 }, "monitoring": { "enabled": false, "logFile": "./wyzer-mcp-requests.log" } } ``` Environment variable overrides: - `WYZER_HTTP_PORT` - HTTP server port (default: 8000) - `WYZER_HTTP_HOST` - HTTP server host (default: 127.0.0.1) ## Usage ### stdio Transport (Claude Desktop) ```bash node src/index.js ``` ### HTTP Transport (Home Assistant) The HA custom component requires the MCP server to be exposed over HTTP/SSE. Use `mcp-proxy` to bridge the stdio server. #### Install mcp-proxy ```bash brew install mcp-proxy ``` #### Start the proxy ```bash # Binds to all interfaces so Docker can reach it mcp-proxy --port 8081 --host 0.0.0.0 -- node /path/to/wyzer-mcp/src/index.js ``` ### Home Assistant Integration Tested with Home Assistant **2026.1.3**. 1. Copy the custom component to your HA config directory: ```bash cp -r custom_components/wyzer_mcp ~/.home-assistant/custom_components/ ``` 2. Restart Home Assistant 3. Add the integration: Settings → Devices & Services → Add Integration → "Wyze MCP" 4. Enter connection details: - Host: `host.docker.internal` (for Docker) or your Mac's IP - Port: `8081` #### Optional: Card-Mod and Theme This repo includes a [card-mod](https://github.com/thomasloven/lovelace-card-mod) JS file and a clean theme for customizing the HA frontend. To install: ```bash # Copy card-mod.js to HA www directory mkdir -p ~/.home-assistant/www cp card-mod.js ~/.home-assistant/www/ # Copy the clean theme mkdir -p ~/.home-assistant/themes cp themes/clean.yaml ~/.home-assistant/themes/ ``` Then add to your `configuration.yaml`: ```yaml frontend: themes: !include_dir_merge_named themes extra_module_url: - /local/card-mod.js ``` The included `configuration.yaml` shows a complete example with template sensors. #### Configure Devices Edit `custom_components/wyzer_mcp/devices.yaml` to define which devices appear in HA: ```yaml switches: # Plugs - id: my_plug name: My Plug device_id: "XXXXXXXXXXXX" # Wyze device ID (MAC address) device_type: plug # Wall Switches - id: my_switch name: My Switch device_id: "LD_SS1_XXXXXXXXXXXX" device_type: switch purifiers: # Air Purifiers (fan entity with preset modes + AQI sensor) - id: my_purifier name: My Purifier device_id: "CO_AP1_XXXXXXXXXXXX" thermostats: # Combined thermostat + plug (for space heaters) - id: my_thermostat name: My Thermostat device_id: "combined_CO_EA1_XXXXXXXXXXXXXXXXXXXXXXXX" plug_id: "XXXXXXXXXXXX" # Creates a separate heater switch entity ``` **Notes:** - Use the device ID (MAC address) rather than nickname for stability - `device_type` must be `plug` or `switch` to call the correct control API - For combined thermostats with `plug_id`, a separate "Heater" switch entity is created #### Entity Types The integration creates the following entity types: | Type | Platform | Description | |------|----------|-------------| | Plugs | `switch` | On/off control for Wyze plugs | | Wall Switches | `switch` | On/off control for Wyze wall switches | | Thermostats | `climate` | Temperature control, HVAC mode | | Heater Switches | `switch` | On/off control for plug in combined devices | | Air Purifiers | `fan` | On/off + preset modes (auto/sleep/min/mid/max/turbo), AQI attribute | | AQI | `sensor` | Air quality index reading per purifier | | API Status | `sensor` | Shows API rate limit info | #### Device Availability Devices show as "Unavailable" in HA if they haven't reported to Wyze in over 2 days. This is determined by the RSSI timestamp from the Wyze API. #### Auto-start mcp-proxy with launchd Create `~/Library/LaunchAgents/com.wyzer.mcp-proxy.plist`: ```xml Label com.wyzer.mcp-proxy ProgramArguments /opt/homebrew/bin/mcp-proxy --port 8081 --host 0.0.0.0 -- /opt/homebrew/bin/node /path/to/wyzer-mcp/src/index.js WorkingDirectory /path/to/wyzer-mcp RunAtLoad KeepAlive StandardOutPath /tmp/wyzer-mcp-proxy.log StandardErrorPath /tmp/wyzer-mcp-proxy.err ``` Then load it: ```bash launchctl load ~/Library/LaunchAgents/com.wyzer.mcp-proxy.plist ``` To stop/unload: ```bash launchctl unload ~/Library/LaunchAgents/com.wyzer.mcp-proxy.plist ``` #### Managing the service ```bash # Check status launchctl list | grep wyzer # View logs tail -f /tmp/wyzer-mcp-proxy.err # Restart launchctl unload ~/Library/LaunchAgents/com.wyzer.mcp-proxy.plist launchctl load ~/Library/LaunchAgents/com.wyzer.mcp-proxy.plist # Stop launchctl unload ~/Library/LaunchAgents/com.wyzer.mcp-proxy.plist ``` ### Claude Desktop Integration Add to `~/.claude/claude_desktop_config.json`: ```json { "mcpServers": { "wyzer": { "command": "node", "args": ["/path/to/wyzer-mcp/src/index.js"], "env": {} } } }

Wyzer MCP Server

Installation