meteohub.de

Hello,

I have a wired Davis Vantage Pro2 ISS + Direct Connect kit from smartbedded UG connected to TP-LINK TL-WR703N v1. I did not have a USB 2.0 yet, but I have direct connect kit USB connected directly to TP-Link.
I did not have Toradex USB pressure sensor, which is no longer in production and could not be purchased anywhere in the World (I tried Swiss, Germany, Italy, Japan...)
This combination works, but with some problems.

My main problem is that when data are send to WeatherUnderground, Meteobridge send there this:

<pressure_string>-999.00" (-33826.1 mb)</pressure_string>
<pressure_mb>-33826.1</pressure_mb>
<pressure_in>-999.00</pressure_in>

Is there any way to disable sending of pressure or to add a new option in tab Select Station Davis: wired Vantage Pro2 ISS (with smartbedded "direct connect kit" WITHOUT Toradex OAK-P USB sensor)?

Another problem which is releated to this is, that datalogger restart itself every 7.5 minutes! Is is really not a good think.
Here is a small post from Meteobridge System messages:

logger (17.09.2013 16:34:06): data logger stopped.
logger (17.09.2013 16:34:06): Historical data loaded (10 records).
logger (17.09.2013 16:34:06): data logger (version 4.9v, build 2484) started.
logger (17.09.2013 16:34:07): station 0 (ISS direct), adapter is version "1.1".
logger (17.09.2013 16:34:07): connect station 0 (ISS direct via USB serial).
logger (17.09.2013 16:34:07): connect station 1 (OAK Baro via USB HID).
logger (17.09.2013 16:41:36): no data synchronization with station 1 (OAK Baro) for 450 seconds, data logger will be restarted.
logger (17.09.2013 16:41:37): disconnect station 0 (ISS direct): exit
logger (17.09.2013 16:41:37): disconnect station 1 (OAK Baro): exit
logger (17.09.2013 16:41:37): data logger stopped.
logger (17.09.2013 16:41:37): Historical data loaded (10 records).
logger (17.09.2013 16:41:37): data logger (version 4.9v, build 2484) started.
logger (17.09.2013 16:41:38): station 0 (ISS direct), adapter is version "1.1".
logger (17.09.2013 16:41:38): connect station 0 (ISS direct via USB serial).
logger (17.09.2013 16:41:38): connect station 1 (OAK Baro via USB HID).
logger (17.09.2013 16:49:08): data logger stopped.
logger (17.09.2013 16:49:08): Historical data loaded (10 records).
logger (17.09.2013 16:49:08): data logger (version 4.9v, build 2484) started.
logger (17.09.2013 16:49:09): station 0 (ISS direct), adapter is version "1.1".
logger (17.09.2013 16:49:09): connect station 0 (ISS direct via USB serial).
logger (17.09.2013 16:49:09): connect station 1 (OAK Baro via USB HID).

I really like Meteobridge and will buy it, but these errors are not good for my data collection.

I don't think Meteobridge is storing "-999" there, but that WU is filling that in when no valid pressure provided.

The restart problem can be solved with next update.

Many thanks for fast reply and correction of datalogger restart in next release.
But what about option to have only Davis IIS wihout a Todarex USB pressure in Select station tag?
And is it necessary to have a USB 2.0 hub with my settings (Davis ISS + Direct connect kit + TP-Link)?

not having a pressure sensor will be troublesome with most weather networks. howver, when no pressure sensor avail, pressure will not be reported regardless if toradex is tried to being used or not.

Thanks for clarify it.
I am planning to use Arduino + pressure sensor for barometric pressure read and upload to weather sites.
Hope that in next release will be fix for datalogger restart.

fixed with uploaded update, please reboot to get this new version.

I installed a new verison based on your info, but it did caused another problem. It runs a while, but after some time all sensors were frozen and Meteobridge did not read any data from ISS.

wnetd (20.09.2013 07:51:04): process started.
logger (20.09.2013 07:51:06): Historical data loaded (10 records).
logger (20.09.2013 07:51:06): data logger (version 4.9v, build 2523) started.
logger (20.09.2013 07:51:07): station 0 (ISS direct), adapter is version "1.1".
logger (20.09.2013 07:51:07): connect station 0 (ISS direct via USB serial).
logger (20.09.2013 07:51:07): connect station 1 (OAK Baro via USB HID).
logger (20.09.2013 09:21:07): data logger stopped.
logger (20.09.2013 09:21:07): Historical data loaded (10 records).
logger (20.09.2013 09:21:07): data logger (version 4.9v, build 2523) started.
logger (20.09.2013 09:21:08): station 0 (ISS direct), adapter is version "1.1".
logger (20.09.2013 09:21:08): connect station 0 (ISS direct via USB serial).
logger (20.09.2013 09:21:08): connect station 1 (OAK Baro via USB HID).

UPDATE, Meteobridge sensors were frozen for second time today. Did not show live data at all (from cca 10:35 till 12:00).

wnetd (20.09.2013 09:43:04): process started.
logger (20.09.2013 09:43:05): Historical data loaded (10 records).
logger (20.09.2013 09:43:05): data logger (version 4.9v, build 2523) started.
logger (20.09.2013 09:43:07): station 0 (ISS direct), adapter is version "1.1".
logger (20.09.2013 09:43:07): connect station 0 (ISS direct via USB serial).
logger (20.09.2013 09:43:07): connect station 1 (OAK Baro via USB HID).
logger (20.09.2013 12:04:50): no data synchronization with station 1 (OAK Baro) for 5400 seconds, data logger will be restarted.
logger (20.09.2013 12:04:50): disconnect station 0 (ISS direct): exit
logger (20.09.2013 12:04:50): disconnect station 1 (OAK Baro): exit
logger (20.09.2013 12:04:50): data logger stopped.
logger (20.09.2013 12:05:12): Historical data loaded (10 records).
logger (20.09.2013 12:05:12): data logger (version 4.9v, build 2523) started.
logger (20.09.2013 12:05:13): station 0 (ISS direct), adapter is version "1.1".
logger (20.09.2013 12:05:13): connect station 0 (ISS direct via USB serial).
logger (20.09.2013 12:05:13): connect station 1 (OAK Baro via USB HID).

This looks like a problem with connectivity of direct connect kit with weather station to me.
Can you cure the symptoms by disconnecting ISS from the connect kit an then connecting
the ISS again (without restarting datalogger of Meteobridge)?
Answer on this might help to understand at what point the error occurs. I doubt it is
Meteobridge related, as all other stations seem to run fine.

Meteobridge runs for one day, then freeze again. I check a web interface to see what going on but MB restart himself. Then I unplug a cabel as you advice and MB send a really crazy amount of rain falls to internet, cca 2500mm/hour at first moment after reconnect. Then situation goes slowly to normal (no other crazy amount). I will check it in few hours to see whats going on...

UPDATE:
It is up and running, but did not know how long, because watch time period is too short. I will see more tommorow (after one day).

wnetd (21.09.2013 14:13:02): process started.
logger (21.09.2013 14:13:04): Historical data loaded (10 records).
logger (21.09.2013 14:13:04): data logger (version 4.9v, build 2523) started.
logger (21.09.2013 14:13:05): station 0 (ISS direct), adapter is version "1.1".
logger (21.09.2013 14:13:05): connect station 0 (ISS direct via USB serial).
logger (21.09.2013 14:13:05): connect station 1 (OAK Baro via USB HID).
logger (21.09.2013 17:13:06): data logger stopped.
logger (21.09.2013 17:13:06): Historical data loaded (10 records).
logger (21.09.2013 17:13:06): data logger (version 4.9v, build 2523) started.
logger (21.09.2013 17:13:07): station 0 (ISS direct), adapter is version "1.1".
logger (21.09.2013 17:13:07): connect station 0 (ISS direct via USB serial).
logger (21.09.2013 17:13:07): connect station 1 (OAK Baro via USB HID).

UPDATE 2 from 9:00 AM (22/9)
Situation is repeating, it did stop again. It is really not good at all
Stuck all night till reboot now What can I do with this? Any solution?

wnetd (21.09.2013 14:13:02): process started.
logger (21.09.2013 14:13:04): Historical data loaded (10 records).
logger (21.09.2013 14:13:04): data logger (version 4.9v, build 2523) started.
logger (21.09.2013 14:13:05): station 0 (ISS direct), adapter is version "1.1".
logger (21.09.2013 14:13:05): connect station 0 (ISS direct via USB serial).
logger (21.09.2013 14:13:05): connect station 1 (OAK Baro via USB HID).
logger (21.09.2013 17:13:06): data logger stopped.
logger (21.09.2013 17:13:06): Historical data loaded (10 records).
logger (21.09.2013 17:13:06): data logger (version 4.9v, build 2523) started.
logger (21.09.2013 17:13:07): station 0 (ISS direct), adapter is version "1.1".
logger (21.09.2013 17:13:07): connect station 0 (ISS direct via USB serial).
logger (21.09.2013 17:13:07): connect station 1 (OAK Baro via USB HID).
logger (21.09.2013 20:13:07): data logger stopped.
logger (21.09.2013 20:13:07): Historical data loaded (10 records).
logger (21.09.2013 20:13:07): data logger (version 4.9v, build 2523) started.
logger (21.09.2013 20:13:08): station 0 (ISS direct), adapter is version "1.1".
logger (21.09.2013 20:13:08): connect station 0 (ISS direct via USB serial).
logger (21.09.2013 20:13:08): connect station 1 (OAK Baro via USB HID).
logger (21.09.2013 23:13:08): data logger stopped.
logger (21.09.2013 23:13:08): Historical data loaded (10 records).
logger (21.09.2013 23:13:08): data logger (version 4.9v, build 2523) started.
logger (21.09.2013 23:13:09): station 0 (ISS direct), adapter is version "1.1".
logger (21.09.2013 23:13:09): connect station 0 (ISS direct via USB serial).
logger (21.09.2013 23:13:09): connect station 1 (OAK Baro via USB HID).
logger (22.09.2013 01:49:43): child process received timeout signal (14).
logger (22.09.2013 01:49:44): data logger stopped.
logger (22.09.2013 01:49:44): Historical data loaded (10 records).
logger (22.09.2013 01:49:44): data logger (version 4.9v, build 2523) started.
logger (22.09.2013 01:49:47): station 0 (ISS direct), adapter is version "1.1".
logger (22.09.2013 01:49:47): connect station 0 (ISS direct via USB serial).
logger (22.09.2013 01:49:47): connect station 1 (OAK Baro via USB HID).
logger (22.09.2013 03:50:17): child process received timeout signal (14).
logger (22.09.2013 03:50:18): data logger stopped.
logger (22.09.2013 03:50:18): Historical data loaded (10 records).
logger (22.09.2013 03:50:18): data logger (version 4.9v, build 2523) started.
logger (22.09.2013 03:50:22): station 0 (ISS direct), adapter is version "1.1".
logger (22.09.2013 03:50:22): connect station 0 (ISS direct via USB serial).
logger (22.09.2013 03:50:22): connect station 1 (OAK Baro via USB HID).
logger (22.09.2013 05:50:52): child process received timeout signal (14).
logger (22.09.2013 05:50:53): data logger stopped.
logger (22.09.2013 05:50:53): Historical data loaded (10 records).
logger (22.09.2013 05:50:53): data logger (version 4.9v, build 2523) started.
logger (22.09.2013 05:50:56): station 0 (ISS direct), adapter is version "1.1".
logger (22.09.2013 05:50:56): connect station 0 (ISS direct via USB serial).
logger (22.09.2013 05:50:56): connect station 1 (OAK Baro via USB HID).
logger (22.09.2013 07:51:26): child process received timeout signal (14).
logger (22.09.2013 07:51:27): data logger stopped.
logger (22.09.2013 07:51:27): Historical data loaded (10 records).
logger (22.09.2013 07:51:27): data logger (version 4.9v, build 2523) started.
logger (22.09.2013 07:51:30): station 0 (ISS direct), adapter is version "1.1".
logger (22.09.2013 07:51:30): connect station 0 (ISS direct via USB serial).
logger (22.09.2013 07:51:30): connect station 1 (OAK Baro via USB HID).

If you want to know better times when it stops, you can check http://www.wunderground.com/weatherstat ... =IPLZEU015

I am really unhappy. The situation did not changed after 3 days of checking. MB stops reading sensor and the reboot is necessary. It works sometimes almost whole day, sometimes just few hours. I have no idea, what can I do more to solve this problem.

I am wondering if the situation will changed for better, if I will buy a wireless Davis VP2 + USB datalogger and connect them to MB. Is this configuration better tested? I dont want to deal with this anymore, just plug and play, not plug and pray. I was hoping that this configuration cabled Davis + Direct connect will work smoothly, but I was mistaken. I will probably use a cabled version of Davis VP2 + Direct connect kit directly with PC. It works in this configuration earlier without any major issues. Instead of one I will have two weather station, 1 home + 1 cottage, more than I wanted, but such is a life, we need find easy solution and live a happy life

hajovka wrote:I am really unhappy. The situation did not changed after 3 days of checking. MB stops reading sensor and the reboot is necessary. It works sometimes almost whole day, sometimes just few hours. I have no idea, what can I do more to solve this problem.

I am wondering if the situation will changed for better, if I will buy a wireless Davis VP2 + USB datalogger and connect them to MB. Is this configuration better tested? I dont want to deal with this anymore, just plug and play, not plug and pray. I was hoping that this configuration cabled Davis + Direct connect will work smoothly, but I was mistaken. I will probably use a cabled version of Davis VP2 + Direct connect kit directly with PC. It works in this configuration earlier without any major issues. Instead of one I will have two weather station, 1 home + 1 cottage, more than I wanted, but such is a life, we need find easy solution and live a happy life

Asking the question is giving the answer:
I think 90% percent of Davis users nowadays have a wireless Davis VP2 with either an USB or an IP logger.
Every weather-program I tested works without glitches with these stations, even if you have soil/temp/leaf sensors/ extra temp sensors/UV/ solar and so on. And as a WeatherTemplate developer I tested with at least three different DAVIS stations with and without extras but always with at an official logger (USB, serial or IP) with Meteohub/ Meteobridge (and with WD / WL / CU and even on the Mac with WeatherSnoop).
But if you are in that grey area of not that commomn configurations? If you can afford it, please choose the most common weather station with the most common logger. Thats makes live for programmers and for the users of the program much more pleasant.
My MB works for weeks / months in a row and I have to restart it only to test a new version of MB. One of the Meteohub stations is working since 26-04-2013 13:13.
Three Davis stations and not one glitch with the Meteohub / Meteobridge software.
Uploading to 4 different websites at three diferent providers and to Meteoplug, without any noticible interruption.
I hope you can solve your problems with the connection between davis and MB soon, Wim

@hajovka: I fear the direct connect kit is not working stable in your setup. That appears to be a HW problem to me. Tricky thing is that the converter does also feed the ISS with power and that might not provide enough juice in all situations. To get you rid of these problems, I can offer to refund the kit so that you don't have a dead invest when adding a Davis envoy (not the 8x!) or console with logger to it. Please email to "info@meteohub.de" how to proceed.

Dear all, thank you very much for your information.
The way with cabled Envoy will be probably the best solution.