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 \u2014 on a company page, in a case study, or on a screen in your reception area.<\/p>\n\n
Free and Pro<\/strong><\/p>\n\n Free<\/strong> \u2014 no limits: add as many installations, data sources and widgets as you need.<\/p>\n\n Pro<\/strong> \u2014 everything in Free, plus:<\/p>\n\n Agency<\/strong> \u2014 everything in Pro, plus:<\/p>\n\n Widgets<\/strong><\/p>\n\n 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 \u2014 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.<\/p>\n\n Data sources<\/strong><\/p>\n\n You can edit every data source later \u2014 for example, replace an API key or a Home Assistant token \u2014 without losing its settings or breaking the widgets that use it.<\/p>\n\n Pro<\/strong><\/p>\n\n Agency \u2014 for installers<\/strong><\/p>\n\n Beta data sources<\/strong><\/p>\n\n 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\u2013100 %, 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 \u2014 if something is wrong, send them with the diagnostic report and we will correct the mapping. Nothing is sent anywhere automatically.<\/p>\n\n Home consumption<\/strong><\/p>\n\n 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 \u2212 battery charging power (grid: positive when taking power from the grid; battery: positive when charging), and marks the value with \"\u2248\" and this formula wherever it is shown.<\/p>\n\n Privacy by default<\/strong><\/p>\n\n 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 \u2014 never the source address, keys or raw API responses.<\/p>\n\n Performance<\/strong><\/p>\n\n 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.<\/p>\n\n Diagnostics<\/strong><\/p>\n\n 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 \u2014 without addresses, tokens or API keys.<\/p>\n\n This plugin connects to one service that is not<\/strong> the data source you configure yourself:<\/p>\n\n Every other outbound request goes only to the addresses you<\/strong> configure:<\/p>\n\n 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 \u2014 a few times a day, when readings are missing \u2014 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<\/a>, Privacy Policy<\/a>.<\/p><\/li>\n 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<\/a>, Privacy Policy<\/a>.<\/p><\/li>\n Push channels receive data on your own site and send nothing out.<\/p>\n\n Network safety<\/strong><\/p>\n\n 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.<\/p>\n\n\n [veloxa_solar widget=\"power|today|total|summary|battery|co2\" connection=\"ID\" style=\"card|minimal\" label=\"Your label\"]. Pro adds Energy produced \u00d7 an emission factor: the amount of CO\u2082 one kWh of grid electricity causes where the installation is. The default is 0.7 kg CO\u2082 per kWh, about the Polish grid according to KOBiZE. Set the factor for your country or your energy supplier under Solar Widget \u2192 Connections \u2192 Settings. The widget always shows the factor it used \u2014 it is an estimate, not a measurement.<\/p><\/dd>\n No. Inverter clouds and gateways update every few minutes, so the widgets show the current production with the time of the last update.<\/p><\/dd>\n 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 \u2014 for example one used only for a screen in your reception area \u2014 the data may be refreshed late. For such sites we recommend a real system cron job:<\/p>\n\n Most hosting control panels have a \"Cron jobs\" screen for this.<\/p>\n\n 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 \u2014 so the history and statistics stay complete even with few visitors.<\/p><\/dd>\n No. Visitors only read the last saved reading from your WordPress database \u2014 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.<\/p><\/dd>\n 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 \u2014 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).<\/p><\/dd>\n 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 \u2014 the channel screen shows a ready-to-paste example.<\/p>\n\n 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 \u2192 Connections screen. Then an address such as 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 \u2014 the old one stops working immediately, and the collected values and history stay.<\/p><\/dd>\n Nothing is removed unless you tick \"Remove all plugin data when the plugin is deleted\" in the plugin settings.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
\n
\n
\n
result.acpower<\/code>) \u2014 or add several together with +<\/code> (e.g. result.powerdc1+result.powerdc2<\/code>) \u2014 and pick the unit the API uses; the plugin converts it.<\/li>\n\n
\n
External services<\/h3>\n\n
\n
\n
\n
[veloxa_solar widget=\"summary\"]<\/code>.<\/li>\n<\/ol>\n\n\n\n
Which shortcode attributes are available?<\/h3><\/dt>\n
widget=\"chart|flow|history|stats\"<\/code>, with period=\"30d|12m|year\"<\/code> for history and show=\"year,total,best_day,max_power\"<\/code> for statistics. Agency adds widget=\"portfolio\"<\/code> with show=\"power,today,total,co2,list\"<\/code> and optionally connections=\"id1,id2\"<\/code> (by default all data sources shown on public pages). The connection<\/code> attribute takes the connection's ID, shown under its name on the Solar Widget \u2192 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<\/code> can be left out. An unknown value shows editors a message with the allowed values.<\/p><\/dd>\nHow is the avoided CO\u2082 calculated?<\/h3><\/dt>\n
Is the data real-time?<\/h3><\/dt>\n
My site gets few visitors. Will the data still refresh?<\/h3><\/dt>\n
\n
define( 'DISABLE_WP_CRON', true );<\/code> to wp-config.php<\/code>.<\/li>\n*\/5 * * * * wget -q -O - https:\/\/example.com\/wp-cron.php?doing_wp_cron >\/dev\/null 2>&1<\/code> or wp cron event run --due-now<\/code> with WP-CLI.<\/li>\n<\/ol>\n\nWill many visitors cause many requests to my data source?<\/h3><\/dt>\n
Can I use the same Solarman APP ID for several plants or sites?<\/h3><\/dt>\n
My Home Assistant is on my home network.<\/h3><\/dt>\n
http:\/\/homeassistant.local:8123<\/code> or http:\/\/192.168.1.10:8123<\/code> works. On multisite, only a network administrator can change this setting. Leave it off on regular web hosting.<\/p><\/dd>\nCan I replace an API key or token without setting everything up again?<\/h3><\/dt>\n
What happens to my data when I delete the plugin?<\/h3><\/dt>\n
0.7.2<\/h4>\n\n
\n
0.7.1<\/h4>\n\n
\n
0.7.0<\/h4>\n\n
\n
0.2.0<\/h4>\n\n
\n
0.1.2<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n