03-22-2023, 03:38 PM
(This post was last modified: 03-22-2023, 03:50 PM by TheOldPresbyope.
Edit Reason: edited for better format
)
(03-22-2023, 09:15 AM)psychofaktory Wrote:(03-21-2023, 09:08 PM)Tim Curtis Wrote: There is only the one setting in UPnP Config otherwise I just used a stock 32-bit 8.3.0 image. My network is a single ASUS WiFi Router with 4 x Ethernet ports.
Based on my experience your symptoms suggest something external to moOde software or Pi hardware for example some sort of network configuration issue.
OK, thats all kind of strange.
I did....
So it seems to be a software problem after all, where the Raspberry Pi 1B under Raspian Bullseye does not deal with the Openhome standard.
(03-22-2023, 08:32 AM)the_bertrum Wrote: Has the old standard of re-flashing/different SD been tried on this problem yet? It has been known to work wonders in the past.
Yes, did that two times before, with the same result of UPnP-renderer keeping not showing up on network
Two things: you need to stop saying the renderer doesn't show up on the network---because you have established only that your particular control point doesn't list it under the conditions you have described---and you need to stop saying the Pi 1B on Raspberry Pi OS doesn't deal with the OpenHome standard ---because what you've done hasn't established that yet.
The UPnP-A/V (with DLNA constraints) and OpenHome specs are related in that they both describe UPnP stacks but the services they offer are incompatible. Some control points and renderers understand both, some understand only one or the other, and as the_bertrum has repeatedly said, some get confused when caches get stale.
Since you are using an Android phone to run BubbleUPnP [1], check your Play Store for an app named "UPnP Tool for Developer" by TJ App. If you find it, install it.
Now, configure the moOde UPnP renderer for service type UPnP - A/V, let the renderer restart, then check the Device List in UPnP Tool. You should see your moOde player show up in the Device List with whatever name you gave the renderer. Click on it. You should see a list of services with urns like:
Code:
urn:schemas-upnp-org:service:AVTrsansport:1
etc.
Next, configure the moOde UPnP renderer for service type OpenHome, let the renderer restart, and again check the Device List in UPnP Tool. You should see a new entry for your moOde player. Click on it. You should see a list of services with urns like:
Code:
urn:av-openhome-org:service:Time:1
etc.
In my case at least, the Device List now shows both instances of the renderer---an example of caching.
The UPnP Tool app is doing the UPnP discovery work itself so it's a test of both UPnP devices and the interconnecting network.
There are similar diagnostic tools available for Android and for other O/Ses (like gssdp-discover in LInux) but I found this particular Android app to be easy to install and easy to interpret.
Regards,
Kent
[1] as an aside, there is the BubbleUPnP for DLNA/Chromecast app and there is the BubbleDS for Linn DS/OpenHome app. Both from Bubblesoft.