News about SolarNetwork platform updates and new features.
SolarNetwork has added support for Cloud Integrations — the ability to acquire data from external systems, when you do not have a SolarNode edge device delpoyed to collect the data directly. Some device manufacturers have deployed their own cloud services that their devices publish data to, so a Cloud Datum Stream can help to get that data into SolarNetwork.
SolarNetwork has added the ability to control how aggregate datum streams are published to SolarFlux.
SolarNetwork has added a fully-managed HTTP integration service that allows arbitrary devices and systems to post arbitrary “messages” to SolarNetwork at a custom SolarNetwork URL that get converted into SolarNode instructions that execute immediately, with the instruction results converted into an external message response.
SolarNetwork has added a new FTP datum export destination service that allows you to export datum to URLs using FTP. The exports can be scheduled to run automatically (hourly, daily, weekly, or monthly) or they can be run on demand.
SolarNetwork has added a new HTTP datum export destination service that allows you to export datum to URLs using HTTP. The exports can be scheduled to run automatically (hourly, daily, weekly, or monthly) or they can be run on demand.
SolarNetwork has added a fully-managed HTTP integration service that allows arbitrary devices and systems to supply real-time measurements to SolarNetwork directly, converting them into datum streams , without using a SolarNode to collect the measurements. We call this service Datum Input Endpiont, or just DIN for short.
SolarNetwork has added a fully-managed Distributed Network Protocol 3 (DNP3 ) Remote Substation (often referred to as an Outstation) server service, that DNP3 compliant Control Center (often referred to as Master) applications can integrate with. DNP3 is commonly used in the energy and water utility industries, and provides a convenient method of monitoring and controlling distributed industrial equipment in real time such as power inverters, meters, switches, and dynamic parameters.
SolarNetwork recently added Open Smart Charging Protocol support for dynamic grid load management, but configuring everything was only available through SolarUser API methods . Now SolarNetwork supports a simple OSCP management user interface, so the OSCP infrastructure can be managed easily in a browser.
SolarNetwork has added an Open Smart Charging Protocol 2.0 Flexibility Provider service , to support demand-response forecast signals from electric grid operators. The OSCP Flexibility Provider service allows grid operators to send detailed grid constraint forecasts to SolarNetwork.
SolarNetwork has supported OCPP -compliant EV charging stations for a couple of years now , but only via SolarUser API methods . Now SolarUser supports a simple OCPP management user interface, so the OCPP infrastructure can be managed easily in a browser.
SolarUser has a supported scheduled data exports for a couple of years now , and the SolarUser API has supported ad hoc data exports for more than a year. Now we’ve added an easy-to-use UI in the SolarUser Data Export page for submitting ad hoc data exports.
SolarUser has a new set of REST endpoints under /user/event/node that are designed to support configuring “hooks” into external applications based on node-related events happening in SolarNetwork.
The SolarQuery /datum/list and /location/datum/list endpoints no longer require the dataPath parameter when using the DayOfWeek/SeasonalDayOfWeek or HourOfDay/SeasonalHourOfDay aggregation types.
The SolarQuery /datum/list endpoint now supports a new partialAggregation parameter that can provide aggregated results for partial aggregate time periods when the overall query date range does not perfectly align on aggregate period dates.
The SolarQuery /datum/list endpoint now supports the Year aggregation type, to return calendar year aggregated results efficiently.
We’ve deployed beta support for OCPP 1.6j compliant charging stations to connect with SolarNetwork, turning the energy data they generate while charging electric vehicles into datum streams that can be used like any other datum stream within SolarNetwork.
Almost one year ago SolarNetwork launched SolarFlux, a real-time publish/subscribe system for SolarNode data. We’ve now expanded SolarFlux’s reach by adding automatically-calculated aggregate data topics, so applications have real-time access to hour, day, and month aggregated data in addition to the raw data published by SolarNode.
For a long time now SolarNetwork has supported APIs for managing a flexible metadata object structure, which can be attached to various things like accounts , nodes , and node sources . There hasn’t been a good way to query the metadata, however.
SolarNetwork has a new feature designed to help you design token security policies that restrict which API endpoints are allowed to be used with an associated security token.
SolarNetwork has a new feature that provides access to SolarNode data in real-time, which we are calling SolarFlux. The system allows applications to access the real-time data via the MQTT publish/subscribe protocol.
SolarNetwork has a new feature designed to help you migrate data collected from other systems into SolarNetwork. The new Data Import page allows you to upload a CSV file with the data you want to import.
SolarQuery has a new REST endpoint /datum/reading that is designed to provide easy-to-use “meter reading” values. This is used to determine how much a measurement changed over a period of time.
SolarNetwork has a new feature that helps you see an overview of the data collected by SolarNodes in your account, at a glance. The new Data Insight page shows you a tally of the number of nodes in your account, and the number of unique sources they are posting data under.
SolarNetwork has a new feature that allows configuring data retention policies so data collected by the SolarNodes in your account can be automatically purged after it is no longer useful.
SolarNetwork has a new feature that allows configuring automated jobs to export the data collected by SolarNodes in your account to Amazon S3. Jobs can be scheduled to run hourly, daily, weekly, or monthly, and can export the data as CSV or JSON.
One of the nicest about SolarNode as a platform is that it is highly customisable. It seems as if each SolarNode deployment is unique. We’ve added a Node Image Maker tool to help create custom SolarNode OS images.
SolarNode devices generally don’t require much maintenance once they are initially deployed and configured. Like any IoT device, however, they do require periodic maintenance, for example to apply security patches or add/update SolarNode plugins.
Our charitable aim is to protect the environment through supporting energy education and using technology to help people understand energy conservation and renewable energy.
Take control of your energy usage and costs with our powerful platform.