> 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.

| URC            | Description                                  |
| -------------- | -------------------------------------------- |
| `+EMQ:`        | Reports data received on a subscribed topic. |
| `+EMQPERSIST:` | Reports a cloud persistence-service change.  |

`+EMQ:` identifies a `singletopic` message with `S`, or a subscribed topic with its index. The response includes the data length and content. The `urcautoformat` setting controls whether the content uses ASCII-hex or text. See [EMQ – publish a message to singletopic](/smartconnect/at-command-reference/mqtt-at-commands/emq-publish-a-message-to-singletopic.md) and [Using the AnyNet SMARTconnect™ configuration file](/smartconnect/getting-started/using-the-anynet-smartconnect-tm-configuration-file.md).

In simple `AWSSHADOW` mode, `+EMQPERSIST:` returns changed values. In complete mode, it returns the complete JSON message:

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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eseye.com/smartconnect/at-command-reference/mqtt-at-commands/+emq-unsolicited-response-codes-urcs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.