-
Notifications
You must be signed in to change notification settings - Fork 15
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
BubbleUPNP devices not being discovered #157
Comments
please attach the complete (unedited) debug log. |
Thanks. The problem is simple: the location header in the SSDP response should be uppercase "LOCATION:", but for some reason Bubble uses "Location:". You will see in your log that all other devices properly use LOCATION. Idem for the ST header, Bubble uses St. Easily fixed, probably tomorrow. |
Should be fixed in release 1.12.1. |
Still having the same issue: |
You're right, the comparison was already case insensitive, so I'll have to investigate properly... |
The reason: it's the only device I have ever encountered that puts the Location header last. |
This time I hope I fixed it properly. Sorry for the mess... |
log.txt Let me know if you need any more info from me, thanks for your quick responses |
If I expose an openhome renderer in BubbleUPNP that one takes the place of the "Living room speaker (DLNA)" renderer in the UI. Possibly only the first BubbleUPNP renderer discovered is being properly shown? |
For swyh-rs a "device" is identified by it's IP address as discovered in the SSDP responses. But Bubble UPNP uses the same IP address and port number for every endpoint:
So the last one to respond wins, and Openhome is preferred to AV. As it is now, swyh-rs can not handle that. Now if the port numbers were different, I could perhaps support that, but if both are identical they are one device. |
Looking at the code I think it's not a monumental task to support this, but I would need your assistance in testing my attempts to implement the necessary changes. |
If I release a new beta to test, do you need the setup or is a debug binary sufficient? |
If it's just replacing the swyh-rs.exe I can handle that |
try to support multiple players at the same IP address (issue #157)
There's a new beta setup. |
log.txt |
I expected problems but I thought the buttons for the players would at least show up. However, since the streaming is totally disconnected from UPNP, I have no means to connect a device that is currently streaming to the buttons in the GUI, and I don't think I can solve that. I only have the IP address of any device that starts streaming, and nothing more. So it's probably not something that I can support reliably. |
But I'll see if I can up with something that works if you are prepared to wait a bit. |
The beta has been updated. I think it should work now. Some things will probably no longer work, let me now if you find something (or if it still doesn't work at all). |
Looks to be the same with beta 2, albeit with no regression either from what I can tell. |
The beta has been updated again. I think it should work now, honestly :) Some things will probably no longer work, let me now if you find something (or if it still doesn't work at all). |
Beta 3 also looks to be exact same behavior, still able to stream to the one exposed bubble upnp dlna device just fine: |
For some reason you're still running the original beta. This line:
should be similar to this one:
I have no idea how this is possible, as I delete the old setup every time and replace it with the new one on Github. But it certainly explains why you don't see any changes... |
I have no idea if Bubble or Chromecast support changing the volume, reading it out seems to work though. Looking at your screenshot, I see that the SSDP interval is extremely short, if you're on shaky WiFi connections it might interfere with the streaming. I will wait a couple of days before releasing this officially, in case you find any problems. One restriction when using devices sharing the same IP address: if you start streaming from swyh-rs, and terminate it with some other means (breaking the streaming connection from the device end), swyh-rs is not able to reflect this on the button, it will remain lighted even though the device is no longer streaming. The streaming code only has the IP address of the device that requests HTTP streaming, and there is no way to link this back to the DLNA device that got the Play command from the GUI (except guessing) |
Oh, and thanks for testing this and bearing with my attempts to fix it. Much appreciated! |
Fixed with release 1.12.3. |
swyh.txt
The devices are responding to SSDP but not sure what's going on after that. These all show up in swyh original but not in -rs
The text was updated successfully, but these errors were encountered: