-
-
Notifications
You must be signed in to change notification settings - Fork 29.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
Login attempt or request with invalid authentication from HEOS-HomeCinema #69489
Comments
heos documentation |
Hey there @andrewsayre, mind taking a look at this issue as it has been labeled with an integration ( |
Have you actually used the heos.sign_in service to log it into your Heos account? It'll not work until you do. |
Yes I've done that. Favorites are working and everything. But the error still occurs. I will try it tomorrow with a clean Hass vm to confirm that there's nothing else in my setup causing it. |
Since this issue also occurs when playing through the media browser, I feel like it might be the same issue that was reported here. Do you have a similar message in your own logs @ianfretwell ? |
@frankvollebregt No errors at all for me - it just doesn't do anything so I'm pretty sure it's different. |
After enabling the logs as per the documentation, I can view the URL that is sent to the Heos to be played. It looks a bit like this (some parts obscured for obvious reasons):
Sure enough, running this URL in Postman returned the same 401 (unauthorized) error.
When I put this URL in my browser's address bar, it plays as expected. In conclusion, I suspect that the URL is encoded twice: Once in pyheos, and once in the HA component. I'm not very experienced with how HA works, so I hope I may have saved someone some time figuring things out :) EditNever mind the above, since it's a URL inside a URL, of course the inner part would have to be encoded twice (otherwise it might break the outer URL...) I see there have been some changes on the dev channel to the |
To supplement to the original issue, here is a part of the debug logs I get:
|
And yet I'm not having ANY problem playing to my Heos Homecinema through the media browser. Just for clarity I'm selecting music from a DLNA server. My original issue still stands that it won't play an album, only individual tracks. Playing an album just causes the previous Heos instigated queue to play instead - as per here. |
I have Marantz amp and when I try to play media through the hass media player I get the same login error and I cannot play any local media from the media browser when I select the HEOS output. It just jumps to play one of the working HEOS playlists. Seems like the url that is given from hass to the HEOS and which it is trying to play inside the amp is not reachable from the hass instance and hass gives HEOS the login prompt in which it does not have creds. Am I right? I'm running: Home Assistant 2022.4.3 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
bump |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
I'm getting the following error when I try playing music to my heos soundbar HEOSHCBKE2 via the media browser.
I've tried re adding the integration but no luck.
Login attempt or request with invalid authentication from HEOS-HomeCinema (192.168.1.72). (AvegaMediaServer/2.0 Linux/2.6)
What version of Home Assistant Core has the issue?
core-2022.4.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Integration, heos
Link to integration documentation on our website
https://www.home-assistant.io/integrations/heos
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: