You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integration to Raritan can be done by Power IQ web services REST API. This integration is based on a Basic Access Authentication and all request bodies will need to be in JSON format although GET methods don’t require any content in the body of the request.
The relevant API functional area for this project is Power and Sensor reading (see page 40 of API guide) which consist of GET methods to the following endpoints:
/api/v2/outlet_readings
/api/v2/outlet_readings_rollups/hourly
/api/v2/outlet_readings_rollups/daily
/api/v2/outlet_readings_rollups/monthly
/api/v2/circuit_breaker_readings
/api/v2/circuit_breaker_readings_rollups/hourly
/api/v2/circuit_breaker_readings_rollups/daily
/api/v2/circuit_breaker_readings_rollups/monthly
/api/v2/inlet_readings
/api/v2/inlet_readings_rollups/hourly
/api/v2/inlet_readings_rollups/daily
/api/v2/inlet_readings_rollups/monthly
An example of sensor readings is shown below. The sensor readings are created from data collected from PDU sensors and the response will have reading time and value. If rollups endpoint is chosen, the value will be an average of the rollup interval chosen (hourly, daily, monthly)
Integration to Raritan can be done by Power IQ web services REST API. This integration is based on a Basic Access Authentication and all request bodies will need to be in JSON format although GET methods don’t require any content in the body of the request.
The relevant API functional area for this project is Power and Sensor reading (see page 40 of API guide) which consist of GET methods to the following endpoints:
/api/v2/outlet_readings
/api/v2/outlet_readings_rollups/hourly
/api/v2/outlet_readings_rollups/daily
/api/v2/outlet_readings_rollups/monthly
/api/v2/circuit_breaker_readings
/api/v2/circuit_breaker_readings_rollups/hourly
/api/v2/circuit_breaker_readings_rollups/daily
/api/v2/circuit_breaker_readings_rollups/monthly
/api/v2/inlet_readings
/api/v2/inlet_readings_rollups/hourly
/api/v2/inlet_readings_rollups/daily
/api/v2/inlet_readings_rollups/monthly
An example of sensor readings is shown below. The sensor readings are created from data collected from PDU sensors and the response will have reading time and value. If rollups endpoint is chosen, the value will be an average of the rollup interval chosen (hourly, daily, monthly)
SensorReadings
{"sensor_reading":
{
"id":4950,
"reading_time":"2011/10/19 14:39:34 +0000",
"value":44.0,
"sensor_id":3,
"max_value":null,
"min_value":null,
"uom":"%"
}
}
SensorReadings*Rollups
{
"sensor_reading_hourly_rollup": {
"id": 1,
"rollup_interval": 1,
"reading_time": "2011/10/07 14:00:00 +0000",
"min_value": 31.0,
"max_value": 31.0,
"average_value": 31.0,
"sensor_id": 45
}
}
Sensors must be retrieved to access sensor specs. I.e.
{"sensor":
{
"id":10,
"pdu_id":28,
"type":"HumiditySensor",
"label":"H6_45.246",
"removed":null,
"position":"INLET",
"reading":{},
"state":{}
}
}
For more info, chat to Mario or Will
The text was updated successfully, but these errors were encountered: