This is my first HA add-on, and my first community code contribution of any kind…so buyer beware.
I couldn’t find the i386 build script. So, despite the fact that my add-on advertises support for the i386 architecture, it doesn’t really. If anyone can offer some help there, I’d appreciate it. I appears I need proper authorization to pull that builder from Docker Hub???
I’ve tested this on my Raspberry Pi Hass.io setup.
Thanks a lot. I use the Dropbox backup addon which works perfectly but since my log is so big (1gb +) it fills up my Dropbox space immediately so for me is unusable.
From first reading seems this addon enables to choose which files to backup (what I would need is just NOT backup a single file, the log file), so it’s great for my needs, thanks
Hmmm… I have no idea what the cause might be. I did try something, though. I removed i386 from the list of supported architectures in the configuration for my add-on (I shouldn’t have had it in the list to begin with). That shouldn’t cause a problem with you adding the repository, though. But, it was the only thing I could think of to try. You may try again, but I’m honestly not hopeful that what I did would make a difference.
18-11-05 11:03:13 INFO (SyncWorker_7) [hassio.docker.addon] Start Docker add-on homeassistant/amd64-addon-mosquitto with version 3
18-11-05 11:03:13 INFO (MainThread) [hassio.services.mqtt] Set core_mosquitto as service provider for mqtt
18-11-05 11:03:13 INFO (MainThread) [hassio.discovery] Send discovery to Home Assistant mqtt from core_mosquitto
18-11-05 11:03:13 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-11-05 11:03:13 INFO (MainThread) [hassio.discovery] Discovery 74313f3847c04af080xxx message send
18-11-05 11:06:54 INFO (MainThread) [hassio.addons.git] Update add-on GitHub - danimtb/dasshio: Hass.io add-on to easily use Amazon Dash Buttons with Home Assistant repository
18-11-05 11:06:54 INFO (MainThread) [hassio.addons.git] Update add-on GitHub - stefangries/hassio-addons: Addons for HomeAssistannt's HassIO. repository
18-11-05 11:06:54 INFO (MainThread) [hassio.addons.git] Update add-on GitHub - stefangries/hassio-addons: Addons for HomeAssistannt's HassIO. repository
18-11-05 11:06:54 INFO (MainThread) [hassio.addons.git] Update add-on GitHub - neffs/hassio-addons repository
18-11-05 11:06:54 INFO (MainThread) [hassio.addons.git] Update add-on GitHub - home-assistant/addons: ➕ Docker add-ons for Home Assistant repository
18-11-05 11:06:54 INFO (MainThread) [hassio.addons.git] Update add-on GitHub - marthoc/hassio-addons: Hass.io Add-ons repository
18-11-05 11:06:54 INFO (MainThread) [hassio.addons.git] Update add-on GitHub - hassio-addons/repository: Home Assistant Community Add-ons repository
18-11-05 11:06:55 WARNING (MainThread) [hassio.addons.git] It is already a task in progress
18-11-05 11:06:55 WARNING (MainThread) [hassio.addons.git] It is already a task in progress
18-11-05 11:06:55 WARNING (MainThread) [hassio.addons.git] It is already a task in progress
18-11-05 11:06:55 WARNING (MainThread) [hassio.addons.git] It is already a task in progress
18-11-05 11:06:55 WARNING (MainThread) [hassio.addons.git] It is already a task in progress
18-11-05 11:06:55 WARNING (MainThread) [hassio.addons.git] It is already a task in progress
18-11-05 11:06:55 WARNING (MainThread) [hassio.addons.git] It is already a task in progress
18-11-05 11:06:55 INFO (MainThread) [hassio.addons] Load add-ons: 80 all - 0 new - 0 remove
18-11-05 11:06:56 INFO (MainThread) [hassio.addons] Load add-ons: 80 all - 0 new - 0 remove
As a test/workaround, could you try setting my add-on up as a local add-on? This involves these steps:
Create a subdirectory in your hassio addons directory named something like googlebackup. You may need to use something like the Samba add-on to get access to do this.
Download my config.json file and place it into that directory.
Go to your hass.io add-on store and click the refresh circle in the top-right corner.
You should (hopefully) see my add-on appear there under “Local add-ons”.
Let me know how that goes. If it doesn’t show up, please look in your logs to see if there are any helpful messages from this test. Thank you.
Well, the good news is that it worked. The bad news is that it’s still a mystery as to why it would not add directly from my repository, and this is not a very good long-term workaround because you won’t get updates with this setup.
I’ll keep giving this some thought. It seems more likely now that the problem is with my repository rather than with my add-on. That at least helps narrow down where I need to focus. Thank you for your patience.
You are using the wrong string for the google drive folder - follow instructions in the documentation. I had the same issue.
Blockquote
You must instead provide Google Drive’s unique opaque ID of the folder. Google Drive doesn’t make it easy to get this value. But, here’s how you can get it:
In your favorite web browser, navigate to the Google Drive folder to which you plan to upload your files (create a new folder in Google Drive if you wish). Be sure that you have the perferred folder open so that its contents (even if it’s empty) are displayed.
From the address bar of your browser, copy the last portion of the URL. That value is Google Drive’s unique opaque ID for the folder. Paste that value in for the backupDirID value in the configuration.