It does not require a ST hub. The app and driver code are able to work with either HE or ST. The documentation is written/geared for ST, but one can equate the steps for HE. I, and many others, have Echo Speaks working on HE.
1 Like
As @jkudave mentioned, "Echo Speaks" works fine on Hubitat without any need for SmartThings.
I think it would be interesting to know if you can get Echo Speaks running successfully using your Australian Alexa account. This would help me to understand whether or not it is even possible to do so at this time.
1 Like
I don’t know if it’s any help in dignosing, I replaced the .js with the updated one, cleared out everything and started the process over. I selected the option to force a cookie refresh and it populated the cookie. A few days later I’m getting an error and the auto refresh is no longer working ... looks like it worked on initial refresh ...
This is exactly what I saw as well. Going through the process again after the failure did obtain a valid cookie as I mentioned above.
@gabriele - any idea of what is going on? Are you seeing the same issue?
Yes, same here. I'll have a look next week when I'll be back at home.
1 Like
Not sure what you’re asking? Are you referring to the “Echo Speaks” integration? If so, follow the directions for it in the first post of that thread. It is not a trivial installation, but the directions are pretty detailed (although they are designed for SmartThings, so you have to interpret them for Hubitat.)
If you’re attempting to still make my Alexa TTS Manager app work, ignore everything regarding the automatic cookie renewal NodeJS server. Just use the Chrome Browser instructions for retrieving the cookie after logging into alexa.amazon.com.au.
Hey @ogiewon - you have 3 methods listed in the readme.
Method 1A
Method 1B
Method 2
I did method 1A the other night and the cookie error was getting thrown up when trying to get to the next screen as I had notify to send error to pushover. Step 7 from the readme on github.
OK. Thanks for testing.
How about trying "Echo Speaks" instead to see if it works in Australia?
i'll give echo speaks a try tonight 
all of the instructions are for smartthings - it makes no sense to me..
Sorry to hear that. I guess you're SOL for now if you can't interpret those instructions into Hubitat steps. Just follow the Manual App and Driver installation instructions to copy and paste the code into Hubitat. Then follow along with the Heroku instructions. If it says to do something the ST Mobile App, just use the Hubitat web admin UI to interface with creating and using the Echo Speaks app. Good luck!
1 Like
does SOL mean what I think it means ? lmao
I also won a google mini this week, was going to look at possibly mounting that in the kitchen as a singular notification device (I have 5 echos I would prefer to use).
I am reading the ES guide, but everytime I see ST I have NFI if I should be setting up a ST account and doing all this there or on my hub shakes first at screen.
So I go install // manual install // smart app install and everything I see that says ST, ignore and paste into HE..
Also looks like the lads over there are having issues..
Yea, do NOT create a ST account. Not needed whatsoever.
SOL means exactly what you're thinking. 
Since your an Aussie, I figured you could probably handle some good-natured humor. I visited Melbourne, Australia 18 years ago on a business trip. Still my favorite business trip by far. Awesome city and people!
hahaha - classic. Yeah, nice place this little island, crapshoot if you want anything mainstream/cheap though. Or if you're not down for deadly animals bitting you..
im stuck with this hey - I just want HE to be able to use the many echos I have to tell me my kids stealing chocolate from the fridge at 1am or that the boogieman just opened the laundry window and to wake up..
Dan did you get the auto refresh working ? Mine still won't.
It seems to work one time, but subsequent automatic refreshes fail. @gabriele stated earlier that he'd take a look at it once he was back home. Until then, you should be able to manually refresh your cookie, like we used to in the stone age! 
damn ok
The setup on this worked great. The devices all work. When I incorporate a speak to device in "Rule Machine" I get an error. I'll copy the two log files here (minus some long ID cookie). I removed a couple of the ID's but did check for differences in the ID's in the log files and there were none.
Thanks,
Leon
Case 1: This is Passing Case: Sending Speak Command from Device
app:762019-06-29 12:11:38.326 debug Command = [uri:https://pitangui.amazon.com/api/behaviors/preview, headers:[Cookie:x-amzn-dat-gui-client-v=1.24.206077.0; skin=noskin; ubid-main=134-2403526-2311102; unique_id=Removed; s_cc=true; s_sq=%5B%5BB%5D%5D; csrf=146854901; s_vnum=1989436342362%26vn%3D3; session-id=135-7616146-3999539; session-id-time=2082787201l; s_ppv=55; s_nr=1557797105591-Repeat; s_dslv=1557797105594; x-wl-uid=REMOVED Stuff Here==;, Referer:https://alexa.amazon.com/spa/index.html, Origin:https://alexa.amazon.com, csrf:146854901, Connection:keep-alive, DNT:1], contentType:text/plain, body:{"behaviorId":"PREVIEW","sequenceJson":"{"@type":"com.amazon.alexa.behaviors.model.Sequence","startNode":{"@type":"com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode","type":"Alexa.Speak","operationPayload":{"deviceType":"A32DOYMUN6DTXA","deviceSerialNumber":"G090VC0990750B7H","locale":"en-US","customerId":"A3D1JDAZ5Z2FJG","textToSpeak":"Test"}}}","status":"ENABLED"}]
app:762019-06-29 12:11:38.283 debug Sending 'Test' to 'Office'
dev:432019-06-29 12:11:38.197 debug Speaking message = 'Test'
Case 2: This is the Failing Case using Rule Machine
dev:332019-06-29 12:14:59.492 error groovy.lang.StringWriterIOException: java.io.IOException: Stream closed on line 43 (deviceNotification)
app:762019-06-29 12:14:59.331 error 'speakMessage()': Error making Call (getMessage): Bad Request
app:762019-06-29 12:14:59.327 error 'speakMessage()': Error making Call (Status): 400
app:762019-06-29 12:14:59.324 error 'speakMessage()': Error making Call (Data): {"Message":null}
app:762019-06-29 12:14:58.629 debug Command = [uri:https://pitangui.amazon.com/api/behaviors/preview, headers:[Cookie:x-amzn-dat-gui-client-v=1.24.206077.0; skin=noskin; ubid-main=134-2403526-2311102; unique_id=Removed; s_cc=true; s_sq=%5B%5BB%5D%5D; csrf=146854901; s_vnum=1989436342362%26vn%3D3; session-id=135-7616146-3999539; session-id-time=2082787201l; s_ppv=55; s_nr=1557797105591-Repeat; s_dslv=1557797105594; x-wl-uid=REMOVED Stuff Here ==;, Referer:https://alexa.amazon.com/spa/index.html, Origin:https://alexa.amazon.com, csrf:146854901, Connection:keep-alive, DNT:1], contentType:text/plain, body:{"behaviorId":"PREVIEW","sequenceJson":"{"@type":"com.amazon.alexa.behaviors.model.Sequence","startNode":{"@type":"com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode","type":"Alexa.Speak","operationPayload":{"deviceType":"A32DOYMUN6DTXA","deviceSerialNumber":"G090VC0990750B7H","locale":"en-US","customerId":"A3D1JDAZ5Z2FJG","textToSpeak":"Test "}}}","status":"ENABLED"}]
app:762019-06-29 12:14:58.509 debug Sending 'Test ' to 'Office'
dev:432019-06-29 12:14:58.458 debug Speaking message = 'Test '
app:772019-06-29 12:14:58.371 info Action: Speak on AlexaTTS Office: 'Test'
app:772019-06-29 12:14:58.300 info Garage Door Left Open: became True
app:772019-06-29 12:14:58.292 info --> Garage Car Door open [true]
app:772019-06-29 12:14:58.124 info Garage Door Left Open: Garage Car Door contact open
dev:422019-06-29 12:14:58.018 info Garage Car Door was opened
--- Live Log Started, waiting for events
