> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/smartconnect/at-command-reference/mqtt-at-commands/+emq-unsolicited-response-codes-urcs.md). # +EMQ Unsolicited Response Codes (URCs) When the MQTT broker publishes data to your thing, AnyNet SMARTconnect™ forwards the data through the AT command interface using an appropriate URC. If the data buffer contains only printable characters, it is presented unmodified. This makes transfer of JSON and ASCII text transparent. If non-printable characters are contained in the buffer, the entire buffer is converted to ASCII-hex and sent within quotes.
URCDescription

+EMQ: <S>,<len>\r\n<data>

or

+EMQ: <id>,<len>\r\n<data>

Indicates data received on a subscribed topic, where:

  • S is for singletopic only. Indicates data received on a single topic. For information about singletopic, see EMQ – publish a message to singletopic.
  • <id> is the subscribed topic index number, not for singletopic use
  • <len> is the length of the incoming data

  • <data> is the received data in either ASCII-hex format or as text, depending on both the urcautoformat setting in the configuration file, and if <data> appears within quotes.

    For example, if the urcautoformat setting = 1, then:

    • <id>,<len>\r\n"<data>" reports data in ASCII-hex format
    • <id>,<len>\r\n<data> reports data in text format

    For more information, see Using the AnyNet SMARTconnect™ configuration file.

+EMQPERSIST: <len>

<JSON>

Reports a message from the cloud service indicating something in the persistence service has changed.

For simple AWSSHADOW mode, only the '{"state":{...' parameters that have changed in the AWS delta are listed.

For example:

+EMQPERSIST: {"key1":"value1","key2":"value2"}

where value1 and value2 are any type of value, including strings, integers, decimals and negative numbers.

For complete AWSSHADOW mode, the entire JSON is listed.

For example:

+EMQPERSIST:{"version":186201,"timestamp":1573232068,"state":{"key1":"value1","key2":"value2"},"metadata":{"key1":{"timestamp":1573232068},"key2":{"timestamp":1573232068}}}

where value1 and value2 are numeric values, including decimals and negative numbers.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.eseye.com/smartconnect/at-command-reference/mqtt-at-commands/+emq-unsolicited-response-codes-urcs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.