Api key / Usage Limits
I really don’t understand the introduction and application of the api key. Can you pls help with a couple of queries please?
(1) the whole process is quite ‘long tail’, ie it takes a finite time to complete and while it’s in process you cannot (rightly so) trigger another audio notification. The api uses a result code 409 to indicate this contention state and handling against this code is a useful way of slugging the users app to retry until the speaker is free to handle the next notification. The trouble I see is that any call to the api to check for 409 counts as one call against the 100 limit even though a notification was not executed. Is this the case?
(2) what is the thinking behind the inconsistency of application between the control api and the audio notification api? One uses it, the other doesn’t.
(3) my speaker is in my network and a call to the api does not hit or impact your cloud app? The speaker itself does not seem to be impacted by frequent calls, not a blink. In which case what are you trying to protect or monetise?
(4) how would you count one functional request made to 3 speakers? The way I see it you cannot call a group so it comes out on all speakers. So we have a 3 times hit on the 100 limit even though I am spreading whatever risk you are trying to mitigate across 3 devices. This seems draconian and will only further put off the home automators.
I had great expectations for this, and indeed developed some interesting trials with audio now playing announcements, environment sensor read outs etc but starting to think Soundtouch may not be the way forward given the constraints.