You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When used by various integrations such as alexa (or in the near future google assistant) you can't currently easily control device with voice commands like play or pause because the only method that was implemented was media_play_pause which is mostly meant for service calls and has basic support in lovelace components.
Roku only supports a "play" keypress that is really a play/pause behavior and doesn't offer discrete pause support.
This means that the implementation cant promise to actually pause but it can atleast toggle the play state and make available the "pause" action to integrations. In lovelace it should allow the pause icon rather than stop icon which is more accurate to what the actual keypress does.
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)
Breaking change (fix/feature causing existing functionality to break)
Code quality improvements to existing code or addition of tests
Example entry for configuration.yaml:
# Example configuration.yaml
Additional information
This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:
Checklist
The code change is tested and works locally.
Local tests pass. Your PR cannot be merged unless tests pass
Not exactly besides app being open and no screensaver. Which is the current logic for state. Effectively calling play or pause would always call the same thing (play) so checking state didnt really seem useful. Roku remotes also merge the two controls into 1 button.
i guess its a feature but as it already supported PLAY and had the async_media_play_pause. I see if more as a fix to being partially implemented than a new feature. guess it doesnt hurt to wait a few weeks though
fair point, i guess i overlooked that option as it was a bit more technical about video stream. Ill have to review using that but it would increase number of API calls something ive been trying to reduce/optimize lately since taking on maintenance of roku
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Breaking change
Proposed change
When used by various integrations such as alexa (or in the near future google assistant) you can't currently easily control device with voice commands like play or pause because the only method that was implemented was media_play_pause which is mostly meant for service calls and has basic support in lovelace components.
Roku only supports a "play" keypress that is really a play/pause behavior and doesn't offer discrete pause support.
This means that the implementation cant promise to actually pause but it can atleast toggle the play state and make available the "pause" action to integrations. In lovelace it should allow the pause icon rather than stop icon which is more accurate to what the actual keypress does.
Type of change
Example entry for
configuration.yaml:# Example configuration.yamlAdditional information
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.The integration reached or maintains the following Integration Quality Scale: