-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Bug]: Adapter seems to create wrong url #104
Comments
Open the link and post it here: http://192.168.0.113:1400/xml/device_description.xml |
The Output of http://192.168.0.73:1400/xml/device_description.xml which is the Symfonic/Sonos-Device Can't get an Output of http://192.168.0.81:8080/xml/device_description.xml which should be the Output of the Silvercrest-Device.
|
If it is no sonos device the file name is not the same. You can search for it with the app "upnp tool" for Android. |
Attached are all XML outputs created with the UPnP tool. There are four different devices. A Sonos-compatible device "Symfonisk" from IKEA - SYMFONISK_neu.zip Three devices from Silvercrest that work in the manner of Fontier Silicon. However, the expenditure should be uniform so far. It is about: I hope I could help 😁 |
The URL is wrong because the silvercrest devices deliver it wrong. Leave this issue open, as reminder to add validation for the url. |
You mean: In this case I get following warn-message: 😢 Or I didn't understand what you meant and you may write your suggestion in englisch AND german ;-) |
Or maybe you just show the full-Objekt-ID, like |
Contact Details
No response
What happened?
As written in https://forum.iobroker.net/topic/51767/vorlage-upnp-media-player/10?_=1643386555921 the adapter seems to create a wrong url.
Attached wanted Objekt AVTransport.
2022-01-28 - 17_18 - Objekte - upnp.0.1__OG_-Salon-_Internetradio.MediaRenderer.AVTransport.txt
Adapter Version
1.0.20
JS-Controller Version
3.3.22
Node JS Version
v14.18.2
NPM Version
6.14.15
Operating System
Ubuntu
Relevant log output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: