overkill32
After adding repo, clicking install, nothing happens on 0.92.1
Hi Nicolai, added repo to hass.io 0.92.1, clicking install - nothing happens. Used the new url:
https://github.com/overkill32/hassio-addons
Greetings from Tromsø!
Log lines: 19-05-03 13:01:02 INFO (SyncWorker_2) [hassio.docker.interface] Pull image fixated/remote-backup-armv7 tag 0.3.2. 19-05-03 13:01:04 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install fixated/remote-backup-armv7:0.3.2 -> 404 Client Error: Not Found ("pull access denied for fixated/remote-backup-armv7, repository does not exist or may require 'docker login'").
The logs are helpful. Can you provide information on the platform you are using?
RPi 3 B+, running latest Raspbian with docker from SSD. Home Assistant 0.92.2
Any progress in finding out what happens with this issue?
@phellarv I've fixed the issue in a fork :)
Any progress in finding out what happens with this issue?
@phellarv I've fixed the issue in a fork :)
Working confirmed, though I get the following log:
Adding SSH key Creating local backup: "Automated backup 2019-05-20 09:39" Backup created: b63e2432 Copying b63e2432.tar to ~/hassio_backups on 192.168.2.3 using SCP Warning: Permanently added 192.168.2.3 (ECDSA) to the list of known hosts. ok parse error: Invalid numeric literal at line 1, column 10 date: option requires an argument: date BusyBox v1.29.3 (2019-01-24 07:45:10 UTC) multi-call binary.
Any progress in finding out what happens with this issue?
@phellarv I've fixed the issue in a fork :)
Working confirmed, though I get the following log:
Adding SSH key Creating local backup: "Automated backup 2019-05-20 09:39" Backup created: b63e2432 Copying b63e2432.tar to ~/hassio_backups on 192.168.2.3 using SCP Warning: Permanently added 192.168.2.3 (ECDSA) to the list of known hosts. ok parse error: Invalid numeric literal at line 1, column 10 date: option requires an argument: date BusyBox v1.29.3 (2019-01-24 07:45:10 UTC) multi-call binary.
Did you use my fork? And, what version of HA are you using?
Any progress in finding out what happens with this issue?
@phellarv I've fixed the issue in a fork :)
Working confirmed, though I get the following log:
Adding SSH key Creating local backup: "Automated backup 2019-05-20 09:39" Backup created: b63e2432 Copying b63e2432.tar to ~/hassio_backups on 192.168.2.3 using SCP Warning: Permanently added 192.168.2.3 (ECDSA) to the list of known hosts. ok parse error: Invalid numeric literal at line 1, column 10 date: option requires an argument: date BusyBox v1.29.3 (2019-01-24 07:45:10 UTC) multi-call binary.Did you use my fork? And, what version of HA are you using?
Yes, I used your fork. HA version 0.93.1 (most recent)
Hmm, saw in my fork I had not updated the URL for addons, did you use : https://github.com/thestigh/hassio-addons
Ah, but I know what's wrong :) I've not yet fixed the 'control how many local backups you want to preserve' part. For now; use setting
"keep_local_backup": "XYZ"
and it will work. I will fix the rest soon. The "" means keep no backups. The "all" means keep all backups.
Hmm, saw in my fork I had not updated the URL for addons, did you use : https://github.com/thestigh/hassio-addons
Ah, but I know what's wrong :) I've not yet fixed the 'control how many local backups you want to preserve' part. For now; use setting
"keep_local_backup": "XYZ"and it will work. I will fix the rest soon. The "" means keep no backups. The "all" means keep all backups.
@TheStigh thanks mate, your fork works, although it gives some errors, here's the log: ` Adding SSH key Creating local backup: "Automated backup 2019-06-29 15:38" Backup created: fe468562 Copying fe468562.tar to ~/HA_Backups on XXX.XXX.X.XX using SCP Warning: Permanently added 'XXX.XXX.X.XX' (ECDSA) to the list of known hosts. ok parse error: Invalid numeric literal at line 1, column 10 date: option requires an argument: date BusyBox v1.29.3 (2019-01-24 07:45:10 UTC) multi-call binary.
Usage: date [OPTIONS] [+FMT] [TIME]
Display time (using +FMT), or set time
[-s,--set] TIME Set time to TIME
-u,--utc Work in UTC (don't convert to local time)
-R,--rfc-2822 Output RFC-2822 compliant date string
-I[SPEC] Output ISO-8601 compliant date string
SPEC='date' (default) for date only,
'hours', 'minutes', or 'seconds' for date and
time to the indicated precision
-r,--reference FILE Display last modification time of FILE
-d,--date TIME Display TIME, not 'now'
-D FMT Use FMT for -d TIME conversion
Recognized TIME formats: hh:mm[:ss] [YYYY.]MM.DD-hh:mm[:ss] YYYY-MM-DD hh:mm[:ss] [[[[[YY]YY]MM]DD]hh]mm[.ss] 'date TIME' form accepts MMDDhhmm[[YY]YY][.ss] instead ` Any ideas on this?
@TheStigh can you open a PR to this repo so the original can get the fix? @overkill32 the fix seems pretty simple. For easy reference: https://github.com/overkill32/hassio-remote-backup/compare/master...TheStigh:master
Most of the changes are just changing the owner's name. The actual fix seems to be changing
hassio snapshots new --options name="${name}" to
hassio snapshots new --name="${name}". Is that correct?
Actually, after reviewing this I'm a bit lost as to what actually is different that would affect the pulling of the container...
@TheStigh basically @overkill32 took over the project from the previous developer a few months ago, but I don't think he has much to time to dedicate to it, since there are two PR which are ready for inclusion and I can see the issues piling up without any interaction from him. Would you be interested in taking over the project if @overkill32 agrees? I can help you fixing some of the issues.
@pho3nixf1re so I think that @overkill32 should initiate something like he did with the original developer, transferring ownership of the repository with this procedure
Then I suggest to grant more people the commit privileges so that some of us can help tracking issues and merging PRs
The fork from @carstenschroeder works great in the current Version of Home Assistant.
https://github.com/carstenschroeder/hassio-addons
@overkill32 can you begin transferring maintenance of this to @TheStigh and/or myself? It seems that several people are forking this repo and there are a series of features that could be added here.