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

The volume is stuck and does not change on DLNA players #2127

Closed
1 task done
sp0ngeboobs opened this issue Apr 15, 2024 · 9 comments
Closed
1 task done

The volume is stuck and does not change on DLNA players #2127

sp0ngeboobs opened this issue Apr 15, 2024 · 9 comments
Labels

Comments

@sp0ngeboobs
Copy link

What version of Music Assistant has the issue?

2.0.0b136

What version of the Home Assistant Integration have you got installed?

2024.3.6

Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

  • Yes

The problem

The sound level is displayed incorrectly.

  1. When I change the sound in HA, the volume of the speakers changes, but the slider is stuck at one level. Also, the level in MA is stuck.
  2. When I change the sound level in MA, then the slider remains in the right position, but when I load the page, the sound level is not correct, it is taken from HA.

as I understand MA always takes the sound level from HA player attributes ( volume_level: ) which are always at the same level. And if you set a level ( volume_level: ) in developer tools, it will be stuck at that level in the future.

How to reproduce

try changing the sound level in HA and MA

Music Providers

DLNA

Player Providers

radio stream from URL
Soundcloud.

Full log output

I am attaching the log, but there is nothing displayed about the sound level.
log.txt

Additional information

No response

What version of Home Assistant Core are your running

2024.4.3

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Raspberry Pi

@OzGav
Copy link
Contributor

OzGav commented Apr 16, 2024

Do you have other players that do work?

@sp0ngeboobs
Copy link
Author

Do you have other players that do work?

Yes. I have 6 DLNA players in MA and all of them have such a glitch.
I also have a HomePod connected via an Apple TV add-on, the sound level there works fine.

@OzGav
Copy link
Contributor

OzGav commented Apr 16, 2024

Please adjust the title then to properly reflect that this is only a DLNA issue

@sp0ngeboobs sp0ngeboobs changed the title Volume is stuck and won't change The volume is stuck and does not change on DLNA players Apr 16, 2024
@marcelveldt
Copy link
Member

I am super confused. You say you are using DLNA players but you're talking about HA attributes ?
Which one is it, dlna player in MA or HA players ?

@sp0ngeboobs
Copy link
Author

I am super confused. You say you are using DLNA players but you're talking about HA attributes ? Which one is it, dlna player in MA or HA players ?

DLNA music provider in MA.
MA creates an entity (media_player.name ) in HA, in which there is volume_level: in the attributes, and this level does not change through the MA or lovelace interface, it is stuck on one value. But the sound in the speakers changes

@marcelveldt
Copy link
Member

Most probably your player is not sending any state changes then after a volume change (DLNA is an awfully flawed protocol)

The log you shared above, is that collected after you tried changing the volume ?

@sp0ngeboobs
Copy link
Author

Most probably your player is not sending any state changes then after a volume change (DLNA is an awfully flawed protocol)

The log you shared above, is that collected after you tried changing the volume ?

the fact is that this glitch did not exist before. I noticed this about a month ago.
Yes, I recorded the log when I changed the sound level several times, so there in the log I see the entries "Handling command cmd_volume_set for player"

@sp0ngeboobs
Copy link
Author

ok, I tried to connect the player via DLNA integration in HA, created a new entity. And the glitch with the sound continues, so I conclude that maybe it's not a MA problem. Close the topic or let it be?

@OzGav
Copy link
Contributor

OzGav commented Apr 18, 2024

If you are happy it is not MA then yes we will close

@OzGav OzGav closed this as completed Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants