<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Thema "Re: Betreff: Returns from an API request change order." in Getting started programming with the Viessmann API</title>
    <link>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/183237#M55</link>
    <description>&lt;P&gt;&lt;a href="https://community.viessmann.de/t5/user/viewprofilepage/user-id/23149"&gt;@JueBag&lt;/a&gt; for completeness: There is no defined order in the features within the response. So you need to evaluate the arrays in the JSON like you already are doing.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Aug 2021 12:20:03 GMT</pubDate>
    <dc:creator>CustomerCareMichael</dc:creator>
    <dc:date>2021-08-13T12:20:03Z</dc:date>
    <item>
      <title>Returns from an API request change order.</title>
      <link>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/179908#M1</link>
      <description>&lt;P&gt;I'm using the (new) API for a couple of days now with such a request:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;"&lt;A href="https://api.viessmann.com/iot/v1/equipment/installations/" target="_blank" rel="noopener"&gt;https://api.viessmann.com/iot/v1/equipment/installations/&lt;/A&gt;"+ installationID +"/gateways/" +gatewaySerial + "/devices/0/features?regex=heating.(sensors.temperature.outside%7Cdhw.(oneTimeCharge%7Csensors.temperature.hotWaterStorage%7Cpumps.circulation))%7Cventilation.operating.programs.active"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why does the order of data entries in the return change? ( That happened this morning July 2nd between 03:00 and 11:00&amp;nbsp; UTC +2).&lt;/P&gt;&lt;P&gt;The sequence in the returned string was and still is not inline with the request, also the number of data entries is 5 instead of 4.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jul 2021 10:55:14 GMT</pubDate>
      <guid>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/179908#M1</guid>
      <dc:creator>JueBag</dc:creator>
      <dc:date>2021-07-02T10:55:14Z</dc:date>
    </item>
    <item>
      <title>Betreff: Returns from an API request change order.</title>
      <link>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/180107#M8</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.viessmann.de/t5/user/viewprofilepage/user-id/23149"&gt;@JueBag&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;could you please share the response that you receive from the request?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In general, my first assumption is that the feature request is not accounting for the order of the features. To have a more robust implementation, I would recommend anaylsing feature names instead of the order of the features.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, I will check with the development teams to make sure, how the device features is ordered within the response.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 15:00:12 GMT</pubDate>
      <guid>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/180107#M8</guid>
      <dc:creator>CustomerCareMichael</dc:creator>
      <dc:date>2021-07-05T15:00:12Z</dc:date>
    </item>
    <item>
      <title>Betreff: Returns from an API request change order.</title>
      <link>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/180117#M30</link>
      <description>&lt;P&gt;&lt;a href="https://community.viessmann.de/t5/user/viewprofilepage/user-id/29136"&gt;@CustomerCareMichael&lt;/a&gt;&amp;nbsp; Thanks for the reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My actually used request in JavaScript is.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;var headers = [];&lt;BR /&gt;headers["Authorization"] = "Bearer "+ token;&lt;BR /&gt;var url ="&lt;A href="https://api.viessmann.com/iot/v1/equipment/installations/" target="_blank" rel="noopener"&gt;https://api.viessmann.com/iot/v1/equipment/installations/&lt;/A&gt;"+ installationID +"/gateways/" +gatewaySerial + "/devices/0/features?regex=heating.(sensors.temperature.outside%7Cdhw.(oneTimeCharge%7Csensors.temperature.hotWaterStorage%7Cpumps.circulation))%7Cventilation.operating.(programs.active)";&lt;BR /&gt;var returnvalue = HTTP.sendHttpGetRequest(url, headers, 10*1000);&lt;/P&gt;&lt;P&gt;returnvalue = JSON.parse(returnvalue);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, that is a request for 5 data-points, so the number is and was correct.&lt;/P&gt;&lt;P&gt;I would have expected the order:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Outside Temperature&lt;/LI&gt;&lt;LI&gt;OneTimeCharge&lt;/LI&gt;&lt;LI&gt;HotWaterStorageTemp&lt;/LI&gt;&lt;LI&gt;HotWaterCirculationPump&lt;/LI&gt;&lt;LI&gt;VentilationProgtramsActive&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;The return I'm getting actually is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;( see attached file API Return.pdf).&lt;/P&gt;&lt;P&gt;The order in there is&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Outside Temperature&lt;/LI&gt;&lt;LI&gt;HotWaterStarageTemp&lt;/LI&gt;&lt;LI&gt;HotWaterCirculationPump&lt;/LI&gt;&lt;LI&gt;VentilationProgtramsActive&lt;/LI&gt;&lt;LI&gt;OneTimeCharge&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;As for the actual usage, I changed my code in order to evaluate each JSON array element by feature.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 16:05:00 GMT</pubDate>
      <guid>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/180117#M30</guid>
      <dc:creator>JueBag</dc:creator>
      <dc:date>2021-07-05T16:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: Betreff: Returns from an API request change order.</title>
      <link>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/183237#M55</link>
      <description>&lt;P&gt;&lt;a href="https://community.viessmann.de/t5/user/viewprofilepage/user-id/23149"&gt;@JueBag&lt;/a&gt; for completeness: There is no defined order in the features within the response. So you need to evaluate the arrays in the JSON like you already are doing.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Aug 2021 12:20:03 GMT</pubDate>
      <guid>https://community.viessmann.de/t5/Getting-started-programming-with/Returns-from-an-API-request-change-order/m-p/183237#M55</guid>
      <dc:creator>CustomerCareMichael</dc:creator>
      <dc:date>2021-08-13T12:20:03Z</dc:date>
    </item>
  </channel>
</rss>

