{"owner":"al-one","repo":"hass-xiaomi-miot","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":[".agents/skills/hass-docs/SKILL.md",".agents/skills/miot-docs/SKILL.md"],"skills":{".agents/skills/hass-docs/SKILL.md":"---\nname: hass-docs\ndescription: Home Assistant documentation and helper\n---\n\n# Home Assistant Developer Docs\n\n## Ask context7\n```bash\nnpx -y ctx7 docs /home-assistant/developers.home-assistant \"How to ...\"\n```\n\n## Ask deepwiki\n```bash\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"home-assistant/developers.home-assistant\",\n  \"question\": \"How to ...\"\n}'\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"home-assistant/core\",\n  \"question\": \"How to ...\"\n}'\n```\n\n## About `mcporter`\nTo improve compatibility, use `npx -y mcporter` instead of `mcporter` when executing commands.\n",".agents/skills/miot-docs/SKILL.md":"---\nname: miot-docs\ndescription: Xiaomi Miot documentation and helper. Recommended to use when users submit an issue/PR.\n---\n\n# Xiaomi Miot\n\n## Ask deepwiki\n```bash\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"al-one/hass-xiaomi-miot\",\n  \"question\": \"How to adding entities to a device ?\"\n}'\n```\n\n## MCP Tools\n```bash\n# List MCP servers\nnpx -y mcporter --config .mcp.json list\n\n# List MCP tools\nnpx -y mcporter --config .mcp.json list <server_name>\nnpx -y mcporter --config .mcp.json list tools\n\n# Call MCP tool\nnpx -y mcporter --config .mcp.json call <server>.<tool> --args '{\"key\":\"val\"}'\nnpx -y mcporter --config .mcp.json call tools.device_specs --args '{\"model\":\"brand.type.model\"}'\n```\n\n## About `mcporter`\nTo improve compatibility, use `npx -y mcporter` instead of `mcporter` when executing commands.\n\n\n## Adding entities to a Device\nTo adding entities to a device in the Xiaomi MIoT integration, you'll need to modify the `DEVICE_CUSTOMIZES` dictionary in the `device_customizes.py` file.\n\n### Add Your Device Configuration\nAdd your device model to the `DEVICE_CUSTOMIZES` dictionary following the existing pattern:\n```python\nDEVICE_CUSTOMIZES = {\n    # ... existing devices ...\n    'your.device.model': {\n        'sensor_properties': 'temperature,relative_humidity',\n        'switch_properties': 'uv,switch',\n        'select_properties': 'mode',\n        # Add more entity mappings as needed\n    },\n}\n```\n\n### Available Entity Mapping Options\n> More customization options can be found at https://github.com/al-one/hass-xiaomi-miot/issues/600\n\n| Option | Description | Example |\n|--------|-------------|---------|\n| `sensor_properties` | Properties to expose as sensors | `temperature,humidity` |\n| `binary_sensor_properties` | Properties to expose as binary sensors | `motion_detected,door_state` |\n| `switch_properties` | Properties to expose as switches | `on,night_light` |\n| `select_properties` | Properties to expose as selects | `mode,fan_level` |\n| `number_properties` | Properties to expose as numbers | `target_temperature,volume` |\n| `button_actions` | Actions to expose as buttons | `reset_filter_life` |\n\n### Finding Property Names\nTo find the correct property names for your device:\n1. Use `tools.device_specs` MCP tool to get device specifications\n2. Look at the available services and properties\n3. Replace hyphens (`-`) with underscores (`_`) in service/property/action names\n\n## Notes\n- Consider using `exclude_miot_properties` to improve performance by excluding unused properties\n- For complex devices, you can use `chunk_coordinators` to optimize polling intervals\n- Pattern matching is supported (e.g., `*.aircondition.*` for all air conditioners)\n"},"files":{".agents/skills/hass-docs/SKILL.md":"---\nname: hass-docs\ndescription: Home Assistant documentation and helper\n---\n\n# Home Assistant Developer Docs\n\n## Ask context7\n```bash\nnpx -y ctx7 docs /home-assistant/developers.home-assistant \"How to ...\"\n```\n\n## Ask deepwiki\n```bash\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"home-assistant/developers.home-assistant\",\n  \"question\": \"How to ...\"\n}'\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"home-assistant/core\",\n  \"question\": \"How to ...\"\n}'\n```\n\n## About `mcporter`\nTo improve compatibility, use `npx -y mcporter` instead of `mcporter` when executing commands.\n",".agents/skills/miot-docs/SKILL.md":"---\nname: miot-docs\ndescription: Xiaomi Miot documentation and helper. Recommended to use when users submit an issue/PR.\n---\n\n# Xiaomi Miot\n\n## Ask deepwiki\n```bash\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"al-one/hass-xiaomi-miot\",\n  \"question\": \"How to adding entities to a device ?\"\n}'\n```\n\n## MCP Tools\n```bash\n# List MCP servers\nnpx -y mcporter --config .mcp.json list\n\n# List MCP tools\nnpx -y mcporter --config .mcp.json list <server_name>\nnpx -y mcporter --config .mcp.json list tools\n\n# Call MCP tool\nnpx -y mcporter --config .mcp.json call <server>.<tool> --args '{\"key\":\"val\"}'\nnpx -y mcporter --config .mcp.json call tools.device_specs --args '{\"model\":\"brand.type.model\"}'\n```\n\n## About `mcporter`\nTo improve compatibility, use `npx -y mcporter` instead of `mcporter` when executing commands.\n\n\n## Adding entities to a Device\nTo adding entities to a device in the Xiaomi MIoT integration, you'll need to modify the `DEVICE_CUSTOMIZES` dictionary in the `device_customizes.py` file.\n\n### Add Your Device Configuration\nAdd your device model to the `DEVICE_CUSTOMIZES` dictionary following the existing pattern:\n```python\nDEVICE_CUSTOMIZES = {\n    # ... existing devices ...\n    'your.device.model': {\n        'sensor_properties': 'temperature,relative_humidity',\n        'switch_properties': 'uv,switch',\n        'select_properties': 'mode',\n        # Add more entity mappings as needed\n    },\n}\n```\n\n### Available Entity Mapping Options\n> More customization options can be found at https://github.com/al-one/hass-xiaomi-miot/issues/600\n\n| Option | Description | Example |\n|--------|-------------|---------|\n| `sensor_properties` | Properties to expose as sensors | `temperature,humidity` |\n| `binary_sensor_properties` | Properties to expose as binary sensors | `motion_detected,door_state` |\n| `switch_properties` | Properties to expose as switches | `on,night_light` |\n| `select_properties` | Properties to expose as selects | `mode,fan_level` |\n| `number_properties` | Properties to expose as numbers | `target_temperature,volume` |\n| `button_actions` | Actions to expose as buttons | `reset_filter_life` |\n\n### Finding Property Names\nTo find the correct property names for your device:\n1. Use `tools.device_specs` MCP tool to get device specifications\n2. Look at the available services and properties\n3. Replace hyphens (`-`) with underscores (`_`) in service/property/action names\n\n## Notes\n- Consider using `exclude_miot_properties` to improve performance by excluding unused properties\n- For complex devices, you can use `chunk_coordinators` to optimize polling intervals\n- Pattern matching is supported (e.g., `*.aircondition.*` for all air conditioners)\n"},"items":[{"name":"SKILL.md","path":".agents/skills/hass-docs/SKILL.md","title":"hass-docs Skill","content":"---\nname: hass-docs\ndescription: Home Assistant documentation and helper\n---\n\n# Home Assistant Developer Docs\n\n## Ask context7\n```bash\nnpx -y ctx7 docs /home-assistant/developers.home-assistant \"How to ...\"\n```\n\n## Ask deepwiki\n```bash\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"home-assistant/developers.home-assistant\",\n  \"question\": \"How to ...\"\n}'\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"home-assistant/core\",\n  \"question\": \"How to ...\"\n}'\n```\n\n## About `mcporter`\nTo improve compatibility, use `npx -y mcporter` instead of `mcporter` when executing commands.\n","category":".agents","tokens":169},{"name":"SKILL.md","path":".agents/skills/miot-docs/SKILL.md","title":"miot-docs Skill","content":"---\nname: miot-docs\ndescription: Xiaomi Miot documentation and helper. Recommended to use when users submit an issue/PR.\n---\n\n# Xiaomi Miot\n\n## Ask deepwiki\n```bash\nnpx -y mcporter call mcp.deepwiki.com/mcp.ask_question --timeout 120000 --args '{\n  \"repoName\": \"al-one/hass-xiaomi-miot\",\n  \"question\": \"How to adding entities to a device ?\"\n}'\n```\n\n## MCP Tools\n```bash\n# List MCP servers\nnpx -y mcporter --config .mcp.json list\n\n# List MCP tools\nnpx -y mcporter --config .mcp.json list <server_name>\nnpx -y mcporter --config .mcp.json list tools\n\n# Call MCP tool\nnpx -y mcporter --config .mcp.json call <server>.<tool> --args '{\"key\":\"val\"}'\nnpx -y mcporter --config .mcp.json call tools.device_specs --args '{\"model\":\"brand.type.model\"}'\n```\n\n## About `mcporter`\nTo improve compatibility, use `npx -y mcporter` instead of `mcporter` when executing commands.\n\n\n## Adding entities to a Device\nTo adding entities to a device in the Xiaomi MIoT integration, you'll need to modify the `DEVICE_CUSTOMIZES` dictionary in the `device_customizes.py` file.\n\n### Add Your Device Configuration\nAdd your device model to the `DEVICE_CUSTOMIZES` dictionary following the existing pattern:\n```python\nDEVICE_CUSTOMIZES = {\n    # ... existing devices ...\n    'your.device.model': {\n        'sensor_properties': 'temperature,relative_humidity',\n        'switch_properties': 'uv,switch',\n        'select_properties': 'mode',\n        # Add more entity mappings as needed\n    },\n}\n```\n\n### Available Entity Mapping Options\n> More customization options can be found at https://github.com/al-one/hass-xiaomi-miot/issues/600\n\n| Option | Description | Example |\n|--------|-------------|---------|\n| `sensor_properties` | Properties to expose as sensors | `temperature,humidity` |\n| `binary_sensor_properties` | Properties to expose as binary sensors | `motion_detected,door_state` |\n| `switch_properties` | Properties to expose as switches | `on,night_light` |\n| `select_properties` | Properties to expose as selects | `mode,fan_level` |\n| `number_properties` | Properties to expose as numbers | `target_temperature,volume` |\n| `button_actions` | Actions to expose as buttons | `reset_filter_life` |\n\n### Finding Property Names\nTo find the correct property names for your device:\n1. Use `tools.device_specs` MCP tool to get device specifications\n2. Look at the available services and properties\n3. Replace hyphens (`-`) with underscores (`_`) in service/property/action names\n\n## Notes\n- Consider using `exclude_miot_properties` to improve performance by excluding unused properties\n- For complex devices, you can use `chunk_coordinators` to optimize polling intervals\n- Pattern matching is supported (e.g., `*.aircondition.*` for all air conditioners)\n","category":".agents","tokens":683}]}