Everything had been working well but yesterday I added a 4th gen dot & renamed a few devices. Now the app won’t open & the log states
errorgroovy.json.JsonException: Expected a value or a closing curly brace '}' on line: 1, column: 37631. But got ':' instead. on line 78 (initialize)
Any clues?
I made some bookmarklets that anybody can use in their browser to easily get and search automationIds for the Execute Routine Id feature:
https://jamiegluk.github.io/alexa-get-routine-ids-bookmarklets/
Hopefully someone can help with my staggered delay/lag between speakers here.
Normally, I've been getting a 6-8 second delay after one of my Echo Dots firing and then the other 2 in the house.
Most of my notifications are coming from RM or the built in HE notifier app.
I was about to start making some rules within ES to see if that fixed the lag, but used the built in test feature, and that also produces the delay with notifications, not announcements, although at much more random and inconsistent intervals.
I don't get the lag using Alexa Announcements directly from my phone or from a Dot either. Announcements seem to have perfect sync.
Must be something relating to the notifications only.
What can I do to eliminate this delay?
EDIT: Alternatively, can I have RM and other apps trigger announcements through TTS rather than notifications? Is that possible, it would fix this issue, plus I like the chime at the beginning.
I'm having a problem with executeSequenceCommand() -- the "stop" command doesn't seem to work from a string passed to that method.
I have a WebCoRE piston that uses the following flow:
In response to event 1 - executeSequenceCommand('volume::80,, amazonmusic::something')
In response to event 2 - executeSequenceCommand('stop, volume::70,, weather')
Event 1 works fine. The problem is with event 2. In the example I gave above, it completely fails to do anything. But if I take the "stop" out of the sequence command and change the piston to
with echoDevice
Stop;
executeSequenceCommand('volume::70,, weather')
That works.
Any idea why one of my echo dots will not speak? I just reinstalled and it still is not working.
Did you go back into ES and and make sure the dot was added back under the Manage Devices section?
Yes it is
you were missing the double comma after stop so it should look like this executeSequenceCommand('stop,, volume::70,, weather')
Does anyone know if it’s possible to have Echo Speaks use the Samuel Jackson celebrity voice? I’m about ready to put a contact sensor on my fridge and want to get everyone’s attention when the door is left open!!
There may be, I remember playing with some commands you could put in the strings you sent to the device to use the different canned male and female voices available. This was back before the Samuel Jackson voice option. So don't know if that would work.
I can't remember, however, where I saw it. Someone posted something about it, I think, over at the ST forum in the Alexa speaks thread over there. I did a couple of quick searches but couldn't find it again. The list of commands was on one of the Amazon developer pages I believe.
Ok thanks for the pointers. Going to do some more research and will provide an update if I find anything.
Use the ES Actions app and set it to announcement. It works perfectly synchronously.
Thanks for the tip! I'll do this for the easy rules.
I guess I'll just confine all the other apps' notifications to one Echo Dot, if they can't speak in sync.
Looks like you didn't do this?
https://tonesto7.github.io/echo-speaks-docs/configuration/hubitat/config_server/
Does it ever actually let me use the name that I copied?
It just keeps saying name not available.
I think I got it now.
You have to paste the name, press the spacebar, and then press the back key. For some reason it doesn't recognize just pasting, it has to have that extra step of clicking forward and back once.
Download the Hubitat app
