Check device readiness before an event
Connected vs offline, and enrolled vs able to dispatch
Before an event, confirm that devices on Enrolled enrollments are online and the right type for the commands you plan to send. Use Programs → Monitoring.
- Open Programs → Monitoring.
- Select the program in the page header.
The map and metrics show devices on enrollments in the Enrolled stage for that program. If no devices appear, enrollments may still be incomplete or devices may not be linked yet. Check Understand your enrolled base.
Connection, state, and grid#
Use the view control above the map:
| View | What it shows |
|---|---|
| State | Operating state counts (for example charging, discharging, idle), depending on device type. This is the default view. |
| Grid | Grid interaction counts (importing, exporting, idle) where that applies. |
| Connection | How many devices are connected vs disconnected, plus uptime. Switch to this before an event. |
The map plots those devices; the legend explains the markers for the current view. The page refreshes automatically about every 30 seconds; use Refresh for an immediate update.
Offline or unreachable devices will not respond to dispatch even if the member is enrolled.
Enrolled vs able to dispatch#
These are not the same:
| Concept | Meaning |
|---|---|
| Enrolled | The member completed enrollment for the program (Enrolled stage). |
| Connected | The device is online and reporting. Visible under Monitoring → Connection. |
| Eligible to dispatch | The device type can receive the command you will send (for example batteries for battery operating-mode actions, chargers for charging-control actions). Ineligible device types are excluded when you build the event. |
A large enrolled count with a low connected count, or with devices that cannot take your planned action, means the event will under-deliver relative to enrollment headcount.
After the check#
When connected count and device mix look right for the window you plan to run, continue with Schedule an event.