Page 3 of 5

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Wed Feb 21, 2018 9:46 am
by jay (support)
Check the Restarting a Plugin example in the docs.

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Wed Feb 21, 2018 10:29 am
by matt (support)
It sounds like the problem isn't how to restart the plugin, but how to know when to restart (trigger) it? Unfortunately, based on what I'm seeing in the Event Log I think that would require modifying the plugin itself to somehow perform an action (or change an Indigo variable value that you can trigger off of).

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Wed Feb 21, 2018 1:04 pm
by chobo
Jay and Matt, That's exactly the issue -- knowing when to trigger a restart. The restart part is easy. Here's to hoping that Nick will add functionality like what Matt describes in a future release (it sure would be useful for situations like this!). Thanks for the assist!
matt (support) wrote:
It sounds like the problem isn't how to restart the plugin, but how to know when to restart (trigger) it?

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Wed Feb 21, 2018 2:10 pm
by siclark
And now I have finally got home to my unresponsive system and finally managed to remote connect to it as barely responding, and find out that the Sonos plugin is using 6.5Gb of Memory.

Nick, hoping you have some time to help with the issues. For now think I am going to set it to reload every 4 hours, I have too much use cases that I rely on this for.

Sonos Plugin 1.09 Update

PostPosted: Thu Feb 22, 2018 3:24 pm
by mvignola29
In trying to access the Sonos update site I get the message below, Do not know how to turn the Wiki services


Wiki service is turned off.
An administrator can turn it on using the Server application.

Any help is appreciated

Michael

Re: Sonos Plugin 1.09 Update

PostPosted: Thu Feb 22, 2018 7:38 pm
by DaveL17
mvignola29 wrote:
In trying to access the Sonos update site I get the message below, Do not know how to turn the Wiki services


Wiki service is turned off.
An administrator can turn it on using the Server application.

Any help is appreciated

Michael

If I recall, that's Nick's own site and he'd be the one to have to fix it.

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Sat Feb 24, 2018 6:13 am
by Seeker
i just noticed that 1.09 is giving me this also:

Sonos Error [Sat Feb 24 06:08:28 2018] Error getting SiriusXM Channel Lineup


i've re-entered the Sonos device to listen to, restarted the plugin, still get the error. non-sirius stations and controls seem to work.

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Wed Feb 28, 2018 5:13 pm
by nlagaros
Popping in for a second... the Sirius issue is due to Sonos changes with newer firmware. They are making it harder! The open api they keep talking about is for music providers not those that want to hook in for full control. I will be updating in the next week or two with a low level library update to help with the errors several are seeing.

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Wed Feb 28, 2018 5:15 pm
by chobo
Sounds wonderful, Nick. Thanks so much for sharing an update.

As someone experiencing the errors, I’m more than happy to test when you get to that point!

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Thu Mar 08, 2018 9:03 pm
by Christian777
Hello! I'm new with indigo and I'm having some trouble. I just downloaded Sonos plugin, but I can't set it up! the "configure" button is disable and the automatic window didn't pop up when I first installed then plugin. What could be the problem?

Thank you!

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Thu Mar 08, 2018 9:41 pm
by matt (support)
Check the Event Log for any Sonos Plugin related messages. Copy/paste them into a follow-up post so we can see what errors (if any) are occurring.

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Fri Mar 09, 2018 10:41 am
by jay (support)
Christian777 wrote:
Hello! I'm new with indigo and I'm having some trouble. I just downloaded Sonos plugin, but I can't set it up! the "configure" button is disable and the automatic window didn't pop up when I first installed then plugin. What could be the problem?


The download link in the plugin store wasn't correct. It's fixed now.

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Fri Mar 09, 2018 10:51 am
by mvignola29
Still not working get the following errors

Mar 9, 2018 at 11:49:38 AM
Connected to PowerLinc 2413U interface on port usbserial-A501LCMB
PowerLinc address 1E.4E.F6, firmware version 9.11
Enabling plugin "Sonos 1.0.9"
Starting plugin "Sonos 1.0.9" (pid 43083)
Sonos Error Error in plugin execution InitializeMain:

Traceback (most recent call last):
File "plugin.py", line 9, in <module>
File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/Sonos.indigoPlugin/Contents/Server Plugin/Sonos.py", line 31, in <module>
ImportError: No module named twisted.internet

Stopping plugin "Sonos 1.0.9" (pid 43083)
Stopped plugin "Sonos 1.0.9"

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Fri Mar 09, 2018 1:19 pm
by Christian777
jay (support) wrote:
Christian777 wrote:
Hello! I'm new with indigo and I'm having some trouble. I just downloaded Sonos plugin, but I can't set it up! the "configure" button is disable and the automatic window didn't pop up when I first installed then plugin. What could be the problem?


The download link in the plugin store wasn't correct. It's fixed now.


Still don't work!
Same error as mvignola29 in the post above!
I actually uninstalled completely the plugin by removing the file from: /Library/Application Support/Perceptive Automation/Indigo 7/Plugins. and installed it again but no success.

Re: Error after Sonos Plugin 1.09 Update

PostPosted: Fri Mar 09, 2018 4:39 pm
by jay (support)
I don't know exactly where Nick (the developer) is. Go to his website and download the the plugin from there. You will probably have to manually uninstall the current one before double-clicking on the one you get from there. I have no idea if it'll work (and I can't test), but if it does let me know and I'll fix it in the plugin store.