meteohub.de

You can also export from the Meteobridge, script see appendix.
The output in the browser must then be saved in a text editor as 2023.csv

http://MB-IP/cgi-bin/export.cgi?period=2023&resolution=day&template=MB_year_output.exp


Does that work on the regular Meteobridge software though? Or just ...

that probably is demo data , but yes if you have been using for example the template throughout 2023 then yes you can simply replace the 2023.csv file in the weather34charts folder if you have it stored safely (most dont practice backups :-) ) if not get in touch next week we will back in Istanbul ...

I just installed this template a few days ago, but I see historical data on all of the yearly charts. Looking through the files on my web server, I see the source data appears to be in the /weather34charts folder. It does not match my records--not that I expected it to since Meteobridge does not ...

Hi Brian. For some time now I have had an error displaying the weather via the wu api key and the metar one. I bring some screenshots to try to show you what I'm talking about. I don't know what I can depend on, but it's as if the dashboard doesn't draw from the api keys. could you try to ...

Hi Brian. For some time now I have had an error displaying the weather via the wu api key and the metar one. I bring some screenshots to try to show you what I'm talking about. I don't know what I can depend on, but it's as if the dashboard doesn't draw from the api keys. could you try to figure ...

My VP2 console displays a "Rain Storm" value on the console which I find very useful. Could this be added to Meteobridge? I searched but could not find any similar previous requests.

I did a reboot. Now running Meteobridge 3.6 (May 13 2018, build 12196), FW 1.3
And the "tooltips" are shown as usual.

It looks like a problem of a "security" setting in Chrome to not allow pop-ups and-the-likes.
Could you test with FF or Safari?
And do a reboot of the Meteobridge to see if May 13 ...

wvdkuil wrote: Sat May 26, 2018 8:50 am Working correctly here with Google Chrome Versie 66.0.3359.181 (Officiële build) (64-bits)

Hmm, same version of Chrome for me, but I am on the May 8 release of Meteobridge and I see you are on February 12. Perhaps something changed in Meteobridge between those releases?

-Mike

I recall that previously when hovering the mouse over a data value on the Live Data page, it would show the date/time that data point was recorded. That seems to have stopped working for me over the past few months on the last few releases of Google Chrome (currently on version 66) on Windows 10 ...

It has been over a month since my posts, just wanted to see if you could at least consider any of this Boris, or if anyone else had any feedback. Thank you.

-Mike

Awesome, glad you found it -- happy to help.

Boris, perhaps the Templates wiki can be clarified so others don't run into this?

-Mike

"#welsum [hh]:00 Temp:[th0temp-act.1]C Gras:[th1temp-hmin.1]C"

* it succeeds always when I execute this template manually (by pushing the test-button). Literaly, always
* it fails always when I schedule this template 'after every full hour'. Literaly, always
* it succeeds always when I schedule ...

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 ...

Another suggestion.. I am aware of problems using the percent (%) and double-quotes (") characters with certain template and Twitter push functions; perhaps there is a way to add Meteobridge variables (i.e. [char-percent] and [char-quotes]) that could handle them properly?

-Mike

Turns out my VP2 console was reporting the low battery condition, but for some reason the Meteobridge was not identifying it immediately. A couple days later it did trigger the alert. Could have been related to my failed supercapacitor which is now fixed.

-Mike