All Apps and Add-ons

Website Input: Why am I unable to extract HTTP server XML data?

cmodyssey
Explorer

Hi,

I have data in an XML file (example at the bottom of this posting)

In the Selector field, I have put COOK_TEMP

When I try to preview results, it says "No matches found"

When I put the same data and Selector into the "try jsoup" site, I get the results I expect.

I have managed to get some data to match by setting the Selector to nutcallstatus.

Does anyone know what is causing the match to not work for me?

Thanks in advance.

Richard.

<nutcallstatus>
   <!--this is similar to status.xml, but with more values-->
   <!--all temperatures are displayed in tenths F, regardless of setting of unit-->
   <!--all temperatures sent by browser to unit should be in F.  you can send tenths F with a decimal place, ex: 123.5-->  
   <COOK>
      <COOK_NAME>Cook</COOK_NAME>
      <COOK_TEMP>695</COOK_TEMP>
      <COOK_SET>1000</COOK_SET>
      <COOK_STATUS>0</COOK_STATUS>
   </COOK>
   <FOOD1>
      <FOOD1_NAME>Food1</FOOD1_NAME>
      <FOOD1_TEMP>OPEN</FOOD1_TEMP>
      <FOOD1_SET>1800</FOOD1_SET>
      <FOOD1_STATUS>4</FOOD1_STATUS>
   </FOOD1>
   <FOOD2>
      <FOOD2_NAME>Food2</FOOD2_NAME>
      <FOOD2_TEMP>OPEN</FOOD2_TEMP>
      <FOOD2_SET>1800</FOOD2_SET>
      <FOOD2_STATUS>4</FOOD2_STATUS>
   </FOOD2>
   <FOOD3>
      <FOOD3_NAME>Food3</FOOD3_NAME>
      <FOOD3_TEMP>OPEN</FOOD3_TEMP>
      <FOOD3_SET>1800</FOOD3_SET>
      <FOOD3_STATUS>4</FOOD3_STATUS>
   </FOOD3>
   <OUTPUT_PERCENT>100</OUTPUT_PERCENT>
   <TIMER_CURR>00:00:00</TIMER_CURR>   
   <TIMER_STATUS>0</TIMER_STATUS>
   <DEG_UNITS>1</DEG_UNITS>
   <COOK_CYCTIME>6</COOK_CYCTIME>
   <COOK_PROPBAND>300</COOK_PROPBAND>
   <COOK_RAMP>0</COOK_RAMP>
</nutcallstatus>
1 Solution

LukeMurphey
Champion

I'm not sure why this isn't working. I tested on my end with a unit test and the bug reproduces for me. I opened a bug ticket to take a look: http://lukemurphey.net/issues/1144. I plan on supporting this soon.

Update

Version 1.2 has a fix for this.

View solution in original post

0 Karma

LukeMurphey
Champion

I'm not sure why this isn't working. I tested on my end with a unit test and the bug reproduces for me. I opened a bug ticket to take a look: http://lukemurphey.net/issues/1144. I plan on supporting this soon.

Update

Version 1.2 has a fix for this.

View solution in original post

0 Karma

cmodyssey
Explorer

Hi,

Thanks for looking into this.

I have done some more playing with this and have found that if I use lower case in the selector, it works!

What I had originally done is copied and pasted the exact tag/element (removing the <> characters) and used that in the selector. It just so happens that the XML data source uses upper case for most of it's elements.

Should this app be able to take upper and lower case for the selector?

Thanks,

Richard.

0 Karma

LukeMurphey
Champion

Yeah, it turns out that lxml converts the XML to lowercase. I have a fix in place for this locally and my unit tests all pass; I just need to do a bit more testing before I push out an update.

0 Karma