| 开发者 | wpveloxa |
|---|---|
| 更新时间 | 2026年10月14日 15:00 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
result.acpower) — or add several together with + (e.g. result.powerdc1+result.powerdc2) — and pick the unit the API uses; the plugin converts it.[veloxa_solar widget="summary"].[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.
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.
No. Inverter clouds and gateways update every few minutes, so the widgets show the current production with the time of the last update.
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:
define( 'DISABLE_WP_CRON', true ); to wp-config.php.*/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.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.
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).
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.
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.
Nothing is removed unless you tick "Remove all plugin data when the plugin is deleted" in the plugin settings.