03-22-2023, 04:26 PM
(This post was last modified: 03-22-2023, 04:28 PM by psychofaktory.)
Thank you for your tests and clarifications!
Thus, my conclusions were unfortunately not correct in all points.
To check whether the UPnP renderer works, I had used the BubbleUPnP app on my Android smartphone on the one hand, and the BubbleUPnP server on the other, to be able to exclude that the problems are related to the Wifi connection.
However, the BubbleUPnP server seems to be designed to only show UPnP A/V renderers so that they can be proxied as OpenHome renderers if needed.
Thus, the server is probably not suitable to check whether an OpenHome renderer is actually accessible.
The "UPnP Tool for Developer", on the other hand, recognized all variants on my Android smartphone. Both the Moode UPnP-A/V renderer, as well as the Moode Openhome renderer. The Openhome proxy of the UPnP-A/V renderer created via the BubbleUPnP server was also found.
So it can be said that on the part of the Raspberry Pi 1B and Moode also in version 8.3.0 the UPnP renderer for mpd works.
The BubbleUPnP app now seems to be the component that shows a strange behavior.
There is neither the UPnP A/V, nor the Openhome variant displayed. Only the proxy created via the BubbleUPnP server is listed.
Other UPnP renderers (both Openhome and non-openhome) are displayed.
And I'm also sure that with Moode 6.4.1, Moode's openhome renderer could still be displayed in the app, and in the BubbleUPnP server too.
I had used the procedure to bypass the cache issue in each case.
In the meantime, I had even completely rebuilt the BubbleUPnP server and completely deleted and reinstalled the BubbleUPnP app.
In the case of the BubbleUPnP app, however, I found that it was sufficient to close the app completely once and then start it again.
Network-wise, on the other hand, everything seems to be fine.
In the upmpdcli repo was confirmed to me by the maintainers that there is purely network-technically no difference between UPnP-A/V and Openhome. Only the service description downloaded from the control point would differ.
It was also stated there that the version of upmpdcli used in Moode is quite outdated.
I had then performed an update of upmpdcli as described here.
This did not improve my problem, but there were no negative consequences.
I really appreciate the patience you guys have with me.
Thus, my conclusions were unfortunately not correct in all points.
To check whether the UPnP renderer works, I had used the BubbleUPnP app on my Android smartphone on the one hand, and the BubbleUPnP server on the other, to be able to exclude that the problems are related to the Wifi connection.
However, the BubbleUPnP server seems to be designed to only show UPnP A/V renderers so that they can be proxied as OpenHome renderers if needed.
Thus, the server is probably not suitable to check whether an OpenHome renderer is actually accessible.
The "UPnP Tool for Developer", on the other hand, recognized all variants on my Android smartphone. Both the Moode UPnP-A/V renderer, as well as the Moode Openhome renderer. The Openhome proxy of the UPnP-A/V renderer created via the BubbleUPnP server was also found.
So it can be said that on the part of the Raspberry Pi 1B and Moode also in version 8.3.0 the UPnP renderer for mpd works.
The BubbleUPnP app now seems to be the component that shows a strange behavior.
There is neither the UPnP A/V, nor the Openhome variant displayed. Only the proxy created via the BubbleUPnP server is listed.
Other UPnP renderers (both Openhome and non-openhome) are displayed.
And I'm also sure that with Moode 6.4.1, Moode's openhome renderer could still be displayed in the app, and in the BubbleUPnP server too.
I had used the procedure to bypass the cache issue in each case.
In the meantime, I had even completely rebuilt the BubbleUPnP server and completely deleted and reinstalled the BubbleUPnP app.
In the case of the BubbleUPnP app, however, I found that it was sufficient to close the app completely once and then start it again.
Network-wise, on the other hand, everything seems to be fine.
In the upmpdcli repo was confirmed to me by the maintainers that there is purely network-technically no difference between UPnP-A/V and Openhome. Only the service description downloaded from the control point would differ.
It was also stated there that the version of upmpdcli used in Moode is quite outdated.
I had then performed an update of upmpdcli as described here.
This did not improve my problem, but there were no negative consequences.
I really appreciate the patience you guys have with me.
