[DEPRECATED] Echo Speaks

tonesto7 · January 26, 2019, 5:31pm

Hmm... I will add some more logging into that section before I release today.
The broadcast and announce test is not actually using the device handlers to send the commands which I need to make sure I didn't miss anything there.

I will let you know what I find

Andrew1 · January 26, 2019, 5:33pm

OK, happy to test for you when released, but don't want this to detract from your great work with this app! As an ex-developer myself, I know that these little things can take some finding!

tonesto7 · January 26, 2019, 5:49pm

This is one of my biggest flaws as a developer
I'm always working on and optimizing stuff and working on new ideas that I likely got sidetracked and left something unhandled.

tonesto7 · January 26, 2019, 11:53pm

tonesto7:

V2.4.0 (January 26th, 2019)

App

FIXED: Echo Device Filter not stopping selected devices from being created.

FIXED: Updated the UI some for devices. It's easy to distinguish between unsupported and devices ignored by user.

UPDATED: Rewrote the broadcast test logic it works extremely well now. Devices that are shown to not support TTS are not selectable in the list.

UPDATED: Also rewrote the announcement test logic it works extremely well now. Devices that are shown to not support TTS are not selectable in the list.

UPDATED: Echo Device Filter not stopping selected devices from being created.

UPDATED: Streamlined the new install flow in the app to reduce page changes. (Update the documentation as well)

Device

FIXED: Speaking long text on ST would through exception

FIXED: fixed broken attributes lastVoiceActivity and lastSpokenToTime from last update.

FIXED: wait sequence command was breaking the whole sequence (Multiple waits are having issues).

FIXED: Made changes to address the random exception errors on async responses.

UPDATED: Speak commands now handle long strings but splitting them into multiple sequence commands and playing them 1 by 1

ADDED: Music search available in the sequence commands.

ADDED: Speak command now cleans the strings of unnecessary characters.

ADDED: Speak command will attempt to transform items like temperature 19F to 19 degrees and directions SSW to south southwest. (This can be disabled under each device)

Just released

Notice: The announcement test in the app needs more work. It's not setting the volume like I want before announcing.

CAL.hub · January 27, 2019, 3:54am

In the most trivial of bugs...

volume::40,, speak::this is so silly,, wait::60, weather,, cannedtts_random::goodbye,, traffic,, amazonmusic::green day,, volume::30

If someone (me ) copies the sample sequence phrase to test, the single comma after wait::60 causes the test to fail.

tonesto7 · January 27, 2019, 3:55am

thanks for catching that

Andrew1 · January 27, 2019, 8:04am

Great work with V2.4.0, it's solved my problems with the broadcast test and the announcement test.

tonsofguns · January 27, 2019, 9:59am

Is this allowing custom text to speech ?

tonesto7 · January 27, 2019, 9:49pm

yes and much more

Matthew · January 27, 2019, 10:49pm

Thanks for adding Fabriq TTS! It works great.

I'm not sure if my next question is about Echo Speaks, or Rule Machine? I want to use the '%device%' variable in RM in a playTextandResume() custom command, but I'm not sure if that can be done? I have a RM that triggers on presence arriving/departing. I want the message to be '%device%' has left.' and %device% would be replaced with the device name that triggered the rule ... like 'Matthew has left.'

I created a RM Custom Command for PlayTextandResume('%device% has left',45) and it enunciates 'Percent device percent has left'. I could hard code a custom command for all five of our presence sensors, but hope to not have to do that. I also use a similar RM to says what windows are open, and we have a lot of windows so that would be a lot of rules to create if that are all hard coded.

Has anyone done this or have a suggestion I could try? Thanks.

tonesto7 · January 28, 2019, 2:54am

I'm not sure how to answer that question.
but i do have a companion app in development that will allow for easy creation of performing these type of event based alerts

tonsofguns · January 28, 2019, 3:37am

Just wanted to say thanks for this app. Got it installed very quickly and the first rule I made to test worked great.

I do have a question. I went in and renamed my fire cubes since I installed this. It updates in the app settings, but the names are not updated in rule machine. I have auto rename enabled. Is it just a waiting game or is something wrong?

tonesto7 · January 28, 2019, 4:19am

I need to work on the rename under Hubitat. It works fine on the SmartThings side

tonsofguns · January 28, 2019, 4:20am

For now should I just select the old name or do a reinstall of the app?

tonesto7 · January 28, 2019, 4:48am

Just edit the names under the devices page

tonsofguns · January 28, 2019, 4:53am

Will do. Thanks

Andrew1 · January 28, 2019, 6:32pm

Got it all set-up and working yesterday, but the Amazon cookie expired early this morning and I had to re-login to the Amazon service today, is this normal and how long should the cookie be expected to last?

I'm also seeing lots of debug message in the log, even though no speech is being used, this is a typical example period of 8 minutes....

dev:82019-01-28 06:22:51.317 pm debugAlexa Playlists Changed to [:]
dev:72019-01-28 06:22:28.369 pm debugAlexa Playlists Changed to [:]
dev:82019-01-28 06:21:51.350 pm debugAlexa Playlists Changed to [:]
dev:72019-01-28 06:21:28.401 pm debugAlexa Playlists Changed to [:]
dev:82019-01-28 06:20:51.345 pm debugAlexa Playlists Changed to [:]
dev:72019-01-28 06:20:28.348 pm debugAlexa Playlists Changed to [:]
dev:82019-01-28 06:19:51.384 pm debugAlexa Playlists Changed to [:]
dev:72019-01-28 06:19:28.329 pm debugAlexa Playlists Changed to [:]
dev:82019-01-28 06:18:51.377 pm debugAlexa Playlists Changed to [:]
dev:72019-01-28 06:18:28.422 pm debugAlexa Playlists Changed to [:]
dev:82019-01-28 06:17:51.349 pm debugAlexa Playlists Changed to [:]
dev:72019-01-28 06:17:28.338 pm debugAlexa Playlists Changed to [:]
dev:82019-01-28 06:16:51.346 pm debugAlexa Playlists Changed to [:]
dev:72019-01-28 06:16:28.483 pm debugAlexa Playlists Changed to [:]
dev:82019-01-28 06:15:52.050 pm debugAlexa Playlists Changed to [:]
dev:72019-01-28 06:15:28.326 pm debugAlexa Playlists Changed to [:]
dev:82019-01-28 06:14:51.456 pm debugAlexa Playlists Changed to [:]

Is this to be expected?

tonesto7 · January 28, 2019, 8:38pm

Thanks for reporting this. Your not the first users to say they are seeing this in the logs. (It's nothing to be concerned about)
You really shouldn't be seeing that log entry unless the new value is different than the current playlist.

I will investigate

Andrew1 · January 28, 2019, 8:48pm

OK, thanks. My other issue (sorry) is that I can't configure my Pushover device for the notifications, I can't get to see the list of devices to select my pushover device.

tonesto7 · January 28, 2019, 8:55pm

Yea that was another overlooked item. The pushover integration in this app uses my pushover manager app for a whole platform level support with no virtual devices. Support just needs to be added to the app.

When I get some time I will add support for the devices themselves.