⚙️ Settings

Start with Automation Cycle Interval and Pricing Data Cache. Keeping both around 60 seconds gives responsive rule decisions without excessive API traffic.

Inverter APIs often have stricter rate limits than local rule evaluation. A 5 minute inverter cache avoids unnecessary API pressure while automation can still run every minute using fresh-enough telemetry.

Each automation cycle evaluates rules using the latest available cached values. If a cache has expired, that source is refreshed first, then used by the same cycle.

Recommended baseline: 60s automation, 60s pricing, 5m inverter, 30m weather. Adjust only if you have a clear need for faster or slower refresh behavior.

Common use cases include:
• Overnight quiet hours — Pause automation from 11pm-6am when you don't want mode changes
• Scheduled maintenance — Temporarily disable automation during system updates
• Peak demand events — Prevent discharge during grid emergencies when you want to keep battery full

Yes! A window from 22:00 to 06:00 correctly spans midnight. The system understands that the end time is on the following day.

Automation cycles are completely skipped — no rules are evaluated and no actions are taken. Your inverter continues running in whatever mode it was in before the blackout started.

During each automation cycle (every 1 minute by default), the system checks if:
• Curtailment is enabled
• Current feed-in price is below your threshold
If both conditions are met, export power is set to 0 watts.

When the feed-in price rises above your threshold, export power is automatically restored to 12000 watts (normal operation). The system tracks state to avoid sending redundant commands to your inverter.

Curtailment runs AFTER automation rules in each cycle. If a rule updates your scheduler segments, curtailment will execute afterward. Both can operate in the same cycle without conflict.

If the system can't update export power (e.g., inverter offline, API error), an alert will appear on your dashboard. The automation cycle continues normally — curtailment errors don't disrupt rule execution.

Your weather location determines the local timezone, sunrise/sunset times, and cloud cover forecasts — all critical for solar production predictions. Getting the location correct ensures automation reacts appropriately to local weather conditions. For example, a forecast heavy rain in your area will reduce solar output and might trigger battery discharge modes to maximize export during remaining sunny hours.

Location determines the actual sunrise/sunset times and cloud cover for your area. If you set a rule like "Discharge during peak export hours", the system uses your location to calculate when peak sun is expected. Wrong location = wrong time windows = suboptimal discharge timing. Additionally, timezone information from your location is used to align with local electricity-market data (pricing providers use local times).

The system will fetch new weather data for the new location on the next update cycle. Historical weather data for the old location is discarded, and your weather cache resets. Automation rules will immediately start using the new sunrise/sunset times and timezone. No manual adjustment needed.

Weather forecasts typically update hourly from data providers. A 30 minute cache reduces unnecessary API calls while keeping your forecast fresh enough for automation decisions. Shorter caching would hit rate limits; longer caching might miss rapid weather changes like sudden cloud cover.

Currently, the system accepts location names (e.g., "Sydney, Australia"). The weather provider resolves the name to coordinates internally. Using specific addresses or coordinates isn't supported, but city/state is precise enough for weather forecasting.

6 days (default) is ideal for most users — it's enough to plan weekly without overwhelming the UI. If you want to see longer-term trends, increase to 10-16 days. For real-time operation focused on today/tomorrow, reduce to 2-3 days.

Check the nameplate on your inverter or its datasheet. It is often labelled Rated AC Output Power. Common sizes are 5, 8, 10, 12 and 15 kW.

Usable capacity is the energy available between the minimum and maximum state-of-charge limits (often 10%–90% of rated capacity). For a 50 kWh pack at 10–90%, usable = 80% × 50 = 40 kWh. Check your battery's technical spec sheet.

Cooldown prevents a rule from triggering repeatedly in quick succession. For example, if prices fluctuate around your threshold, a 5 minute cooldown prevents the rule from toggling on/off every cycle. This protects your battery from excessive cycling.

When a rule triggers, it creates a scheduler segment lasting this many minutes. After the duration expires, the inverter returns to its default mode. 30 minutes is a good balance for most price arbitrage scenarios.

This controls how fast your battery charges/discharges. 5000W is typical for most home setups. Lower values (3000W) are gentler on the battery; higher values (7000-10000W) maximize throughput but increase wear.