Invalid or missing params.sound_mode attribute when Sound mode command is assigned to a button and the button is pressed

[fbutler]

Is there an existing issue for this?

• I have searched the existing issues

Description

I mapped the Sound mode command to a "Movie" button in an Activity and assigned a Mode of MOVIE from the drop down list of available Modes. This appears to be correctly saved as the Mode assigned remains associated with the button if I move away from that screen and return to it.

However when I press the "Movie" button, to which the Sound mode command has been associated, when running that Activity I get the error "Invalid or missing params.sound_mode attribute"

How to Reproduce

Go to the button mapping screen within an Activity.
Assign the Sound mode command to a button.
Select a Mode from the drop down list of available Modes.
Exit the button mapping dialogue.
Start that Activity using the remote.
Press the button that the Sound mode command is assigned to.
See the error as per the photo above.

Expected behavior

When pressed, the button assigned the Sound mode command should result in the assigned Mode being applied.

In the case of my Denon AVR this should result in a menu of available sound options for the Mode selected being displayed on the TV screen which can be scrolled through by repeatedly clicking the button to which the Sound mode command has been assigned.

I have a Home Assistant script mapped to another button which functions correctly. The script is:

System version

1.4.5

What part of the system affected by the problem?

Integration

Additional context

No response

[zehnm]

Found the issue, fixed in the next release.

• Home Assistant integration was implemented according to the media-player entity command specification 0.8.0
  • Selecting a sound mode defines a parameter named sound_mode
• Unfortunately the command metadata for the web-configurator used mode instead of sound_mode.
  • This parameter gets stored in the sequences and UI screen definitions.

I will change the entity command specification to mode and fix the Home Assistant integration. It's the most pragmatic solution, otherwise all activity screens, macro and activity sequences using a sound mode command, would become invalid. Doing a data migration is way more work and riskier...

[fbutler]

Thanks

Fergal

[zehnm]

Status: fix is released in the BETA group and available later this week if we don't find any showstopper.

[zehnm]

Fixed in the just released v1.4.8 update