Does uPnP Mate run on an pure IPv6 network?
Yes. uPnP Mate supports the UPnP Device Architecture V1.0. Devices compliant with this specification are required to self-assign IPv4 link-local IP addresses in a pure IPv6 or an otherwise unmanaged IPv4 network. Such devices are fully supported by uPnP Mate.
I am not seeing any devices
Make sure your iOS device is connected to the network via Wi-Fi and not Mobile Data. UPnP operates over a local area network, not a wide area network.
Make sure your Wi-Fi router is not running in client isolation (also known as AP isolation, Wireless isolation, Station isolation) mode, which prevents devices on your Wi-Fi network from communicating with each other, including your iOS device.
I am missing some devices
First of all, try refreshing the display. This is achieved by pulling down the view containing the list of devices. If the device you are looking for is still missing, then it is possible that the device in question is not fully compliant with the UPnP specifications. Device discovery is done through an exchange of messages between uPnP Mate and the devices on the network. These messages are logged and can be reviewed in the SSDP message log (uPnP Mate v1.1 and later). Please contact us if you think that the missing device has responded correctly in the discovery process but is not being detected by uPnP Mate.
I get an error when I click on a service. The error message tells me to turn on the device, but the device is already on. What's going on?
The error message gives the URL of the web page that uPnP Mate is failing to load. To diagnose the problem, please note down the URL and enter it into the address bar of the mobile Safari browser on your device. It the web page loads successfully on Safari, then please contact us with a description of the problem using the Contact Form. If the web page does not load properly with the mobile Safari browser, then the likely cause is a bug in the device. For example, we have a Blu-ray player that reports the wrong content-length when returning the web page, thus causing a corrupted document to be returned to uPnP Mate. In such a case, please contact the manufacturer of the device for support.
I get a network error saying I need to enable Wi-Fi and grant local network access.
uPnP Mate does not work over a mobile data connection - it is designed to discover UPnP devices connected to your local (i.e. Wi-Fi) network, hence you must have an active Wi-Fi connection to use it.
In recent versions of iOS, access to the local network requires explicit permission from the user. Permission is requested when the app is launched for the first time after installation. You need to grant the permission for the app to function correctly. Unfortunately, while permission is being sought from the user, the underlying networking code will fail, so the app displays the error message. This should only happen once after the app is installed. Simply close the app and re-open it. If you have accidentally blocked the app from accessing the local network, open the Systems app, scroll down to find the uPnP Mate entry and enable access to local network.
I get an error message saying the device's cache entry has expired.
When a UPnP device advertises its presence on the network, the message contains a cache-control max-age entry which defines how long the advertisement remains valid. It is the responsibility of the device to send a NOTIFY message before the max-age expires to say that it is still alive. The error message is displayed if no NOTIFY message is received within the max-age period.
A NOTIFY message can be missed if it arrives when uPnP Mate is not running in the foreground - this is an iOS limitation. When you see the error message, simply refresh the devices list and reselect the device.
A device (of a given USN) appears multiple times on the devices list.
This can happen under the following conditions:
- The USN is supposed to contain a UUID unique to each device. If same USN is being used by multiple devices, then multiple entries will appear in nPnP Mate. The error may be due to a configuration oversight (e.g. a user replicating the configuration of a media server from one computer to another and forgetting to change the USN), or a misconfiguration by the manufacturer (e.g. I have come across devices where the same UUID is used by the root device and it's embedded devices).
- A devices has several network interfaces. For example, a media server running on a Mac that is connected to the local network via both ethernet and Wi-Fi will be advertising its services over the ethernet's IP address as well as the Wi-Fi's IP address. uPnP Mate will pick them up as separate instances.
I have a comment/suggestion to make
Please contact us using the Contact Form.