core: Error unloading entry 'DSMname' for button - on every restart
The problem
I’m using the Synology integration. My server name is Plumbus. On every restart of Home Assistant, I see a log error as follows.
Logger: homeassistant.config_entries
Source: helpers/entity_component.py:172
First occurred: 8:16:59 AM (6 occurrences)
Last logged: 8:16:59 AM
Error unloading entry Plumbus for button
Error unloading entry Plumbus for camera
Error unloading entry Plumbus for sensor
Error unloading entry Plumbus for switch
Error unloading entry Plumbus for update
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 474, in async_unload
result = await component.async_unload_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 173, in async_unload_entry
return await component.async_unload_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 172, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
I’m unsure why this is being generated. It doesn’t look specific to the Synology integration, but I’ve not seen it on any other integrations.
What version of Home Assistant Core has the issue?
core-2022.4.1, core-2022.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Synology
Link to integration documentation on our website
https://www.home-assistant.io/integrations/synology_dsm/
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (4 by maintainers)
(Off topic but) Thanks for the tip on the bonding - that’s what I had always assumed was happening already with the two NICs. I’ve just enabled this now. For others’ reference, here is info on this from the Synology KB..
@kellyatkinson can you re-open the issue?