CropWatch Knowledge Base
EN English

Reading the dashboard

The dashboard answers one question: is everything all right? This guide explains every part of it, and what to do when something is not.

On this page

What you see when you sign in

The dashboard: a search box, the Table and Sensor Cards buttons, and a location card for North Field marked Warning, holding four sensor cards, one of them showing Sensor Error

One card per location, with its sensors inside.

One card per location, with its sensors inside.

The dashboard is the first thing CropWatch shows you, and it answers one question above all others: is everything all right?

It has two views, chosen with the two buttons at the top. “Table” is a list with one row per sensor. “Sensor Cards” gives each location a card of its own, with its sensors inside it, so you read the page location by location. The first time you open the dashboard on a computer it shows the table, and on a phone it shows the cards. After that it opens on whichever you picked last in that browser.

The search box runs the full width of the page, above everything else; on a phone it has a row to itself, with the two buttons underneath. In Sensor Cards view on a larger screen, two small icon buttons beside them change the layout: the first keeps the location cards in tidy rows, the second packs short cards up under each other so less space is left empty.

A sensor with no location set sits under “No location”. The cards load 20 locations at a time; if you have more, a “Load more” button at the bottom brings the next 20.

What one card tells you

The same sensor card closed and open: closed it shows the readings and a coloured edge, open it lists everything it sent with Last Seen at the bottom

Closed, then opened with Details.

Closed, then opened with Details.

A location card carries four things along its top:

  • A coloured dot: how the whole location is doing.
  • The location's name: where these sensors are.
  • A word beside the name: the same state in words, such as “Online” or “Warning”. It is the quickest read on the page.
  • An arrow at the right: opens that location's own page. See The location page.

Each sensor inside shows its name, up to two of its latest readings, and a coloured edge down the left. A small symbol beside each number says what it is, such as a thermometer for temperature or a drop for humidity and moisture. A relay shows 🟢 On or 🔴 Off; see Switching relays. A reading missing from the last message shows a dash, not a zero.

Clicking a sensor card opens its “Details”: every reading in its last message, by name, with “Last Seen” at the bottom saying how long ago that message arrived. On a soil sensor the probe's readings are called “Soil Temperature” and “Soil Moisture”, so they are not confused with the air readings some soil boards also send. A card you open stays open the next time you visit.

Under the details, the “Details” button opens the sensor's own page. On an air sensor you are allowed to write notes on, a small add-note button sits beside it; see Notes on readings.

Under the details, the “Details” button opens the sensor's own page. On an air sensor you are allowed to write notes on, a small add-note button sits beside it; see Notes on readings.

The colours, and what they mean

The four states: Online green, Warning amber, Offline red and Loading purple, each shown as a word and as an edge colour

A word on a location, an edge colour on a sensor.

A word on a location, an edge colour on a sensor.

The same four states appear twice over: as a dot and a word on a location card, and as the colour of the edge on each sensor card.

  • Green, Online. Readings are arriving as expected.
  • Amber, Warning. Only on a location: some of its sensors have gone quiet and some have not. Look inside to see which.
  • Red, Offline. Nothing has arrived for longer than it should have. On a location it means every sensor there has gone quiet.
  • Purple, Loading. Either CropWatch is still fetching it, or nothing has ever arrived from it. A newly installed sensor stays purple until its first reading.

“Last Seen”, and when to worry

Sensors do not report constantly. Each one sends a reading on its own schedule: every ten minutes, every half hour, whatever it was set to. So a gap of twelve minutes is perfectly healthy for a sensor that reports every fifteen.

CropWatch knows each sensor's schedule, or failing that the usual schedule for its model, and turns the card red once nothing has arrived for longer than that. If neither is recorded, it allows an hour. When a card goes red its readings fade, and a line under them says how long it has been, such as “Last seen 3h 07m ago”.

You do not have to reload the page to see a sensor come back. In Sensor Cards view the dashboard checks each sensor again when its next reading is due, and fetches everything again when you come back to the tab or the app, with “Loading devices…” over the cards while it does. The table view fetches again when you come back to the tab.

“Last Seen” inside a card's details counts up from the last message: “7m 05s”, “3h 07m”. The table view shows the same thing as a plain date and time instead.

A location's own page judges this its own way: it takes the sensor's own schedule plus one minute, and assumes ten minutes when the sensor has none recorded. A sensor that reports every half hour by its model's default can therefore read Offline there after eleven quiet minutes, while the dashboard still calls it Online.

When a sensor stops

A sensor card with a red edge reading Sensor Error where the readings would be

“Sensor Error” replaces the readings when the sensor reports a fault with itself.

“Sensor Error” replaces the readings when the sensor reports a fault with itself.

A red edge, with faded readings and a “Last seen … ago” line under them, means nothing recent has arrived. Open the card's details and “Last Seen” tells you how long it has been, which is usually the clue.

Two other signs mean something different:

  • “Sensor Error” in place of the readings: the sensor has reported a fault with itself. Contact support, and give them the DevEUI shown on the sensor's page.
  • A dash in place of one number: the last message did not carry that reading.

When a sensor has gone quiet, these are the usual causes, in the order worth checking:

  • The gateway is off or has lost its internet connection. If several sensors went quiet at the same moment, this is almost always why.
  • The sensor's battery is flat. One sensor, gone quiet on its own, often means this.
  • Something has changed between the sensor and the gateway: a door closed, a vehicle parked, equipment moved.

When a sensor has gone quiet, these are the usual causes, in the order worth checking:

Finding one sensor

Once there are more than a screenful of sensors, use the search box at the top. It works in both views and matches part of a sensor's name, part of its DevEUI, or part of a location's name; capital letters make no difference. The list narrows a moment after you stop typing. Any of these work:

  • The sensor's name, such as “Greenhouse 1”.
  • The location, such as “North Field”, which brings up everything there.
  • The long serial number, or just its last few characters, if you are holding the sensor and reading the label.

If your locations are sorted into groups, the menu on the left shows a “Dashboard Filters” panel while you are on the dashboard. Open it and pick a group under “Location Groups” to see only those locations; “All location groups” brings everything back. A location's group is set in its location settings.

The table view

The dashboard in Table view: columns for Name, Location, Group, Primary and Last Updated

The same sensors as a list, one row each.

The same sensors as a list, one row each.

“Table” swaps the cards for a list, one row per sensor: Name, Location, Group, Primary, Secondary and Last Updated. Press a row to open that sensor.

On a narrow screen some columns are left out to make room: Last Updated goes first, then Group, then Secondary, so a phone shows Name, Location and Primary. The list comes in pages of 25, and the controls under it move between pages or show 50 or 100 at a time.

It is the better view when you have many sensors. “Sensor Cards” brings the cards back, and CropWatch remembers which you chose.

“Primary” and “Secondary” are the first and second readings a sensor sends, and each cell names its reading, such as “Temperature: 21.4 °C”. A relay reads “Relay 1: 🟢 On”, and a soil sensor's temperature is labelled “Soil Temperature”.

Opening one sensor

Clicking a sensor opens its own page: the current readings, and a chart of how they have moved over time. Four buttons choose how far back to look: “Today Only”, “Last 24 Hours”, “Last 48 Hours” and “Last 72 Hours”. It opens on Today Only, which is why an early-morning visit can look sparse.

The figures on that page, the highest, the lowest and the average, are worked out for the stretch of time you picked, not for all time. Change the buttons and they change with it.

On an air temperature and humidity sensor, the table of readings at the bottom also marks each reading taken while an alert rule was set off, and has buttons for adding notes. What the sensor's page shows goes through it.

This is the screen for questions the dashboard cannot answer: whether last night was colder than the one before, whether the humidity always climbs at four in the morning, whether a problem is new.

This is the screen for questions the dashboard cannot answer: whether last night was colder than the one before, whether the humidity always climbs at four in the morning, whether a problem is new.

The rest of the menu

Down the left are the other screens:

  • Overview: how all your sensors, gateways and alerts are doing, summed up on one page. See The Overview page.
  • Dashboard: this page.
  • Locations: your locations and what is installed at each, which is the tidier way in when you have several.
  • Rules: being told when a reading crosses a limit. See Creating an alert rule.
  • Reports: regular summaries by email. See Creating a report.
  • Gateways: the boxes that carry your sensors' readings to the internet. See Gateways in the app.

Quick answers

  • A number looks wrong. Open the sensor and look at the chart. One odd reading among normal ones is usually noise; a step change that stays is usually real.
  • A card's details say “No data yet”. Nothing has ever arrived from it. New sensors show this until their first reading.
  • A card says “Sensor Error”. The sensor has reported a fault with itself. Contact support with its DevEUI.
  • Everything went red at once. Look at the gateway rather than the sensors.
  • A sensor is missing entirely. It may be at a location you do not have access to, or set to Disabled for you. Ask whoever manages your account.
  • The dashboard says “No devices”. That is also what a failed load looks like. Refresh the page before concluding anything.
  • The page looks out of date. Cards fetch each sensor's next reading when it is due, and both views fetch again when you come back to the tab. If something still looks stale, refresh the page.