Veloxa Solar Widget

Veloxa Solar Widget is a presentation layer for photovoltaic data you already monitor elsewhere. It is not a monitoring system: it takes the data your inverter cloud, gateway or Home Assistant already has and shows it nicely on your website — on a company page, in a case study, or on a screen in your reception area.

Free and Pro

Free
Pro
Agency

Widgets: current power, energy today, total energy, summary, battery, avoided CO₂
✓
✓
✓

Data sources: Generic REST / JSON, push, Home Assistant, SolaX Cloud (beta)
✓
✓
✓

Number of installations, data sources and widgets
unlimited
unlimited
unlimited

Daily production chart
—
✓
✓

Production history (30 days, 12 months, this year) and statistics
—
✓
✓

Full-screen display for a TV or tablet
—
✓
✓

Energy flow: solar, home, battery and grid in one diagram
—
✓
✓

Solarman cloud data source (your own Solarman API access)
—
✓
✓

SolarEdge cloud data source (beta)
—
✓
✓

“Our installations”: all your installations in one widget
—
—
✓

Add every plant of a Solarman account at once
—
—
✓

Your branding: company name, logo and brand colour
—
—
✓

The free version has no limits: add as many installations, data sources and widgets as you need.

Widgets

• Current power (e.g. 4.82 kW)
• Energy today (e.g. 24.8 kWh)
• Total energy, scaled automatically (e.g. 38.4 MWh)
• Summary — all three in one card
• Battery — charge level and whether it is charging, discharging or idle, with the charging/discharging power
• Avoided CO₂ — the emissions your solar production has saved so far and today, as an estimate with the emission factor shown

Every widget is available as a block and as a shortcode, shows when the data was last updated, and marks data as out of date when the source stops sending it. Data sources refresh roughly every 5 to 15 minutes, so widgets show the current production — not a real-time feed. A widget is offered only for values your source actually provides: no battery in the source means no battery value to choose, not a zero.

Data sources

• Generic REST / JSON — any cloud API that returns JSON. Point each value at its place in the response with a dot path (e.g. result.acpower) — or add several together with + (e.g. result.powerdc1+result.powerdc2) — and pick the unit the API uses; the plugin converts it.
• Push — your device, script or Home Assistant automation sends readings to your site. Each channel has its own token, which you can replace at any time.
• Home Assistant — sensors are offered by their type and unit. For Solarman/Sofar they are pre-selected; for Huawei Solar, Fronius, GoodWe, SMA, Enphase, SolarEdge and similar integrations they are pre-selected by their names (beta) — check them before saving. Gaps caused by rare refreshes are filled from Home Assistant’s own history.
• SolaX Cloud (beta) — enter the token ID from SolaxCloud (Service → API) and the registration number of the dongle; solar power, energy, battery and grid are mapped for you.

You can edit every data source later — for example, replace an API key or a Home Assistant token — without losing its settings or breaking the widgets that use it.

Pro

• Daily production chart built from the history the plugin collects.
• Production history — daily bars for the last 30 days, or monthly bars for the last 12 months or this year. A day without data is shown as a gap, never as zero; estimated days and the current, incomplete day or month are marked.
• Statistics — production this year, total production since data collection started, the best day and the peak power. Choose which items are shown publicly.
• Full-screen display at an address such as /solar-display/your-connection-id/ for a TV or tablet in your reception area — large type, refreshing automatically, without the theme’s navigation. Three layouts (summary; energy flow with battery; flow with today’s chart and statistics), dark or light, for landscape TVs and portrait tablets. When data stops arriving or the screen loses its network connection, it says so and resumes by itself.
• Energy flow — solar panels, home, battery and grid on one diagram, with the direction of each flow. Shown when your source reports the solar power and the home consumption; parts your source does not report (for example no battery) are left out.
• SolarEdge cloud data source (beta) — reads solar power, energy today and total, and — with a meter — home consumption, grid and battery, using the site API key from the SolarEdge monitoring portal (or an installer’s account key; Agency: add every site at once). Refreshes every 15 minutes by default to stay within SolarEdge’s 300 requests a day.
• Solarman cloud data source — reads solar power, home consumption, battery and grid directly from the Solarman cloud, without Home Assistant or a custom API mapping. Requires your own Solarman API access (APP ID and APP SECRET, requested from Solarman support) and your Solarman account login. Energy today is calculated from the inverter’s total energy counter. When your site has few visitors and data is refreshed rarely, the plugin fills the gaps from Solarman’s own history: exact daily totals, energy today and the 5-minute readings for the daily chart and peak power.

Agency — for installers

• “Our installations” — all your public installations in one widget: how much they produce right now, energy today, total energy and avoided CO₂, with a list of the installations and their current power. Ideal for an installer’s “our projects” page.
• Solarman: add every plant of a Solarman account as a separate data source in one step, with refresh intervals that keep all plants within the daily request limit.
• Your branding — your company name and logo in the header of the full-screen display, and your brand colour for the chart line, the battery level and the history bars.

Beta data sources

SolaX Cloud, SolarEdge and the name-based Home Assistant suggestions are built from the manufacturers’ documentation and have not yet been confirmed on a real installation of each type. They are marked “beta”. Compare the values with the manufacturer’s app; the plugin also checks every reading of a beta source (for example energy today larger than total energy, negative solar power, battery outside 0–100 %, a daily counter going down) and writes problems to the Diagnostics error log. The raw values received are shown on the data source’s edit screen — if something is wrong, send them with the diagnostic report and we will correct the mapping. Nothing is sent anywhere automatically.

Home consumption

Use your source’s own home consumption value when it has one. If it does not, the plugin estimates it as solar power + power taken from the grid − battery charging power (grid: positive when taking power from the grid; battery: positive when charging), and marks the value with “≈” and this formula wherever it is shown.

Privacy by default

Solar production can reveal when people are at home. Widgets of a data source are hidden from visitors until you switch on “Show on public pages” for that source. Public widgets show only the values themselves — never the source address, keys or raw API responses.

Performance

Data is fetched in the background (WP-Cron) and served from the database. A visitor loading a page never triggers a request to your data source.

Diagnostics

The Diagnostics screen shows whether each data source is up to date, when it was last measured and refreshed, the background tasks and the most recent errors. One button copies it all as a text report for a support request — without addresses, tokens or API keys.

External services

This plugin connects to one service that is not the data source you configure yourself:

• Freemius (licensing, update delivery, and — if you opt in — basic usage analytics). On first activation you’re asked whether to allow anonymous diagnostic data (server environment, WordPress/PHP version, plugin version, site URL) to be sent — you can decline, and review/opt out again later from your account on freemius.com. No data about your data sources, installations, or the production values they return is ever included. Terms of Service, Privacy Policy.

Every other outbound request goes only to the addresses you configure:

• Generic REST sources: the API URL you enter, with the authorization header you enter. The plugin requests it in the background at the interval you set (at least every 5 minutes) to read your production data. Refer to your data provider’s terms of use and privacy policy.
• Home Assistant: the Home Assistant address you enter, using the access token you enter, to read the states of the sensors you choose — when you set up the connection and then in the background at the interval you set — and, when readings are missing, the recorded history of those sensors.

• Solarman (Pro only, when you add a Solarman data source): the Solarman cloud API at globalapi.solarmanpv.com. The plugin sends your APP ID, APP SECRET, account e-mail and a SHA-256 hash of your Solarman password to obtain an access token, then requests your plant’s current data in the background at the interval you set, and — a few times a day, when readings are missing — your plant’s daily and 5-minute history (at most 500 requests per day per APP ID in total). Solarman (IGEN Tech Co., Ltd.): Terms of Service, Privacy Policy.

• SolaX Cloud (when you add a SolaX Cloud data source): www.solaxcloud.com. The plugin sends your SolaxCloud token ID and the registration number of your inverter’s dongle to read its current data, in the background at the interval you set (SolaX allows 10 requests a minute and 10,000 a day). SolaX: Terms of Use, Privacy Policy.

• SolarEdge (Pro only, when you add a SolarEdge data source): monitoringapi.solaredge.com. The plugin sends your API key and site ID to read the site overview and current power flow, in the background at the interval you set (at most 280 requests a day per API key). SolarEdge: API Terms and Conditions, Privacy Policy.

Push channels receive data on your own site and send nothing out.

Network safety

For security, the plugin refuses to connect to local and private network addresses (such as 192.168.x.x or homeassistant.local) unless an administrator enables “Allow local network addresses” in the plugin settings. Link-local addresses used by cloud metadata services (169.254.x.x) are always blocked. Redirects are checked with the same rules.