-
Notifications
You must be signed in to change notification settings - Fork 2
OpenWeatherMap Cloud Integrations
This page descirbes the Cloud Integrations support for OpenWeatherMap. See the OpenWeatherMap documentation site for information about their APIs.
The OpenWeatherMap integration service identifier is s10k.c2c.i9n.owm
. The following service
properties are supported:
Property | Description |
---|---|
apiKey |
The OpenWeatherMap API key to use for authentication |
baseUrl |
An optional alternate URL to use to access the cloud service |
The OpenWeatherMap integration supports the following Cloud Datum Stream Service implementations:
Service | Identifier | Description |
---|---|---|
OpenWeatherMap Day | s10k.c2c.ds.owm.day |
Polling datum stream using the OpenWeatherMap API for day (sunrise, sunset, etc.) data |
OpenWeatherMap Forecast | s10k.c2c.ds.owm.forecast |
Polling datum stream using the OpenWeatherMap API for weather forecast data |
OpenWeatherMap Weather | s10k.c2c.ds.owm.weather |
Polling datum stream using the OpenWeatherMap API for weather observation data |
☝️ Note that these services are geared towards collecting Location Datum streams. That means an appropriate location datum stream (location ID and source ID) must be configured before setting up an OpenWeatherMap Cloud Datum Stream. The Location Request API can be used to submit requests for new location streams, if one does not already exist.
The datum stream services also automatically collect datum using SolarNetwork standardized properties and no Cloud Datum Stream Mapping Property entities are required (a Cloud Datum Stream Mapping entity is still required, but does not need any Property entities associated with it).
These services do not support the Cloud Datum Stream import service.
The OpenWeatherMap Datum Stream Service implementations all support the following common service properties:
Property | Description |
---|---|
lat |
The GPS decimal latitude to query |
lon |
The GPS decimal longitude to query |
locId |
An OpenWeatherMap location (city) identifier to use, instead of GPS coordinates |
☝️ If a
locId
property is configured thenlat
andlon
are ignored. See OpenWeatherMap's city.list.json resource for the list of supported values.
The OpenWeatherMap Day datum stream service identifier is s10k.c2c.ds.owm.day
. This service
accesses the Current Weather API to collect basic day-level
information such as sunrise and sunset times.
The common service properties are supported. No Data Filters are supported.
The OpenWeatherMap Day datum stream service identifier is s10k.c2c.ds.owm.forecast
. This service
accesses the Forecast API to collect future-dated weather
forecast information, such as temperature, wind, and sky conditions.
The common service properties are supported. No Data Filters are supported.
The OpenWeatherMap Day datum stream service identifier is s10k.c2c.ds.owm.weather
. This service
accesses the Current Weather API to collect current weather
observation information, such as temperature, wind, and sky conditions.
The common service properties are supported. No Data Filters are supported.
- SolarNetwork API access
- SolarNetwork API authentication
- SolarNetwork global objects
- SolarNetwork aggregation
- SolarFlux API
- SolarIn API
- SolarQuery API
-
SolarUser API
- SolarUser enumerated types
- SolarUser datum expire API
- SolarUser datum export API
- SolarUser datum import API
- SolarUser event hook API
- SolarUser location request API
- SolarUser Cloud Integrations API
- SolarUser DIN API
- SolarUser DNP3 API
- SolarUser ININ API
- SolarUser OCPP API
- SolarUser OSCP API
- SolarUser SolarFlux API