[RELEASE] Echo Speaks


#223

Sonos for TTS is buggy.

I tested this last week or so?


#224

@pcgirl, I was testing the Notification app to ensure the lastes hotfix corrected an issue I was having with a custom driver I was using (it did :grinning: ). I decided to add a TTS to my Sonos to verify for you. I tested both the speech and music device functionality. Both worked fine.


#225

Did they resume?


#226

I have just tested this and I have 4 sonos grouped together. It will speak the notification but it resumes back to the beginning of the playlist. It also doesn't resume on all sonos. First it dropped two of them and then it dropped 1 and then two again. Different ones each time. But the Grouped parent sonos stayed. When I regrouped them the sonos that had been dropped had not reset the volume to what is was before. So they were very loud.


#227

Exactly why I use my Sonos for audio only and Google devices for tts. Sonos has never played nice with tts and resume for me.


#228

It used to work perfectly in ST. I used to use WebCore for announcing arrivals and departures and it would speak in unisence and resume where it left off and with the correct volume. It wouldn't break the group. However, I think Sonos has since changed things because even using it with ST Webcore was having issues. I really wish that they would get this working again.


#229

OK, I have also tested the notifications with the echos and two out of three threw an error in the log before speaking. They all spoke at different times also. And I can confirm that the volume did not resume to what it was before they spoke the TTS. Something isn't working correctly. Here is the log:

dev:6762019-03-22 07:50:09.181 pm tracecheckQueue | Nothing in the Queue... Performing Queue Reset

dev:6762019-03-22 07:50:06.129 pm infoSpeakCommand Sent Successfully | Length: (37) | Execution Time (414ms) | Recheck Wait: (2 sec) | CmdID: (205)

dev:6762019-03-22 07:50:05.714 pm debugspeakVolumeCmd([cmdDesc:SpeakCommand, message:The Test Button is being tested dummy, newVolume:100, oldVolume:100, cmdDt:1553298605713])...

dev:6762019-03-22 07:48:26.508 pm tracecheckQueue | Nothing in the Queue... Performing Queue Reset

dev:6762019-03-22 07:48:23.459 pm infoSpeakCommand Sent Successfully | Length: (37) | Execution Time (5966ms) | Recheck Wait: (2 sec) | CmdID: (228)

dev:6762019-03-22 07:48:23.025 pm debugspeakVolumeCmd([cmdDesc:SpeakCommand, cmdId:104, newVolume:100, queueKey:qItem_1, oldVolume:100, message:The Test Button is being tested dummy, cmdDt:1553298497491, msgDelay:2])...

dev:6762019-03-22 07:48:21.330 pm errorjava.lang.Exception: No response data exists for async request on line 2415 (asyncSpeechHandler)

dev:6762019-03-22 07:48:20.991 pm debugspeakVolumeCmd([cmdDesc:SpeakCommand, cmdId:56, newVolume:100, queueKey:qItem_1, oldVolume:100, message:The Test Button is being tested dummy, cmdDt:1553298497491, msgDelay:2])...

dev:6762019-03-22 07:48:17.918 pm infoSpeakCommand Sent Successfully | Length: (37) | Execution Time (426ms) | Recheck Wait: (2 sec) | CmdID: (56)

dev:6762019-03-22 07:48:17.493 pm debugspeakVolumeCmd([cmdDesc:SpeakCommand, message:The Test Button is being tested dummy, newVolume:100, oldVolume:100, cmdDt:1553298497491])...


#230

:rofl:


#231

Ha! Have to amuse myself somehow!:stuck_out_tongue_winking_eye:


#232

Does anyone else have a 3rd generation echo dot that is lazy? I have a rule setup to play a random greeting on my echo dot 3rd gen when a lock code is triggered. My 3rd gen dot will sometimes take as long as 30 seconds to play the TTS greeting. I thought maybe it was something with my hub so I swapped it out with a 1st Gen dot and it executed almost instantly. Same thing with my regular echo, played very quickly. But my 3rd gen will sometimes take forever. Anyone else?


#233

Iā€™m having repeat issues. Why?


#234

I think there is something with queue function in echo speaks. hubitat processes too fast and it messes with the queue timing causing a repeat. I turned off the queue and do not get repeats anymore.

Echospeaks does toss error s for me fairly regularly though.


#235

Where do you turn off the queue?


#236

So I found it and disabled it.

Still get repeats. If I open my door and shut it right away it throws the message twice


#237

I also noticed repeats on short messages. What do you have it saying?


#238

The item is removed from the queue based on the response from Amazon that it was received. I will try to take a look at it tonight.


#239

I've noticed in the event log of the contact sensor, it has a double entry for every open and close event? Maybe it's something with the contact sensor?


#240

Where do you turn this off?


#241

It's on the device property page for each echo.


#242

Thanks! Found it!