[RELEASE] Echo Speaks v3 + Actions

djgutheinz · July 26, 2020, 11:24am

Warning message in logs. I am receiving the following warning message in my logs for EchoSpeaks:

EchoApp (v3.6.3.1) | CODE UPDATES REQUIRED: Echo Speaks Integration may not function until the following items are ALL Updated [Echo Speaks Server].

I use the app for TTS and it appears to work.

I know it is looking for the Echo Speaks Server which is not installed using HPM. I tried a repair in HPM (no updates were listed).

Anything I can do to correct the warning?

Dave

Ken_Fraleigh · July 26, 2020, 12:28pm

In the Heroku app, add Tonesto7@gmail.com as the collaborator and it will automatically update.

eibyer · July 26, 2020, 5:32pm

I've completed the install but it's not pulling any devices for me.

The following has devices in it:
https://alexa.amazon.com/api/devices/v3

What else can I check?

Edit: I can see the Echo - Echo Device Name in my live log when I interact with Alexa

Edit2: And I can see the Echo devices in my device list... and actually use it for playing speech

chipworkz · July 28, 2020, 3:29pm

Yes, I just finished the setup on my Hubitat and I still have Echo Speaks installed in SmartThings as well. Both are working fine together.

eibyer · July 28, 2020, 3:33pm

Thanks. I ended up going ahead and removing my ST installation. As you can see from my previous post, I got it installed on the HE side but my Apps page doesn't show me my devices that it pulled. I do see the devices in my device list and they're usable which is good enough for me.

But.... the slight ocd is there and wants to fix it lol.

greglsh · July 29, 2020, 6:01pm

Hi

I keep getting this in my log file, anybody know what this means and how to stop the logging?
dev7 is my Echo dot in the kitchen. It logs this almost every minute.

dev:7 2020-07-29 19:58:24.756 debuglastVoiceActivity:

dev:7 2020-07-29 19:57:25.955 debuglastVoiceActivity:

dev:7 2020-07-29 19:56:25.687 debuglastVoiceActivity:

dev:7 2020-07-29 19:55:25.727 debuglastVoiceActivity:

dev:7 2020-07-29 19:54:26.150 debuglastVoiceActivity:

dev:7 2020-07-29 19:54:14.839 debuglastVoiceActivity:

dev:7 2020-07-29 19:53:24.816 debuglastVoiceActivity:

neonturbo · July 29, 2020, 6:02pm

Look up a dozen or so posts, it describes modifying a line in the driver. It seems to work, although I sure wish I knew why it only happened on one my devices.

tonesto7 · July 29, 2020, 6:06pm

I just pushed out a code fix disabling that entry when debug is disabled

neonturbo · July 29, 2020, 6:25pm

Cool, thanks for fixing this.

Good to see you are around again.

tonesto7 · July 29, 2020, 7:08pm

I also just pushed out v2.6.0 which I hope will resolve the login issues outside the US

jkudave · July 29, 2020, 10:12pm

@tonesto7, I'm not seeing 2.6.0 in the repo:

tonesto7 · July 29, 2020, 10:16pm

Maybe it takes some time for your fork to update. It's available under my branch

Evilborg · July 30, 2020, 12:33am

For those running echo speaks locally -- to upgrade go into your echo-speaks-server folder and type git pull then run sudo pm2 restart index. That's it...

mhburall · August 1, 2020, 1:41am

i get errors when i login to amazon for echo speaks, if i bring up a web browser sign in to amazon i have no issue.

error
There was a problem

Enter a valid email or mobile number

Sebastien · August 1, 2020, 1:59am

I’m trying to setup a RM that will provide me information from the same Alexa device that I used to ask the question, but it is not working...

Any recommendations would be appreciated!

I am looking for the device with “wasLastSpokenToDevice” that is set to “True”, assuming that it would be the device from to which I asked the questions, but unfortunately, it is not. (I have a routine that flips a switch. This switch triggers the RM rule...)

I’m wondering... Is there a way to refresh the “wasLastSpokenToDevice” value? Would there be a better way to do this?

Thanks!

Edit: Found it! Running “getDeviceActivity()” on all my echo devices prior to having it check which was the last device that was spoken to works. It now provides the answer on the device where the question was asked. (I suspect that if someone else speaks to another echo afterwards, it would move it to that one, but I’m not too worried about that...)

mhburall · August 1, 2020, 2:22am

redeployed server setup everthing good now

mhburall · August 1, 2020, 3:00am

Updates Required for:
• Echo Speaks Websocket
• Echo Speaks Actions

If you just updated the code please press Done/Save to let the app process the changes.

when i bring up websocket driver it says current same as actions

Echo Speaks WebSocket
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
in compliance with the License. You may obtain a copy of the License at:

 http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
for the specific language governing permissions and limitations under the License.
*/
// This is based on the Amazon WebSocket used on Alexa.amazon.com and is ported from Javascript to Groovy and inspired from the work of @Apollon77 Alexa-Remote

// NOTICE: This device will not work on SmartThings

String devVersion() { return "3.3.1.1"}
String devModified() { return "2020-07-19" }
Boolean isBeta() { return false }
Boolean isST() { return (getPlatform() == "SmartThings") }
Boolean isWS() { return true }

/**

Echo Speaks Actions
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
in compliance with the License. You may obtain a copy of the License at:

 http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
for the specific language governing permissions and limitations under the License.

*/

String appVersion() { return "3.6.3.1" }
String appModified() { return "2020-07-19" }
String appAuthor() { return "Anthony S." }
Boolean isBeta() { return false }
Boolean isST() { return (getPlatform() == "SmartThings") }

mhburall · August 1, 2020, 3:29am

don't know what happen, but everything has synced now.

mattias · August 1, 2020, 7:26am

@tonesto7 I just installed ES using the Hubitat Package Manager. It has installed version 3.6.3 .1 of Echo Speaks and ver 2.6.0 of the Heroku server code. I have the same issue that @VilifiedFerret reported above. I can log in to the Alexa website just fine (alexa.amazon.com.au) but when trying to get the cookie, it says it successfully got the cookie, but then it goes back to the logon page.
I frequently also get asked to put a one time password in when trying to log in to the website. I don't get the same through Heroku, but maybe that is what is causing the issue? The Heruko log say:

2020-08-01T07:00:46.496234+00:00 app[web.1]: 8-1-2020 - 7:00:46am debug: Alexa Login Status: There was an error

Any idea what might be causing this? This is the first time I'm trying to install this, so everything has been installed from scratch.

mhburall · August 1, 2020, 4:30pm

getting this error in the logs from the hub, how do i fix this ?

app:722020-08-01 12:28:41.627 pm errorError making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_e0a24720-b036-4687-b37f-65372f7c162c_1596299320726.0..ASRLS_e0a24720-b036-4687-b37f-65372f7c162c_1596299320726"},"payload":{"code":"INVALID_REQUEST_EXCEPTION","description":"Cannot read the request payload as: Cannot construct instance of com.amazon.iota.driver.v3.StateReportProperty, problem: arg3 must not be null\n at [Source: UNKNOWN; line: -1, column: -1] (through reference chain: com.amazon.iota.driver.directive.v3.MessageEnvelope$V3Builder["context"]->com.amazon.iota.driver.directive.v3.Context["properties"]->com.amazon.iota.driver.v3.StateReportPropertyArray[1])"}}