meteohub.de

Q.: Is the VP2 barotrend part of the data that can be read by meteohub? Or is this only visible on the VP2 console?

I´m asking, because if possible I´d like to have a meteohub variable using the VP2 3h barotrend feature.
The one hour variable more or less sticks at steady all the time, regardless how steep the pressure changes. And the 24h variable´s timeframe is to large to reflect a current change in air pressure.

Just in case it would be nice if the 1h baro_trend variable could be changed that it reflects smaller delta p in altering the trend to rise or fall.

Thanks,
Wolfgang

I'm using the Vantage VP2 with Meteohub, the barometer reading is no problem, The VP2 is connected by LAN to Meteohub.

The barometer is thb0

barotrend is supported by variable "hour1_thb0_press_trend" (and also for other time periods as hour1).

Hi!

Wolfgang asks for the three hours trend.

But the tag

[last3h_thb0_press_trend]


will not work. There are just the time periods hour1, last60m, last24h, and so on.

But more interesting would be the last3h trend.

Cheers,

Christian

admin wrote:barotrend is supported by variable "hour1_thb0_press_trend" (and also for other time periods as hour1).

I know this is an old story, but I´m now sure that the "hour1_thb0_press_trend" variable isn´t working.
Using it on my website, it shows 99.99% of the time steady (0) - which does not reflect the real pressure trend situation.

If you look at this current graphs it shows exactly that "hour1_thb0_press_trend" calculation is incorrect (most probably using a too large value for the change difference)



I still think the limits Davis VP2 is using for baro trend make sense.

Divided by 3 and it would be "hour1_thb0_press_trend"
"hour1_thb0_press_trend" = 1 --> pressure difference in 1 hour greater equal than 0.23 hPa
"hour1_thb0_press_trend" = 0 --> pressure difference in 1 hour less than 0.23 hPa
"hour1_thb0_press_trend" = -1 --> pressure difference in 1 hour less equal than -0.23 hPa

It would be great, if this variable could be adjusted that it really reflects the change in pressure and showing a correct trend. Thanks

Just saw that VP2´s 3hour Barometer Trend can be read via USB.
That would be really a great thing, if a new variable, lets say "vp2_pressure_trend" could be built and added into meteohubs existing list of variables.

vp2_pressure_trend = 2 --> Rising Rapidly
vp2_pressure_trend = 1 --> Rising Slowly
vp2_pressure_trend = 0 --> Steady
vp2_pressure_trend = -1 --> Falling Slowly
vp2_pressure_trend = -2 --> Falling Rapidly

from Vantage ProTM and Vantage Pro2TM
Serial Communication Reference Manual

Is the value reported to clientraw.txt -- item 50 (Baro Trend) from the one hour trend value or the three hour trend of the LOOP packet?

I've noticed that the Baro Trend of clientraw is almost always reported as steady, yet the weatherlink.com site will show increasing/decreasing conditions instead.

I´ve now done it with the subtraction of seqhour1_thb0_press_hpa@3 - actual_thb0_press_hpa
That works, but nevertheless I would be happy, if Boris could look into this, and might getting enthusiastic about above proposals (correction & new barotrend variable for VP2 users)

Thanks,
Wolfgang


...........................

Boris,

any plans ro remedy the barotrend glitch?

Thanks ...