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
Last working Home Assistant release (if known): < 0.92.0
Operating environment (Hass.io/Docker/Windows/etc.): All
Component/platform: media_player
Description of problem: #22878 introduced a gate that checks a media player platform reports a support feature flag corresponding to a service call before invoking the service. volume_down and volume_up were mapped to SUPPORT_VOLUME_SET but should allow SUPPORT_VOLUME_STEP. This affects platforms that only support stepping the volume up/down and not setting it to an explicit value.
Additional notes:*
The gate should check for either SUPPORT_VOLUME_SET or SUPPORT_VOLUME_STEP in required features.
The text was updated successfully, but these errors were encountered:
andrewsayre
changed the title
Media player volume up/down requires volume set
Media player volume up/down requires SUPPORT_VOLUME_SET but not SUPPORT_VOLUME_STEP
Apr 26, 2019
andrewsayre
changed the title
Media player volume up/down requires SUPPORT_VOLUME_SET but not SUPPORT_VOLUME_STEP
Media Player volume up/down requires SUPPORT_VOLUME_SET but not SUPPORT_VOLUME_STEP
Apr 26, 2019
Home Assistant release with the issue: 0.92.0
Last working Home Assistant release (if known): < 0.92.0
Operating environment (Hass.io/Docker/Windows/etc.): All
Component/platform: media_player
Description of problem:
#22878 introduced a gate that checks a media player platform reports a support feature flag corresponding to a service call before invoking the service.
volume_down
andvolume_up
were mapped toSUPPORT_VOLUME_SET
but should allowSUPPORT_VOLUME_STEP
. This affects platforms that only support stepping the volume up/down and not setting it to an explicit value.Additional notes:*
The gate should check for either
SUPPORT_VOLUME_SET
orSUPPORT_VOLUME_STEP
in required features.The text was updated successfully, but these errors were encountered: