1. Control Commands & Dispatch
FoxCloud OpenAPI
Vpp Flow
  • Vpp Flow
  • Full API Reference
  • What's New & Milestones
  • Getting Started
    • 1. Overview & Integration Scope
    • 2. Environments & Prerequisites
  • End-User Enrollment & OAuth Flow
    • 0. Introduction
    • 1. The User Authorization Journey
    • 2. OAuth Token Operating Model
    • 3. Implementation Guide
  • API Technical Specifications
    • 1. Universal Request Rules
    • 2. Rate Limiting Strategy
    • 3. Response Structure
    • 4. Error Code Reference
  • Telemetry & Data Acquisition
    • 1. Data Pipeline & Scaling Strategy
    • 2. Telemetry Data Query (Real-time)
    • 4. Telemetry Variable Dictionary
    • 5. System Performance & SLA
    • 3. Device Configuration & Settings: Pre-Dispatch State Awareness
  • Control Commands & Dispatch
    • 1. Core Dispatch Architecture: Scheduler V3
    • 2. Scheduler V3 Operations
    • 3. Real-time Device Settings
    • 4. Strategic Roadmap: Scaling for Massive Fleets
  • FAQ
    • Troubleshooting Quick Guide
  1. Control Commands & Dispatch

1. Core Dispatch Architecture: Scheduler V3

The core of VPP control is the Scheduler, which allows you to define specific charging, discharging, or export-limiting behaviors for devices over time.

1.1 The Segment Concept & Persistence#

The Scheduler operates on a Segment model. A segment defines a specific time window (e.g., 08:00 - 12:00) and the corresponding operational mode or power limit for that period.
️ Critical Logic: Device-Level Persistence
Scheduler instructions are stored directly on the device layer. They are not one-off commands.
Recurring Execution: If you send a schedule for 08:00 - 09:00, the device will execute this instruction every day during that time window, indefinitely.
How to Cancel: To clear all active schedules and stop recurring execution, you must explicitly send a clear command by passing an empty list ([]) to the scheduler enable endpoint.

1.2 API Version Strategy#

To ensure optimal performance and feature support, FoxCloud enforces a strict version strategy for the Scheduler APIs:
VersionStatusDescription
Scheduler V3RecommendedSupports granular segment control and batch asynchronous operations. All new integrations must use V3.
Scheduler V2️ CompatibilityMaintained strictly for legacy integrations requiring specific V2 logic.
Scheduler V1DeprecatedNot recommended. Retained only for older hardware. New projects must avoid using V1.
Modified at 2026-07-09 12:17:48
Previous
3. Device Configuration & Settings: Pre-Dispatch State Awareness
Next
2. Scheduler V3 Operations
Built with