DCE api temperature issue

[michael1]

Hello,

Does anyone know how to change the temperature unit on DCE? It appears that DCE 7.7.1 is storing values as Fahrenheits when 7.6 version has Celsius in our environments. We have Netbotz 250 devices which DCE monitor, and then temperatures are read from DCE using API. When calling AverageSensorData function the return value has different units, see the attached file 'API_returned_temperatures.txt'.

Both DCE versions are reading same Netbotz device so there isn't difference in device settings. This change must come from difference on DCE versions but how to fix it. I didn't find any related article about similar issue.

Br, Michael

[Cory_McDonald · Accepted solution]

Hello Michael,

I ran some test around this with version DCE 7.5.0, DCE 7.7.1, & DCE 7.8.0 and here are the results:

7.5.0 - getSensorData

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
   <soapenv:Header/>
   <soapenv:Body>
      <isx:getSensorDataRequest>
         <!--Optional:-->
         <isx:locale>?</isx:locale>
         <isx:ISXCElementID>Bfb21e8_nbSNMPEnc6F417A99_SUPPLY_TEMP</isx:ISXCElementID>
      </isx:getSensorDataRequest>
   </soapenv:Body>
</soapenv:Envelope>

7.5.0 getSensorData Results

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soap:Body xmlns:ns1="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
      <ns1:getSensorDataResponse>
         <ns1:ISXCSensorData>
            <ns2:timeStamp xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">2020-04-28T01:16:47-04:00</ns2:timeStamp>
            <ns2:units xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">° C</ns2:units>
            <ns2:value xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">23.9</ns2:value>
            <ns2:ISXCValueType xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">FLOAT</ns2:ISXCValueType>
         </ns1:ISXCSensorData>
      </ns1:getSensorDataResponse>
   </soap:Body>
</soap:Envelope>

7.7.1 getSensorData

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
   <soapenv:Header/>
   <soapenv:Body>
      <isx:getSensorDataRequest>
         <!--Optional:-->
         <isx:locale>?</isx:locale>
         <isx:ISXCElementID>B09dd31_nbSNMPEncC5F0B0F1_SUPPLY_TEMP</isx:ISXCElementID>
      </isx:getSensorDataRequest>
   </soapenv:Body>
</soapenv:Envelope>

7.7.1 getSensorData Results

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soap:Body xmlns:ns1="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
      <ns1:getSensorDataResponse>
         <ns1:ISXCSensorData>
            <ns2:timeStamp xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">2020-04-28T10:59:57-04:00</ns2:timeStamp>
            <ns2:units xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">° C</ns2:units>
            <ns2:value xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">23.1</ns2:value>
            <ns2:ISXCValueType xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">FLOAT</ns2:ISXCValueType>
         </ns1:ISXCSensorData>
      </ns1:getSensorDataResponse>
   </soap:Body>
</soap:Envelope>

7.8.0 getSensorData

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
   <soapenv:Header/>
   <soapenv:Body>
      <isx:getSensorDataRequest>
         <!--Optional:-->
         <isx:locale>?</isx:locale>
         <isx:ISXCElementID>B1db239_nbSNMPEnc8E127200_SUPPLY_TEMP</isx:ISXCElementID>
      </isx:getSensorDataRequest>
   </soapenv:Body>
</soapenv:Envelope>

7.8.0 getSensorData Results

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soap:Body xmlns:ns1="http://www.apc.com/stdws/xsd/ISXCentralSensors-v2">
      <ns1:getSensorDataResponse>
         <ns1:ISXCSensorData>
            <ns2:timeStamp xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">2020-04-28T10:42:34-04:00</ns2:timeStamp>
            <ns2:units xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">° C</ns2:units>
            <ns2:value xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">23.3</ns2:value>
            <ns2:ISXCValueType xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">FLOAT</ns2:ISXCValueType>
         </ns1:ISXCSensorData>
      </ns1:getSensorDataResponse>
   </soap:Body>
</soap:Envelope>

From quick testing, it appears that nothing has changed.  The server locales for all 3 server are set to English (United States) under: DCE Client > System > Server Administration Settings > Time Settings.

By default, the locale is supposed to be the server locale, per documentation, but per the results I have above, this appears to not be the case.  I have made product management aware of this aspect of the issue, whether the issue is documentation or how the API responds:

Note: If either no locale (null) or an unsupported locale is specified in a method call, the current server locale configuration is assumed. 

What is your server locale?  Per my testing with English (United States) I am not seeing that anything has changed, but maybe something changed with a different server locale option?  It would also help if you can provide the example request, not just the results, so we can see how you have locate formatted in the request.

As a work around, to always get the locale that you desire, you can fill in the local to be one of the following, pulled from the DCE_WS_DEVELOPMENT.doc file that is part of the DCE web services documentation:

• US English (en-US)
• Japanese (ja-JP)
• Korean (ko-KR)
• Chinese (zh-CN)
• Russian (ru-RU)
• Brazilian Portuguese (pt-BR)
• French (fr-FR)
• Spanish (es-ES)
• Italian (it-IT)
• German (de-DE)

These should display the results of the local specified in the request.

Kind Regards,

Cory

[michael1]

Hi Cory,

Seems that the root cause was the server locale definition, thanks for the good tip @Cory_McDonald.

Our test server which has newer 7.7.1 version, locale was defined to English (United States) and this was giving Fahrenheits. Our production servers are using English (METRIC) which explain why we got Celsius from the older version. Changing the test server to English (METRIC) was resolving the issue.

Thank you,

 Michael