Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devialet integration play/pause not supported #124395

Open
Geweldich opened this issue Aug 22, 2024 · 11 comments · May be fixed by #134168
Open

Devialet integration play/pause not supported #124395

Geweldich opened this issue Aug 22, 2024 · 11 comments · May be fixed by #134168

Comments

@Geweldich
Copy link

The problem

According to HA play/pause support is not available for my Phantom II (firmware version 2.17.5) using the Devialet integration. The error message displayed on screen is "Actie media_player/media_play_pause kon niet worden uitgevoerd. Entity media_player.kantoor does not support this service." If I'm not mistaking this was supported before. Currently I'm only able to set the device volume through HA.

I am able to use play/pause if I use different controllers to play music, such as Music Assistant, Spotify or AirPlay.

What version of Home Assistant Core has the issue?

2024.8.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

devialet

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

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

Code owner commands

Code owners of devialet 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 devialet 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)


devialet documentation
devialet source
(message by IssueLinks)

@Geweldich
Copy link
Author

Please note that I have removed, rebooted an readded the device. This didn't bring back play/pause support, or other functionality such as being able to skip to the next or previous track (which I totally forgot to mention).

@fwestenberg
Copy link
Contributor

Can you please provide the Diagnostics information?

@Geweldich
Copy link
Author

@fwestenberg
Copy link
Contributor

Thanks for the diagnostics. I see you are using upnp as source, actually I never used play/pause on upnp before. Can you use these buttons in the original Devialet app?

@Geweldich
Copy link
Author

Hi. Yes the buttons in the Devialet app are working. I also tried Spotify Connect (diagnostics added), with the same results. Spotify Connect adds 'previous' and 'next' as available operations, but only volume up and down work. HA errrors out in the same way.
config_entry-devialet-01J5R0HNHG29T4V5DMG0XY8G61(2).json

@Geweldich
Copy link
Author

Also tried Airplay after re-adding the device to HA. Same results.
config_entry-devialet-01J69T8QQZVKS7VGX93TJ63B87.json

@Geweldich
Copy link
Author

Geweldich commented Sep 6, 2024

Is there anything else I can supply/do to help? @fwestenberg

@fwestenberg
Copy link
Contributor

fwestenberg commented Oct 3, 2024

I tried to find out what went wrong, but no success so far. Can you change the log level of the Devialet python component as described here and here ?

In the Developer tools (from the sidebar), go to Actions and execute the following action:

action: logger.set_level
data:
  devialet: debug

Now press the play/pause button again and check the log for information.

@Geweldich
Copy link
Author

I tried to find out what went wrong, but no success so far. Can you change the log level of the Devialet python component as described here and here ?

In the Developer tools (from the sidebar), go to Actions and execute the following action:

action: logger.set_level
data:
  devialet: debug

Now press the play/pause button again and check the log for information.

Hi, the play/pause is not available at all using the HA built-in cards. It's only visible when e.g. using the custom Mini Media Player card, which displays the allowed actions even when it's not available (which is the case here). Pressing the button throws the generic HA error I mentioned before, because the action is not available/possibble at all.

@RSDynamics
Copy link

RSDynamics commented Dec 17, 2024

I think I have the same issue with my Phantom 1 stereo setup.
Whatever source I use the supported_features are always 67852. I would expect the supported_features to change when I switch source from optical_left to Spottify Connect for instance.

I tried reloading the integration when I was playing Spotify Connect but the supported_features are always the same.

I also tried to overrule the supported_features to 84285 in the customize.yaml
The media player card then shows the buttons but when using them the error message as stated in the opening post is shown.

The only thing I see in the logs is when he integration is in debug mode is:

Error in log

[547132409744] Unexpected exception Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<7 lines>... ) ^ File "/usr/src/homeassistant/homeassistant/core.py", line 2802, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2845, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 989, in entity_service_call raise HomeAssistantError( f"Entity {entity.entity_id} does not support this service." ) homeassistant.exceptions.HomeAssistantError: Entity media_player.phantom does not support this service.

I hope this extra information helps.

@fwestenberg fwestenberg linked a pull request Dec 28, 2024 that will close this issue
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants