meteohub.de

While lot of technical things do kept my attention during development of Meteohub in the last months, I would like to focus next update on long waiting improvements on weather data functionality.

On top of my todo list are:
- fixing evotranspiration for Vantage
- baro trends for weather networks

What else is of urgent importance for you?

Hi Boris,

I'm surprised that nobody jumps on this tread.

Personally I feel that the issues listed are the ones most requested.

Can you also have a look at this one:
viewtopic.php?f=8&t=8185
I've seen various ways of working around the lack of yesterdays summary information, but it would be much better if those are natively provided.

Another things is the measurement reporting for the media wear. Would be useful if it not only reports the number of rounds, but also the number of days this number refers to. And make those numbers available in the standard way other hardware facts are reported (like [actual_system_platform_text]).

Thanks so much for making it better!

Ysbrand

Hi Boris,

Can you change the firmware so a virtual sensor can be used to trigger another virtual sensor?

I have three sensors from a CC128. I would like to sum two and subtract the third (data20 + data21 - data23). I am currently using sensaddmaster/slave and making a virtual sensor but I cannot use the resulting virtual sensor with sensdiffmaster/slave.

Or, is there a better way?

Andrew
SMB_weather
http://www.4852q.info

Maybe viewtopic.php?f=13&t=6949&p=9184#p9184

lg
Martin

Having a separate field for the wind speed/direction sensor elevation from the weather station console elevation field to improve windchill and other dependent parameters computations more accurately

Dont know if it is possible but it would be great to have Meteohub report the battery level for each wireless sensor of the AWS ... maybe even an email alert when it gets down to 20% level?

Boris for some unknown reason we are experimenting in at least 6 MEADE TE923W WS, all used with Sheeva plug/Meteohub 4.9k firmware that one of the sensor stops logging and their console doesnt search for the "missing" sensor after 5 minutes without receiving data to reconnect to it. If I press channel search the console reconnects to the sensor. Are you aware of this? Is there any way to set up the Meteohub application to do a sensor communication search after 5 minutes without data to reestablish the wireless link? If this is not available in the Meteohub application it should be implemented URGENTLY what do you think?

As a former Weather Display and WDL user for 5 years (and for a year a very happy and stable Meteohub user) there are a few that are missing with Meteohub:

For WDL
Highest daily rainfall
Highest rain in 1 hour
Warmest day
Coldest night
Coldest day
Warmest night

are missing.

and a choice for manually enter your weather records would be perfect.... Then I really do not have anything to wish for (might be a bad thing itself )

Also some kind of Boltek Lightning detectors integration to the Meteohub and making the data they report available to the web through FTP upload would suit my future needs/plans

YJB wrote:I've seen various ways of working around the lack of yesterdays summary information, but it would be much better if those are natively provided.

At the risk of querying the obvious, I wonder if the following concept would be possible natively?

At midnight, instead of just initialising fresh "today" values, first copy all the final "today" values to "yesterday" equivalents.

With that approach there would (I think) be only a minimal extra processing load during day to day running, in return for a lot of extra data.

I think that the only occasion when significant extra processing would be needed would be the case of a recompute, in which case "yesterday" values would need to be fully re-assessed.

Just a thought...

PS. Last month & last year?

- Automatic data backup interval according to the selected folder / public / and or FTP. This is me most is missing
- Me no further accumulation of precipitation viewtopic.php?f=13&t=8462

Already mentioned before by YJB.

Becoming more important as our devices are aging continuously.
Is it possible to have the number of rounds the media is written (since release 4.9) not only visible on the webpage
Storage
Media: TS4GCF300 20110615 (344.58 rounds)
but also in a data variable as a System Data ID.

I could then display that on my website which is far more easier than going to a local device to log on and check.

Thanks for considering this,

Wim

Boris,

There still is an issue of SLP reporting from a VP2. Your SLP calculation differs slightly from Davis based on a publication of the Davis formula applied to the raw baro when the station is located significantly above sea level. But the difference is not enough to explain the big and unresolved difference in what is reported to Weather Underground by my VP2 wx station at 1350m altitude (despite applying the numerous workarounds posted here and on other boards).

Jim

Does it say "firmware version cannot be read" (or similar) in "meteohub log"?
If so, it is not making use of LOOP2 packets and therefore lacks original
station pressure data but tries to reconstruct these from Vantages SLP,
which does not work too good at larger altitudes. Station pressure is
used to compute altimeter pressure, where you then get aware of the problem.

Hi Boris. The FW ver and LOOP2 packets are read successfully (it required a bugfix by you that I pointed out a year or so ago). But it never made any difference in the significant discrepancy in the SLP.

Hi,

it would be really great if we had the ability to create variables of the type: "YYYYMMDD_th0_temp_c". Since we have the raw data, is it so difficult to create such variables? If we had these variables, we could easily create daily, monthly or yearly weather summaries.