How PyMox works, end to end.

The top-level container for topology, location, thermal parameters, and strategy.

• Location: latitude and longitude for solar and weather.
• Thermal mass and heat loss drive climate-aware loads.
• Strategy determines dispatch priorities.

DC or AC buses define voltage domains and capacity constraints.

• Loads, batteries, chargers, and grid connections attach to buses.
• Converters bridge buses with efficiency and standby cost.

Loads can be static or scheduled to reflect real behavior.

• Schedules describe HVAC, occupancy, daylight, and heating patterns.
• Schedules map to device-level consumption curves during simulation.

Batteries define capacity, SoC limits, and charge/discharge power.

• Daily rollups seed simulations and show real SoC history.
• Manual rollups can correct or backfill data.

Chargers represent power sources and connect to buses.

• Solar, wind, alternator, and generator chargers are supported.
• Each charger contributes generation to its bus by type.

Grid links define import/export power limits and event history.

• Grid events record connect/disconnect timelines.
• Forecasting can plan scheduled grid availability.

Loads represent everything that consumes power on a bus.

• Name and icon help you identify the device or category.
• Rated power sets the baseline draw used by the simulator.
• Power bus determines which voltage domain supplies the load.
• Power profile adds schedules and behavior curves for realistic demand.
• Enabled flag allows you to include or exclude the load in runs.

Batteries store energy and buffer peaks.

• Capacity (Wh) sets total available energy.
• Min and max SoC define usable energy limits and safety buffers.
• Max charge/discharge power caps how fast energy can move.
• Round-trip efficiency applies conversion loss during charge and discharge.
• Enabled flag includes or excludes the battery from dispatch.
• Daily rollups set the starting SoC baseline for simulations.

Chargers represent energy sources feeding a bus.

• Type determines generation behavior (solar, wind, alternator, generator).
• Max charge power sets a ceiling for produced energy.
• Efficiency applies conversion loss before power reaches the bus.
• Power bus defines where generated energy enters the system.
• Enabled flag controls whether the source participates in simulations.

Grid connections define how the system interacts with shore power.

• Max import power caps how much energy can be pulled from the grid.
• Max export power caps how much energy can be pushed back.
• Grid events record connection state changes used in simulations.
• Forecasting can model scheduled grid availability.
• Power bus defines the grid entry point.

Converters move energy between buses with limits and losses.

• Input and output buses define the direction of conversion.
• Max power caps how much energy can pass through each step.
• Efficiency reduces delivered power based on losses.
• Standby power adds constant overhead when enabled.
• Enabled flag decides whether the converter is active.

Onboarding or the System page creates buses, loads, storage, and sources.

Your components form a connected map that mirrors the real system.

Simulations evaluate each time step, dispatch, and energy routing.

Dashboards present SoC, runtime, grid impact, and forecasted risk.

Step-by-step setup for categories, strategy, sources, batteries, and loads.

• Captures location and thermal assumptions for climate-aware forecasting.
• Builds suggested buses and converter connections.
• Generates the first system for your team.

The system map and resource panels live here.

• Resource panels manage buses, loads, batteries, chargers, grid connections, and converters.
• System flow diagram shows the relationships between components.

A daily snapshot with SoC, runtime, and net power signals.

• Uses simulation results for the current day.
• Highlights net surplus or deficit with status labels.

Last 24 hours of grid, battery, and self-consumption performance.

• Combines grid import/export with battery rollups.
• Calculates estimated cost and backup runtime.

Plan days ahead with adjustable reserve, usage, and grid schedules.

• Supports manual battery rollups to refine the baseline.
• Lets you scale panel, battery, and load assumptions.

Explore ranges from today to 90 days with energy breakdowns.

• Tracks deep discharge events and deficit summaries.
• Compares solar, load, conversion loss, and grid impact.

Scenario dashboards for long-range planning.

• Resolution supports hourly, daily, monthly, and yearly views.
• Some views may show placeholders while scenario data is finalized.

Subscription management for teams with checkout and a billing portal.

• Plan selection and portal access are team-aware.

Team members, roles, and API tokens are managed in the account area.

• Teams gate access to shared systems and billing.
• API tokens use scoped permissions for integrations.

Daily SoC rollups establish the starting point for simulations.

• Sources include API and manual entries.
• Used for both SoC percent and kWh series.

Daily temperature rollups seed climate and HVAC demand modeling.

• Stored per system with min, max, and last temperature.

Forecasted outdoor temperatures inform climate-aware loads.

• Forecasting supports auto or overridden assumptions.
• SolarProductionEstimator uses location data.

Grid connection changes are stored as events.

• Events annotate simulations and chart overlays.
• Forecasting can plan grid availability schedules.

System resources keep configuration consistent across the app.

• Validates input types and converts percent fields.
• Manages charger subtypes and resource panels.

Charts render series built from your simulation and rollup data.

• Series and categories are built per view.
• Visual settings adjust per context.