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.
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.
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.
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.
@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](http://192.168.1.38/logs#dev734)2018-06-13 16:59:30.735:infoOffice Sonos is stopped
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:30.731:debugenqueuedUri: http://192.168.1.38:8080/tts/508e4d559302c1cd1c603ab7923aeb36.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:30.729:debugtrackUri: http://192.168.1.38:8080/tts/508e4d559302c1cd1c603ab7923aeb36.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:30.727:debugtrackNumber: 1
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.975:infoOffice Sonos is playing
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.967:debugenqueuedUri: http://192.168.1.38:8080/tts/508e4d559302c1cd1c603ab7923aeb36.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.965:debugtrackUri: http://192.168.1.38:8080/tts/508e4d559302c1cd1c603ab7923aeb36.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.964:debugtrackNumber: 1
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.516:infoOffice Sonos audio level is 50%
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.024:infoOffice Sonos playing: Warning. The Nook Sliding Door has been opened by Hubitat from TTS
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.013:infoOffice Sonos is transitioning
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.009:debugtransportUri: http://192.168.1.38:8080/tts/508e4d559302c1cd1c603ab7923aeb36.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.007:debugenqueuedUri: http://192.168.1.38:8080/tts/508e4d559302c1cd1c603ab7923aeb36.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.006:debugtrackUri: http://192.168.1.38:8080/tts/508e4d559302c1cd1c603ab7923aeb36.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:28.004:debugtrackNumber: 1
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:27.989:debugnot parsed: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"></u:SetVolumeResponse></s:Body></s:Envelope>
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:27.731:debugnot parsed: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetAVTransportURIResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:SetAVTransportURIResponse></s:Body></s:Envelope>
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:26.058:infoOffice Sonos is playing
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:26.054:debugenqueuedUri: http://192.168.1.38:8080/tts/71feae2f8638e64bf6f926fca854f967.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:26.053:debugtrackUri: http://192.168.1.38:8080/tts/71feae2f8638e64bf6f926fca854f967.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:26.052:debugtrackNumber: 1
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:25.662:infoOffice Sonos audio level is 50%
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:25.183:infoOffice Sonos playing: Warning. The Office Entry has been opened by Hubitat from TTS
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:25.109:debugtransportUri: http://192.168.1.38:8080/tts/71feae2f8638e64bf6f926fca854f967.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:25.107:debugenqueuedUri: http://192.168.1.38:8080/tts/71feae2f8638e64bf6f926fca854f967.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:25.105:debugtrackUri: http://192.168.1.38:8080/tts/71feae2f8638e64bf6f926fca854f967.mp3
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:25.104:debugnot parsed: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:PlayResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:PlayResponse></s:Body></s:Envelope>
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:25.102:debugtrackNumber: 1
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:25.074:debugnot parsed: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetAVTransportURIResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:SetAVTransportURIResponse></s:Body></s:Envelope>
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:24.723:debugnot parsed: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"></u:SetVolumeResponse></s:Body></s:Envelope>
[dev:734](http://192.168.1.38/logs#dev734)2018-06-13 16:59:24.700:debugnot parsed: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:StopResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:StopResponse></s:Body></s:Envelope>
Hi Mike, Just some feedback. The repeating message issue seemed to be mostly fixed with 1.1.1.1, but now that the hotfix 1.1.1.113 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.
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.
@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.
