meteohub.de

Thank you.

I didn't put the brackets in the template. But when I click the 'i" icon, they are present. See photo.

the "*0}" ending does a rounding to an integer. If you want to have a truncation like cutting off the decimals please use "*t}".
{* ([wind0wind-dmax=mph.0:0] - 24) / 4 *t} gives a values as follows:
24, 25, 26, 27 ->0
28, 29, 30, 31 -> 1
32, 33, 34, 35 -> 2
"*t" isn't firing any alerts. I'm ...

Thanks. I think I've got the gist of it now. I was missing the fact that I don't get an alert when the value is 0. So to receive alerts when gusts reach 25mph or higher I've changed my template to:
{* ([wind0wind-dmax=mph.0:0] - 21) / 4 *t}
which should fire alerts when wind gusts incrementally ...

I'm still trying to figure out why some of my alerts are not firing at specific values when using incremental alarms that are not set to fire at every 1 increment, but rather every 4 or every 10. Below is data from two very windy days this month, where I pose some questions in red . Since wind gusts ...

Using "{* ([wind0wind-dmax=mph.0:0] - 24) / 5 *0}" I'm getting less alerts than I used to, but still not triggering at quite every 5mph or 25+, 30+, 35+, 40+...

Today's gusts (it's been a windy week)...

Event 1: "[wind0wind-dmax=mph.0:0] - 24" had alerts fired at 25, 26, 27, 28, 29, 30, 31, 32, 34 ...

I don't have precise answers for you, but have some suggestions.

First of all I don't see a way to remove Weather Network's either. Perhaps toggle to "no upload", Save, then back to "10 minutes", Save?

I setup Weathercloud in mid-November 2015, and haven't had any upload issues. https://app ...

Sorry, maybe my original question wasn't clear...

Another example: Today I setup 2 different events, sending to 2 different email addresses.

Event 1: "[wind0wind-dmax=mph.0:0] - 24" had alerts fired at 25, 26, 27, 29, 34, 35, 37, 38
Event 2: "{* ([wind0wind-dmax=mph.0:0] - 24) / 2 *0}" had alerts ...

try
{* ([wind0wind-dmax=mph.0:0] - 24) / 2 *0}

Divides your integer result by two and makes an integer (zero decimals) of it.
Please see attached screenshot to see if I perhaps missed something when entering your suggested syntax? Yesterday I had a peak gust of 33mph, and received alerts at 25 ...

Thanks for the reply. Just to confirm I understand correctly, if I wanted it to fire every 5mph over 24mph would I use the following?:
{* ([wind0wind-dmax=mph.0:0] - 24) / 5 *0}

After looking at page http://meteobridge.com/wiki/index.php/Templates have you tried "max1440", "min1440", "avg1440" or "max24h", min24h", "avg24h"?

I haven't tried it and don't know for sure, but that's what I would try.

[wind0wind-dmax=mph.0:0] - 24

Above is an incremental email that I have setup which triggers for every 1mph above 24mph. On very windy days when gusts reach 40-60mph I can get up to 35 alerts. To lessen the number of daily wind alerts, instead of the current configuration I would like to have it ...

Here's my hourly observations that I receive as a text message on my phone via my carrier's email-to-SMS gateway:

[hh]:[mm] TEMP [th0temp-act=F.0:--] ([wind0chill-avg10=F.0:--])\n Hi/Lo [th0temp-dmax=F.0:--]/[th0temp-dmin=F.0:--]\n HUM [th0hum-act.0:--]%\n WIND [wind0dir-avg10=endir ...

I can confirm problem with rain values since upgrading to Meteobridge 2.5 Build 6582 this morning. An hourly email I send with the template [rain0total-sum60=in.2:--] has returned the following values over the past few hours even though there has been NO rain...

06:00: 36.68
07:00: 282.97
08:00 ...

Thanks for the August 3, 2014 update:
"adds a passcode field for validating radio amateur call signs used with CWOP"

My CWOP raw data now reads