You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have put together a basic ControlPoint and MediaRenderer, both of which are running on my MacBook. While the ControlPoint is able to see all of the devices in my house (so far), other ControlPoints do not see the MediaRenderer. Specifically, the built-in music players on the Samsung Galaxy S5 and LG V10, as well as other Android Apps, such as BubbleUPnP and UPnP Scanner. The latter two are built on the Cling UPnP stack. A third Android App, AirWire, does find the MediaRenderer, and is able to control it without issue.
At first I thought this might be a problem restricted to Cling-based devices discovering CyberGarage devices, but since the Android music players are unable to find them either, it appears to be a broader issue.
The text was updated successfully, but these errors were encountered:
I did notice that other devices send response messages from the same port, but the CyberGarage device sends each response message from a different port. I'm not sure if that is the issue with discovery, but it seems it should bind to one port, rather than a series of random ports.
I have put together a basic ControlPoint and MediaRenderer, both of which are running on my MacBook. While the ControlPoint is able to see all of the devices in my house (so far), other ControlPoints do not see the MediaRenderer. Specifically, the built-in music players on the Samsung Galaxy S5 and LG V10, as well as other Android Apps, such as BubbleUPnP and UPnP Scanner. The latter two are built on the Cling UPnP stack. A third Android App, AirWire, does find the MediaRenderer, and is able to control it without issue.
At first I thought this might be a problem restricted to Cling-based devices discovering CyberGarage devices, but since the Android music players are unable to find them either, it appears to be a broader issue.
The text was updated successfully, but these errors were encountered: