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

Saving the device state when shutting down and restarting Home Assistant (yaml setting) #913

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

glebsterx
Copy link
Contributor

Some (many) devices can save the selected state before turning off and restore it after turning on. This change will also allow you to remotely see what state the device is in: what signal source is selected, the sound mode, and whether the sound is muted. But all this without feedback from the device. On the other hand, the on / off state may also not have feedback. Therefore, for those who may need this function, they will have to configure their device in yaml

Adds the is_volume_muted property, which will allow you to see if the media player is muted until the media player is put to standby or turned off
Adds a sound_mode list that will allow these modes to be controlled on audio systems and audio receivers until the media player is put into standby or turned off. Made by analogy with source_list, but with one caveat: by default, the GUI selector "Sound mode" does not disappear when the media player is turned off, so this feature is removed from supported_features every time it is turned off (because it is illogical to control the sound mode of a turned off device)
…ant (yaml setting)

Some (many) devices can save the selected state before turning off and restore it after turning on. This change will also allow you to remotely see what state the device is in: what signal source is selected, the sound mode, and whether the sound is muted. But all this without feedback from the device. On the other hand, the on / off state may also not have feedback. Therefore, for those who may need this function, they will have to configure their device in yaml
@stale
Copy link

stale bot commented Sep 21, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 21, 2022
@glebsterx
Copy link
Contributor Author

Almost 2 years have passed, and I consider the test passed and successful, because I use the component with the modification from this PR every day

@stale stale bot removed the stale label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant