Preview and Beta: Amazon Echo Control

Just wanted to make sure you saw the error log data I posted above - does it seem like I pulled the right log details to troubleshoot what is causing the issue(s)?

For the memory leak, it’s suggesting I "set the OkHttpClient logger level to FIN
E: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);" but I’m not entirely certain how one does that - do I perhaps modify a .config file somewhere?

Also, it looks like @Andrew_Rowe already helped to find a solution for this very same problem about a month ago, so I am going to try the solution in this post and see if that helps.

I do remember a while back when many of us suddenly started having rate limit issues because of too many requests for TTS in a short amount of time. I have no clue what I’m talking about, but I guess this is too many requests to retrieve the device statuses and LastVoiceCommand data from the Amazon servers? Can we slightly slow down the rate at which the system is requesting this data? Or is the issue with authentication or something like that perhaps?

One last question (sorry!) but I never really know which option to select here when setting up the Amazon Account Thing for the binding - could these settings possibly have any impact on our error?

1 Like