Now I’ve had various Sonos plug-ins over the years, and from what what I can tell the feedback on the forum has been that these are due to upnp messages that Vera is seeing. …
However…
Enable UPNP is disabled (not ticked) on the controller
To assure UPNP is realy disabled you can run these two lines in the Lua Test window. Without this my Vera Edge’s go into a LUUP restart loop when on the same network as Sonos.
Does that suggest that somewhere there is a trigger set or invoked that then looks for a file called …
D_FUP_uuid RINCON_000E5832CCA201400.xml
Would creating a file with that name help, if only to remove the message from the top/banner, yet still notify me ? If so - what something like this using luup.task help ?
<?xml version="1.0"?>
<implementation>
<functions>
local TASK_ERROR = 2
local TASK_ERROR_PERM = -2
local TASK_SUCCESS = 4
local TASK_BUSY = 1
local MSG_CLASS = "Dummy"
function clearTask()
dbg.log("Clearing the task panel in UI5", dbg.DEBUG_VERBOSE)
luup.task("Clear", TASK_SUCCESS)
end
function task(text, mode)
local mode = mode or TASK_ERROR
if (mode == TASK_ERROR_PERM) then
taskHandle = luup.task(text, TASK_ERROR, MSG_CLASS, taskHandle)
else
taskHandle = luup.task(text, mode, MSG_CLASS, taskHandle)
if (mode ~= TASK_SUCCESS) then
luup.call_delay("clearTask", 30, "", false)
end
end
end
</functions>
<startup>SonosRICON</startup>
</implementation>
The way this is supposed to work (and this has nothing to do with the Sonos plugin) is that UPnP device discovery (Vera) is supposed to find the device, and using the response in the discovery packet, it gets the device description. That DD enumerates a bunch of services, which either the host (Vera) can recognize natively, or if not, it can request them from the UPnP device (Sonos). It then keeps them and “learns” them. On Vera, this is all broken, and produces nothing useful, which is why the Sonos plugin exists. It will goof things up mightily, though. So yes, by all means, turn off with extreme prejudice.
You need to reload Luup after changing the UPnP settings also. I don’t see that in @reneboer’s code… don’t forget that step.
Thanks, and while not specifically mentioned I did do a reload too, but that still didn’t change anything, nothing I do seems to stop those bl**dy system error messages coming up.
Ah, so go ahead and delete those broken devices. You might not be able to see them in the UI, so you’ll have to sleuth them out in the log and use the Luup action DeleteDevice in urn:micasaverde-com:serviceId:HomeAutomationGateway1 (only parameter is DeviceNum).