Get latest on reboot

[grwkak]

I seem to be missing something. Thought I would roll back Meteobridge to ver 3.7 to test the Twitter issue.
Used the "stick with 3.7" in the drop-down in the system tab.
Ver 3.7 still had the Twitter issue - can't seem to get to ver 3.8 even though "get latest on reboot" is selected before a reboot.
What am I missing?

Guy

[Mattk]

The latest version for the MBPro I think is still 3.7 (Oct 21,2018)? It's only the NANO that has a V3.8 which has been updated 2 times (22 & 28 Oct)? Maybe Boris can clarify this further between the MB & Nano releases?

[weatherist34]

3.8 only appears on Nano here not seeing 3.8 on TP-LINK MR3030 with meteobridge so i would say your spot on..

[hymrog]

Running Meteobridge 3.8 on tp link tl-mr 3020 build 12419. That is latest version available I believe.

[grwkak]

Did another reboot - got 3.8 now. Not sure why it would not load before.

Guy

[Mattk]

Yes it does now as of the latest update released October 31, 2018 but would not go to V3.8 releases on the 22 & 28 Oct which were tagged as only "Meteobridge NANO" changes.

Whether this was the intent or not, not sure but certainly working now for the latest release with a Pro fix.

[Mattk]

Have a NANO which does not appear to get "get newest on boot" and will only install V3.7 (October 21,2018) and won't pick up V3.8. Anybody else not getting V3.8 on a NANO?

[weatherist34]

do backup for restore file option and open it in a editor and look for line too see if it exists xvcontrol 3.7 if so delete it and save restore saved file and reboot. mine is near the bottom might work for you

xsyncmisc 0
xhws 0
xhwstries 5
xvcontrol 3.7
x_country Turkey
x_flagurl http://www.ip-tracker.org/images/ip-flags/tr.png
x_region Istanbul
x_city Istanbul
x_postalcode 34110
x_provider Turk Telekom
x_timezone Europe/Istanbul
x_latitude 41.0177
x_longitude 28.9744

[Mattk]

Thanks weatherist34 that did work.

Rebooted to 3.8 and Version Control allowed the normal options "get newest on boot" and "stick to version 3.7". I don't use "get newest on boot" by default so selected "stick to version 3.7", rebooted, it does load V3.7, Version control now only allows "get newest on boot", reboot again and same issue before, doesn't get the newest version and stays stuck to V3.7

Restore modified config, reboot, get V3.8 back but as above trying to stick to 3.7 doesn't work as normal/expected.

Original issue fixed, have 3.8 but Version control only really accepts "get newest on boot". Maybe once there is another/new version the option to stick to a version may work?

[hymrog]

It looks like at some point the ability to choose to stick to a certain version has been removed. I am running 3.2 on one of my rigs and it gives the option to to stick to current version.

[Mattk]

It looks like at some point the ability to choose to stick to a certain version has been removed. I am running 3.2 on one of my rigs and it gives the option to to stick to current version.

No I don't think that is the case at all, this is just an issue with the Nano which only had a new (first) version update on Oct 22 going from initial version 3.7 to 3.8, the MBPro doesn't have this issue neither does the MB both of which have multiple versions to stick to, the Nano will be no different.

[admin]

There was a short period of time during the last weeks where I had to rewind from 3.8 to 3.7 as there was a hard bug in the final 3.7 version that needed a fix. In the meantime available versions are as always:

1) You get the current version which is still subject of development by selecting "newest on boot". Currently that is 3.8 on all platforms.

2) Depending on the platform you are using, you will be able to select older versions that are not subject to change anymore. As some platforms like the MB PRO or MB NANO are newer than the original Meteobridge these just offer downgrades to the version being recent when they entered the market.

3) when you have selected version 3.4 (for example) you will not be able to upgrade to 3.5 directly, as 3.5 was not developed when we finalized 3.4. and so there is not option in the drop-down to select this. When you want to upgrade to newer versions the way is to select "newest on boot" and to reboot. Having done so you will be offered all versions and you can then stick to one you prefer or you can stay at newest which I guess most users do.

[Mattk]

Running 3.8, select stick to 3.7, reboot, now running 3.7, only Version control option is "get newest on boot" so at this point would appear to have no option other than "get newest on boot" at next reboot, unable to stick to 3.7 if I do reboot?

So reboot, still only have 3.7 and only version control option is "get newest on boot", the way around this at the moment is to backup, edit (remove xvcontrol) and restore configuration data, reboot and will be running 3.8 with only Version control options "Stick to version 3.7" or "get newest on boot", essentially the same an an MB (at this stage)

As a totally new device and delivered with say Verison 3.7 the only version control option is "get newest on boot", I would have thought "stick to version 3.7" should also be in the base version options as only option is "get newest on boot" which currently doesn't "get newest on boot" without some editing.

[galfert]

I think there is a bug in 3.7.

Solution
Roll back to 3.6
Reboot
Then select Latest Version.
Reboot
You'll now be on 3.8

Version 3.7 has a bug which doesn't let you jump to 3.8.

[Mattk]

Nano only started with the first version/release of 3.7 (unable to roll back to 3.6 as a MB might) but now with the SD card version management is same as MBPro, much more flexible.