VaDa SmartHouse

Showing 25 of 30 from the live probe.

• Analizar escenarios energéticos con VaDa Genius

  Read-only VaDa Genius tool for one home-energy decision: investment path, PV size, solar/load alignment, EV fit or quote review. Select one decision_kind using quote > EV > sizing > alignment > general. Trust returned calculations, evidence labels, eligibility, ordering, blocked claims and data_sufficiency; never recreate or rerank scenarios. If the user requests a chart, set presentation=native_charts and use only returned visual_insights. quality_partial means incomplete coverage, not automati

• Get authenticated SolarBrain user

  Use this when the user asks to test Auth0, verify SSO, check which SolarBrain user is logged in, or confirm whether ChatGPT is sending an authenticated OAuth token to the MCP server. This tool requires OAuth when Auth0 is enabled.

• Planificar tus horas solares

  Use when the user asks when PV normally exceeds home consumption, reaches equilibrium, surplus starts or ends, whether the window is stable or fragmented, about today, at least X W, or one appliance. This is the only Energy Balance tool. Set threshold_w=0 unless an explicit margin is requested. Appliance profiles are typical hypotheses; never turn historical margin into guaranteed device power or full-cycle coverage. Insufficient is a valid result. Lead with the domestic conclusion and evidence;

• Get current energy state

  Use this when the user asks what is happening right now with PV production, home load, grid import/export, battery state, or current energy balance, including questions such as 'como esta la bateria ahora'. This returns data only, without the house widget.

• Get solar forecast

  Use this when the user asks about solar generation today, tomorrow, remaining solar energy, the best solar hour, or solar production windows.

• Get energy prices

  Use this when the user asks for the current electricity price, today's cheapest or most expensive hours, tomorrow's prices, or whether to move consumption today. For a complete hourly day, a graph or visual of today's prices, yesterday, a month, a custom range, or P1/P2/P3 averages, use solarbrain_get_energy_price_range. Price data comes from the published hourly catalog independently of household telemetry. Answer only the price question unless the user also asks about battery, weather, or auto

• Get energy prices for a date range

  Use this when the user asks for a complete hourly price series or graph for today, or for prices over explicit or inferable date ranges such as yesterday, today and yesterday, this month, last month, P1/P2/P3 averages, cheapest or most expensive hours in a range, or comparisons across days. date_from and date_to are inclusive local dates. This reads the published price catalog independently from household telemetry and returns at most one semantic visual_insight for short ranges. Answer only the

• Get battery forecast

  Use this when the user asks whether the battery will charge fully, expected state of charge, evening discharge risk, battery forecast for today, or battery evolution by hour. Prefer human, by-hour reasoning when the backend returns hourly battery data.

• Get daily SolarBrain outlook

  Use this when the user asks how today is going: solar generated so far, solar now, remaining forecast, battery outlook, export/import risk, or a short daily energy briefing. This is energy-only for the authenticated installation; use device tools for configured or active VaDa automations.

• Show live SolarBrain house snapshot

  Use this only when the user asks for the visual house dashboard or explicitly asks about 'la casa' as a whole, for example 'muestrame la casa', 'como va la casa', or 'estado de la casa'. For direct questions about battery, solar production, grid, or what is switched on now, use the data/list tools instead.

• Get active control state

  Use this for Smart/EV installations when the user asks 'que hay encendido ahora', what VaDa has switched on now, which flexible loads are active, how much controlled power is running, or asks for a list/table of active devices. Use user_summary_es and active_assets for user-facing wording, locations, power, and timing fields when available; avoid technical IDs and avoid saying 'activos controlados encendidos'.

• Get configured assets

  Use this when the user asks what VaDa devices are configured, how they are named, where they are, their trigger availability, priority rules, average power, start/stop delays, or whether they are available now. This is read-only configuration; do not use it to switch devices on or off. Use display_name and location in answers, never technical IDs.

• Recommend manual load timing

  Use this when the user asks whether to run a manual load now or today, such as a washing machine, dishwasher, dryer, oven, iron, or custom appliance.

• Get VaDa Genius energy profile

  Use this when the user asks what VaDa Genius knows about their connected energy profile or since when energy readings exist: installation, data sources, first and last observed reading, billing context, contracted power P1/P2, and capabilities. history_availability is an observed extent only; continuity is not assessed. It is read-only and focuses on energy context, not civil identity.

• Plan flexible household loads

  Use this when the user asks what to run today or tomorrow, in what order, or when to place flexible loads such as washing machine, dishwasher, dryer, oven, iron, pool, air conditioning, or a custom appliance. This is read-only advice and never switches devices. For SMART/EV installations, first separate loads already active/configured in VaDa from manual loads; do not tell the user to start something VaDa is already managing.

• Assess PV or battery upgrade

  Use this when the user asks whether it is worth adding solar panels, expanding PV, adding battery capacity, or reviewing whether the installation is well sized. Provide an explicit date range and return evidence, caveats, and next steps. For contracted-power questions use the contracted-power tool.

• Assess EV readiness from export surplus

  Use this when the user asks whether an electric car makes sense with their current installation, how many electric kilometers exported surplus could cover, or what EV usage could fit historical surplus. If the profile is DataDis/grid_only, call it exportacion a red or excedente visible, not measured solar surplus.

• Explain an energy anomaly

  Use this when the user asks why something happened in their energy data, such as unusual import, export, low solar, high consumption, battery behavior, or an unexpected time slot. Use target_date and optional local times when the question is about a specific window.

• Get daily operational summary

  Use this when the user asks about yesterday, today so far, a daily historical recap, or 'como fue ayer': solar generated, house consumption, grid import/export, battery behavior, device activation availability, and estimated variable cost. Do not answer that yesterday is unavailable before calling this tool for date_preset=yesterday.

• Get period operational summary

  Use this when the user asks about this month, last month, monthly history, 'este mes', or 'el mes pasado'. This returns the backend semantic analytics summary: measured house consumption when DataDis import is valid as consumption, grid import/export, contract context, data-quality flags such as export_anomaly, and known missing dimensions. Prefer this over raw monthly telemetry for DataDis/grid_only installations.

• Get VaDa Genius energy patterns

  Use this when the user asks about historical energy patterns over a date range: hourly profile, night use, weekend vs weekday behavior, solar-window alignment, peak hours/days, or load-shifting opportunities. This is read-only pattern analysis; use contracted-power tools for P1/P2 decisions.

• Get VaDa Genius opportunity cards

  Use this when the user asks what VaDa Genius recommends next: solar, battery, EV, tariff, automation, or contracted-power opportunities. It returns read-only opportunity cards with evidence, assumptions, missing data, risks, and next actions for an explicit date range.

• Analyze contracted power demand

  Use this when the user asks whether to lower or raise contracted power, or about P1/P2, maximeter, grid-demand peaks, risk, or savings. Request a wide range, but treat period.days_covered as requested calendar days only. Use historical_coverage for real observed dates and valid days, decision_readiness for recommendation versus hypothesis, and each period's recommended_kw or candidate_kw without mixing them. The basis is power demanded from the grid, not total house consumption; house_max_kw is

• Estimate VaDa Genius reference solar production

  Use this when the user asks for solar reference production, PVGIS/JRC, solar potential, expected PV generation, or a kWp scenario. It estimates European reference production for a date range and scenario. For measured-vs-reference comparisons, also use measured history tools.

• Get energy summary for a custom date range

  Use this for measured energy totals over a custom date range: year-to-date, a season, summer/winter windows, Semana Santa, or any from/to period. Provide inclusive YYYY-MM-DD dates and granularity. For cohort comparisons, use the cohort tool.