Fix Shelly media player availability

[bieniu]

Breaking change

Proposed change

Fixes:

2026-05-11 09:57:59.787 ERROR (MainThread) [homeassistant.components.shelly] Unexpected error updating listener 137947086113280 for Shelly Wall Display X1i [F78A6A]
Traceback (most recent call last):
  File "/workspaces/home-assistant-core/homeassistant/helpers/update_coordinator.py", line 201, in async_update_listeners
    update_callback()
    ~~~~~~~~~~~~~~~^^
  File "/workspaces/home-assistant-core/homeassistant/components/shelly/entity.py", line 439, in _update_callback
    self.async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/workspaces/home-assistant-core/homeassistant/helpers/entity.py", line 1054, in async_write_ha_state
    self._async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/workspaces/home-assistant-core/homeassistant/helpers/entity.py", line 1203, in _async_write_ha_state
    ) = self.__async_calculate_state()
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/workspaces/home-assistant-core/homeassistant/helpers/entity.py", line 1132, in __async_calculate_state
    if (entity_picture := self.entity_picture) is not None:
                          ^^^^^^^^^^^^^^^^^^^
  File "/workspaces/home-assistant-core/homeassistant/components/media_player/__init__.py", line 1082, in entity_picture
    if self.state == MediaPlayerState.OFF:
       ^^^^^^^^^^
  File "/workspaces/home-assistant-core/homeassistant/components/shelly/media_player.py", line 134, in state
    if self.status["playback"]["buffering"]:
       ^^^^^^^^^^^
  File "/workspaces/home-assistant-core/homeassistant/components/shelly/entity.py", line 429, in status
    return cast(dict, self.coordinator.device.status[self.key])
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/ha-venv/lib/python3.14/site-packages/aioshelly/rpc_device/device.py", line 909, in status
    raise NotInitialized
aioshelly.exceptions.NotInitialized

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 #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @thecode, @chemelli74, @bdraco, mind taking a look at this pull request as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of shelly can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant mark-draft Mark the pull request as draft.
• @home-assistant ready-for-review Remove the draft status from the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign shelly Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant update-branch Update the pull request branch with the base branch.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

[chemelli74]

Looks good!

[Copilot]

Pull request overview

Fixes a Shelly RPC media player crash when a device goes offline by preventing entity_picture evaluation from accessing media-player state while the entity is unavailable.

Changes:

• Add an entity_picture override in the Shelly RPC media player to return None when available is false.
• Add a regression test asserting the media player transitions to unavailable on disconnect.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
homeassistant/components/shelly/media_player.py	Avoids entity_picture triggering state/status access while the device is unavailable.
tests/components/shelly/test_media_player.py	Adds a disconnect/unavailable regression test for the Shelly RPC media player.

[erwindouna]

Looks good, thanks @bieniu!