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

Added fast forward and rewind support to the Alexa cloud/smart home component #15370

Closed

Conversation

iliketoprogram14
Copy link
Contributor

@iliketoprogram14 iliketoprogram14 commented Jul 8, 2018

Added fast forward and rewind support to the Alexa cloud/smart home component. It simply invokes the next and previous track functions.

Description:

The Alexa PlaybackController interface supports fast forward and rewind, whereas Home Assistant's media_player component does not, only next_track and previous_track. As a result, Alexa for the HA cloud skill or smart home skills does not support fast forward and rewind.

I propose adding fast forward and rewind and mapping them to next_track and previous_track, at least until Home Assistant's media_player ever gets fastforward and rewind services. I've tested this on my local setup with success. Existing users would probably have to rediscover their devices if they would want to make use of this functionality.

I'm not sure if I should add this capability to the docs here, since it might be confusing that media_player doesn't have those functions. Happy to add it if someone thinks I should.

Related issue (if applicable): N/A

Pull request in home-assistant.github.io with documentation (if applicable): N/A

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass

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

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

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

…omponent. It simply invokes the next and previous track functions.
@iliketoprogram14
Copy link
Contributor Author

Note: I disabled the pylint warnings because pylint can't detect decorators for that error. See this issue for more info.

@balloob
Copy link
Member

balloob commented Jul 9, 2018

We should not add incorrect mappings because it is confusing and it means that we need to break that in the future.

@balloob balloob closed this Jul 9, 2018
@ghost ghost removed the in progress label Jul 9, 2018
@iliketoprogram14
Copy link
Contributor Author

That's too bad. I guess I'll have to maintain this locally then. Thanks for following up.

@home-assistant home-assistant locked and limited conversation to collaborators Dec 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants