TTS problems - sonos

I’m seeing an issue with TTS on my sonos kit.

I have a rule that triggers a TTS message “the garage alarm has been armed” when a virtual switch is turned on and then “the garage alarm has been disarmed” when it’s turned off.

I will very often get a repeat of the previous message eg it will correctly announce “the garage alarm has been armed” and then immediate play “the garage alarm has been disarmed”. It’s like it’s storing the previous “track” (the last TTS message) and then resuming it.

Any ideas ?

Same issue via rule machine and webcore



That's exactly what's hapening.

If the sonos state is play when a tts comes in, then the previous track is resumed, otherwise we don't resume.
I've seen this happen when two tts messages (or any track for that matter) are sent one right after the other and the sonos hasnt had a chance to report back that it has stopped yet.

Is this the case in your situation?

This is driving my household crazy as well. Sometimes it IS when two TTS's are sent one right after the other, but most of the time its a single door opening followed by two messages.

@DeveloperDavidB I was just about to reply with the same thing.. observing the same issue

It does this for me usually on st as well. Stopped using it.

Of course this doesn't happen to me, so if one of you could enable debug logging on your sonos, fire up live logging, and then post up a screen shot of the logs when this happens I may be able to see what's happening and fix it.

For this one, I opened a sliding door. Sonos spoke "Warning, The nook sliding door has been opened" twice.

[dev:736]( 11:37:42.632:infoKitchen Sonos is stopped

[dev:736]( 11:37:42.626:debugenqueuedUri:

[dev:736]( 11:37:42.624:debugtrackUri:

[dev:736]( 11:37:42.622:debugtrackNumber: 1

[dev:736]( 11:37:39.125:infoKitchen Sonos audio level is 51%

[dev:736]( 11:37:35.898:debugtransportUri:

[dev:736]( 11:37:35.896:debugenqueuedUri:

[dev:736]( 11:37:35.895:debugtrackUri:

[dev:736]( 11:37:35.894:debugtrackNumber: 1

[dev:736]( 11:37:35.641:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:SetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"></u:SetVolumeResponse></s:Body></s:Envelope>

[dev:736]( 11:37:35.575:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:SetAVTransportURIResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:SetAVTransportURIResponse></s:Body></s:Envelope>

[dev:736]( 11:37:33.135:infoKitchen Sonos is playing

[dev:736]( 11:37:33.132:debugtransportUri:

[dev:736]( 11:37:33.130:debugenqueuedUri:

[dev:736]( 11:37:33.129:debugtrackUri:

[dev:736]( 11:37:33.128:debugtrackNumber: 1

[dev:736]( 11:37:32.612:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:PlayResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:PlayResponse></s:Body></s:Envelope>

[dev:736]( 11:37:32.573:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:SetAVTransportURIResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:SetAVTransportURIResponse></s:Body></s:Envelope>

[dev:736]( 11:37:32.560:infoKitchen Sonos audio level is 50%

[dev:736]( 11:37:32.520:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:SetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"></u:SetVolumeResponse></s:Body></s:Envelope>

[dev:736]( 11:37:32.491:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:StopResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:StopResponse></s:Body></s:Envelope>

@mike.maxwell Here is a log from my office sonos from when my office entry opened. It spoke the configured TTS, but then immediately spoke a tts for a door that did not open. The Sonos spoke "Warning, the office entry has been opened""Warning, the nook slider has been opened" I should also mention this is a sonos playbar

[dev:734]( 16:59:30.735:infoOffice Sonos is stopped

[dev:734]( 16:59:30.731:debugenqueuedUri:

[dev:734]( 16:59:30.729:debugtrackUri:

[dev:734]( 16:59:30.727:debugtrackNumber: 1

[dev:734]( 16:59:28.975:infoOffice Sonos is playing

[dev:734]( 16:59:28.967:debugenqueuedUri:

[dev:734]( 16:59:28.965:debugtrackUri:

[dev:734]( 16:59:28.964:debugtrackNumber: 1

[dev:734]( 16:59:28.516:infoOffice Sonos audio level is 50%

[dev:734]( 16:59:28.024:infoOffice Sonos playing: Warning. The Nook Sliding Door has been opened by Hubitat from TTS

[dev:734]( 16:59:28.013:infoOffice Sonos is transitioning

[dev:734]( 16:59:28.009:debugtransportUri:

[dev:734]( 16:59:28.007:debugenqueuedUri:

[dev:734]( 16:59:28.006:debugtrackUri:

[dev:734]( 16:59:28.004:debugtrackNumber: 1

[dev:734]( 16:59:27.989:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:SetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"></u:SetVolumeResponse></s:Body></s:Envelope>

[dev:734]( 16:59:27.731:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:SetAVTransportURIResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:SetAVTransportURIResponse></s:Body></s:Envelope>

[dev:734]( 16:59:26.058:infoOffice Sonos is playing

[dev:734]( 16:59:26.054:debugenqueuedUri:

[dev:734]( 16:59:26.053:debugtrackUri:

[dev:734]( 16:59:26.052:debugtrackNumber: 1

[dev:734]( 16:59:25.662:infoOffice Sonos audio level is 50%

[dev:734]( 16:59:25.183:infoOffice Sonos playing: Warning. The Office Entry has been opened by Hubitat from TTS

[dev:734]( 16:59:25.109:debugtransportUri:

[dev:734]( 16:59:25.107:debugenqueuedUri:

[dev:734]( 16:59:25.105:debugtrackUri:

[dev:734]( 16:59:25.104:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:PlayResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:PlayResponse></s:Body></s:Envelope>

[dev:734]( 16:59:25.102:debugtrackNumber: 1

[dev:734]( 16:59:25.074:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:SetAVTransportURIResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:SetAVTransportURIResponse></s:Body></s:Envelope>

[dev:734]( 16:59:24.723:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:SetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"></u:SetVolumeResponse></s:Body></s:Envelope>

[dev:734]( 16:59:24.700:debugnot parsed: <s:Envelope xmlns:s="" s:encodingStyle=""><s:Body><u:StopResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:StopResponse></s:Body></s:Envelope>

Any progress with this issue?


Doesn't look like it. Sonos is still making double announcements with the 1.1.0 update.

Confirmed as being a prob still too..

You may want to post up your logs as well in case they show something mine aren't showing. In case it matters what Sonos devices are you using?

I am using
1X Sonos Playbar
2X Sonos Connect Amp
1X Sonos connect
1X Play 5
1X Play 3

Only one of the Connect Amps, the Playbar, and the Play 3 are used for Hubitat announcements.

I have a Sonos Play Bar
Sonos Play 5
Sonos Play 1
Sonos Connect

The announcements are playing through the sonos playbar, but the same issue is seen through any of the sonos players..

Hope this helps..

dev:3222018-06-30 18:31:23.585:infoTelevision Sonos is stopped

app:5462018-06-30 18:31:22.178:errorjava.lang.NullPointerException: Cannot invoke method toLong() on null object (deviceHandler)

dev:3222018-06-30 18:31:22.112:infoTelevision Sonos is playing

dev:3222018-06-30 18:31:22.048:infoTelevision Sonos audio level is 35%

dev:3222018-06-30 18:31:21.766:infoTelevision Sonos playing: I've turned off the garage alarm by Hubitat from TTS

dev:3222018-06-30 18:31:21.757:infoTelevision Sonos is transitioning

app:1502018-06-30 18:31:20.772:debugPushing switch off to Garage Alarm(99911) Response: 200

Hi @mike.maxwell , Neither of us tagged you when we left our logs, so just wanted to make sure you see this.

I have enough info at this point, now just need the time to dig into it a little.

Hi Mike, Just some feedback. The repeating message issue seemed to be mostly fixed with, but now that the hotfix has been installed, it's repeating messages again. I would be surprised if you unwound any TTS fixes in between the updates, but that's whats happening.

you are correct, the hot fix didn't have any sonos changes.
Ok, we'll have to see what other users report on this matter than.

Just in case it has anything to do with it, I am going to move my WebCore pistons into Rule Machine 2.5 rules, and uninstall webcore. I will let you know if things change. Really the only reason I like WebCore so much better than rule machine for voice stuff is because I can concatenate the device variable wherever I want in the speech string. Example: "Attention. The (DeviceName) has been opened" instead of in rule machine, "The following door or window has opened. (DeviceName)". It would be a huge improvement if we could do this in Rule machine.

1 Like

@mike.maxwell @bravenel Today I deleted all of my pistons, and uninstalled Webcore. I also deleted all of my rules, and recreated the rules and pistons with Rule Machine 2.5.

I am still getting double TTS announcements quite often. It may be improved from before 1.1.1, but not enough time has gone by to be sure. Its really confusing when the announcements say something like "Attention. The following door has been opened. Front Door. Attention. The following door has been opened. Nook slider." I don't know if the Nook Slider really opened, or if it's just a double notification. People in this house are starting to just not trust and ignore the announcements.

Overall performance seems a little more snappy without webcore, but I really wish I could insert the device name in the speech string where it would make more sense. See my previous post above this one for more detail.

Ive been busy

1 Like