home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.65k stars 30.79k forks source link

No longer able to control media player entity. #98482

Closed Cergon closed 7 months ago

Cergon commented 1 year ago

The problem

Upgrading HA Core results in loss of control for the Frontier Silicon device (Roberts RS1). The integration is loaded and media player entity available however the device does not respond to either UI control or service commands through HA. This does not happen immediately after upgrade, it takes about 10/15 mins before the behaviour is observed. Please see log file output for error generated.

What version of Home Assistant Core has the issue?

2023.8.2

What was the last working version of Home Assistant Core?

2023.7.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Frontier Silicon

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.media_player
Source: helpers/entity_platform.py:855
Integration: Media Player (documentation, issues)
First occurred: 18:08:30 (639 occurrences)
Last logged: 19:54:51

Updating frontier_silicon media_player took longer than the scheduled update interval 0:00:10
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:908
First occurred: 18:08:30 (1 occurrences)
Last logged: 18:08:30

Update of media_player.roberts_rs1 is taking over 10 seconds

Additional information

No response

home-assistant[bot] commented 1 year ago

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

Code owner commands Code owners of `frontier_silicon` 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 frontier_silicon` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


frontier_silicon documentation frontier_silicon source (message by IssueLinks)

beeh5 commented 1 year ago

Not sure if related, but I have also lost my frontier silicon media player entity... re-adding the entry within the integration did not fix the issue...

WonkoMcSane commented 1 year ago

Don't know if related but I'm having a similar problem with my PS4 and Roku TV when updating from .6.3.

https://github.com/home-assistant/core/issues/98607 https://github.com/home-assistant/core/issues/98606

pepsonEL commented 1 year ago

Not sure if related, but I have also lost my frontier silicon media player entity... re-adding the entry within the integration did not fix the issue...

I also has the same problem with Medion Player. No any entities....

beeh5 commented 1 year ago

@Cergon @pepsonEL @WonkoMcSane after updating to v2023.09 I see the media player entities / devices again for the Frontier Silicon integration. Please check.

Cergon commented 1 year ago

Upgrading to 2023.9.1 does not resolve the issue for me.

WonkoMcSane commented 1 year ago

Thanks for the poke, but also a no-go for resolving my problem.

philpem commented 1 year ago

Also seeing this issue on a Pure Connect+ DAB radio, Home Assistant 2023.8.4. Upgrading to 2023.9.2 to see if that resolves the issue.

Cergon commented 1 year ago

Upgrading from 2023.7.3 to 2023.9.3 still fails to resolve the problem. Can this be looked into please?

Cergon commented 1 year ago

Upgrading from 2023.7.3 to 2023.10.3 still fails to resolve the problem. I'm really hoping that I do not need to get rid of this Frontier Silicon device :(

WonkoMcSane commented 1 year ago

How are you accessing HA? Browser, app or combination?

I've been stuck at .6.x for months now and I'm thinking about trying a build from scratch to see if it still exists. I also need to see if it's an issue that exists outside the app since that's pretty much the only way I interact with it unless I'm fighting something (ie: restoring a back-up when the file-system falls down).

Cergon commented 1 year ago

Combination - I experience the issue when attempting to control the device from either the app or browser.

cakoolen commented 10 months ago

For me it appears to happen when I try to control the device from an automation. When I send commands in slow succession all appears to be fine but when I send them too quickly after each other the integration crashes. Reloading the integration from the integrations menu fixes it temporarily.

issue-triage-workflows[bot] commented 7 months ago

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.