If you add /text to the path the result is easier to parse.
For that matter, owhttpd isn't the easiest way to get pure data (as opposed
to a nice display). The file system, shell utilities, ownet within your own
program all give pure text.
On Oct 14, 2014 4:25 PM, "somewire" <ung...@gmail.com> wrote:
> Nevermind, I managed to find a way to get those temperatures. I take the
> whole answer (html headers, links, text) as a big string then I extract the
> only interesting part (from character 1000 to 1004, by example), knowing
> that the lenghth of the answering string is constant.
>
>
>
>
> --
> View this message in context:
> http://owfs-developers.1086194.n5.nabble.com/owhttpd-get-clean-output-tp10885p10886.html
> Sent from the OWFS Developers mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
