I just committed a new change that should certainly help with UI6/UI7.
You can find it in my “working in progress” version of the plugin: trunk – DLNA Media Controller
I have done no tests neither with UI6 nor with UI7, but I can at least confirm that the plugin continues working well with UI5.
Let me know if these changes solve issues with plugin UI when using UI6 or UI7.
[quote=“jamezel13, post:3, topic:182611”]I’m new to Vera. How do we test if they work?
I would like to trigger audio with scenes, but the DNLA plugin can’t find my servers.[/quote]
You shoould be sure to have enabled UPnP AV in your network router.
Have you another UPnP controller in your network that see your UPnP servers ?
If UPnP discovery inside the VeraLite is not working, a workaround was discovered, this workaround works at least for his author and me: http://forum.micasaverde.com/index.php/topic,16905.msg132502.html#msg132502
Strangely, this workaround is now no more required for my VeraLite and the only changes I made during this time are firmware updates of my network router…
I don’t think the problem is relative to UI7 as I think I see it working in @HaPe’s Vera running UI7. I will check again.
I am not used to creating devices based on the Lua files, rather than “packaged” apps. I have uploaded the ten files from Trunk @ 60. I don’t know which files should correspond to which category in the creation.
Device type
Internal ID
Description
Upnp Device Filename
Upnp Implementation Filename
Could you let me know which files should match which? I’m happy to test once it is set up both with PC, and an XMBC interface.
So I put D_DLNAMediaController1.xml as Upnp Device Filename and I_DLNAMediaController1.xml as Upnp Implementation Filename and that seemed to create it, but I could not discover my XBMC device. I am going to try the linked thread two comments up and see if that works. I am using a Veralite and so it sounds unneccesary, but it currently is not working yet.
I just committed new changes; compatibility with UI7 should be ok.
The only minor thing that should not be ok is the icon for the device: the DLNA icon will not be displayed.
Is anyone able to use this on UI6? I have 1.1 installed but it is not able to discover my XMBC machine either using the Discover button, or directly adding the URL on the settings page. I double checked and it is set to be discoverable in XBMC, and I am able to find it using BubbleUPnP on my Android. I tried editing the fields on the Advanced menu as well, but it does not seem to work. I tried changing the IP field to the ip address of XBMC, and then tried that in combination with the RouterIP field empty and with the ip address of my router as well. None of that seemed to work. Has anyone else been able to use discover in UI6 and or have suggestions for what I can try? Thank you.
@rd: please check your installation. You should have only 9 files with name containing DLNA in your directory /etc/cmh-ludl, all with a suffix .lzo and a not null size. I would advice to delete your device, reload, create another one, reload and finally free your WEB browser cache.
@everybody: can someone else confirm that the plugin is not working with UI6. That would be strange but in this case I will suppress all references to UI6 in my communications.
For information, for XBMC 13.1, I can confirm that the URL to be used looks like: http://192.168.0.100:1396/
The ending / is important, it does not work if you enter http://192.168.0.100:1396
Of course, you have to use your IP address and probably the port number is not always the same.
I deleted the app, and saw that the files were still there so I ssh’ed in and removed them. Then reinstalled using 1.1 in the official app repository. It still did not find or recognize it using the discover button. Adding the ‘http://’ and the final ‘/’ allowed me to enter it in the New Url filed and then appear in the description URL, but it perpetually thinks that it is offline, when it is not. Below is the log that I generated after all of that trying to use the discover method again. It is Device 66.
I partially got it working. Discover still does not work, but entering the URL directly did. I had mistakening been using the “Presentation URL” that was set in XBMC (:8080) whereas using DeviceSpy I found the “base URL” was (:1336). It now sees XBMC and what is playing and the state. I haven’t got the TTS to work yet, but the major issue has been solved I think.
Best Home Automation shopping experience. Shop at Ezlo!