SynologyDSMSwitchUpdateCoordinator data: 'NoneType' object has no attribute 'get_home_mode_status'

[guyuga]

The problem

Synology integration returns an error. looking at the logs it says SynologyDSMSwitchUpdateCoordinator data: 'NoneType' object has no attribute 'get_home_mode_status'

ERROR (MainThread) [homeassistant.components.synology_dsm.coordinator] Unexpected error fetching 10.10.0.10 SynologyDSMSwitchUpdateCoordinator data: 'NoneType' object has no attribute 'get_home_mode_status' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 290, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/synology_dsm/coordinator.py", line 73, in _async_update_data "switches": {"home_mode": await surveillance_station.get_home_mode_status()} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get_home_mode_status'

What version of Home Assistant Core has the issue?

2023.11.2

What was the last working version of Home Assistant Core?

NA

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

home-assistant_synology_dsm_2023-11-12T19-41-33.820Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @hacf-fr, @quentame, @mib1185, mind taking a look at this issue as it has been labeled with an integration (synology_dsm) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `synology_dsm` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign synology_dsm` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

synology_dsm documentation synology_dsm source _{^{(message by IssueLinks)}}

[mccasian]

Same here. I've tried with Home Mode disabled and enabled... it still gives that error.

[mib1185]

please download and provide the diagnostics data for this integration.

[soppem]

diagnostic data from my HA home-assistant_synology_dsm_2024-01-02T23-57-09.375Z.log

[mccasian]

Hello everyone.

I've managed to make it work. To me, all this was happening after i've temporary disabled the 2 Factor Authentication on my Synology DS in order to easily play with the configuration for a while(incl. Surveillance Station). I just couldn't make the integration work after, no matter what i've tried. However, my setup is now pretty stable, so i've decided to turn 2 factor authentication on again. Since i didn't remembered how the HA integration is dealing with 2FA, i've decided to give a try... just for fun. And it worked - everything works again

So, i am not sure if i am just lucky or this is indeed a glitch, but i've re-activated the 2 factor authentication on the account I use for HA, then reconfigured the integration and it's now working. I'm curious if this will work for others or just for me.

[mcattle]

I'm now getting this same error after upgrading my Synology to 7.x from, 6.x. I'm running Home Assistant OS, Core version 2024.3.0.

[Destroyer061090]

same error to me: 2024-05-09 03:27:29.138 ERROR (MainThread) [homeassistant.components.synology_dsm.coordinator] Error fetching ARSENALE SynologyDSMCentralUpdateCoordinator data: Error communicating with API: {'api': None, 'code': -1, 'reason': 'Unknown', 'details': 'TimeoutError'}

[issue-triage-workflows[bot]]

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.