mirrors
/
Tasmota
mirror of https://github.com/arendst/Tasmota.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Upgrading (markdown)

Michael Ingraham 2019-10-04 09:56:20 -04:00
parent c3a66e42c0
commit 9358d182d0
1 changed files with 19 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
Upgrading.md

@ -5,7 +5,7 @@ The first rule of upgrading: _**If it ain't broke, don't fix it!**_ In other wor
Any time you upgrade it is highly recommended that you [back up your device settings](#device-settings). This is found in the web UI under the `Configuration` menu.
# OTA upgrade
Most convenient way to upgrade. Open a web browser to you device's Web UI and select Firmware Upgrade.
Upgrading the device firmware [over-the-air](https://en.wikipedia.org/wiki/Over-the-air_programming) is the convenient way to upgrade. Open a web browser to you device's Web UI and select Firmware Upgrade.
![Firmware Upgrade screen](https://user-images.githubusercontent.com/5904370/55826325-144d7f80-5b08-11e9-93dd-5e2160eaa5a4.png)
@ -25,20 +25,20 @@ After the upgrade is completed you can reconnect back to the Web UI and check th
If you wish to switch to a different [build](Builds) you have to change OtaUrl to the desired binary from our [OTA Server](http://thehackbox.org/tasmota/release/).
It is possible to create your own simple http OTA server (https is not supported) using Python and perform upgrades from there.
Install Python and from the folder where the binary (make sure sonoff-minimal.bin is located there too) is located run :
Install Python and from the folder where the binary (make sure `sonoff-minimal.bin` is located there too) is located run :
```
python -m http.server 8000
```
Change your OtaUrl to http://ipoftheserver:8000/yourbinary.bin and start the upgrade process.
## Upgrade by file upload
This process requires you to have a minimal build ([sonoff-minimal.bin](http://thehackbox.org/tasmota/release/sonoff-minimal.bin)) of the firmware since the upload process needs the space in flash memory to upload the new binary.
This process requires you to have a minimal build ([`sonoff-minimal.bin`](http://thehackbox.org/tasmota/release/sonoff-minimal.bin)) of the firmware since the upload process needs the space in flash memory to upload the new binary.
When you try to immediately upgrade to a new binary without using minimal firmware you will be greeted with this error.
![Upload error](https://user-images.githubusercontent.com/5904370/55827974-b327ab00-5b0b-11e9-968b-a654c4241ee9.png)
Browse to the minimal binary with **Choose File**. The chosen filename should be visible. *In our example we use **sonoff-minimal.bin***
Browse to the minimal binary with **Choose File**. The chosen filename should be visible. *In our example we use **`sonoff-minimal.bin`***
![minimal upgrade](https://user-images.githubusercontent.com/5904370/55828203-29c4a880-5b0c-11e9-8315-dff8a3aa9134.png)
@ -46,7 +46,7 @@ Wait until the device restarts. Web UI will display this warning message on top.
![minimal message](https://user-images.githubusercontent.com/5904370/55828993-e834fd00-5b0d-11e9-9221-b106f622c9fb.png)
Go to **Firmware Upgrade** again. This time browse to the binary you want to upgrade to with **Choose File** and click **Start upgrade**. *In our example we use **sonoff-sensors.bin***
Go to **Firmware Upgrade** again. This time browse to the binary you want to upgrade to with **Choose File** and click **Start upgrade**. *In our example we use **`sonoff-sensors.bin`***
![image](https://user-images.githubusercontent.com/5904370/55827836-68a62e80-5b0b-11e9-830b-9240d83ba11e.png)
@ -67,7 +67,7 @@ upgrade 1
Wait for the upgrade process to complete and check the Tasmota version. If in console you can use `status 2`.
## OTA upgrade using on-device button
Devices with a built in button (the one used to put your device into [flash mode](https://github.com/arendst/Sonoff-Tasmota/wiki/Hardware-Preparation#bringing-the-module-in-flash-mode)) can initiate OTA upgrade with it.
Devices with a built in button (the one used to put your device into [flash mode](Hardware-Preparation#bringing-the-module-in-flash-mode)) can initiate OTA upgrade with it.
7 short presses of the button will start OTA download of firmware using the Ota Url. Device LED is lit during the update.
@ -80,7 +80,7 @@ Upload the new version over serial using the same process as in [Flashing](Flash
[**Tasmota Device Manager**](https://github.com/jziolkowski/tdm) or TDM is a multiplatform GUI application written in Python for discovery and management of Tasmota devices.
You can set up OTA url and initiate OTA upgrade from TDM using GUI.
[**openHAB**](https://github.com/arendst/Sonoff-Tasmota/wiki/openHAB#maintenance-actions) - implement an automation rule to upgrade devices from openHAB
[**openHAB**](openHAB#maintenance-actions) - implement an automation rule to upgrade devices from openHAB
[**Node-RED OTA server and firmware manager**](https://flows.nodered.org/flow/888b4cd95250197eb429b2f40d188185) - [Node-RED](https://nodered.org/) flow for managing OTA updates
@ -94,18 +94,22 @@ Migrating from one version to the next is mostly painless as the settings are sa
As said, mostly painless. There are some deviations to this rule as the flash positions got rearranged. In the next list you'll find an overview of supported migrations paths.
* No migration from **Sonoff-MQTT-OTA** to **Sonoff-MQTT-OTA-Arduino** or **Sonoff-Tasmota**.<br/>The settings flash layout and OTA image locations are different from the Arduino versions
* Easy migration from **Sonoff-MQTT-OTA-Arduino 1.0.11** to **Sonoff-Tasmota 3.9.x**.<br/>After installing Sonoff-Tasmota for the first time some settings need to be adjusted via web configuration or MQTT commands.
* Easy migration from **Sonoff-MQTT-OTA-Arduino 3.1.0** to **Sonoff-Tasmota 4.x**.<br/>After installing Sonoff-Tasmota for the first time some settings need to be adjusted via web configuration or MQTT commands.
* Easy migration from **Sonoff-Tasmota 4.x** to **Sonoff-Tasmota 5.14**.<br/>As a safeguard perform a **Backup Configuration** before installing the new version. If settings are lost after the upgrade perform a **Restore Configuration**.
* Easy migration from **Sonoff-Tasmota 5.2** to **Sonoff-Tasmota 6.x**.<br/>As a safeguard perform a **Backup Configuration** before installing the new version. If settings are lost after the upgrade perform a **Restore Configuration**.
So to migrate from **Sonoff-MQTT-OTA-Arduino versions before 3.1.0** to **Sonoff-Tasmota 6.x** you will need to take four steps:
* No migration from **Sonoff-MQTT-OTA** to **Sonoff-MQTT-OTA-Arduino** or **Sonoff-Tasmota**.
The settings flash layout and OTA image locations are different from the Arduino versions
* Easy migration from **Sonoff-MQTT-OTA-Arduino 1.0.11** to **Sonoff-Tasmota 3.9.x**.
After installing Sonoff-Tasmota for the first time some settings need to be adjusted via web configuration or MQTT commands.
* Easy migration from **Sonoff-MQTT-OTA-Arduino 3.1.0** to **Sonoff-Tasmota 4.x**.
After installing Sonoff-Tasmota for the first time some settings need to be adjusted via web configuration or MQTT commands.
* Easy migration from **Sonoff-Tasmota 4.x** to **Sonoff-Tasmota 5.14**.
As a safeguard perform a **Backup Configuration** before installing the new version. If settings are lost after the upgrade perform a **Restore Configuration**.
* Easy migration from **Sonoff-Tasmota 5.2** to **Tasmota 6.x**.
As a safeguard perform a **Backup Configuration** before installing the new version. If settings are lost after the upgrade perform a **Restore Configuration**.
So to migrate from **Sonoff-MQTT-OTA-Arduino versions before 3.1.0** to **Tasmota 6.x** you will need to take four steps:
1. Migrate to **Sonoff-Tasmota 3.9.x**
2. Migrate to **Sonoff-Tasmota 4.x**
3. Migrate to **Sonoff-Tasmota 5.14**
4. Migrate to **Sonoff-Tasmota 6.x**
4. Migrate to **Tasmota 6.x**
# Device Settings
Tasmota uses flash memory to store many options and settings. Newer versions of Tasmota add features and use more and more of this area than earlier versions. These regions of flash were therefore not used by Tasmota before. If you did not erase flash when you originally flashed your device, a newer update may be accessing areas with values left over from the original factory firmware. Therefore there could be unexpected behavior. It is best to address this before upgrading across major versions of Tasmota.