Linux 软件免费装
Banner图

Veloxa Solar Widget

开发者 wpveloxa
更新时间 2026年10月14日 15:00
PHP版本: 8.1 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

energy solar home assistant photovoltaic inverter

下载

详情介绍:

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 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 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 Agency — for installers 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.

安装:

  1. Install and activate the plugin.
  2. Go to Solar Widget → Connections and add a data source.
  3. Switch on "Show on public pages" for the source when you want visitors to see it.
  4. Add the "Solar production" block to a page, or use a shortcode such as [veloxa_solar widget="summary"].

屏幕截图:

  • A Generic REST source — each value points at its place in the JSON response, with the unit the API uses.
  • A push channel — the address, the token, ready-to-use curl and Home Assistant examples, and "Check if data arrives".
  • Choosing Home Assistant sensors — only sensors that match each value by type and unit are listed.
  • The Summary widget on a page — current power, energy today and total energy, with the time of the last update.
  • The "Solar production" block in the editor, with the widget, data source and style settings.
  • Pro: the daily production chart.
  • Pro: the full-screen display on a TV in a reception area.
  • Pro: energy flow — solar, home, battery and grid with the direction of each flow.
  • Pro: production history for the last 30 days and statistics.

常见问题:

Which shortcode attributes are available?

[veloxa_solar widget="power|today|total|summary|battery|co2" connection="ID" style="card|minimal" label="Your label"]. Pro adds widget="chart|flow|history|stats", with period="30d|12m|year" for history and show="year,total,best_day,max_power" for statistics. Agency adds widget="portfolio" with show="power,today,total,co2,list" and optionally connections="id1,id2" (by default all data sources shown on public pages). The connection attribute takes the connection's ID, shown under its name on the Solar Widget → Connections screen. The ID never changes, so renaming a connection does not break your shortcodes or the full-screen display address. With only one data source, connection can be left out. An unknown value shows editors a message with the allowed values.

How is the avoided CO₂ calculated?

Energy produced × an emission factor: the amount of CO₂ one kWh of grid electricity causes where the installation is. The default is 0.7 kg CO₂ per kWh, about the Polish grid according to KOBiZE. Set the factor for your country or your energy supplier under Solar Widget → Connections → Settings. The widget always shows the factor it used — it is an estimate, not a measurement.

Is the data real-time?

No. Inverter clouds and gateways update every few minutes, so the widgets show the current production with the time of the last update.

My site gets few visitors. Will the data still refresh?

The plugin refreshes data with WP-Cron, which WordPress runs only when someone opens a page of your site. On a site with few visitors — for example one used only for a screen in your reception area — the data may be refreshed late. For such sites we recommend a real system cron job:

  1. Add define( 'DISABLE_WP_CRON', true ); to wp-config.php.
  2. Ask your host to run WP-Cron every 5 minutes, e.g. */5 * * * * wget -q -O - https://example.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1 or wp cron event run --due-now with WP-CLI.
Most hosting control panels have a "Cron jobs" screen for this. The Diagnostics screen warns you when a data source was refreshed much less often than set in the last 24 hours. Home Assistant and Solarman (Pro) data sources fill the gaps from their own history: daily totals for days without readings (Home Assistant keeps 10 days of history by default), the daily chart and the peak power — so the history and statistics stay complete even with few visitors.

Will many visitors cause many requests to my data source?

No. Visitors only read the last saved reading from your WordPress database — the plugin requests data in the background, once per the interval you set for each data source, however many people view the page. For Solarman (Pro) there is also a hard limit of 500 requests a day per APP ID.

Can I use the same Solarman APP ID for several plants or sites?

Yes. All plants with the same APP ID on one site share its daily request budget; the connection form shows the estimated number of requests and warns you when the refresh intervals are too short. Requests from another website using the same APP ID are not counted here — set longer intervals on both sites so that together they stay within your Solarman plan (the free plan allows 200,000 requests a year, about 548 a day).

My Home Assistant is on my home network.

If your website is on external hosting, it cannot reach your home network. Use Home Assistant Cloud (Nabu Casa) or your own reverse proxy, or send data to a push channel from a Home Assistant automation — the channel screen shows a ready-to-paste example. If your WordPress site runs in the same network as Home Assistant (for example on a Raspberry Pi at home), an administrator can enable "Allow local network addresses" in the settings at the bottom of the Solar Widget → Connections screen. Then an address such as http://homeassistant.local:8123 or http://192.168.1.10:8123 works. On multisite, only a network administrator can change this setting. Leave it off on regular web hosting.

Can I replace an API key or token without setting everything up again?

Yes. Click "Edit" next to the data source and enter the new key or token; fields you leave empty keep their current value. For push channels, "Generate a new token" on the channel screen replaces the token — the old one stops working immediately, and the collected values and history stay.

What happens to my data when I delete the plugin?

Nothing is removed unless you tick "Remove all plugin data when the plugin is deleted" in the plugin settings.

更新日志:

0.7.2 0.7.1 0.7.0 0.2.0 0.1.2 0.1.0