Awareness| API responses are not received from Shure devices
Learn how Shure devices handle API responses.
If you are not finding the results you need and still have questions, submit a request using the form below and our Tech Docs team will get right on it. Our goal is to provide the content you need!
Your engagement helps us create the content you need. Click here to review this article.
Table of Contents
Shure's API (for their mics and related devices) does not use the typical Linefeed or Carriage Return delimiter. Thus, any read messages received back need to be compared against the delimiter that they do use, which is ">".
In Block Controller, as one example, you would use Custom, along with ">". Then, any message comparisons should be done against the message expected minus that character (">"). The reason for this is so that the "message" includes all that is received with the exception of the expected delimiter.
The same type of consideration applies to the Text Controller component.