Unable to detect some DLNA players about jupii

[mkiol]

Thank you for your report.

Let me sum up. There are at least two issues:

1. Jupii does not detect Jupiter device
2. Jupiter device detects Jupii but you cannot connect ("Connection timeout" message)

To investigate the issues I need to see the log. In the most recent Jupii version (version 2.5.3 - OpenRepos) I've added option to enable logging to file. Please install it.

Do following steps:

1. Enable logging in Jupii (Settings page, last option)
2. Restart Jupii
3. Try to find devices (many times click on "Find devices")
4. Close Jupii
5. Copy /home/nemo/jupii.log fine to your computer. Rename it to something like jupii_issue_1.log.
6. Start Jupii
7. Try to find Jupii on your Jupiter device and try to connect (many times)
8. Close Jupii
9. Copy /home/nemo/jupii.log fine to your computer. Rename it to something like jupii_issue_2.log.

Please send both log files to jupii[at]mkiol.net.

[mkiol]

If problem still occurs, please provide the log and re-open this issue.

[dikonov]

I tested it with the new version and it seems to work, but(!) discovering this device takes a lot more time and tries than Kodi on my notebook. I had to run device discovery 5 times and manually reconnect the radio to the net before it appeared in jupii. The radio itself was connected all the time and played radio without problems before and after connection.

Maybe the radio is slow and timeout in jupii is too short. Could the discovery be done in a background thread and last longer? Maybe UPNP devices could be cached and probed for availability before lengthy scanning?

Here is part of the log (file attached
jupii.log.gz
)
] :0 - ==> Visitor
[D] :0 - Device
[D] :0 - friendlyName: "Jupiter 6.2 002261b3626a"
[D] :0 - deviceType: "urn:schemas-upnp-org:device:MediaRenderer:1"
[D] :0 - UDN: "uuid:3dcc7100-f76c-11dd-87af-002261b3626a"
[D] :0 - modelName: "Jupiter"
[D] :0 - URLBase: "http://192.168.169.5:80/"
[D] :0 - Service
[D] :0 - controlURL: "AVTransport/control"
[D] :0 - eventSubURL: "AVTransport/event"
[D] :0 - SCPDURL: "AVTransport/scpd.xml"
[D] :0 - serviceId: "urn:upnp-org:serviceId:AVTransport"
[D] :0 - serviceType: "urn:schemas-upnp-org:service:AVTransport:1"
[D] :0 - ==> Visitor

[mkiol]

Thank you for the log.

Did you observe discovering delay for other UPnP devices as well? Kodi for instance.

In the recent version, I've added option to mark device as a favorite. All favorites devices are always available, therefore you can skip discovering phase. Of course it works only when IP address of your Jupiter device is always the same. It is sort of workaround but maybe it will resolve your issue.

[mkiol]

I can also provide configuration option to increase discovery timeout. Currently it is set to 5s.

Jupii/core/directory.cpp

Line 177 in 880ac0d

m_directory = UPnPClient::UPnPDeviceDirectory::getTheDir(5);

[dikonov]

I only have 3 devices. Kodi and LG TV LF650 are detected reliably and almost instanttly.

Longer discovering delay is good, but (ideally) it should run in background. Already discovered devices should appear immediately and the user must be able to select/use them before the long discovery process finishes without waiting for "slow" devices to be found, unless they are needed.

[dikonov]

BTW, please, update the ru translation in the rpm ;)

[mkiol]

Longer discovering delay is good, but (ideally) it should run in background. Already discovered devices should appear immediately and the user must be able to select/use them before the long discovery process finishes without waiting for "slow" devices to be found, unless they are needed.

I agree. I'm adding it to my (very long) TODO list.

[mkiol]

BTW, please, update the ru translation in the rpm ;)

Thank you for the update. Will be in the next release.