Problems with latest update

Posted on
Sun Dec 28, 2014 4:13 pm
Sleepy81 offline
Posts: 47
Joined: Sep 25, 2014

Re: Problems with latest update

I just updated from 0.7.1 to 0.8.7 and had the same problem.

Changed the publish/subscribe port from 9999 to 9998 since I got an error 48 stating port still in use during plugin startup.

Now it starts up without any errors, but I get errors when i attempt to run things from the control page.
For example, when trying to adjust the volume i get this:
Code: Select all
 Sonos Error                     Error in plugin execution ExecuteAction:

Traceback (most recent call last):
  File "plugin.py", line 123, in actionVolumeUp
  File "/Library/Application Support/Perceptive Automation/Indigo 6/Plugins/Sonos-2.indigoPlugin/Contents/Server Plugin/Sonos.py", line 676, in actionDirect
<type 'exceptions.ValueError'>: invalid literal for int() with base 10: ''


Also, album art won´t update, no song info is displayed, toggle play partly works (I can play but hitting it again to pause does nothing), shuffle/repeat status is not updated etc. etc.

So it seams like I don´t get any information BACK from my Sonos, but I can communicate TO it.

Any ideas?

Posted on
Sun Dec 28, 2014 7:10 pm
Sleepy81 offline
Posts: 47
Joined: Sep 25, 2014

Re: Problems with latest update

A restart of the Mac fixed it. Guess there where some remnants from the 0.7.1 version in memory still or something. After the restart everything worked fine, even port 9999 which it previously claimed was in use.


Sent from my iPhone using Tapatalk

Posted on
Tue Dec 30, 2014 8:19 am
nlagaros offline
Posts: 1646
Joined: Dec 20, 2010

Re: Problems with latest update

I believe the port lock would have eventually timed out - say i you disabled the plugin for a few minutes, but glad it is working.

Posted on
Tue Dec 30, 2014 9:08 am
richo offline
Posts: 158
Joined: Nov 25, 2014
Location: Pomorskie, Poland

Re: Problems with latest update

In my case it works on MacbookPro but still doesn't work on my iMac - a bit confused ...


Sent using Tapatalk

Ryszard

Posted on
Sat Apr 18, 2015 2:09 pm
DU Lou offline
Posts: 279
Joined: Mar 08, 2012
Location: Florida

Re: Problems with latest update

UPDATE:
Al_M provided the answer in a PM.

Thanks,
~Lou


nlagaros wrote:
OK folks, I gave up on pure automation. There is now an option in the main plugin configuration to enter the IP address of the Indigo server. Remember to re-save the plugin configuration immediately after installation.

Thanks.


I just upgraded from 8.9 to 8.13 and now receive
Code: Select all
Cannot start HTTP Streamer on None: [Errno 8] nodename nor servname provided, or not known
How do I determine what Indigo's server IP is?

Thanks!
~Lou
Last edited by DU Lou on Sat Apr 18, 2015 3:57 pm, edited 1 time in total.

Posted on
Sat Apr 18, 2015 2:20 pm
Al_M offline
Posts: 19
Joined: Nov 17, 2014

Re: Problems with latest update

Hmm. I'm getting the ZonePlayer get muted after a group announcement. It also does not return to the previous source. I have to unmute in Sonos controller and raise volume back to previous level. This use to work flawlessly... :cry:

Posted on
Sat Apr 18, 2015 4:23 pm
nlagaros offline
Posts: 1646
Joined: Dec 20, 2010

Re: Problems with latest update

Two ways:

1. In a terminal window, type "ifconfig -a". If you are hardwired, look at the en0 interface and you should see the ip address.
2. Open up System Preferences. Click on the interface that is active, then the advanced button, and the TCP/IP tab. You will see the address in that window.

DU Lou wrote:
UPDATE:
Al_M provided the answer in a PM.

Thanks,
~Lou


nlagaros wrote:
OK folks, I gave up on pure automation. There is now an option in the main plugin configuration to enter the IP address of the Indigo server. Remember to re-save the plugin configuration immediately after installation.

Thanks.


I just upgraded from 8.9 to 8.13 and now receive
Code: Select all
Cannot start HTTP Streamer on None: [Errno 8] nodename nor servname provided, or not known
How do I determine what Indigo's server IP is?

Thanks!
~Lou

Posted on
Sat Apr 18, 2015 4:24 pm
nlagaros offline
Posts: 1646
Joined: Dec 20, 2010

Re: Problems with latest update

I'm not sure why it is not working now. If you can give me a little more info, I hope I can help. What version of the plugin are you running? I've seen this happen if the plugin is not receiving state updates from the ZonePlayers. Can you restart the plugin in debug mode and post all the output here? Also, please post the log output when running your group announcement action.

Thanks.

Al_M wrote:
Hmm. I'm getting the ZonePlayer get muted after a group announcement. It also does not return to the previous source. I have to unmute in Sonos controller and raise volume back to previous level. This use to work flawlessly... :cry:

Posted on
Sat Apr 18, 2015 5:30 pm
DU Lou offline
Posts: 279
Joined: Mar 08, 2012
Location: Florida

Re: Problems with latest update

nlagaros wrote:
Two ways:

1. In a terminal window, type "ifconfig -a". If you are hardwired, look at the en0 interface and you should see the ip address.
2. Open up System Preferences. Click on the interface that is active, then the advanced button, and the TCP/IP tab. You will see the address in that window.

DU Lou wrote:
UPDATE:
Al_M provided the answer in a PM.

Thanks,
~Lou


nlagaros wrote:
OK folks, I gave up on pure automation. There is now an option in the main plugin configuration to enter the IP address of the Indigo server. Remember to re-save the plugin configuration immediately after installation.

Thanks.


I just upgraded from 8.9 to 8.13 and now receive
Code: Select all
Cannot start HTTP Streamer on None: [Errno 8] nodename nor servname provided, or not known
How do I determine what Indigo's server IP is?

Thanks!
~Lou


Thanks Nathan. Back in business!

~Lou


Sent from my iPhone using Tapatalk

Posted on
Mon Apr 20, 2015 9:29 am
Al_M offline
Posts: 19
Joined: Nov 17, 2014

Re: Problems with latest update

nlagaros wrote:
I'm not sure why it is not working now. If you can give me a little more info, I hope I can help. What version of the plugin are you running? I've seen this happen if the plugin is not receiving state updates from the ZonePlayers. Can you restart the plugin in debug mode and post all the output here? Also, please post the log output when running your group announcement action.

Thanks.

Al_M wrote:
Hmm. I'm getting the ZonePlayer get muted after a group announcement. It also does not return to the previous source. I have to unmute in Sonos controller and raise volume back to previous level. This use to work flawlessly... :cry:


OK, I am having issues pasting the text into this reply. I keep getting a "too few characters" error. I think it may actually be too long.
So I have attached a text file with the log outputs.

Plugin version is 0.8.13.

Here is what I get after triggering the group announcement:

2015-04-20 09:11:44.737 Trigger Motion Detected - 2nd Floor
2015-04-20 09:11:44.743 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: GetMediaInfo
2015-04-20 09:11:44.747 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: GetPositionInfo
2015-04-20 09:11:44.752 Sonos Debug zoneIP: 192.168.1.69, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: GetMediaInfo
2015-04-20 09:11:44.757 Sonos Debug zoneIP: 192.168.1.69, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: GetPositionInfo
2015-04-20 09:11:44.763 Sonos Debug zoneIP: 192.168.1.65, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: GetMediaInfo
2015-04-20 09:11:44.768 Sonos Debug zoneIP: 192.168.1.65, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: GetPositionInfo
2015-04-20 09:11:44.945 Z-Wave sent "011 - 2nd Floor Stairwell" set brightness to 25
2015-04-20 09:11:45.240 Z-Wave sent "011 - 2nd Floor Stairwell" on
2015-04-20 09:11:45.574 Sonos Announcement: Be careful going down the stairs! Hold on to the railing., Volume: 40
2015-04-20 09:11:45.576 Sonos Debug Announcement: mute
2015-04-20 09:11:45.576 Sonos Debug Announcement: set standalone, stop, turn off queue repeat
2015-04-20 09:11:45.580 Sonos remove zone from group: SONOS: Kitchen
2015-04-20 09:11:45.580 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: SetAVTransportURI
2015-04-20 09:11:45.640 Sonos Debug Announcement: add announcement zones to group
2015-04-20 09:11:45.642 Sonos Debug Announcement: set volume, unmute
2015-04-20 09:11:45.645 Sonos Debug Current Volume: , New Volume: 40
2015-04-20 09:11:45.646 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /RenderingControl, soapAction: SetVolume
2015-04-20 09:11:45.651 Sonos Announcement Length: 3.672
2015-04-20 09:11:45.651 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: SetAVTransportURI
2015-04-20 09:11:45.745 Sonos Debug Sonos Action: PlayMode NORMAL
2015-04-20 09:11:45.745 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: SetPlayMode
2015-04-20 09:11:45.854 Sonos Debug Sonos Action: Play
2015-04-20 09:11:45.854 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: Play
2015-04-20 09:11:49.642 Sonos remove zone from group: SONOS: Kitchen
2015-04-20 09:11:49.643 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: SetAVTransportURI
2015-04-20 09:11:49.775 Sonos Debug Restore States: RINCON_000E58DAA12601400:RINCON_000E58DAA12601400:SONOS: Kitchen
2015-04-20 09:11:49.776 Sonos Debug 01:Q_Crossfade: False
2015-04-20 09:11:49.776 Sonos Debug 02:Q_Repeat: False
2015-04-20 09:11:49.776 Sonos Debug 03:Q_Shuffle: False
2015-04-20 09:11:49.776 Sonos Debug 04:ZP_MUTE:
2015-04-20 09:11:49.776 Sonos Debug 05:ZP_STATE:
2015-04-20 09:11:49.776 Sonos Debug 06:ZP_VOLUME:
2015-04-20 09:11:49.777 Sonos Debug 07:ZP_CurrentURI:
2015-04-20 09:11:49.777 Sonos Debug 08:CurrentURI MetaData:
2015-04-20 09:11:49.777 Sonos Debug 09:ZP_CurrentTrack:
2015-04-20 09:11:49.777 Sonos Debug 10:GROUP_Coordinator:
2015-04-20 09:11:49.777 Sonos Debug 12:Relative Time: 0:00:00
2015-04-20 09:11:49.778 Sonos Debug 13:ZonePlayerUUIDsInGroup: RINCON_000E58DAA12601400
2015-04-20 09:11:49.778 Sonos Debug RINCON_000E58DAA12601400: Restore Mute:
2015-04-20 09:11:49.778 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /RenderingControl, soapAction: SetMute
2015-04-20 09:11:49.779 Sonos Debug RINCON_000E58DAA12601400: Restore Volume:
2015-04-20 09:11:49.780 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /RenderingControl, soapAction: SetVolume
2015-04-20 09:11:49.784 Sonos Debug RINCON_000E58DAA12601400: Restore URI:
2015-04-20 09:11:49.785 Sonos Debug zoneIP: 192.168.1.64, soapRoot: /MediaRenderer, soapBranch: /AVTransport, soapAction: SetAVTransportURI
2015-04-20 09:13:14.318 Schedule Motion Detected - 2nd Floor (delayed action)
2015-04-20 09:13:14.546 Z-Wave sent "011 - 2nd Floor Stairwell" off
Attachments
2015-04-20 Events.txt
(99.6 KiB) Downloaded 159 times

Posted on
Mon Apr 20, 2015 9:40 am
nlagaros offline
Posts: 1646
Joined: Dec 20, 2010

Re: Problems with latest update

Thanks for the text dump. I think I found the problem. It has to do with DNS / name resolution. Here are the relevant lines from the log:

Code: Select all
2015-04-20 09:09:27.342   Sonos Debug   SonosEvents: WARN  coherence                   Apr 20 09:09:25  Coherence UPnP framework version 0.6.6.2 starting... (coherence/base.py:283)
2015-04-20 09:09:27.343   Sonos Debug   SonosEvents: WARN  coherence                   Apr 20 09:09:25  hostname can't be resolved, maybe a system misconfiguration? (coherence/base.py:291)
2015-04-20 09:09:27.343   Sonos Debug   SonosEvents: WARN  coherence                   Apr 20 09:09:25  detection of own ip failed, using 127.0.0.1 as own address, functionality will be limited (coherence/base.py:308)


Can you check your hostname and DNS settings.

Posted on
Tue Apr 21, 2015 2:13 pm
Al_M offline
Posts: 19
Joined: Nov 17, 2014

Re: Problems with latest update

nlagaros wrote:
Thanks for the text dump. I think I found the problem. It has to do with DNS / name resolution. Here are the relevant lines from the log:

Code: Select all
2015-04-20 09:09:27.342   Sonos Debug   SonosEvents: WARN  coherence                   Apr 20 09:09:25  Coherence UPnP framework version 0.6.6.2 starting... (coherence/base.py:283)
2015-04-20 09:09:27.343   Sonos Debug   SonosEvents: WARN  coherence                   Apr 20 09:09:25  hostname can't be resolved, maybe a system misconfiguration? (coherence/base.py:291)
2015-04-20 09:09:27.343   Sonos Debug   SonosEvents: WARN  coherence                   Apr 20 09:09:25  detection of own ip failed, using 127.0.0.1 as own address, functionality will be limited (coherence/base.py:308)


Can you check your hostname and DNS settings.


Nick,

I'm sorry, but this is a little above my knowledge level. I know how and where to find the hostname and DNS settings, but what specifically am I looking for? How do I properly set them?

This has happened a couple of times now. Once I inadvertently powered down my router/modem and the SONOS components got new IP addresses. I changed them in the plugin config and all was good. The last time this happened, I had a power outage. Same thing happened, but this time I could not get it to work. I went into the SONOS controller software on my Mac mini and found the component IP addresse under Sonos -> About My Sonos System and then re-configured the plugin with the new addresses. This time I also added my Mac mini's IP address as well in the plugin's HTTP streaming IP box.

I don't know how to keep the Mac mini and the SONOS components from changing after a router reboot...? Maybe someone could help me out with this?

Posted on
Tue Apr 21, 2015 2:47 pm
nlagaros offline
Posts: 1646
Joined: Dec 20, 2010

Re: Problems with latest update

I guess we can start with your Mac. What version of OS X are you running? Do you have OS X Server running on it? Does it get a dynamic IP address from your router or is manually assigned.

As far as y our Sonos devices go, you should be able to input the hardware addresses into the router for each one and give them a static address. I can help if you want to share the make and model of the router. I'll go through the documentation and help take your through it. This way, the ZonePlayers will always receive the same address if anything restarts.

Posted on
Tue Apr 21, 2015 8:34 pm
Al_M offline
Posts: 19
Joined: Nov 17, 2014

Re: Problems with latest update

nlagaros wrote:
I guess we can start with your Mac. What version of OS X are you running? Do you have OS X Server running on it? Does it get a dynamic IP address from your router or is manually assigned.

As far as y our Sonos devices go, you should be able to input the hardware addresses into the router for each one and give them a static address. I can help if you want to share the make and model of the router. I'll go through the documentation and help take your through it. This way, the ZonePlayers will always receive the same address if anything restarts.


Mac mini running OS X 10.10.3. I am not running OS X Server. Should I be? Dynamic IP address from the router.

My router is an Apple Airport Time Capsule. Hardwired (Cat6) between Mac mini and router.

Let me know if there is any more info you need.

And thanks for walking me through it.

Posted on
Wed Apr 22, 2015 2:35 am
nlagaros offline
Posts: 1646
Joined: Dec 20, 2010

Re: Problems with latest update

If you bring up the Apple Time Machine properties in AirPort Utility, we can check some settings and set addresses dynamically.

Click on the Network tab.
  • You should have a DHCP Range set here.
  • If you see the box for DHCP Reservations, this is where you can type in the hardware address of each Sonos ZonePlayer and give it a static address. You can do the same for your Mac Mini. Click the + button, type in the description (hostname), MAC Address , and IP address you want to give each device. Click the Save button after each entry.
  • Click the Update button at the bottom of the dialog to save all your work. It will probably restart the router.

You can get the MAC addresses of the Sonos devices looking at "About My Sonos System". It is the Serial Number entry. Leave off the last digit/character.
On your MAC, click on Network in System Preferences. For the Ethernet interface, click on the Advanced button, then the Hardware tab. The MAC address should be the first item up on the screen.

On your Mac, open System Preferences and click on the Sharing icon. The Computer Name (hostname)should be entered here. It should say below that the computers on your local network can access your computer at hostname.local, where hostname is the name you have in the entry box.

Who is online

Users browsing this forum: No registered users and 18 guests