go2tv: Can't connect to AVTransport

Hello,

Thanks for building this tool. I can’t connect to my DLNA speakers as I am getting the following error:

SendtoTV set AVT Transport error: setAVTransportSoapCall Do POST error: Post "http://192.168.1.32:54380/upnp/control/AVTransport": POST http://192.168.1.32:54380/upnp/control/AVTransport giving up after 4 attempt(s)

I’m running the tool on Ubuntu 20, and the speakers are working well with other DLNA renderer (like the default one in Windows).

Let me know if you need more information.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 34 (34 by maintainers)

Most upvoted comments

So I finally found what’s happening, and it’s because we didn’t push the media type in the headers, so the player was lost somehow.

So I had a deeper look at the content type and in my tests I got Screenshot from 2022-06-18 10-40-46 From here I see that the headers were already passed correctly when trying to stream an audio file.

same for a flac file

Accept-Ranges: bytes
Content-Length: 336902264
Content-Type: audio/flac
content-type: audio/x-flac <------------------ this is after your PR
Date: Sat, 18 Jun 2022 07:45:56 GMT
Last-Modified: Sun, 29 Jul 2018 16:14:56 GMT
realTimeInfo.dlna.org: DLNA.ORG_TLAG=*
transferMode.dlna.org: Streaming

Just trying to understand if this indeed the issue

EDIT: I think it’s just the HEAD requests suffering from this. Will rework the fix to avoid the double headers

EDIT2: Amended here: https://github.com/alexballas/go2tv/commit/89154bcf30e7fcc6c14f0308177fba1fc5896605

alexballas on Jun 18, 2022

Fixed with 1.12.0, resolving

alexballas on Jul 2, 2022

OK, not unexpected. From a quick search it seems that your speaker work fine with BubbleUPNP on android. I’ll try to reverse engineer the calls and see if there are any discrepancies. Keeping the ticket open as there are certainly improvements to introduce to the UPNP protocol implementation.

alexballas on Jun 7, 2022