# Issue with confirmed messages

**URL:** <https://www.thethingsnetwork.org/forum/t/issue-with-confirmed-messages/33112>\
**Category:** How to get started\
**Created:** [January 3, 2020, 5:25pm UTC](https://www.thethingsnetwork.org/forum/t/issue-with-confirmed-messages/33112 "2020-01-03T17:25:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [January 3, 2020, 6:04pm UTC](https://www.thethingsnetwork.org/forum/t/issue-with-confirmed-messages/33112/4 "2020-01-03T18:04:29Z")

</div>

> [@fhander](#):
>
> I don’t know how the interpret the messages as confirmation messages.

Either [decode the full LoRaWAN packet](https://www.thethingsnetwork.org/forum/t/what-are-these-port-0-downlink-messages/22330/4) that you see in the gateway’s Traffic page (like in your screenshot). Or look at the application’s or device’s Data page, so see TTN Console already giving you some more descriptive details about the downlink.

Given the size of 22 bytes, it’s not just a confirmation for sure.

By the way: I wonder why all downlinks are on SF12, and use the same frequency. Is the node set to use a single frequency? And why SF12?

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/issue-with-confirmed-messages/33112)._