--- name: ecowitt-station description: Use the unofficial ecowitt-weather MCP tools when the user asks about current indoor, tent, or outdoor conditions, VPD-relevant temperature and humidity (temp/RH), or recent EcoWitt station history (e.g. a GW3000). Call get_current_reading, get_history, or get_device_info; never invent sensor data. --- # EcoWitt station This skill and plugin are unofficial and are not affiliated with EcoWitt. Tools from the `ecowitt-weather` MCP server wrap the EcoWitt Cloud API v3 for the configured gateway (typically a GW3000). They need the plugin variables `ECOWITT_APPLICATION_KEY`, `ECOWITT_API_KEY`, and `ECOWITT_MAC`. If a tool says a variable is not set, tell the user where to create keys (ecowitt.net account settings → API) and how to find the station MAC on the device dashboard. Do not guess readings. ## When to call which tool - Current tent, indoor, or outdoor conditions, including temperature, humidity, dew point, feels-like, pressure, wind, rain, solar/UV, or extra sensors the station actually reports → `get_current_reading`. - VPD or other psychrometric questions that need a paired temp/RH snapshot → `get_current_reading` first (use `indoor` and any present `extra.temp_and_humidity_ch*` channels; `outdoor` only if the reading includes it). Compute VPD from the returned values; do not invent a VPD the API did not provide. - Recent trends ("what was it this afternoon", "last 24 hours", a date range) → `get_history` with `start_date`, `end_date`, and a `cycle_type` of `5min`, `30min`, `4hour`, or `auto`. Dates are the station's local timezone; ISO timestamps are converted automatically. Narrow `fields` when only some metrics are needed (e.g. `["indoor", "temp_and_humidity_ch1"]`). This gateway may have no `outdoor` / rain / wind group — use indoor plus `extra` channels. - "What station is this / is the gateway online / what's its timezone?" → `get_device_info`. Imperial units are the default (°F, inHg, mph, inches, W/m²). Pass `metric: true` for °C, hPa, m/s, mm. ## Rules - Never invent, interpolate, or reuse stale numbers as if they were live. If a tool errors or a group is missing from the StationReading, say so. - Only report extra channels (`temp_and_humidity_ch1..8`, `soil_ch1..8`, and similar) when they appear in the tool result. - Prefer `rain.source` from the reading (`rainfall_piezo` vs `rainfall`) rather than mixing the two. If `rain` is absent, the station has no rain sensor in the current payload. - `get_history` is bounded by EcoWitt retention and span limits (for example, `5min` data should be requested one day at a time). If the API rejects a window, shrink the range or use a coarser `cycle_type` instead of fabricating points.