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

Can't Add STRDN1080 Amp - But Home Assistant Pi Can cURL, and see as Chromecast Device #142

Closed
old-square-eyes opened this issue Dec 8, 2023 · 2 comments

Comments

@old-square-eyes
Copy link

old-square-eyes commented Dec 8, 2023

Edit: SOLVED. See comment.

Songpal controls used to work, but have stopped. I can connect to my amp from the Pi with cURL.

Adding it as a device manually fails. It's not clear whether to use IP or full url, but neither work. Tried various versions of the below...

http://192.168.X.XX:10000/sony/system

image

In some ways it feels like it's set up already. But there are no Songpal controls like volume, input channel... like there used to be.

I deleted and re-added a tile but it's just a Google Cast tile with a power control, not the full control I had before. Incidentally the device also doesn't appear in my Android Music Center app any more either and they seem to have removed manual setup via IP.

image image
@old-square-eyes
Copy link
Author

Solved. Deleted Songpal Integration and re-added. Endpoint format is http://192.168.X.XX:10000/sony/

It would be helpful if the setup pane displayed the required format.

@rytilahti
Copy link
Owner

rytilahti commented Dec 8, 2023

Feel free to improve the homeassistant documentation on this regard! Having it written down in the documentation would be a great help for anyone else stumbling upon the very same issue :-)

This report made me wonder if the songpal integration (which I haven't used for some years now) does automatically update the config entries on IP address changes. The issue you had to my understanding was that the IP address of the device changed, so homeassistant didn't know where the endpoint is. Re-triggering the discovery process made it to perform the discovery again and discovered the device with the new IP address.

It may very well be, that updating config entries on ssdp responses wasn't supported back then by homeassistant and and it might be still a bit tricky (as the endpoint information is not contained in the advertisemenets, but inside a separate device description file whose location is stored in the ssdp advertisements. I doubt the location changes on these devices, so it'd be fairly risk-free to update the endpoint URL on address changes.

If someone wants to improve the integration, I'm still marked as the codeowner and will receive notifications on pull requests and can thus perform reviews, but I'm not personally going to invest in time on developing the integration further in the foreseeable future.

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

No branches or pull requests

2 participants