Thank you very much for the backup improvements, especially the ability to change the time of the backup, which I had requested. This is a great community.
Not so important but worth a mention. In the settings, an error currently appears at the bottom of the tip display. The problem appears in the German version.
2025-02-11 07:34:58.595 ERROR (MainThread) [frontend.js.modern.202502100] Failed to format translation for key 'ui.panel.config.tips.join' in language 'de'. Error: The intl string context variable "mastodon" was not provided to the string "Werde Teil der Community in unseren {forums}, per {mastodon}, {bluesky}, {twitter}, {discord}, {blog} oder {newsletter}."
2025-02-11 07:38:21.683 ERROR (MainThread) [frontend.js.modern.202502100] Failed to format translation for key 'ui.panel.config.tips.join' in language 'de'. Error: The intl string context variable "mastodon" was not provided to the string "Werde Teil der Community in unseren {forums}, per {mastodon}, {bluesky}, {twitter}, {discord}, {blog} oder {newsletter}."
2025-02-11 07:38:23.550 ERROR (MainThread) [frontend.js.modern.202502100] Failed to format translation for key 'ui.panel.config.tips.join' in language 'de'. Error: The intl string context variable "mastodon" was not provided to the string "Werde Teil der Community in unseren {forums}, per {mastodon}, {bluesky}, {twitter}, {discord}, {blog} oder {newsletter}."
Synology still acting up in patch 2 release.
while being offline
it is still displayed in the available locations:
However, it is Not shown in the successfully created backup list:
nor is it counted in the overview:
proof it was made correctly:
Note it also does Not repeat the max retention number (set to 3)
to be precise, this Synology backup location is from the Integration, Not from a configured network share.
oddly enough, there is this log which occurred at an unexpected time (my Synology is only scheduled to wakeup at 09:00)
Maybe the logging is not related, I cant relate it to anything else though
Logger: homeassistant.components.backup
Bron: components/synology_dsm/backup.py:242
integratie: Backup (documentatie, problemen)
Eerst voorgekomen: 07:51:36 (2 gebeurtenissen)
Laatst gelogd: 07:52:30
Unexpected error for synology_dsm.CBLBN01857: {'api': None, 'code': -1, 'reason': 'Unknown', 'details': "ClientConnectorError = ConnectionKey(host='192.168.1.81', port=1705, is_ssl=True, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None)"}
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1115, in _wrap_create_connection
sock = await aiohappyeyeballs.start_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<5 lines>...
)
^
File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 93, in start_connection
raise first_exception
File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 71, in start_connection
sock = await _connect_sock(
^^^^^^^^^^^^^^^^^^^^
current_loop, exceptions, addrinfo, local_addr_infos
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 163, in _connect_sock
await loop.sock_connect(sock, address)
File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 641, in sock_connect
return await fut
^^^^^^^^^
File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 681, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.1.81', 1705)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/synology_dsm/synology_dsm.py", line 377, in _execute_request
response = await self._session.get(
^^^^^^^^^^^^^^^^^^^^^^^^
url_encoded, timeout=timeout, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 703, in _request
conn = await self._connector.connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
req, traces=traces, timeout=real_timeout
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 548, in connect
proto = await self._create_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1056, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1400, in _create_direct_connection
raise last_exc
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1369, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<7 lines>...
)
^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1130, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.81:1705 ssl:default [Connect call failed ('192.168.1.81', 1705)]
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/synology_dsm/backup.py", line 220, in async_list_backups
return list((await self._async_list_backups(**kwargs)).values())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/synology_dsm/backup.py", line 242, in _async_list_backups
files = await self._file_station.get_files(path=self.path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/synology_dsm/api/file_station/__init__.py", line 80, in get_files
raw_data = await self._dsm.get(
^^^^^^^^^^^^^^^^^^^^
...<11 lines>...
)
^
File "/usr/local/lib/python3.13/site-packages/synology_dsm/synology_dsm.py", line 251, in get
return await self._request("GET", api, method, params, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/synology_dsm/synology_dsm.py", line 330, in _request
response = await self._execute_request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
request_method, url, params, raw_response_content, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/synology_dsm/synology_dsm.py", line 465, in _execute_request
raise SynologyDSMRequestException(exp) from exp
synology_dsm.exceptions.SynologyDSMRequestException: {'api': None, 'code': -1, 'reason': 'Unknown', 'details': "ClientConnectorError = ConnectionKey(host='192.168.1.81', port=1705, is_ssl=True, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None)"}
Nice job, the new Backup functionality is awesome, no need to use a google drive addon for uploading my backups to drive.
But, I didnāt find a option for a storage based retention policy. I need to store 6 month on google drive, but only 7 days in local disk.
The retention seems to be a global option for all backup locations (exept nabucasa).
My Home Assistant update has been stuck on āinstallingā for an hour. Is there anything I can do to check whatās happening? Thank you.
Wait.
It took an exceptionally long time for my 2025.2.2 update to go through too. Maybe Github issues.
3 Likes
Thank you Iāll wait then 
It took more than 1 hour but at the end it succeded. Thank you! 
1 Like
I would hold back with that for now. The new charts are disastrous, the horizontal scrolling of the number of entities are not really working on a mobile phone. (Tiny little trinagle to scroll left and right, long entity names does not displayed as expected, or just not visible at all.) The displays are slow to react. Grids are just randomly positioned inside the Tile. So it is a hot mess, maybe fits for an individualās use case, but generally it is a mess.
Some examples:
Itās early days. Theyāve only just introduced it. Have a look at some the example possibilities: Examples - Apache ECharts
I just have mine set up through a normal network share. Itās been decent so far. I didnāt realize they had a separate method for backups. Have you written those issues up?
As a sidebar, those errors are connection related. IIRC you shut synology off during the night?
Yeah, they looks great, it provides brilliant morphing capabilities and graph options where the timeseries data turns back, whatever. But it shows the reason why people like yourself at first place choose to use a custom card. It is rpoviding more features than the built in, and it stable between HA releases. It does not change completely in the name of further development.
The new graphs are insanely slow, and make the whole mobile app slow as well, but that is my own impression.
Mine took a long time so I flipped to the supervisor log tab. Looked like it was waiting to upload my cloud backupā¦ (I flipped the switch to force backup before installing)
For grins I rebooted to cancel the install then did it without the checkbox (no backup) and the machine started the reboot process almost immediately.
Are you doing backup before install perhaps?
(we really need better install status messages. The supervisor log has the status, we just need to surface it in the UI somehow)
1 Like
FYI: I did not do backup before installing as nothing had changed since my nightly backup.
For me the āupdate-timeā mostly depends on the download speed from github. Actually i have very poor dl rate mostly lower than 1mB/s when supervisor pulls the new core image in the background.
Some progress bar would bei nice.
2 Likes
his time, I checked the backup option before installing the update, as I always did, even before the new backup process. Iām performing a local backup, a backup on my NAS, a backup on the Nabu Casa cloud using the new backup method, and a backup on Google Drive using the usual add-on.
1 Like
You have an almost identical setup as I do.
I was getting curious as it was suddenly taking a LOT longer to install at time periods that are typically slower for githubā¦ I saw everything complete in the supervisor LOG INCLUDING backup completed but I had forgotten that those also need to upload.
Looks like it does all the checks l, fires the backup and waits for a completion. Backup is also logged by the supervisor so you see backup complete and it just sits there.
And the I realized the backup is complete but not uploaded and it has to go three placesā¦ Two of which are cloud.
Im thinking we need a drop down on that checkbox with destination checkboxes. To say something like yes local but no cloud this time thanksā¦
1 Like
we had quite a few open, they all got closed but this one, to which I added the link to the post above Backup to local, gdrive and synology with synology shutdown results in 0 backups Ā· Issue #137821 Ā· home-assistant/core Ā· GitHub
also, this is not new behavior and I already reported that during beta, tbh, I got lost during the later developments, because of lifeās peculiaritiesā¦
yes, but as I showed above, the integration kept showing the location while being asleep/offline, and didnt count the backup after waking upā¦
also, I did have that same Share before via the network interface, and am not 100% sure the system/backend/supervisorā¦ got rid of that correctly after having deleted it.
There is nothing in .storage referencing those network shares.
1 Like
Was 2025.2.2 pulled? I see this release mentioned here a few times but it does not appear as an available update in my Home Assistant installations at the moment.
If youāre running HAOS, search for updates. Settings ā Upper right corner ā 3 dots ā Check for updates