Announcement

**pciccone** · January 10, 2017, 07:00 PM

Thread was too long, here is the rest of the log from the top:

I have also attached a screen shot of what the Sonos app shows, after the TTS hangs on starting the station that was playing.

Code:

Jan-10 6:56:20 PM	 	HSTouch Server	Opening connection from:69.162.124.228/44081
Jan-10 6:56:15 PM	 	Sonos	DeletePreviousSavedQueues found 0 playlists for ZonePlayer - Pool House
Jan-10 6:56:15 PM	 	Sonos	DeletePreviousSavedQueues called for ZonePlayer = Pool House with QueueName = SCQueue-Pool House-TTS
Jan-10 6:56:11 PM	 	Sonos	DeletePreviousSavedQueues found 0 playlists for ZonePlayer - LR / Kitchen
Jan-10 6:56:11 PM	 	Sonos	DeletePreviousSavedQueues called for ZonePlayer = LR / Kitchen with QueueName = SCQueue-LR / Kitchen-TTS
Jan-10 6:56:08 PM	 	Sonos	DeletePreviousSavedQueues found 0 playlists for ZonePlayer - Sports Bar
Jan-10 6:56:08 PM	 	Sonos	DeletePreviousSavedQueues called for ZonePlayer = Sports Bar with QueueName = SCQueue-Sports Bar-TTS
Jan-10 6:56:08 PM	 	Sonos	DoCheckAnnouncementQueue is ending and all announcements were processed
Jan-10 6:56:08 PM	 	Sonos	DeleteHeadOfAnnouncementQueue called
Jan-10 6:56:08 PM	 	Sonos	DoCheckAnnouncementQueue is done unlinking
Jan-10 6:56:08 PM	 	Sonos	HandleLinkingOff done with LinkgroupName = TTS and # players = 5
Jan-10 6:56:06 PM	 	Sonos	DeletePreviousSavedQueues found 0 playlists for ZonePlayer - Master Bathroom
Jan-10 6:56:06 PM	 	Sonos	DeletePreviousSavedQueues called for ZonePlayer = Master Bathroom with QueueName = SCQueue-Master Bathroom-TTS
Jan-10 6:56:04 PM	 	Sonos	DeletePreviousSavedQueues found 0 playlists for ZonePlayer - Pool
Jan-10 6:56:04 PM	 	Sonos	DeletePreviousSavedQueues called for ZonePlayer = Pool with QueueName = SCQueue-Pool-TTS
Jan-10 6:56:03 PM	 	Sonos	SavedPlayerList.GetLastIndex called and MyLinkListIndex = 0
Jan-10 6:56:03 PM	 	Sonos	RestoreCurrentTrackInfo is done for zonePlayer Sports Bar
Jan-10 6:56:03 PM	 	Sonos	RestoreCurrentTrackInfo updated HS DeviceValue for zonePlayer Sports Bar. HSRef = 1102 and value = Stopped
Jan-10 6:56:03 PM	 	Sonos	DeviceTrigger called for Zone - Sports Bar with Trigger = Sonos Player Stop
Jan-10 6:56:03 PM	 	Sonos	PlayChangeNotifyCallback called for Zone - Sports Bar with ChangeType = PlayStatusChanged and Changevalue = Stopped and SendDeviceTrigger = True
Jan-10 6:56:03 PM	 	Sonos	SetTransportState called for zoneplayer - Sports Bar with value = STOPPED
Jan-10 6:56:03 PM	 	Sonos	SetPlayMode called for ZoneName Sports Bar with value = NORMAL
Jan-10 6:56:03 PM	 	Sonos	SetMute called for zoneplayer = Sports Bar with Channel = Master and NewState = False and DeviceStatus =Online
Jan-10 6:56:03 PM	 	Sonos	SetVolumeLevel called for ZonePlayer = Sports Bar with values Channel=Master Value=25
Jan-10 6:56:02 PM	 	Sonos	PlayURI called for zoneplayer Sports Bar with strURI = http://10.1.1.100:80/Sonos/Announcements/Ann_TTS_0.wav and MetaData = http://10.1.1.100:80/Sonos/Announcements/Ann_TTS_0.wavhttp://10.1.1.100:80/images/Sonos/Announcement.jpgHomeSeer Announcementobject.item.audioItem.musicTrackDirk CorsusSonosControllerDirk Corsus and isObjectID = False
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo for Zonename = Sports Bar and MySavedTrackinfo = http://10.1.1.100:80/Sonos/Announcements/Ann_TTS_0.wav
Jan-10 6:56:02 PM	 	Sonos	SavedPlayerList.GetLastIndex called and returned UDN = RINCON_B8E9379C473201400
Jan-10 6:56:02 PM	 	Sonos	SavedPlayerList.GetLastIndex called and MyLinkListIndex = 1
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo is done for zonePlayer Pool
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo updated HS DeviceValue for zonePlayer Pool. HSRef = 1100 and value = Stopped
Jan-10 6:56:02 PM	 	Sonos	DeviceTrigger called for Zone - Pool with Trigger = Sonos Player Stop
Jan-10 6:56:02 PM	 	Sonos	PlayChangeNotifyCallback called for Zone - Pool with ChangeType = PlayStatusChanged and Changevalue = Stopped and SendDeviceTrigger = True
Jan-10 6:56:02 PM	 	Sonos	SetTransportState called for zoneplayer - Pool with value = PLAYING
Jan-10 6:56:02 PM	 	Sonos	SetPlayMode called for ZoneName Pool with value = NORMAL
Jan-10 6:56:02 PM	 	Sonos	SetMute called for zoneplayer = Pool with Channel = Master and NewState = False and DeviceStatus =Online
Jan-10 6:56:02 PM	 	Sonos	SetVolumeLevel called for ZonePlayer = Pool with values Channel=Master Value=20
Jan-10 6:56:02 PM	 	Sonos	PlayURI called for zoneplayer Pool with strURI = x-rincon:RINCON_B8E9379C473201400 and MetaData = and isObjectID = False
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo for Zonename = Pool and MySavedTrackinfo = x-rincon:RINCON_B8E9379C473201400
Jan-10 6:56:02 PM	 	Sonos	SavedPlayerList.GetLastIndex called and returned UDN = RINCON_B8E9379C43AE01400
Jan-10 6:56:02 PM	 	Sonos	SavedPlayerList.GetLastIndex called and MyLinkListIndex = 2
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo is done for zonePlayer Master Bathroom
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo updated HS DeviceValue for zonePlayer Master Bathroom. HSRef = 1101 and value = Stopped
Jan-10 6:56:02 PM	 	Sonos	DeviceTrigger called for Zone - Master Bathroom with Trigger = Sonos Player Stop
Jan-10 6:56:02 PM	 	Sonos	PlayChangeNotifyCallback called for Zone - Master Bathroom with ChangeType = PlayStatusChanged and Changevalue = Stopped and SendDeviceTrigger = True
Jan-10 6:56:02 PM	 	Sonos	SetTransportState called for zoneplayer - Master Bathroom with value = PLAYING
Jan-10 6:56:02 PM	 	Sonos	SetPlayMode called for ZoneName Master Bathroom with value = NORMAL
Jan-10 6:56:02 PM	 	Sonos	SetMute called for zoneplayer = Master Bathroom with Channel = Master and NewState = False and DeviceStatus =Online
Jan-10 6:56:02 PM	 	Sonos	SetVolumeLevel called for ZonePlayer = Master Bathroom with values Channel=Master Value=10
Jan-10 6:56:02 PM	 	Sonos	PlayURI called for zoneplayer Master Bathroom with strURI = x-rincon:RINCON_B8E9379C473201400 and MetaData = and isObjectID = False
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo for Zonename = Master Bathroom and MySavedTrackinfo = x-rincon:RINCON_B8E9379C473201400
Jan-10 6:56:02 PM	 	Sonos	SavedPlayerList.GetLastIndex called and returned UDN = RINCON_5CAAFD95FF1801400
Jan-10 6:56:02 PM	 	Sonos	SavedPlayerList.GetLastIndex called and MyLinkListIndex = 3
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo is done for zonePlayer LR / Kitchen
Jan-10 6:56:02 PM	 	Sonos	RestoreCurrentTrackInfo updated HS DeviceValue for zonePlayer LR / Kitchen. HSRef = 1103 and value = Stopped
Jan-10 6:56:02 PM	 	Sonos	DeviceTrigger called for Zone - LR / Kitchen with Trigger = Sonos Player Stop
Jan-10 6:56:02 PM	 	Sonos	PlayChangeNotifyCallback called for Zone - LR / Kitchen with ChangeType = PlayStatusChanged and Changevalue = Stopped and SendDeviceTrigger = True
Jan-10 6:56:02 PM	 	Sonos	SetTransportState called for zoneplayer - LR / Kitchen with value = PLAYING
Jan-10 6:56:02 PM	 	Sonos	SetPlayMode called for ZoneName LR / Kitchen with value = NORMAL
Jan-10 6:56:02 PM	 	Sonos	SetMute called for zoneplayer = LR / Kitchen with Channel = Master and NewState = False and DeviceStatus =Online
Jan-10 6:56:02 PM	 	Sonos	SetVolumeLevel called for ZonePlayer = LR / Kitchen with values Channel=Master Value=15
Jan-10 6:56:01 PM	 	Sonos	PlayURI called for zoneplayer LR / Kitchen with strURI = x-rincon:RINCON_B8E9379C473201400 and MetaData = and isObjectID = False
Jan-10 6:56:01 PM	 	Sonos	RestoreCurrentTrackInfo for Zonename = LR / Kitchen and MySavedTrackinfo = x-rincon:RINCON_B8E9379C473201400
Jan-10 6:56:01 PM	 	Sonos	SavedPlayerList.GetLastIndex called and returned UDN = RINCON_B8E937A88B2A01400
Jan-10 6:56:01 PM	 	Sonos	SavedPlayerList.GetLastIndex called and MyLinkListIndex = 4
Jan-10 6:56:01 PM	 	Sonos	RestoreCurrentTrackInfo is done for zonePlayer Pool House
Jan-10 6:56:01 PM	 	Sonos	RestoreCurrentTrackInfo updated HS DeviceValue for zonePlayer Pool House. HSRef = 1104 and value = Stopped
Jan-10 6:56:01 PM	 	Sonos	DeviceTrigger called for Zone - Pool House with Trigger = Sonos Player Stop
Jan-10 6:56:01 PM	 	Sonos	PlayChangeNotifyCallback called for Zone - Pool House with ChangeType = PlayStatusChanged and Changevalue = Stopped and SendDeviceTrigger = True
Jan-10 6:56:01 PM	 	Sonos	SetTransportState called for zoneplayer - Pool House with value = PLAYING
Jan-10 6:56:01 PM	 	Sonos	SetPlayMode called for ZoneName Pool House with value = NORMAL

Attached Files

**dcorsus** · January 10, 2017, 07:20 PM

Originally posted by pciccone View Post

This has been an issue for me for a long time now, but only getting to posting it now.

After a few DAYS of running 100% correctly the music that is currently playing via Sonos will not resume / continue after a TTS annoucement. The TTS annoucement plays OK, and volume is returned to the correct levels but the radio station playing is never resumed.

Now, here is the good part...

If I remove all saved players from the Sonos config page, then restart the plug-in we will get another few days of all working correctly until I have to do it again.

Right now, I have it "broken". I will not reset it yet, in case I need to do some testing.

Ideas?

Below is a super debug output of the time when Sonos was playing a station, to a TTS announcing to when it gets stuck and never restarts the playing station. Volume, and linking is returned OK. It just never restarts the station.

Let's start with the basics. Which version of the PI are you running? Which OS? What kind of PC, especially how much memory? What kind of firewall on that PC? Are you using VMs? How many players (please post screenshot of player table) and what kind? How are the wired to your network (wire, wireless ...). Is it always the same player that gives you grief or is it random ....

Dirk

**dcorsus** · January 10, 2017, 07:36 PM

On top of the questions above, can you post a screen shot of your linkgroup table and ALL events that you created that lead to announcements.

The log actually shows all players linked and, most likely as part of a prior failed announcement. None of the participating players is playing any radiostation before the announcement kicked in, so either the log is wrong or your test is contaminated.

I suspect you just need to grab your SONOS controller, unlink all the players, have some play a radio station and try it. The log is not indicating any reason why that would not work. You could keep logging on when you try the above, just in case it doesn't work, I'd be interested to see that log.

My first suspicion would be "overlapping" linkgroups/announcement events, where one announcement starts (specific linkgroup) and while that announcement is ongoing, another announcement kicks in for a DIFFERENT linkgroup but containing all or some of the same players. The second announcement now takes a snapshot of a bunch of players linked and playing some announcement and after that second announcement is done, will restore state to a snapshot that was not what you wanted.

Anyway, your screenshots might confirm or deny my theory.

Dirk

**pciccone** · January 10, 2017, 10:23 PM

OK, let me answer each of these questions:

Which version of the PI are you running?
** 3.1.0.18

Which OS?
** Windows 2016 Server

What kind of PC, especially how much memory?
DELL PowerEdge Enterprise Server, 128GB of memory.
What kind of firewall on that PC?
** None / disabled. Firewall at hardware level, only at WAN egress. LAN traffic unfiltered.

Are you using VMs?
** Yes, but HS3 is running native. Admin rights, task scheduler, highest privileges. VMs have nothing to do with HS3.

How many players (please post screenshot of player table) and what kind?
** I'll post a screen shot.

How are the wired to your network (wire, wireless ...).
** Some wired, some wireless. Depends on the player.

Is it always the same player that gives you grief or is it random ....
** They are all link-grouped together, and all are in the same (and only) TTS group.

None of the participating players is playing any radiostation before the announcement kicked in, so either the log is wrong or your test is contaminated.
** Actually, they were playing (I setup a test to send the log to you). The interesting thing is, that I am now seeing, is Sonos devices are not showing what is playing, player state, etc. It seems when I get into this "broken state" that the devices are no longer updating status either. This is the reason the logs look like nothing was playing. So the issue may not really be TTS, maybe the issue is the Sonos module is no longer getting information from what is playing. So the snapshot is faulty, and thus restored faulty? I can send Sonos commands from HS3 with no problem (like playback, volume, etc), but the status of the devices does not update back when the commands are sent. (None of the players). I know if I delete the players, and restart the plugin it will temporarily fix this issue. So this is not a permanent problem, something happens during the course of a couple days that starts this. And, it's always a couple of days. Never minutes, never weeks. Almost like clockwork.

I suspect you just need to grab your SONOS controller, unlink all the players, have some play a radio station and try it. The log is not indicating any reason why that would not work.
** I just unlinked, and re-linked them for the hell of it. No new results to report.

My first suspicion would be "overlapping" linkgroups/announcement events, where one announcement starts (specific linkgroup) and while that announcement is ongoing, another announcement kicks in for a DIFFERENT linkgroup but containing all or some of the same players.
** We only have one linkgroup called "TTS". There is a chance that we can be speaking to the same TTS group from two different events, but as far as I know they queue in that case.

Attached Files

**pciccone** · January 10, 2017, 10:26 PM

I notice during this state player status is a "?" and the uPnP viewer is null

Attached Files

**dcorsus** · January 10, 2017, 10:59 PM

Originally posted by pciccone View Post

OK, let me answer each of these questions:

Which version of the PI are you running?
** 3.1.0.18

Which OS?
** Windows 2016 Server

What kind of PC, especially how much memory?
DELL PowerEdge Enterprise Server, 128GB of memory.
What kind of firewall on that PC?
** None / disabled. Firewall at hardware level, only at WAN egress. LAN traffic unfiltered.

Are you using VMs?
** Yes, but HS3 is running native. Admin rights, task scheduler, highest privileges. VMs have nothing to do with HS3.

How many players (please post screenshot of player table) and what kind?
** I'll post a screen shot.

How are the wired to your network (wire, wireless ...).
** Some wired, some wireless. Depends on the player.

Is it always the same player that gives you grief or is it random ....
** They are all link-grouped together, and all are in the same (and only) TTS group.

None of the participating players is playing any radiostation before the announcement kicked in, so either the log is wrong or your test is contaminated.
** Actually, they were playing (I setup a test to send the log to you). The interesting thing is, that I am now seeing, is Sonos devices are not showing what is playing, player state, etc. It seems when I get into this "broken state" that the devices are no longer updating status either. This is the reason the logs look like nothing was playing. So the issue may not really be TTS, maybe the issue is the Sonos module is no longer getting information from what is playing. So the snapshot is faulty, and thus restored faulty? I can send Sonos commands from HS3 with no problem (like playback, volume, etc), but the status of the devices does not update back when the commands are sent. (None of the players). I know if I delete the players, and restart the plugin it will temporarily fix this issue. So this is not a permanent problem, something happens during the course of a couple days that starts this. And, it's always a couple of days. Never minutes, never weeks. Almost like clockwork.

I suspect you just need to grab your SONOS controller, unlink all the players, have some play a radio station and try it. The log is not indicating any reason why that would not work.
** I just unlinked, and re-linked them for the hell of it. No new results to report.

My first suspicion would be "overlapping" linkgroups/announcement events, where one announcement starts (specific linkgroup) and while that announcement is ongoing, another announcement kicks in for a DIFFERENT linkgroup but containing all or some of the same players.
** We only have one linkgroup called "TTS". There is a chance that we can be speaking to the same TTS group from two different events, but as far as I know they queue in that case.

Hmm, something else is going wrong here. I think you wrote you deleted all the players to get it working again, how did you delete the players? Did you delete them from the HS device page or did you delete the sonos.ini file or used the delete all devices button?
The fact that no player what so ever shows up under the UPNP viewer is disturbing .... If you restart HS (and PI), does it stay that way? If so, that would mean that multicasting is not working, which typically I see issues with with a firewall, but you wrote you don't have any. Does the PC have multiple physical Ethernet ports? I have to admit, I'm all but an expert on servers and VMs, is my assumption correct that when you write "native" it means that you don't share any Ethernet ports or do you still have a virtual bridge and stuff like that? The PI heavily relies on autonomous responses from players wrt to status, if they don't come through (again typically firewall), in some cases you can still control players (different TCP port) but in absence of autonomous responses, all will go wrong. Given that the Sonos UPNP part is 100% dynamic data, deleting players "should" make no difference and only would do anything if for whatever user error the HS DB and the Sonos PI DB are out of sync. If you use the "delete all players" button however, it will not only delete all players it will restart the PI and that might be why it appear to solve issues in the past. In continuation of these assumptions, we would have to find out why "things fall asleep". One thing you could do is leave the debug flag on, leave the log to disk flag on (note this is a toggle flag that will delete any log if turned from off-to-on), and when it happens again, turn log to disk off, zip log file and email or post.

Whenever it happens again, look at player status in the config page and the UPNP viewer info. If players are shown off-line, we know where to start looking.

Dirk

**pciccone** · January 11, 2017, 09:04 AM

This morning, I restarted HS3 (only) and it resolved the problem per expected. Usually I deleted the players, which, in-turn, forced a plugin restart. So, it seems it's not a matter of deleting the players or removing the INI file, but just restarting the plugin and/or HS3 also fixes it. Now, we are running normally. UPnP shows correctly, players show online, devices are updating, TTS is working, etc.

What I did was schedule the task to restart daily in the early morning. If a refresh daily "fixes it" then it will work for me. If you have others who bring this up, or you really want to get to the bottom of it I can remove the daily restart to let it happen again and we can continue to check it out. I'll update you again after it either starts happening again, or we go a good period of time with the daily restarts and no occurrences of failure.

Thanks Dirk! PS - The plugin is great, if it wen't commercial I would not blink an eye paying for it.

Phil

**dcorsus** · January 11, 2017, 10:56 AM

Originally posted by pciccone View Post

This morning, I restarted HS3 (only) and it resolved the problem per expected. Usually I deleted the players, which, in-turn, forced a plugin restart. So, it seems it's not a matter of deleting the players or removing the INI file, but just restarting the plugin and/or HS3 also fixes it. Now, we are running normally. UPnP shows correctly, players show online, devices are updating, TTS is working, etc.

What I did was schedule the task to restart daily in the early morning. If a refresh daily "fixes it" then it will work for me. If you have others who bring this up, or you really want to get to the bottom of it I can remove the daily restart to let it happen again and we can continue to check it out. I'll update you again after it either starts happening again, or we go a good period of time with the daily restarts and no occurrences of failure.

Thanks Dirk! PS - The plugin is great, if it wen't commercial I would not blink an eye paying for it.

Phil

Hi Phil, restarting HS would also restart the PI. I suspect it is not something that builds gradually, I suspect it may show during the day and mess up your players with announcements that simply don't work. So I would recommend if at all possible, keep the debug flag on, keep log to disk on, set UPNP logging to errors only (if not already set) and leave it that way. If you were to find things not responding or annoucements leaving the player group screwed up, just click on turn disk logging off and grab the log file from the <hs root>\html\sonos\logs directory.

Dirk

**mikee123** · January 11, 2017, 02:43 PM

TV does not start after TTS

I have a very similar problem. I have updated to the latest beta, 3.1.0.18, and since on my Sounbar when watching TV, when I have a TTS, it does not go back to TV sound like it used to automatically. I have added another action to the event, after the TTS (clicked wait for speech to finish) play TV and selected the Kitchen. Tv sound now comes on straight away. But after a few seconds the sound goes off again. Looking at my log, I can see this error:

Sonos Error Error in DoCheckAnnouncementQueue. 100 seconds expired since the announcement started and no end was received.

After this error in the log, it repeats the TTS (whithout showing in the log)

This probably explains as well of why its not automatically switching back. But I dont know how to resolve this issue. Here is my config page and the event:

Attached Files

**dcorsus** · January 11, 2017, 05:08 PM

Originally posted by mikee123 View Post

I have a very similar problem. I have updated to the latest beta, 3.1.0.18, and since on my Sounbar when watching TV, when I have a TTS, it does not go back to TV sound like it used to automatically. I have added another action to the event, after the TTS (clicked wait for speech to finish) play TV and selected the Kitchen. Tv sound now comes on straight away. But after a few seconds the sound goes off again. Looking at my log, I can see this error:

Sonos Error Error in DoCheckAnnouncementQueue. 100 seconds expired since the announcement started and no end was received.

After this error in the log, it repeats the TTS (whithout showing in the log)

This probably explains as well of why its not automatically switching back. But I dont know how to resolve this issue. Here is my config page and the event:

I'm having trouble confirming or refuting your solution

There simply is no way to "know" when the announcement ended because it is all asynchronously driven, so in my mind, the action you appended to set the TV to kitchen IS a problem. I suspect it will on more times than not, mess up the announcement or the restoration of the announcement.

So my recommendation is to remove that action, it won't work reliably. Take a log with debug on (not superdebug) from start of the announcement to end, obviously for a failing case. If you take a disk log it is easy appended to your response and readable to me (AND complete because HS log takes out HTML tags).

If you have changed your linkgroups, post the latest configuration because I need to know who is the master of the linkgroup and who is participating. Double check that KitchenTTS and KitGymTTS never fire off announcements at the same time as it will leave one of them in an undefined end state!

Dirk

**mikee123** · January 12, 2017, 02:53 AM

With disc log you mean from the hard disc rather than from the view - log ?
I have only put in the play TV action as a temporary fix. If I do not do this I do not get my TV sound back, and the TV without sound does not impress the other half...
Joking aside, linkgroups still are the same, and I'll take a log tonight and post it

**dcorsus** · January 12, 2017, 11:19 AM

Originally posted by mikee123 View Post

With disc log you mean from the hard disc rather than from the view - log ?
I have only put in the play TV action as a temporary fix. If I do not do this I do not get my TV sound back, and the TV without sound does not impress the other half...
Joking aside, linkgroups still are the same, and I'll take a log tonight and post it

If you go to the sonos pi config page, you see a "log to disk" option. Each you check mark it, it will overwrite the existing SONOS log file and open it for new capturing. By un-checking it, you essentially close the file and you can read/copy it. So the sequence is, set debug flag on, set logging on, do your thing, turn back off and copy file <hs root>\html\sonos\logs\SonosDebug.txt

You posted your event and linkgroup, if you changed any for any reason, post the right action/event/linkgroup that went with your trace.

I probably asked but you are running which PI version?
Is the Playbar by itself or is is paired with other speakers to create a 5:1 setup?

Dirk

**mikee123** · January 12, 2017, 02:32 PM

Ok slightly embarrassing, but I think I found the issue. I never really log onto my HS3 PC, I do everything remotely via the web page from other PC's on teh network. To get to the log I luckily had to access my HS3 PC. There was a notification, Windows firewall - allow access for the Sonos plugin... that obviously came after the upgrade and I had never seen it as its only showing if I logon to the HS3 PC, so I never allowed access, until now. Havent had any problems since...

**dcorsus** · January 12, 2017, 04:04 PM

Originally posted by mikee123 View Post

Ok slightly embarrassing, but I think I found the issue. I never really log onto my HS3 PC, I do everything remotely via the web page from other PC's on teh network. To get to the log I luckily had to access my HS3 PC. There was a notification, Windows firewall - allow access for the Sonos plugin... that obviously came after the upgrade and I had never seen it as its only showing if I logon to the HS3 PC, so I never allowed access, until now. Havent had any problems since...

Yep, one of the biggest issues when people have unexplained and weird behavior. It appears that stepping up the version of an executable, tends to fire off an approval request. I've missed it myself in the past, so you are for sure not alone.

Dirk

Announcement

Music does not start playing again after TTS

Music does not start playing again after TTS

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment