-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
Songpal device with multiple zones confuses HA #14936
Comments
Are you sure you are running 0.70.1? Can you check that the file uses |
I can also vouch for seeing this warning constantly on 0.74.2 with an STR-DN1060. I have tried setting [code]logger: But the warnings persist every 10 seconds. Similarly, setting the endpoint manually in an ubuntu deployment and using the songpal CLI shows volume level as -1/55. |
System HassOS 1.9 Home Assistant 0.76.2 Hi I'm constantly getting the following warning. The device seems to have more than one volume setting. |
The warning is coming from the upstream library, sorry for not taking care of it earlier. The linked PR bumps the dependency (or you can simply install python-songpal==0.0.8 manually) to fix this. edit: or to hide the warning via logger configuration, you can also use |
Thanks rytilahti, sorry how do I install python-songpal==0.0.8 manually in Hass.io? |
Hi @WazWaz any luck with adding the controlling other zones feature request?
|
No, I just stopped using songpal. |
Thanks, @WazWaz so what are you using? |
Home Assistant release with the issue:
0.70.1
Last working Home Assistant release (if known):
Never since songpal was added.
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on RaspberryPi
Component/platform:
https://www.home-assistant.io/components/media_player.songpal/
Description of problem:
The logs continuously reports:
Yes, the device has a volume control for main and for other zones.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):and in entity_registry.yaml:
Traceback (if applicable):
Additional information:
I understand that controlling the other zones is a feature request, and I'll add that, the bug is that it logs the error continuously (every 10 seconds or so), spamming the log.
The text was updated successfully, but these errors were encountered: