openLuup: AV plugins

Actually, that fix doesn’t help. I can reproduce this error, but it goes away if I revert to an earlier version of AltUI. I don’t think this is an openLuup problem, so I’ve asked @amg0 to take a look.


Edit: AltUI build 979 works OK, but build 980 does not. So 979 is the one to go for, for the time being.

http://<VeraIP>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&TracRev=979

[quote=“akbooer”]Actually, that fix doesn’t help. I can reproduce this error, but it goes away if I revert to an earlier version of AltUI. I don’t think this is an openLuup problem, so I’ve asked @amg0 to take a look.


Edit: AltUI build 979 works OK, but build 980 does not. So 979 is the one to go for, for the time being.

http://<VeraIP>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&TracRev=979 [/quote]

Thanks! I will revert and get back to testing!

[quote=“akbooer”]Actually, that fix doesn’t help. I can reproduce this error, but it goes away if I revert to an earlier version of AltUI. I don’t think this is an openLuup problem, so I’ve asked @amg0 to take a look.


Edit: AltUI build 979 works OK, but build 980 does not. So 979 is the one to go for, for the time being.

http://<VeraIP>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&TracRev=979 [/quote]

I reverted back and now discovery, selection, and playing mp3 files works. Thanks!

TTS, however, still does not work. In the terminal where i started openluup i get this error:

rm: /www/Say.4.mp3: No such file or directory

Here is the log:

HA-MacBook:cmh-ludl mda$ grep DLNA LuaUPnP.log 2015-12-12 15:00:02.719 luup.create_device:: [4] D_DLNAMediaController1.xml / I_DLNAMediaController1.xml / D_DLNAMediaController1.json 2015-12-12 15:00:02.729 luup_log:4: DLNA: #4 starting up with id 2015-12-12 15:00:02.729 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.PluginVersion was: 1.4 now: 1.4 #hooks:0 2015-12-12 15:00:02.729 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.BrowseResult was: now: #hooks:0 2015-12-12 15:00:02.729 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.PlaybackResult was: now: #hooks:0 2015-12-12 15:00:02.743 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DiscoveryPatchInstalled was: 1 now: 1 #hooks:0 2015-12-12 15:00:03.756 luup_log:4: DLNA: error: Cannot contact UPnP event proxy: connection refused 2015-12-12 15:00:03.756 luup_log:4: DLNA: UPnP proxy event identified - API version 2015-12-12 15:00:03.756 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DescriptionURL was: now: #hooks:0 2015-12-12 15:00:03.756 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DescriptionURL was: now: #hooks:0 2015-12-12 15:00:08.155 openLuup.server:: /luvd/D_DLNAMediaController1.xml tcp{client}: 0x7fdd2a054028 2015-12-12 15:00:14.553 openLuup.server:: /luvd/J_DLNAMediaController1.js tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:00:27.407 openLuup.server:: /data_request?id=lu_action&output_format=xml&DeviceNum=4&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=StartDMRDiscovery tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:00:27.407 luup.call_action:0: 4.urn:dlna-org:serviceId:DLNAMediaController1.StartDMRDiscovery 2015-12-12 15:00:27.408 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DMRDiscoveryResult was: now: scanning #hooks:0 2015-12-12 15:00:33.941 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DMRDiscoveryResult was: scanning now: <devices><device><ip>192.168.1.177</ip><port>49200</port><descriptionURL>http://192.168.1.177:49200/device.xml</descriptionURL><modelName>XiP813 Hopper</modelName><friendlyName>Hopper with Sling(Home Theater)</friendlyName></device><device><ip>192.168.1.14</ip><port>8080</port><descriptionURL>http://192.168.1.14:8080/description.xml</descriptionURL><modelName>*AVR-4520</modelName><friendlyName>Theater &amp; Whole Home Audio</friendlyName></device></devices> #hooks:0 2015-12-12 15:00:55.738 openLuup.server:: /data_request?id=lu_action&output_format=xml&DeviceNum=4&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=StartDMRDiscovery tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:00:55.738 luup.call_action:0: 4.urn:dlna-org:serviceId:DLNAMediaController1.StartDMRDiscovery 2015-12-12 15:00:55.740 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DMRDiscoveryResult was: <devices><device><ip>192.168.1.177</ip><port>49200</port><descriptionURL>http://192.168.1.177:49200/device.xml</descriptionURL><modelName>XiP813 Hopper</modelName><friendlyName>Hopper with Sling(Home Theater)</friendlyName></device><device><ip>192.168.1.14</ip><port>8080</port><descriptionURL>http://192.168.1.14:8080/description.xml</descriptionURL><modelName>*AVR-4520</modelName><friendlyName>Theater &amp; Whole Home Audio</friendlyName></device></devices> now: scanning #hooks:0 2015-12-12 15:01:04.202 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DMRDiscoveryResult was: scanning now: <devices><device><ip>192.168.1.125</ip><port>49153</port><descriptionURL>http://192.168.1.125:49153/description.xml</descriptionURL><modelName>Epitome</modelName><friendlyName>ROCKI_Sam</friendlyName></device><device><ip>192.168.1.177</ip><port>49200</port><descriptionURL>http://192.168.1.177:49200/device.xml</descriptionURL><modelName>XiP813 Hopper</modelName><friendlyName>Hopper with Sling(Home Theater)</friendlyName></device><device><ip>192.168.1.14</ip><port>8080</port><descriptionURL>http://192.168.1.14:8080/description.xml</descriptionURL><modelName>*AVR-4520</modelName><friendlyName>Theater &amp; Whole Home Audio</friendlyName></device><device><ip>192.168.1.126</ip><port>49153</port><descriptionURL>http://192.168.1.126:49153/description.xml</descriptionURL><modelName>Epitome</modelName><friendlyName>ROCKI_Paging</friendlyName></device></devices> #hooks:0 2015-12-12 15:01:05.103 openLuup.server:: /data_request?id=lu_action&output_format=xml&DeviceNum=4&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=SelectDMRDevice&URL=http%3A%2F%2F192.168.1.125%3A49153%2Fdescription.xml tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:01:05.104 luup.call_action:0: 4.urn:dlna-org:serviceId:DLNAMediaController1.SelectDMRDevice 2015-12-12 15:01:05.104 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DescriptionURL was: now: http://192.168.1.125:49153/description.xml #hooks:0 2015-12-12 15:01:05.283 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.Online was: 0 now: 1 #hooks:0 2015-12-12 15:01:05.283 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.ModelName was: now: Epitome #hooks:0 2015-12-12 15:01:05.326 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.MinVolume was: EMPTY now: 0 #hooks:0 2015-12-12 15:01:05.326 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.MaxVolume was: EMPTY now: 100 #hooks:0 2015-12-12 15:01:05.326 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.ProxyUsed was: now: proxy is not in use #hooks:0 2015-12-12 15:01:12.830 openLuup.server:: /data_request?id=lu_action&output_format=xml&DeviceNum=4&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=SelectDMRDevice&URL=http%3A%2F%2F192.168.1.125%3A49153%2Fdescription.xml tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:01:12.830 luup.call_action:0: 4.urn:dlna-org:serviceId:DLNAMediaController1.SelectDMRDevice 2015-12-12 15:01:12.830 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.DescriptionURL was: http://192.168.1.125:49153/description.xml now: http://192.168.1.125:49153/description.xml #hooks:0 2015-12-12 15:01:12.899 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.MinVolume was: 0 now: 0 #hooks:0 2015-12-12 15:01:12.899 luup.variable_set:4: 4.urn:dlna-org:serviceId:DLNAMediaController1.MaxVolume was: 100 now: 100 #hooks:0 2015-12-12 15:01:36.586 openLuup.server:: /data_request?id=lu_action&output_format=xml&DeviceNum=4&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=Play&URI=http%3A192.168.1.12%2Fdoorbell.mp3&Protocol= tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:01:36.586 luup.call_action:0: 4.urn:dlna-org:serviceId:DLNAMediaController1.Play 2015-12-12 15:01:58.876 openLuup.server:: /data_request?id=lu_action&output_format=xml&DeviceNum=4&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=Play&URI=http%3A%2F%2F192.168.1.12%2Fdoorbell.mp3&Protocol= tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:01:58.876 luup.call_action:0: 4.urn:dlna-org:serviceId:DLNAMediaController1.Play 2015-12-12 15:02:12.462 openLuup.server:: /data_request?id=lu_action&output_format=xml&DeviceNum=4&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=Say&Text=this%20is%20a%20test%201%202%203.%20this%20is%20a%20test%201%202%203.&Language=en&Engine=GOOGLE&Volume= tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:02:12.462 luup.call_action:0: 4.urn:dlna-org:serviceId:DLNAMediaController1.Say 2015-12-12 15:03:00.140 openLuup.server:: /data_request?id=lu_action&output_format=xml&DeviceNum=4&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=Say&Text=this%20is%20a%20test%201%202%203.%20this%20is%20a%20test%201%202%203.&Language=en&Engine=GOOGLE&Volume= tcp{client}: 0x7fdd2a81ae28 2015-12-12 15:03:00.140 luup.call_action:0: 4.urn:dlna-org:serviceId:DLNAMediaController1.Say

I’ve worked with @amg0 on the original problem, so the latest release 1023 works. I’ll take a look now at TTS… haven’t used it recently.

thanks! now that i know what happened i will update altui and make sure i am on the latest openluup and try again as well.

Looks like amg0 released a fix for the Sonos. I can confirm that I can easily add another device now but unfortunately having more than 1 Sonos in the mix causes both to become unresponsive. Remove the second and all is well. I can’t do much right now and this is all I can provide in the way of logs (AltUI non-debug log)… Right now my test box is busy tracing down another problem. I’ll enable debug tonight and re-add the speaker…

Just hoping this helps…

2016-01-05 08:20:39.430   luup.call_action:0: 49.urn:micasaverde-com:serviceId:Sonos1.PlayURI 
2016-01-05 08:20:39.457   luup_log:49: Sonos: error: UPnP_request (SetAVTransportURI, urn:schemas-upnp-org:service:AVTransport:1): status=1 statusMsg=500 result=[<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns="urn:schemas-upnp-org:control-1-0"><errorCode>714</errorCode></UPnPError></detail></s:Fault></s:Body></s:Envelope>]
2016-01-05 08:20:39.520   luup_log:49: Sonos: error: UPnP_request (Play, urn:schemas-upnp-org:service:AVTransport:1): status=1 statusMsg=500 result=[<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns="urn:schemas-upnp-org:control-1-0"><errorCode>701</errorCode></UPnPError></detail></s:Fault></s:Body></s:Envelope>]

And as promised, more data in hopes of isolating the Sonos problem.
Steps leading to issue:

[1] I already have a Play3 loaded and it’s working (music).
[2] Run Lua

do
local sonos = luup.create_device (‘’, “Sonos”, “Sonos”, “D_Sonos1.xml”)
luup.ip_set (“10.0.4.22”, sonos)
end

[3] Inspect device and attempt to play music on device 50 (Play1). No operation.
[4] Attempt to play music on device 37 (Play3). No operation.
[5] Delete device 50. Reload engine.
[6] Attempt to play music on device 37. Works.

AltUI v1.01.1076, ? 2015 amg0
Google Chrome Version 47.0.2526.106 m
2016-01-06 08:19:05.558   :: openLuup STARTUP :: 
2016-01-06 08:19:05.558   openLuup.init::      version 2015.11.27  @akbooer
2016-01-06 08:19:05.570   openLuup.scheduler:: version 2015.11.27  @akbooer
2016-01-06 08:19:05.570   openLuup.server::    version 2015.12.05  @akbooer
2016-01-06 08:19:05.572   openLuup.plugins::   version 2015.11.06  @akbooer
2016-01-06 08:19:05.574   openLuup.scenes::    version 2015.11.12  @akbooer
2016-01-06 08:19:05.576   openLuup.chdev::     version 2015.11.09  @akbooer
2016-01-06 08:19:05.577   openLuup.io::        version 2015.10.15  @akbooer
2016-01-06 08:19:05.577   openLuup.luup:0:      version 2015.11.16  @akbooer
2016-01-06 08:19:05.580   openLuup.rooms::     version 2015.10.15  @akbooer
2016-01-06 08:19:05.581   openLuup.requests::  version 2015.11.09  @akbooer

Does anybody have any idea why I cant see sonos as a device in homewave from openluup??
I have added the devices in my startup.lua and they seem to be working ok except i cant see them in homewave.
If i manually create the device from the ALtUI … Then they show up in homewave but i am unable to set the ip if i do it that way.
Also any device i manually create gets deleted when i reboot as it is not in my statup.lua

I’ve never tried looking for Sonos in Homewave - I’ll take a look!

I have added the devices in my startup.lua and they seem to be working ok except i cant see them in homewave. If i manually create the device from the ALtUI .. Then they show up in homewave but i am unable to set the ip if i do it that way.

That doesn’t make much sense to me… in the end the same code is creating the device. Why can’t you set the IP? Just use:

luup.ip_set ("1.2.3.4", devNo)

or, set it from AltUI… you may need to reload to see the change.

Also any device i manually create gets deleted when i reboot as it is not in my statup.lua

You should not be running a startup.lua every time you reboot. Simply invoke ./openLuup_reload without any parameter and it will pick up the last user_data.json file and you should be up and running where you left off.

You should not be running a startup.lua every time you reboot. Simply invoke ./openLuup_reload without any parameter and it will pick up the last user_data.json file and you should be up and running where you left off.
Oh ok I have been reloading using openLuup_reload startup.lua as I thought it needed the startup.lua everytime. That had me confused. So is the startup.lua only run the very first time?

And also what is the best practice to load plugins?
Should they be put in startup.lua or just create the device manually?

That doesn't make much sense to me... in the end the same code is creating the device. Why can't you set the IP? Just use: Code: [Select] luup.ip_set ("1.2.3.4", devNo) or, set it from AltUI... you may need to reload to see the change.

I have managed to get the ip set but am having problems with the plugin… I can press play and stop but cannot choose playlist or song ?

[quote=“JCH, post:150, topic:189395”]I have been reloading using openLuup_reload startup.lua as I thought it needed the startup.lua everytime.
That had me confused.
So is the startup.lua only run the very first time?[/quote]

Sorry it wasn’t clear. The openLuup_reload loop internally just picks up the last user_data.json file. The only reason you need a parameter is either for a factory reset, or to configure a new system with a startup.lua file from scratch. So, yes, startup.lua for the first time, although read on…

And also what is the best practice to load plugins? Should they be put in startup.lua or just create the device manually?

I always recommend that you keep an up-to-date startup.lua file which reflects any additions you may have made manually. This just makes it so easy to rebuild from scratch - not that you ever really have to do that. It would only be in the case of having royally screwed up your current configuration by hacking the user_data.json file or something equally dreadful. If you do start from scratch you will lose any scene definitions - I have yet to provide an automated solution for that, although it’s not too hard to add back manually from a backup.

I have managed to get the ip set but am having problems with the plugin... I can press play and stop but cannot choose playlist or song ?

Can you elaborate on the symptoms? Is there anything in the log that’s relevant?