Looks fine here.
Here's mine. Definitely looks like it might have been broken with .117... hopefully .118 fixed (just applied now).
| 2019-11-01~2.1.6.112.lzf | 2019-11-01 03:07:04.000 PDT | 2.1.6.112 | 19004896 | Restore | Download |
|---|---|---|---|---|---|
| 2019-11-02~2.1.6.112.lzf | 2019-11-02 10:24:25.000 PDT | 2.1.6.112 | 19703008 | Restore | Download |
| 2019-11-03~2.1.6.117.lzf | 2019-11-03 03:05:30.000 PST | 2.1.6.117 | 19090400 | Restore | Download |
| 2019-11-04~2.1.6.117.lzf | 2019-11-04 03:09:13.000 PST | 2.1.6.117 | 18970144 | Restore | Download |
| 2019-11-11~2.1.6.117.lzf | 2019-11-11 11:59:18.000 PST | 2.1.6.117 | 20073632 | Restore | Download |
seems to have resolved with .118...
1 Like
Nope, backups seem to have stalled out again. It just keeps downloading the one from the 13th. =/ Which makes me think maintenance isn't running... which may explain my hub getting slow (Lutron integration is kinda slow).
Anything I should try?
fwiw, had to adjust this script a bit after 2.2.4.
I now have this:
curl http://10.0.6.4/hub/backup | grep data-fileName | grep download | sed 's/<a class="download mdl-button mdl-js-button mdl-button--raised mdl-js-ripple-effect" href="#" data-fileName="//' | sed 's/">Download</a>//' | sed 's/ //g' | tail -1 | xargs -I @ curl -o @ http://10.0.6.4/hub/backupDB?fileName=@
I believe the change was primarily it's no longer wrapped in a table.
