[Ovmsdev] OVMS v3 v3.2.002 Over-the-Air firmware update

[Stephen Casner]

This evening I have received 6 notifications (so far) from the iOS app
telling me that this new release is available.  I have properly
dismissed each of the notifications, so it is not just a repeat for
lack of acknowledgement.  Is something broken?

                                                        -- Steve

On Mon, 27 May 2019, Mark Webb-Johnson wrote:

> Today, we are pleased to release v3.2.002 to general availability. This is the first
> public v3.2 version, with approximately 200 bug fixes and enhancements (mostly to
> individual vehicle support modules).
> A summary of the major changes is here:
>
> 2019-05-12 MWJ  3.2.002  OTA release
> - Locations: Introduce support for location actions
> - Twizy: Release 1.0.0 -- all V2 features planned are now included in V3
> - Vehicle framework: Regenerative braking signal generation
> - Vehicle framework: DBC and RETOOLS integrations
> - Vehicles: Extensions to Kia Niro, Kia Soul, Mitsubishi, Nissan Leaf,
>   Renault Twizy, SmartID, Tesla Model S, and Think City
> For full detail on all changes, check the GitHub revision history.
> The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all
> without requiring special hardware programmers like the PICKIT used for v2. The
> simplest way to update the module firmware is to connect it as a client to your wifi
> network (or phone hotspot), and then use the web interface Config / Firmware /
> Flash-from-Web; that will show you the version you are running, as well as the latest
> version available for update. One click on 'Flash now' and the update will be
> downloaded and installed. Alternatively, you can download the firmware update to a
> file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the
> card into the module's slot - the new firmware will be updated automatically and the
> file renamed ovms3.done to signify completion.
> This firmware also includes the feature to check for and automatically update to newly
> available firmware, every night (so long as the vehicle is connected to WiFi). After
> updating to 3.1.005 or later, you can enable this for future firmware releases with
> 'config ota auto yes'. You can choose the release level by setting 'config ota tag
> edge|eap|main', as one of:
>
>  *  edge: Bleeding edge developer nightly-builds
>  *  eap: Early Access Program (full releases, but with little public testing)
>  *  main: Publicly tested full releases (the most stable)
>
> Thank you to all the open source developers who have contributed to this, and
> previous, releases, and thank you for your support of the project.
> Open Vehicles