Backup the configs of all your Tasmota devices

• fix duplicate devices created when a device's ip changed (now matched by mac, then hostname, then ip)
• add hostname column, toggle it like the mac column
• fix failed backups being reported as successful (and pruning good backups afterward)
• fix scheduled backups doing nothing until backup-all min hours had been saved once
• fix dark mode settings/lock icons not showing
• restore now reports success or failure instead of no feedback
• fix restore silently failing on tasmota v15.5+ (referer check now enforced by default)
• verified compatible with tasmota v13/v14/v15 http and mqtt api
• add multi-language interface, auto-detects from browser
• seed 28 language catalogues (unreviewed machine translations, see Translations below)
• add docker buildx build option, cross builds without qemu binaries
• add automated test suite, see Development below
• fixup sorting/datatables
• fixed restores
• added wled backups
• fix zero size backup bug
• Add referer for tasmota new security feature
• fixed mqtt overscanning
• changed backup downloads to use device name, version, and date
• added alert if device isn't getting backed up visually
• fixed sorting on ip and version
• fix bug when doing mqtt scanning
• tasmota 9.0 status change
• recording mac addresses

• Add single devices
• Discover devices
• Backup single devices
• Backup all devices
• Remove devices
• Download individual backups
• No duplicates (matched by Mac, then Hostname, then IP)
• Optional Hostname column
• Multi-language interface

Backups of wled are done via downloading the cfg.json and presets.json and putting them in a zip file. the limited mqtt support in wled means there is no way to automatically scan, so only ip scanning is supported

Go into home assisant, then the supervisor Click on the Add-On Store paste in http://github.com/danmed/TasmoBackupV1 into the Add new repository via url box, and click add Scroll down near the bottom and locate TasmoBackup

More info at: https://www.home-assistant.io/hassio/installing_third_party_addons/

version: '2'
services:
    tasmobackup:
        ports:
            - '8259:80'
        volumes:
            - ./data:/var/www/html/data
        environment:
            # MYSQL env's are not needed if you are using sqlite
            - MYSQL_SERVER=IPADDRESS
            - MYSQL_USERNAME=USERNAME
            - MYSQL_PASSWORD=PASSWORD
            # change below to mysql if you don't want to use sqlite
            # you will need to have a mysql server (set above) with a blank database already created.
            - DBTYPE=sqlite
            # if using Mysql remove the data/ from the below line
            # if using Sqlite the data/ is required!
            - DBNAME=data/tasmobackup
        container_name: TasmoBackup
        image: 'danmed/tasmobackupv1'

SQLITE:

docker run -d -p 8259:80 -v ./data:/var/www/html/data -e DBTYPE=sqlite -e DBNAME=data/tasmobackup --name TasmoBackup danmed/tasmobackupv1

Note : pay attention to the difference's between the sqlite and mysql database names.

MYSQL:

docker run -d -p 8259:80 -v ./data:/var/www/html/data -e DBTYPE=mysql -e MYSQL_SERVER=192.168.2.10 -e MYSQL_USERNAME=root -e MYSQL_PASSWORD=password -e DBNAME=tasmobackup --name TasmoBackup danmed/tasmobackupv1

git clone https://github.com/danmed/TasmoBackupV1
cd TasmoBackupV1
mkdir data
chown www-data data
cp config.inc.php.example data/config.inc.php

Edit data/config.inc.php if you wish to change to using mysql database instead of sqlite. Make sure the data directory is owned by the user php runs as, or it will not be able to save your backups or create/update the sqlite file

Run the upgrade.php script to initialize your new database, or to upgrade your existing one when changing versions.

• backupall.php exists to do literally that.. Schedule this with your chosen means (nodered, curl, scheduled tasks etc)

make test        the offline test suite, runs in the same php image the container ships
make test-live    read only checks against real devices on your network, nothing is
                   written or restored, see tests/test_live.php for TB_LIVE_RANGE /
                   TB_LIVE_DEVICE

make build     cross builds with qemu-user-static, the original method
make buildx    cross builds with docker buildx --platform, no qemu binaries needed

Both produce the same per-architecture images and tags, see the Makefile and hooks/ for details.

The interface is translated with gettext. Catalogues live in locale/<lang>/LC_MESSAGES/tasmobackup.po, one directory per language, using the same language codes Home Assistant uses.

Pick a language in Settings, or leave it on Automatic (browser) and it follows the browser's Accept-Language. Anything not translated falls back to English, so a partial catalogue is perfectly usable.

Open the .po file for your language in Poedit or any gettext editor and fill in the entries. Entries marked fuzzy are machine translated starting points that nobody has checked yet: they are ignored at runtime until you confirm them, so correcting and unmarking a fuzzy entry is what puts it on screen.

You never need to touch PHP to add or finish a language.

For a language that does not exist yet, copy locale/tasmobackup.pot to locale/<lang>/LC_MESSAGES/tasmobackup.po and translate from there.

make pot        refresh locale/tasmobackup.pot from the source
make update-po  merge new and changed strings into every catalogue
make mo         compile catalogues for a local, non docker run

The docker image compiles the catalogues during the build, so a normal install needs none of the above. Wrap new user facing strings in t(), or tn() when they count something, and run make pot. make test fails if the template has drifted from the source.

• Parse backup configs