-
Notifications
You must be signed in to change notification settings - Fork 665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In backup.json "size" field always contain 0.0 value #5398
Comments
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
supervisor-2024.11.4 Problem not resolved |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
supervisor-2024.12.3 Problem not resolved |
Describe the issue you are experiencing
Create full backup. Open backup archive file and open backup.json in this archive.
All fields addons...size contein 0.0 value
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Other (e.g., Raspbian/Raspberry Pi OS/Fedora)
Steps to reproduce the issue
This field contain information about all backuped addons
For example:
"addons": [ { "slug": "core_duckdns", "name": "Duck DNS", "version": "1.18.0", "size": 0.0 }, { "slug": "core_configurator", "name": "File editor", "version": "5.8.0", "size": 0.0 },
"size" field always contain 0.0 value
I suspect , field size must contein size addon in backup file.
Anything in the Supervisor logs that might be useful for us?
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Xiaomi Miot Auto
Supervisor diagnostics
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: