Events and dispatch

How Texture sends instructions to your enrolled devices

To dispatch is to tell devices to change what they're doing, for example to discharge batteries during a peak. In Texture, you dispatch devices with a program event or a command.

Program events#

A program event is a dispatch you run for a program, such as a demand response event. It has:

• Targets: the devices on approved enrollments in the program, optionally narrowed to devices with a tag
• Actions: what the devices do, such as discharge a battery or stop charging, each with a start and end time
• A status: Draft, Scheduled, In Progress, or Completed

Texture runs the event in the window you set. It doesn't decide when an event should happen: the window comes from your grid operator, your program's rules, or your own planning.

Dates and times use your browser's time zone. Convert to your program's time zone before you enter them.

Where program events come from#

Which devices respond#

An event reaches devices on approved enrollments, but not every one will respond. A device may be:

• Disconnected: Texture no longer has access through the manufacturer connection
• Offline: the device itself isn't reachable
• Not able to take the action: for example, a charger can't receive a battery command

Check before you dispatch with Check device readiness before an event. After the event, see who responded in Read post-event reports.

Commands#

A command is a single instruction to one device or a group, such as setting a battery's reserve. Program events send commands for you. You can also send a command yourself from a device's page with Send Command. See Devices.

Not to be confused with#

• Webhook events are messages Texture sends to your systems when something changes, such as a device disconnecting. See Event types.
• Recent activity on a site or device page lists changes to that record, such as connection updates. These aren't program events.