@@ -6,7 +6,7 @@ Convert, backup and restore configuration data of devices flashed with [Tasmota
6
6
<img src =" https://github.com/tasmota/decode-config/blob/master/media/pic/decode-config.png " alt =" Overview " title =" decode-config Overview " width =" 600 " >
7
7
8
8
<!-- markdownlint-disable MD033 -->
9
- [ ![ master] ( https://img.shields.io/badge/master-v14.3 .0.0-blue.svg )] ( https://github.com/tasmota/decode-config/tree/master )
9
+ [ ![ master] ( https://img.shields.io/badge/master-v14.4 .0.0-blue.svg )] ( https://github.com/tasmota/decode-config/tree/master )
10
10
[ ![ GitHub download] ( https://img.shields.io/github/downloads/tasmota/decode-config/total.svg )] ( https://github.com/tasmota/decode-config/releases/latest )
11
11
[ ![ PyPI version] ( https://badge.fury.io/py/decode-config.svg )] ( https://badge.fury.io/py/decode-config )
12
12
![ PyPI downloads] ( https://img.shields.io/pypi/dm/decode-config?label=pypi%20downloads )
@@ -43,7 +43,7 @@ Comparing backup files created by **decode-config** and [.dmp](#dmp-format) file
43
43
Using the latest development version of decode-config is only necessary if you also use the latest development version of Tasmota.
44
44
45
45
<!-- markdownlint-disable MD033 -->
46
- [ ![ development version] ( https://img.shields.io/badge/development-v14.3 .0.7 -blue.svg )] ( https://github.com/tasmota/decode-config/tree/development )
46
+ [ ![ development version] ( https://img.shields.io/badge/development-v14.4 .0.0 -blue.svg )] ( https://github.com/tasmota/decode-config/tree/development )
47
47
48
48
## Table of contents
49
49
<details >
@@ -338,7 +338,7 @@ Example:
338
338
decode-config -c my.conf -s tasmota-4281 --backup-file Config_@d_@v
339
339
```
340
340
341
- This will create a file like ` Config_Tasmota_14.3 .json ` (the part ` Tasmota ` and ` 14.3 ` will choosen related to your device configuration).
341
+ This will create a file like ` Config_Tasmota_14.4 .json ` (the part ` Tasmota ` and ` 14.4 ` will choosen related to your device configuration).
342
342
343
343
#### Save multiple backup at once
344
344
@@ -350,18 +350,18 @@ decode-config -c my.conf -s tasmota-4281 -o Config_@d_@v -o Backup_@H.json -o Ba
350
350
351
351
creates three backup files:
352
352
353
- * ` Config_Tasmota_14.3 .json ` using JSON format
353
+ * ` Config_Tasmota_14.4 .json ` using JSON format
354
354
* ` Backup_tasmota-4281.json ` using JSON format
355
355
* ` Backup_tasmota-4281.dmp ` using Tasmota configuration file format
356
356
357
357
### Restore backup
358
358
359
359
Reading back a previously saved backup file, use the ` --restore-file <filename> ` parameter.
360
360
361
- To restore the previously save backup file ` Config_Tasmota_14.3 .json ` to device ` tasmota-4281 ` use:
361
+ To restore the previously save backup file ` Config_Tasmota_14.4 .json ` to device ` tasmota-4281 ` use:
362
362
363
363
``` bash
364
- decode-config -c my.conf -s tasmota-4281 --restore-file Config_Tasmota_14.3
364
+ decode-config -c my.conf -s tasmota-4281 --restore-file Config_Tasmota_14.4
365
365
```
366
366
367
367
Restore operation also allows placeholders ** @v ** , ** @d ** , ** @f ** , ** @h ** or ** @H ** like in backup filenames so we can use the same naming as for the backup process:
0 commit comments