meteohub.de

I have just noticed an anomaly on my Twitter Feed as shown below.

The Low temperature is not the lowest so I am wondering if I have the syntax correct or is the error a timing issue.

Here is the syntax "[hh]:[mm] Temp [th0temp-act=C.1:--]°C (High [th0temp-dmax]°C @ [th0temp-dmaxtime.ij:--=utc]:[th0temp-dmaxtime.kl:--=utc]/Low [th0temp-dmin]°C @ [th0temp-dmintime.ij:--=utc]:[th0temp-dmintime.kl:--=utc]),"

Can you expand more on why you believe you are not getting the lowest temp? What is the lowest temp, where are you seeing this lowest temp, what is the time of this lowest temp? Are you comparing the lowest temp time in different time frames as you are using UTC in the syntax?

Looking at the detail again Twitter correctly reported a temperature 2.2C at the exact time of the tweet. The low temperature in the feed was at 20.58 giving 2.3C. I can only assume this event happened so close the the change in temperature that MB couldn't process it in time. I thought I might have discovered a bug/fault but no worries.

Regarding UTC = we are currently in winter time which = GMT or UTC. Not sure how MB handles Summer Time so should the syntax be changed?

Please delete post or mark as Solved.

See:

2018-11-20,20:57,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,20:58,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,20:59,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,21:00,2.2,95,1.5,1004.9,0.0,0.0,109,0.0
2018-11-20,21:01,2.2,95,1.5,1004.8,0.0,0.0,109,0.0
2018-11-20,21:02,2.2,95,1.5,1004.9,0.0,0.0,109,0.0

Missed some important timings:

2018-11-20,20:50,2.4,95,1.7,1004.9,0.0,0.0,109,0.2
2018-11-20,20:51,2.4,95,1.7,1004.9,0.0,0.0,109,0.0
2018-11-20,20:52,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,20:53,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,20:54,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,20:55,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,20:56,2.3,95,1.6,1004.8,0.0,0.0,109,0.2
2018-11-20,20:57,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,20:58,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,20:59,2.3,95,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,21:00,2.2,95,1.5,1004.9,0.0,0.0,109,0.0
2018-11-20,21:01,2.2,95,1.5,1004.8,0.0,0.0,109,0.0
2018-11-20,21:02,2.2,95,1.5,1004.9,0.0,0.0,109,0.0
2018-11-20,21:03,2.2,96,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,21:04,2.2,96,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,21:05,2.2,96,1.6,1004.9,0.0,0.0,109,0.0
2018-11-20,21:06,2.2,96,1.6,1004.9,0.0,0.0,109,0.0

What station are you using and what is the specified temp update rate?

Mattk wrote: ↑Wed Nov 21, 2018 9:54 pm What station are you using and what is the specified temp update rate?

I have a Davis Vantage Pro2 +. It communicates wirelessly with an Envoy with USB logger that is cabled to the MB Pro.
I have no idea of the update rate I am afraid.
I do have some blank entries as seen below.
Not sure if these are relevant?

I don't see anything in the syntax that is an issue and tested that in a VP2/Envoy/Nano and it appears all good. The temp resolution of the VP2 is 0.1°C and accuracy +/- 0.5°C and the difference between 2.2 and 2.3 can be argued about all day, could be the timing, could be rounding at the raw level? Nothing much else comes to mind at this point

Syntax is wrong.

wrong right: This works for regular templates but I don't know if that also works for iterated export expressions. Give it a try.

Thanks for the change suggestion.

I have changed both the [dmax] and [dmin] syntax.

I had noticed that the 00:00 feed had an error so maybe that change will correct that.

See screenshot:

Sorry, that is still wrong.
will report something like...
or when no data avail...

I have now had a chance to see the results of my syntax changes for my Twitter Feed.
At midnight, and only midnight I receive a Blank output. This doesn't really matter as far as I am concerned as the 00:30 feed corrects the error.
Maybe I still have something wrong or I have misunderstood the suggestions.

Syntax: [hh]:[mm] Temp [th0temp-act=C.1:--]°C (Max: [th0temp-dmax.1:--]°C @ [th0temp-dmaxtime=utc.ij:--]:[th0temp-dmaxtime=utc.kl:--]/Min: [th0temp-dmin.1:--]°C @ [th0temp-dmintime=utc.ij:--]:[th0temp-dmintime=utc.kl:--])

At precisely midnight it is today and generally no records for dmax type selectors to be meaningful.

Mattk wrote: ↑Sun Nov 25, 2018 10:11 pm At precisely midnight it is today and generally no records for dmax type selectors to be meaningful.

Thank you for the explanation Mattk.

There are timing options for periodical tasks like hourly, daily, monthly, etc which trigger exactly before the flip is done and by that data that has shown up in the hour that has just passed is shown. For hours this timing option is named "before every full hour".

Thank you once again.

Here is the result of using your suggestion.