This question was originally posted on DCIM Support by Jimmy Leung on 2019-07-12
The current web service can return all the device ID using the "getAllDevices" Request to get the device ID. However, in the ISXCentralSensorService, there is no service request available to get the sensorID using the device ID. This makes the getSensorData Request extremely difficult and always resulted in returning Invild ID by DCE.
(CID:147194683)
Solved! Go to Solution.
This answer was originally posted on DCIM Support by Brian Ellwood on 2019-07-12
If you know the deviceID you want to fetch all sensors for, you can do the following:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2" xmlns:isx1="http://www.apc.com/stdws/wsdl/ISXCentralSensors-v2"> <soapenv:Header/> <soapenv:Body> <isx:getSensorsForDeviceRequest> <isx:ISXCElementID>--deviceID--</isx:ISXCElementID> </isx:getSensorsForDeviceRequest> </soapenv:Body> </soapenv:Envelope>If there's a specific sensor type you want to get for that same device, you do the following as well:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2" xmlns:isx1="http://www.apc.com/stdws/wsdl/ISXCentralSensors-v2"> <soapenv:Header/> <soapenv:Body> <isx:getSensorsForDeviceRequest> <isx:ISXCElementID>--deviceID--</isx:ISXCElementID> <isx:ISXCSensorType>--sensorType--</isx:ISXCSensorType> </isx:getSensorsForDeviceRequest> </soapenv:Body> </soapenv:EnvelopeSubstituting in your deviceID and sensorType respectively.
You can then process the return to get the sensorID to make your call with getSensorData.
(CID:147194828)
This answer was originally posted on DCIM Support by Brian Ellwood on 2019-07-12
If you know the deviceID you want to fetch all sensors for, you can do the following:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2" xmlns:isx1="http://www.apc.com/stdws/wsdl/ISXCentralSensors-v2"> <soapenv:Header/> <soapenv:Body> <isx:getSensorsForDeviceRequest> <isx:ISXCElementID>--deviceID--</isx:ISXCElementID> </isx:getSensorsForDeviceRequest> </soapenv:Body> </soapenv:Envelope>If there's a specific sensor type you want to get for that same device, you do the following as well:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2" xmlns:isx1="http://www.apc.com/stdws/wsdl/ISXCentralSensors-v2"> <soapenv:Header/> <soapenv:Body> <isx:getSensorsForDeviceRequest> <isx:ISXCElementID>--deviceID--</isx:ISXCElementID> <isx:ISXCSensorType>--sensorType--</isx:ISXCSensorType> </isx:getSensorsForDeviceRequest> </soapenv:Body> </soapenv:EnvelopeSubstituting in your deviceID and sensorType respectively.
You can then process the return to get the sensorID to make your call with getSensorData.
(CID:147194828)
This comment was originally posted on DCIM Support by Jimmy Leung on 2019-07-12
Spot on, this can supplement the Web service guide. thanks
(CID:147194840)
This comment was originally posted on DCIM Support by Brian Ellwood on 2019-07-12
Glad to help.
If you're querying more than three sensors you should use the getMultipleDataSensor method:
Example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2" xmlns:isx1="http://www.apc.com/stdws/wsdl/ISXCentralSensors-v2"> <soapenv:Header/> <soapenv:Body> <isx:getMultipleSensorDataRequest> <isx:ArrayOfISXCElementID> <isx1:string>--sensorID--</isx1:string> <isx1:string>--sensorID--</isx1:string> <isx1:string>--sensorID--</isx1:string> </isx:ArrayOfISXCElementID> </isx:getMultipleSensorDataRequest> </soapenv:Body> </soapenv:Envelope>
...just keep adding elements as needed for all the sensorID's you have.
DCE's web service doesn't take to cursoring very kindly so if you can aggregate the list of sensors you want this call will save you some headaches.
(CID:147194870)
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!