Update to EVOLVIOT

{
  "description": "Discover, inspect, and control devices connected to the user's EVOLVIOT account. Use when the user asks about an EVOLVIOT device, room, device status, switch, fan, light, dimming level, or smart-home command.",
  "included_files": [],
  "name": "control-smart-home",
  "skill_md_contents": "---\r\nname: control-smart-home\r\ndescription: Discover, inspect, and control devices connected to the user's EVOLVIOT account. Use when the user asks about an EVOLVIOT device, room, device status, switch, fan, light, dimming level, or smart-home command.\r\n---\r\n\r\n# Control an EVOLVIOT smart home\r\n\r\nUse `list_devices` before a control operation whenever the exact device ID or\r\ncontrol key is not already established in the current conversation.\r\n\r\nMatch the user's room and device wording against device names and supported\r\ncontrol-key metadata returned by EVOLVIOT. Never invent a device ID, control\r\nkey, range, or enumerated value.\r\n\r\nBefore calling `control_device`, briefly state the concrete device, control,\r\nand value that will be changed. If more than one device is a plausible match,\r\nask the user which one they mean.\r\n\r\nUse values supported by the returned control metadata:\r\n\r\n- Translate “on” and “off” to `ON` and `OFF`.\r\n- Send a numeric percentage only when the control supports that range.\r\n- Use exact enumerated values for list-based controls.\r\n\r\nAfter a control call, report whether the device acknowledged the command. Do\r\nnot claim success when EVOLVIOT reports a timeout, validation error, offline\r\ndevice, or unavailable control.\r\n"
}