Help understanding seq???

[mattbrailsford]

Hi Guys,

I'm new to metetohub and am looking to make a dashboard for my weather data. If have something running here:

http://weather.mattbrailsford.com/

however the graph is generated by scraping data from my PWS page http://www.pwsweather.com/obs/MBWMR180.html.

I've been searching around to see if I can get the data for the graph from my meteohub, and it would seem like the seq??? elements would be my best bet. I've had a look at the all-sensors data export, but I'm not sure I understand exactly what each one is. I get that it's a '_' delimited list of values, but what are the intervals? whatever the unit is in the var name? (ie is seqhour1 one hour intervals?) What dictates how many values are returned? i've seen people suffix the var names with something like @4:-, what does this do? are there any other special things one can do?

Based upon the graph I'm displaying at the moment, the data it represents is the meter reading at every 5 minutes interval for the day starting from 12am. Can I use seq??? to get this data?

Apologies for all the questions, but I've searched the docs and the forum but couldn't find a thorough explanation.

Many thanks

Matt

[EmjayNet]

Hi there,

I can explain the @4:- bit for you I use this type of thing a lot

e.g.
[seqhour1_rain0_total_mm@2:0]

The @ 2 gives me back only the second value from [seqhour1_rain0_total_mm]

The :0 tells MH that if no value exists then put a 0 in its place

Hope that helps.

Mark

[mattbrailsford]

Thanks Mark,

That makes perfect sense.

Matt

[YJB]

seq???? List of data that are used by WD Live to generate weather graphs
Always starts with the last completed timeframe e.g. seqday1 starts yesterday (and NOT today)

seqmin1 Last 60 mins in steps of 1 minute (now -1min .. now -60 minutes)
Updated every minute by both histeval0 (might be a bug) and histeval1 - 7

seqmin15 Last 23.5 hours in steps of 15 minutes hour(now -15mins .. now -23.5 hours)
Updated every 5 minutes by histeval1 - 6

seqhour1 Last 25 hours in steps of 1 hour(now -1hr .. now -25hrs)
Updated every 5 minutes by histeval1 - 8

seqhour6 6 hour interval, total 23 steps (now .. now -~138 hrs)
Updated every 6 hours (00:13/06:13/12:13/18:13) by histeval2 - 3

seqday1 Last 15 days in steps of 1 day(yesterday .. today -23 days)
Updated every 6 hours (00:13/06:13/12:13/18:13) by histeval2 - 2

seqmonth1 Last 14 months in steps of 1 month(last month .. today -14 months)
Updated every day (04:47) by histeval3 - 2

[mattbrailsford]

Brilliant. Thanks YJB. That makes everything crystal clear.

Thanks for spending the time to explain.

Matt

[panos1981]

The variables seq???_wind0 are not working on my meteohub when I use km/h or Bft. They work only if I use knots as measure. Why is this happening? Has to do with WD Live settings?

[wvdkuil]

The variables seq???_wind0 are not working on my meteohub when I use km/h or Bft. They work only if I use knots as measure. Why is this happening? Has to do with WD Live settings?

Those variables are only stored and calculated in knots. The temp values only in C. Pressure only in hpa.
You have to convert them to your UOM (unit of measurement) in your own program code.

And I suspect that these values are internally used for creating those complex clientraw**.txt files. They use the same UOM.
They are really unique to Meteohub. And they are not displayed when you check all variables using ip-of-your-meteohub:5558 to list all measurements.

Wim

[panos1981]

Those variables are only stored and calculated in knots. The temp values only in C. Pressure only in hpa.
You have to convert them to your UOM (unit of measurement) in your own program code.

And I suspect that these values are internally used for creating those complex clientraw**.txt files. They use the same UOM.
They are really unique to Meteohub. And they are not displayed when you check all variables using ip-of-your-meteohub:5558 to list all measurements.

Wim

Thank you for your answer!
Actually I mentioned today that seq??? variables are not working also when I ask maximum or minimum rates for humidity, wind speed and pressure, e.g. "seqday1_wind0_gustspeedmax_kn" or "seqday1_thb0_sealevelmin_hpa".
Any explanation for these problems?

[wvdkuil]

Those variables are only stored and calculated in knots. The temp values only in C. Pressure only in hpa.
You have to convert them to your UOM (unit of measurement) in your own program code.

And I suspect that these values are internally used for creating those complex clientraw**.txt files. They use the same UOM.
They are really unique to Meteohub. And they are not displayed when you check all variables using ip-of-your-meteohub:5558 to list all measurements.

Wim

Thank you for your answer!
Actually I mentioned today that seq??? variables are not working also when I ask maximum or minimum rates for humidity, wind speed and pressure, e.g. "seqday1_wind0_gustspeedmax_kn" or "seqday1_thb0_sealevelmin_hpa".
Any explanation for these problems?

Those tags do not exist.
This is my documentation page http://www.weerstation-leuven.be/weathe ... g=en&wp=MH
The coding for the seq tags
seq<timeframe>_<sensor>_<dimension>_<unit>
For sensor <wind> there are only 4 <dimension>'s: gustspeed speed maindir chill

Hope this helps, Wim

[panos1981]

Those tags do not exist.
This is my documentation page http://www.weerstation-leuven.be/weathe ... g=en&wp=MH
The coding for the seq tags
seq<timeframe>_<sensor>_<dimension>_<unit>
For sensor <wind> there are only 4 <dimension>'s: gustspeed speed maindir chill

Hope this helps, Wim

Thank you, you really helped me!