Workspace · Greenhouse · existing · connecting

Skyberries — strawberry greenhouse

The greenhouse records climate, substrate and yield in Let's Grow today. Connecting is one export job writing one file in the feed schema below; Calibrate then starts from real history and Operate is live from day one.

Site

Let's Grow → SOLARA mapping — stream by stream

Everything on the left exists in the grower's Let's Grow account today. The right column is where it lands in SOLARA's feed schema. No new sensors needed to start.

Stream (in Let's Grow)	Source	Status

The feed schema — the whole integration contract

One JSON file per site, overwritten on a schedule (API pull or scheduled CSV export — both work). This is the same schema the Farm32 Sardinia site runs on today.

{
  "site": "hic-main",
  "updated_iso": "2026-…",
  "source": "sensor-feed",
  "metrics": [
    { "key": "t_air", "label": "Air temperature",
      "value": 21.4, "unit": "°C",
      "target": 21.0, "status": "ok" },
    …
  ],
  "series": { "t_air_5min": [...] }
}

What lights up, in order

Each step needs only the previous one's data.

1 · Calibratefirst Let's Grow export (any length of history)	twin baseline: climate behavior, energy, yield per cycle
2 · Operatescheduled feed refresh	live dashboard vs the calibrated baseline — same page as Farm32 Sardinia
3 · Plana season of calibrated cycles + strawberry price curve	weekly planting/steering plan on the same MILP engine as the other workspaces

The ask

One decision: API access or a scheduled export from Let's Grow.

Both routes end in the same file. API access gives higher frequency and no manual steps; a scheduled CSV export is enough to start and can be set up in an afternoon. Either way, the Skyberries column appears in SOLARA the week the first file lands.