Hi everyone,
I recently encountered a hurdle while trying to integrate Ionos HiDrive into my Home Assistant setup. In my quest to do so, I came across rclone and managed to install the add-on seamlessly. However, I ran into a roadblock when attempting to create the configuration via the terminal, as it kept returning a “command not found” error.
Undeterred, I proceeded to manually create the configuration and encrypted the Ionos password myself using Python 3.11. The add-on appears to be running smoothly, and everything seems to be in order. However, I’m facing an issue in communicating with Ionos, leaving me unable to access its features.
I’m seeking guidance on how to resolve this matter and establish communication with Ionos successfully. Any assistance or insights would be greatly appreciated.
Thank you in advance for your help!
Best regards,
Josch
Protocol:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
Add-on: Rclone Backup
Automatically sync backup to remote locations using rclone
Add-on version: 3.1.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.1 (aarch64 / green)
Home Assistant Core: 2024.4.1
Home Assistant Supervisor: 2024.03.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/init.sh
cont-init: info: /etc/cont-init.d/init.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun rclone (no readiness notification)
services-up: info: copying legacy longrun scheduler (no readiness notification)
s6-rc: info: service legacy-services successfully started
[14:13:54] INFO: Installed rclone version:
[14:13:54] INFO: Starting Rclone Web GUI…
2024/04/08 14:13:54 NOTICE: Serving files from “/usr/share/rclone-webui-react”
2024/04/08 14:13:54 NOTICE: Serving remote control on http://[::]:8099/
2024/04/08 14:13:54 NOTICE: Web GUI is not automatically opening browser. Navigate to http://[::]:8099/ to use.
[14:13:54] INFO: rclone v1.65.0
- os/version: alpine 3.16.0 (64 bit)
- os/kernel: 6.6.20-haos (aarch64)
- os/type: linux
- os/arch: arm64 (ARMv8 compatible)
- go/version: go1.21.4
- go/linking: static
- go/tags: none
[14:13:54] INFO: Starting Scheduler…
[2024-04-08] [14:13:54] [INFO]: rclone config found
[2024-04-08] [14:13:55] [INFO]: checking job configs…
[2024-04-08] [14:13:55] [INFO]: scheduled jobs:
10 4 * * * sync “Sync Daily Backups”; /backup → ionos-webdav:/Backup/Home Assistant
2024/04/08 14:14:52 ERROR : rc: “operations/uploadfile”: error: couldn’t decrypt password: base64 decode failed when revealing password - is it obscured?: illegal base64 data at input byte 22
2024/04/08 14:15:43 ERROR : rc: “operations/uploadfile”: error: couldn’t decrypt password: base64 decode failed when revealing password - is it obscured?: illegal base64 data at input byte 22
Yaml:
jobs:
- name: Sync Daily Backups
schedule: 10 4 * * *
command: sync
sources:- /backup
destination: ionos-webdav:/Backup/Home Assistant
include:
exclude:
flags: {}
dry_run: true
config_path: /config/rclone.conf
- /backup
Config:
[ionos-webdav]
type = webdav
url = https://webdav.hidrive.ionos.com/
vendor = other
user =
pass =