meteohub.de

Version 2.1 is now available and will be installed on next reboot (unless you forced your Meteobridge on "System" tab to stick with version 2.0).

• adapts to a forced change of twitter API from January 14, 2014
• allows for special characters in weather network user ids and passwords
• expands number of ftp file uploads from 4 to 6
• allows for pressure correction with 3 decimals (requested for in/Hg units). After updating from former Meteobridge versions twitter authentification needs to be walked through from scratch again.

It's time to renew! Thanks a lot!

System, System, Version Control has "stick to version 2.0" and "newest".

I'm thinking you want it to be "stick to version 2.1". I loaded v2.1 fine. I then selected "stick to version 2.0" and rebooted and it downgraded from v2.1 to 2.0. Maybe is should be "stick to loaded version" (or something like that)?

it is meant this way...
"newest" = get the latest released version on reboot
"version x.y" = load that particular version on reboot

The version feature was requested to give the user the opportunity to stick to a stable version
and not to take the risk of being faced to new bugs introduced with new versions.
So when you have your Meteobridge in a production environment far away that might
be a good option to improve stability. I will add more proven versions to select from
in the future, so that the list will grow.

I would still recommend to stay with "newest" for most users, as we didn't face much
issues when switching to new releases so far...

OK, I see what you are trying to do. A problem (for me) is that I want to use a feature you implemented (for me – thanks!) in release 2.1, but I don’t want to always automatically upgrade to the next release. Using Newest gives me 2.1, but also will automatically upgrade me to 2.2, 2.3, which I may not want to do, but if I select 2.0 then when I reboot I’ll revert back to 2.0 and lose the change. I personally do like the feature where I'm not automatically upgraded as I typically do my software upgrades on my computer manually - I turn automatic off.

If it isn't a big problem, maybe adding "Don't automatically upgrade my version" would be an option too. So your list could be:

"Newest" (recommended)
"Never" (Don’t upgrade – stick with the version I’m currently using)
2.0 (Added these features…)
3.0 (Added these features…)
etc.

I would use "Never" (like I do with all of my other software), and when I'm ready try out the latest to see how it works I’ll switch to the latest “good” baseline or just the latest and give it a shot.

What you are asking for is not possible, as the Meteobridge cannot store the current image.
It always loads the current image (or one I have marked as a stable fall back version) from
the server. So you have to wait a bit until I make 2.1 the next stable release and you
can then stick your system to that, unless you fall in love with a new feature again #

To give you an impression... the MR3020 has 4 MB of flash and 32 MB of RAM and
the application stack needed for Meteobridge doesn't fit into flash... no way...

Thanks a lot for this update!

OK, thanks. I'm sure you'll be coming out with new features that I'll have to have too.

As a side note, for extra memory can you plan (sometime in the future) to use the (now optional, future mandatory?) USB stick to store various things to relieve the load on RAM? I already have the USB stick ready to go!

What about an option "reboot with last successful version"? There is no need to store firmware. Just store which version number that last time it boot successfully.

Kanok