meteohub.de

As used in a Template then it will be relative to the Resolution setting. Using a 1 minute resolution then the total is for the minute, if using say a 10 minute interval then it's for the 10 minutes. If you were using say a Month [Time Frame] and Resolution set to [Days] then that would be the total ...

I would have thought the FTP is linked to the FTP config Host/User as Test Path: can in effect be blank and just requiring a preceding / (as minimum)before the Path (File): input of the actual event and totally dependent on how the server FTP is configured?

That sort of distance is even pushing beyond standard Davis max expected reception. I don't believe an antenna system will bridge that distance either? A repeater would work and for really confident communication maybe even a second repeater?

I am not sure what the Path(File) substitute %y-%m-%d is meant to represent? Are you trying to export a file as Year-Month-Day.csv? If so then "y" (lower case) is not a variable for year, "m" (lower) is for minute as one or two digit number, no leading zeros and "d" (lower case) as a single letter ...

Is there a way to identify units which might be impacted by this issue before any FW updates? Say by Lic #/Details etc? Or is there some cut-off date etc from which newer units are known to be issue free?

Also does this issue affect the Nano which I believe pre-dated the MBPro2

Power supply is 5V, USB Micro to Pro2 at around 400mA @ 2W

Antenna connectors are SMA for RF and RP-SMA for WiFi

That would be appropriate if the check was "before every full hour", "before every 3rd full hour" and using -havg which is the average value of this hour then at every 3 hours you you are only looking at the past hour and if that is what you expect then all is good?

If you actually wanted the ...

So another way to deal with it, if reqd., would be to put into the syntax, the operators that would deal with no data.......generate dashes if reqd.????


That would be for when there is no valid data (as such) but in the "after each full hour" case using -havg etc the data is not invalid it just ...

This seems good for one event. Set up for "After every full hour".

Sun Exposure @ [[hh]:[mm]##if# {*([sol0rad-havg] >=150.0) && ([uv0index-havg] >=1.5) && ([sol0total-dmax=h] >=3.0)*} #then# Exposure High #else# Low Danger #fi#

But when it actually ran on the hour, all I got was this:

#if ...

Daily Reebot to update versions, simply because of that. It's not a Davis, it's a Fine Offset WT1081. Each rain gauge stroke is 0.3 mm. What would you set in the case of Clear? I'm unsure about that.


On the daily auto Reboot thing to update version, that's not a thing I will ever do for any ...

A problem that I have encountered is that every time my device, the trigger, gives the order to reboot daily with http://templates.meteobridge.com/reboot.sh it trigger a rain event (false).

https://i.postimg.cc/gJgJNqWy/Rain.png

https://i.postimg.cc/y6JgvtDk/reboot.png


Thanks for any help ...

If I wanted to make an alarm that included Solar Radiation, UV Index, and Sunshine duration, how would you fill in the X's? Especially the watts per sq meter??

[sol0rad-act=x.X:X] <= n.n [uv0index-act=x.X:X] <= n.n [sol0total-act=x.X:X] <= n.n


The basic variable structure is sensor-selector ...

Then how about setting up an Email event at a Specific Time [18:00] with a Subj# Body something like

Frost Risk @ [[hh]:[mm]##if# {*(Condition1) && (Conditon2) && (Condition3)*} #then# Yes #else# No #fi#

On the event tab but thinking some more might not be be an option without being able to nest the expression?

But with the one time alert maybe also able to incorporate the time (just thinking again) but just to clarify does the 6:00 PM only relate to the Temp? Assuming it would be, and wind, and ...

You should be able to frame a specific time and the other conditions using #if# #then# #else# #fi# and send an email etc?