HTTP Data Logging Protocol oddity

[YJB]

Hi,

I'm trying to get the "live" value for a single sensor using the datalogging protocol:

Code: Select all

/usr/bin/wget -q -O - "http://meteohub/meteolog.cgi?mode=data&sensor=data12"
20120809122808 thb1 22.7 56 13.5 1026.0 1026.0 3
20120809122811 th2 21.4 59 13.1
20120809122750 data10 10957912.00
20120809122751 data20 18172679.00
20120809122751 data11 883074.00
20120809122751 data12 7214767.00
20120809122658 rain0 0.0 2215.0 0.0
20120809122734 thb0 22.1 60 14.0 1024.0 1024.0 3
20120809122811 wind0 19 1.4 2.8 20.7
20120809115015 th1 24.8 58 16.0
20120809122742 th3 24.6 52 14.1
20120809122803 thb4 24.8 48 13.0 1026.3 1026.3 2
20120809122747 th4 20.7 55 11.3
20120809122713 sol4 114
20120809122811 wind4 24 1.8 2.7 20.7
20120809122801 rain4 0.0 499.4 0.0
20120809122800 data0 0.84
20120809122800 data1 0.73
20120809122800 data3 0.51

As one can see it just gives me all my sensors.

The strange thing is that when I'm using a start timestamp, it does indeed only shows me the requested sensor:

Code: Select all

/usr/bin/wget -q -O - "http://meteohub/meteolog.cgi?mode=data&start=20120809122000&sensor=data12"
20120809122035 data12 7214552.00
20120809122138 data12 7214583.00
20120809122240 data12 7214613.00
20120809122343 data12 7214643.00
20120809122444 data12 7214674.00
20120809122547 data12 7214705.00

So clearly I'm missing something, or is this a bug?

Ysbrand

[ZebraWetter]

I can confirm that.
I am not sure at the moment if I should use the HTTP-protocol or the output from /meteograph.cgi?text=all for my integration into a TYPO3 driven site, so I "played around" with the HTTP-protocol and found this behavior, too.

[admin]

I found this bug. Will be fixed with 4.9n.

[YJB]

Thanks Boris for fixing this!

Code: Select all

/usr/bin/wget -q -O - "http://meteohub/meteolog.cgi?mode=data&sensor=data12"
20120814055338 data12 7277668.00

For the record: this is actually fixed one release early: Update 4.9m

[ZebraWetter]

Great! Thanks!