There was a typo in his post, has 209 when it should have ben 299. I just edited it and fixed it up above.
3 Likes
I should have caught that as well. Thanks. Looks like it fixed mine as well.
@thebearmay Thanks again.
Spoke too soon, still getting it.
Try this. Comment out line 3041.
1 Like
Looks like that did it. Thanks!!
1 Like
So which is it (or both?)
1 Like
Comment out line 3041.
2 Likes
To make sure I changed line 3072 back to the original and left line 3041 commented out and still no longer getting the warns.
1 Like
Good day all,
I am having an issue where I am able to successfully authenticate but it is not finding any devices from alexa.
Below are the logs, It looks like it is looking for a host it cannot find.
Original AppCallBackURL:
https://cloud.hubitat.com/api/XXXXXXXX-da56-4555-820d-3efe838c0c7b/apps/62/receiveData?access_token=XXXXXXXX-ca24-4702-a9db-61db36d5c16a
New URL based on the documentation in the link below.
http://192.168.15.XXX/apps/api/62/receiveData?access_token=XXXXXXXX-ca24-4702-a9db-61db36d5c16a
Documentation link:
https://community.hubitat.com/t/guide-echo-speaks-server-on-docker-or-without/111186#p-1014501-hubitat-app-login-7
I configured a local echo speaks server using this method below and that process works and the hubitat sees that it authenticates properly as seen in the first image above.
Any thoughts what the issue could be?
Alexa has been having problems the past few days. Perhaps she is upset that she wasn't invited to Jeff Bezos' wedding. She was down for me all yesterday, but came back overnight.
Here is the current map:
Remember that AWS was formed because of extra compute that they had during off sales seasons. I guess Prime day/week was a big hit this year because of their outage along with Lutron and many others too.
2 Likes
I fought with mine but won eventually. I'm just seeing a terrible delay (over a minute) for announcements using the docker vs Heroku.
Docker/Heroku is only used to update the cookie - you have a problem somewhere else…
4 Likes
That's helpful in understanding the pathing.
Seems tied to zones. If I go directly to an Echo device it works great. If I go to a zone, it plays the echo devices consecutively (it use to play in parallel previously). Need to dig in closer.
UPDATE: I don't actually know why... but the delay is gone, the options for parallel play, speak, etc. have all returned. Really odd - but it's resolved!
3 Likes
I'm getting this every 15 minutes...but ES is working.
why am i constantly getting this message in the logs.. do i need to go to git hub and update something
i dont see a new version already running what looks like the latest?
/************************************************
//* STATIC VARIABLES *
//************************************************
@Field static final String appVersionFLD = '4.2.4.0'
@Field static final String appModifiedFLD = '2024-03-07'
@Field static final String gitBranchFLD = 'master'
Haven't seen that here. Did you manually change anything in the code? If I'm seeing that right, looks like it's complaining about echoDevice.
NOT THAT i know of.. i have put comments in to see which diff it is complaining about.. i will also do a diff between files.
You can always try to do a repair on Echo Speaks via Hubitat Package Manger.
