Cheers...! I’m in.
Yeah, Amazon restricted a lot of actions on WHA devices.
I'm having a weird issue that I've been trying to fix for 2 days now, to no avail. I have 7 Echo Dots 3rd Generation (among 11 other Echo's). 2 of them (dark grey) show "text-to-speech:(true)" but 5 of them show false. I made sure they are not on "do not disturb", I've also tried Amazon tech support (but those guys don't make the difference between a capability and an app...).
Has anyone faced this issue such as identical models not showing same TTS capability?
UPDATE:
By brute forcing a "return true" statement at the end of isCommandTypeAllowed() in the driver's code, I get my device to speak. So it seems the issue comes from the driver. I don't know what it can be though, since the driver works perfectly fine with other 3rd generation devices. However, I have noticed that they don't have the same firmware. Those that have the Echo firmware #2785574276 work fine. Those that use firmware #2718591876 are those not working. Hope this can help @tonesto7 in figuring it out.
UPDATE 2 Well... turns out I was using an old version of the app... wrongly assuming it was already up to date ; I forgot about the lack of github integration in Hubitat (might be the ONLY thing I miss from ST...)
Thanks for your help!
I've decided that ES is ready for prime time.
5 Likes
Do I have to delete the existing v3 Server in order to install the released v3.0.2.1 server? In the past I just updated the apps and devices code and the just re-deployed the heroku app and everything was good. Seems like the app wont update and is stuck at 3.0.2.0 currently.
I really don't feel like having all my echo devices deleted and having to go into every rule and fix up the rules that use the echo's.
nope just update the existing code and install the new actions app...
Thanks for this.
The set up guide is prob one of the best seen for hubiat and really easy to follow!
Hey @tonesto7,
Just updated to version 3 last night, and sometime this morning my hub went awol (mostly). Lots of logs that look like:
[dev:934](http://10.0.6.4/logs/past#dev934)2019-10-12 10:53:07.372 [error](http://10.0.6.4/device/edit/934)java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. on line 817 (refreshData)
[dev:934](http://10.0.6.4/logs/past#dev934)2019-10-12 10:52:34.765 [error](http://10.0.6.4/device/edit/934)Echo (v3.1.0.2) | getAlarmVolume Exception: java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down.
[dev:934](http://10.0.6.4/logs/past#dev934)2019-10-12 10:47:18.791 [error](http://10.0.6.4/device/edit/934)java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. on line 759 (refreshStage2)
[dev:934](http://10.0.6.4/logs/past#dev934)2019-10-12 10:46:16.833 [error](http://10.0.6.4/device/edit/934)java.sql.SQLException: Connections could not be acquired from the underlying database! on line 1002 (refreshStage2)
[dev:934](http://10.0.6.4/logs/past#dev934)2019-10-12 10:45:14.515 [error](http://10.0.6.4/device/edit/934)java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. on line 817
Any thoughts on what went sideways? Kinda looks like my hub ran out of resources...
Also seeing these every 10 minutes or so:
[dev:940](http://10.0.6.4/logs#dev940)2019-10-12 12:05:23.306 [error](http://10.0.6.4/device/edit/940)Echo (v3.1.0.2) | getWifiDetails | Improperly formatted request sent to Amazon | Msg: Bad Request
The first errors are something I’ve never seen. The second ones can be ignored. It’s a static response I added for a specific response code. It’s been resolved in the upcoming release
Hmmm. Hub was pretty broken before a reboot when those errors were occurring. Error looks like available sockets to DB we’re exhausted (or at least, they look similar to errors I’ve seen MySQL throw when that’s the case). 
Hopefully Hubitat staff could chime in. @mike.maxwell
1 Like
Anyone know what this error means? I keep getting it when trying to do TTS when someone gets home.
2019-10-13 06:14:26.709 pm errorEcho (v3.1.0.2) | getPlaybackState | Improperly formatted request sent to Amazon | Msg: Bad Request
Just reported a bug where the 'run only once per day' doesn't work. I wanted to have a TTS said only once per day when there is motion first thing in the morning. Sadly, it keeps repeating.
Thanks for reporting. I will investigate
1 Like
Has the option to use button trigger been taken out? I can see it here as option Configuration - Echo SpeaksDocumentation but when I go to do it in the app it is not there.
Yeah sorry about that. It was added to list but it never made it into the code logic. I will try to get it added into the upcoming release.
1 Like
Oh that sucks as that is exactly what I need atm.
Unless you have better idea on how I can achive what I am trying to do? I am trying to have a button on dashboard that when selected will play music playlist on echo dots around the house. With out the button the only way I have found (which I think is a bit over complicated) is to have a virtual switch fire a virtual dimmer which is then sent the action to Echo Speaks to do the Spotify search.
Using the dimmer was the only real thing could find that worked, having a button would make it a lot easier.
Using a single virtual switch with Es actions should work. You can even have it turn the switch off
1 Like
Holy shit I am blind! I looked all over for it and was right there. Think I just skimmed over it cause had Outlets first.
Thanks mate!
2 Likes
I worried that might be confusing
