03-20-2023, 01:20 PM
(This post was last modified: 03-20-2023, 01:23 PM by psychofaktory.)
(03-20-2023, 09:53 AM)the_bertrum Wrote: I found the order that you bring things back in seems to matter, restarting all the components isn't enough, they need to all be off for long enough to reset their cache and the restarted in order. The fact that you can see other UPnP devices shows that your network isn't fundamentally wrong.I had left the devices all unpowered for longer and brought them back online in the order you suggested.
My network is totaly fine.
All other components, including the rest of the UPnP devices also work flawlessly.
For testing, I brought the same Raspberry again into a completely independent network, which was created especially for this purpose.
Again, Moode did not show up as a UPnP renderer in BubbleUPnP. Another device, which I had also connected to the network for the counter test, was displayed without any problems.
(03-20-2023, 11:08 AM)Tim Curtis Wrote: UPnP uses IP Multicast for discovery and announcement https://en.wikipedia.org/wiki/Simple_Ser...y_Protocol so you may want to check your Firewall device and servers to make sure there are no explicit deny rules for this protocol or its address space.I have configured the firewall myself. There are no deny rules or similar that could intervene here.
(03-20-2023, 11:08 AM)Tim Curtis Wrote: Post your conf file if it's different than the default file.The configuration (with the exception of my adjustment to debug-logging today) is the default configuration of a fresh Moode installation.
I have a hunch that it is because on the Raspberry Pi 1B, the network stack may be different from the more modern Raspberries and therefore no UPnP multicast is sent from the Raspberry to the network.
Would that be possible?
Does anyone here have a Raspberry Pi 1B with MoodeOS 8.3.0 where the UPnP renderer works without problems?
