[RELEASE] Echo Speaks v3 + Actions

[maffpt]

Hi guys!

I have a RM rule that often send consecutive ES spoken messages and I'm getting a 6 seconds delay between messages. Is this normal?

Thanks in advance!

[nh.schottfam]

Few thoughts:

• what version are you running?
• in the latest releases, we are adding optimizations to handle these cases better. That said there are rules and restrictions the way the Alexa apis work on what can be done.
  • Tony has not put out our latest yet, as we are still doing tests.
• your logs may help you (and others) see what is actually going on

[brad5]

Having a weird problem that seems to have appeared relatively recently on two echos...

I was getting this error message under 3.6.4.4 so I upgraded to the 4.05 beta... same thing is happening.

[maffpt]

Hi @nh.schottfam!

As requested:

Versions

Device 3.6.4.1
Action 3.6.4.2
Socket 3.3.1.1
Server 2.7.0

Hub platform 2.2.5.131
Hub hardware C-5

And the logs

dev:13782021-02-23 09:27:01.772 info Echo (v3.6.4.1) | SpeakCommand Sent | (A primeira coisa que farei será abrir os estores. Afinal, mesmo se o tempo não esteja bom hoje, a vista é sensacional!) | Runtime: (10 sec) | QueueItems: (0)

dev:13782021-02-23 09:26:48.206 info Echo (v3.6.4.1) | SpeakCommand Sent | (Sejam bem-vindos! Vamos começar a demonstração de algumas das funcionalidades de domótica que este apartamento possui.) | Runtime: (10 sec) | QueueItems: (1)

dev:18192021-02-23 09:26:46.146 infoDemonstração was turned off

app:12992021-02-23 09:26:46.136 infoDelay Over: Off: Demonstração --> delayed: 0:00:05

app:12992021-02-23 09:26:40.992 infoAction: Off: Demonstração --> delayed: 0:00:05

app:12992021-02-23 09:26:40.924 infoAction: Speak on Echo - Dot cozinha: 'A primeira coisa que farei será abrir os estores. Afinal, mesmo se o tempo não esteja bom hoje, a vista é sensacional!'

app:12992021-02-23 09:26:40.828 infoAction: Speak on Echo - Dot cozinha: 'Sejam bem-vindos! Vamos começar a demonstração de algumas das funcionalidades de domótica que este apartamento possui.'

app:12992021-02-23 09:26:40.823 infoAction: END-IF

app:12992021-02-23 09:26:40.817 infoAction: Speak on Echo - Dot cozinha: 'Boa noite! Your number is 10' (skipped)

app:12992021-02-23 09:26:40.812 infoAction: Set Noite to true (skipped)

app:12992021-02-23 09:26:40.808 infoAction: ELSE (skipped)

app:12992021-02-23 09:26:40.803 infoAction: Speak on Echo - Dot cozinha: 'Boa tarde!' (skipped)

app:12992021-02-23 09:26:40.798 infoAction: Set Tarde to true (skipped)

app:12992021-02-23 09:26:40.793 infoAction: ELSE-IF (Time between 12:00 and 18:00(F) [FALSE]) THEN (skipping)

dev:13782021-02-23 09:26:40.677 info Echo (v3.6.4.1) | SpeakCommand Sent | (Bom dia!) | Runtime: (4 sec) | QueueItems: (0)

app:12992021-02-23 09:26:40.081 infoAction: Speak on Echo - Dot cozinha: 'Bom dia!'

app:12992021-02-23 09:26:40.057 infoAction: Set Manhã to true

app:12992021-02-23 09:26:40.025 infoAction: IF (Time between 00:00 and 12:00(T) [TRUE]) THEN

app:12992021-02-23 09:26:39.719 infoDemonstração de domótica Triggered

app:12992021-02-23 09:26:39.699 infoDemonstração de domótica: Demonstração switch on

dev:18192021-02-23 09:26:39.417 infoDemonstração was turned on

Thanks for the attention!

[nh.schottfam]

I think the new release will be better.

I see 3 command sent:

• first at :26:40.081
• 2nd at 26:40.828
• 3rd at 26:40.924

I'm just looking at when the command are sent (vs. when they execute).

Just curious as to why the delay between the first and the 2nd (not that it is an issue, just curious)

[wkearney99]

If I have the 3.6.4.1 version already installed, with the cloud setup, what is the 'correct' process for swapping that out for the beta? I'm seeing a bunch of odd errors, coming from an Echo Dot device that's not even being actively used.

2021-02-23 10:11:13.673 am errorEcho (v3.6.4.1) | getPlaybackState | Status: (400) | Message: Bad Request | Data: [message:com.amazon.dee.audible.exceptions.PlayQueueNotFoundException: Failed to find the requested play queue. Requested play queue id = 'playq:audiobook/audible;mv=Audible,xxxxxxxx-257c-xxxx-xxxx-75c47e0xxxxx', userFacingMessage:null]

(guid edited as I'm not sure what sort of data that exposes)

But that's tangential to my question of how do I properly switch between this release and the beta, and then presumably back to the stable release when it emerges?

I want to avoid duplicating/recreating the cloud stuff, if that's not how it's supposed to be done.

[nutcracker]

@tonesto7 FYI - the apostrophe character ‘ causes a http 500 error when used in a message for Alexa to speak.

[tonesto7]

That's odd... apostrophe used to work in speech... Plus we are cleaning up the strings.
I will need to add that to the clean string.

[tonesto7]

Just providing an update on the next release. Eric and I are working on the new centralized queue and grouping of commands.

If we don't have any major issues with the fixes eric is working on I will push up the current dev code to Beta so you can experience all the new fixes.

[d_man97]

When do you plan to move you beta updates into this release?

[tonesto7]

Once the new queue system is stable I will merge it into the master branch. I don't have an ETA. I highly suggest updating your existing install to the new Beta

[d_man97]

Ok thanks. I will try the beta.

[d_man97]

Under apps do I just delete Echo Speaks and leave Actions and Zones? In drivers do I delete both Device and WS?

[tonesto7]

Don't delete anything you can update your existing install...

Use these links to overwrite your existing code:

[RELEASE] Echo Speaks v3 + Actions

If you aren't using HPM then you'll have to manually update the code: For the Apps use these links for the import URL: Echo Speaks: https://raw.githubusercontent.com/tonesto7/echo-speaks/beta/apps/echo-speaks.groovy Echo Speaks Zones: https://raw.githubusercontent.com/tonesto7/echo-speaks/beta/apps/echo-speaks-zones.groovy Echo Speaks Actions: https://raw.githubusercontent.com/tonesto7/echo-speaks/beta/apps/echo-speaks-actions.groovy For the Drivers use these links for the import URL: ES D…

[tonesto7]

NOTICE

I've created a new topic for the Beta

[BETA] Echo Speaks V4

RELEASE V4.0.X.X BETA We wanted to get this release out there for you guys to test. Note I've changed the file structure some so I recommend you use Hubitat Package Manager and select the new entry for Echo Speaks (Beta) to install the code. I highly recommend using Hubitat Package Manager to update your existing install. If you are using HPM now you will need to uninstall HPM and reinstall HPM again and when detecting packages select the Echo Speaks 4.0 beta instead of V3 and it will updat…

I also just pushed out the v4.0.7.0

[BETA] Echo Speaks V4

RELEASE V4.0.7.0 Echo Speaks App (v4.0.7.0) [NEW] Moved to a centralized queue for all speech commands to eliminate Amazon rate limiting. [FIX] Optimizations to allow for grouping of commands to multiple zones [NEW] Control Alexa Guard with the state of a single switch (On=Armed | Off=Disarmed). [FIX] Lot's of UI design updates Echo Speaks Actions (v4.0.7.0) [FIX] Lot's of UI design updates [FIX] Fixed getAlexaRoutines Command. [NEW] Added per zone volume when multiple zone…

Please test out the new speech queue and report any issues in the topic above.

[terminal3]

Anyone else use the LastSpokentoTime? It no longer seems to be updating for me. I use it as a trigger in a few rules.

[piersm2]

Curious if anyone has been able to figure out how to restore to previous volume before an announcement is played? I have an announcement set up so that when my house door opens, it plays a sound then goes back down, but I am only able to figure out how to go to a specific level. Tried to save previous balance in Webcore, but no luck.

[tonesto7]

Pay close attention to the available volume parameters
https://tonesto7.github.io/echo-speaks-docs/devicesupport/commands/speech_commands/#playannouncementmessage

[piersm2]

My question is that if I turn up the volume listening to music, after the announcement plays, it goes to the predetermined volume, not the manually adjusted volume prior to the announcement being played. Is there a way to recall that manual volume?

[norbert.h.davis]

This is a way cool app. I'm playing around with it testing the presence trigger but I receive an error notice. Here is the text:

Unexpected Error

An unexpected error has occurred trying to load the app. Check Logs for more information.

Error: No signature of method: user_app_tonesto7_Echo_Speaks___Actions_77.runIn() is applicable for argument types: (java.lang.Integer, java.util.LinkedHashMap) values: [10, [data:[type:act_]]] Possible solutions: run(), run(), run(java.io.File, [Ljava.lang.String;), println(), any(), dump()

This is probably something I'm doing wrong. I have the presence sensor of my wife's iPhone as the trigger, it speaks "Welcome home" on my Echo Show 8, then it changes a color bulb to blue, then it is supposed to notify my iPhone by text. No text is coming in and the light does not reset. I have only tried the actions by using the "Test" button so perhaps that is the reason or that I'm a n00b and broke something making my selections for the options.

Not sure what other information to provide and not sure how to get you get you what you would need to possibly help.

Again, this is a really cool application and I appreciate all the hard work you have put into this.

Regards,

Norbert