Make UniFi services handle unloaded config entry

[Kane610]

Breaking change

Proposed change

Don't try to access runtime_data if config entry is not loaded

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Unifi Network: websocket_api script: Error executing script. Unexpected error for call_service at pos 1: 'ConfigEntry' object has no attribute 'runtime_data' on Service unifi.reconnect_client #119947
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[Bre77]

LGTM

[frenck]

Thanks, @Kane610 👍

../Frenck

[frenck]

I removed this one from the milestone; there are too many changes in the test at this point to make this one go in cleanly.

[nathan-curtis]

@frenck does that mean this is NOT in 2024.6.4 (i just installed and am still having the issue) if so the relnotes for x.6.4 say the fix is still in...

[Kane610]

I removed this one from the milestone; there are too many changes in the test at this point to make this one go in cleanly.

Thanks @frenck

[Kane610]

@frenck does that mean this is NOT in 2024.6.4 (i just installed and am still having the issue) if so the relnotes for x.6.4 say the fix is still in...

Yes its not part of the latest release. It will be a part of next major release instead. The fix doesnt really change the behavior only avoid crashing the service call. You still need to make sure your integration is connected to the network app