meteohub.de

I've got a Weatherlink Live connected to my Meteobridge Pro. All working well, except my external temp sensor. I have a Davis vantage Pro 2. ISS running on ID=2, external temp sensor running on ID=3. When I look at the Live data-tab, the temp sensor is displayed as 'Outdoor temp #3'. Value is correc...

Hi, I'm sorry to have a Dutch-translation discussion on this forum, to convince a German native speaker of the correctness of Dutch/English translation, but there are some flaws in the given translation. For example, radiation does indeed translate to 'bestraling', but this is the equivalent to the ...

Thanks for the response

Thanks for both replies. Most helpful!

Hi, I am using the RF-unit to directly connect to the ISS and a separate temperature unit (all Davis VPro2). The ISS and temperature unit are not very nearby, therefor I've located some years ago a repeater in between to pick up the original ISS- and unit-signal, and retransmit it to my house. In th...

Hi,

I've connected MBPro to my Davis VPro2. I see LOOP(2)-data coming in nicely.

Question: In the situation that MBPro is shut off for a while (like couple of hours), does it catch up with the archived data from the Davis archive memory? Or is MBPro 'only' eating LOOP(2)-data?

Thanks.

Hi,

thanks for the advise. This worked for me.

Hi, I've purchased a MBPro unit last week, very satisfied. Connected with a Davis VP2 Pro, via RF signals. All is working well. I was wondering if I can set somewhere the annual rain amount of this year 2018. As I am using the saratoga template, together with the WD-live files (clientraw*.txt) gener...

Check, all in working order now. Default values applied. This is my current tweet-template I'm using. Shooting ath the end of every hour (59 minutes in my case): #welsum [hh]:[mm] Temp:[th0temp-act.1:---]°C Gras:[th1temp-hmin.1:---]°C Wind:[wind0wind-avg10.1:---]m/s [wind0dir-act.0:---]° Stoot:[wind...

Agreed Boris. Scheduling is not the root cause, but it is the trigger of the error. Applying default values will solve it.

Thanks for all the help! Will apply the default values, and follow up on this.

Hi Mike, Thanks for the good thoughts. I was convinced the cause must be lying somewhere in the choosen interval, so I tested the schedule 'just before every hour'. And guess what, no errors anymore. I think you nailed it, and your analysis is sound (and logical). Now I have tweets send every 59 min...

Perhaps there is an issue with Meteobridge parsing the '#' symbol as the first character? Have you tried removing that for testing purposes? -Mike Removing the #-sign doesnt make any difference. Still failing on the top of the hour: 2017-09-08 09:00:00 Error: sed: unmatched '/' can not decode tweet...

I use much longer Twitter templates (if statements, numerous variables, plain text, etc) and have no issues with scheduled tweets. The template hoevenvd is using would never even reach half of the 140 character limit for Twitter, unless his temperatures had risen into the millions of degrees! ;) Pe...

Hi, thanks for the response. I've searched the forum before my posting, and eliminated the possibility of a tweet-message that's too long. That's why my current template is very short: "#welsum [hh]:00 Temp:[th0temp-act.1]C Gras:[th1temp-hmin.1]C" So, the length could not be the case. Howe...

Hi, Yes, I understand the error message. But it figures me what that odd character is. As my Twitter-template is: #welsum [hh]:00 Temp:[th0temp-act.1]C Gras:[th1temp-hmin.1]C I absolutely cannot see a strange character in this. Unless the [xx]-variables are somehow 'translated' as a strange-characte...