core icon indicating copy to clipboard operation
core copied to clipboard

Unable to start playback in linkplay device

Open Joe31388 opened this issue 1 year ago • 3 comments

The problem

I bought an arylic upstream amp v4 board and unable to start playback in home assistant. The player changes from buffering to idle within 30 sec after I try to play.
I have tried on wifi and ethernet with the same results.

image

What version of Home Assistant Core has the issue?

2024.8.3

What was the last working version of Home Assistant Core?

13.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

linkplay

Link to integration documentation on our website

https://www.home-assistant.io/integrations/linkplay

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/linkplay/utils.py", line 30, in session_call_api
    async with async_timeout.timeout(API_TIMEOUT):
  File "/usr/local/lib/python3.12/site-packages/async_timeout/__init__.py", line 141, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.12/site-packages/async_timeout/__init__.py", line 228, in _do_exit
    raise asyncio.TimeoutError
TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/linkplay/media_player.py", line 115, in _wrap
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/linkplay/media_player.py", line 159, in async_update
    await self._bridge.player.update_status()
  File "/usr/local/lib/python3.12/site-packages/linkplay/bridge.py", line 82, in update_status
    self.properties = await self.bridge.json_request(LinkPlayCommand.PLAYER_STATUS)  # type: ignore[assignment]
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/linkplay/bridge.py", line 242, in json_request
    return await session_call_api_json(self.endpoint, self.session, command)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/linkplay/utils.py", line 48, in session_call_api_json
    result = await session_call_api(endpoint, session, command)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/linkplay/utils.py", line 34, in session_call_api
    raise LinkPlayRequestException(f"Error requesting data from '{url}'") from error
linkplay.exceptions.LinkPlayRequestException: Error requesting data from 'http://192.168.166.108/httpapi.asp?command=getPlayerStatus'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 942, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1300, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/linkplay/media_player.py", line 117, in _wrap
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Exception occurred when communicating with API <function LinkPlayMediaPlayerEntity.async_update at 0x7f7617eacb80>: Error requesting data from 'http://192.168.166.108/httpapi.asp?command=getPlayerStatus'
2024-09-02 20:20:25.264 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.bathroom_speakers fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/linkplay/utils.py", line 31, in session_call_api
    response = await session.get(url, ssl=False)

Additional information

No response

Joe31388 avatar Sep 03 '24 03:09 Joe31388

Hey there @velleman, mind taking a look at this issue as it has been labeled with an integration (linkplay) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of linkplay 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 linkplay Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


linkplay documentation linkplay source (message by IssueLinks)

home-assistant[bot] avatar Sep 03 '24 03:09 home-assistant[bot]

Is the problem still present in newer Home Assistant versions? Is this sporadic or a common reproducible problem?

silamon avatar Sep 18 '24 13:09 silamon

Nope, I'm able to play now but noticed seeking using a service call and the power/idle button don't work. I was going to make a separate issue.

On Wed, Sep 18, 2024, 8:06 AM Simon Lamon @.***> wrote:

Is the problem still present in newer Home Assistant versions? Is this sporadic or a common reproducible problem?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/125117#issuecomment-2358420590, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYJ3EBLNBJYXKYPBBSNYI23ZXF3FBAVCNFSM6AAAAABNRH2KRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJYGQZDANJZGA . You are receiving this because you authored the thread.Message ID: @.***>

Joe31388 avatar Sep 19 '24 13:09 Joe31388

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.