<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>BLE Sniffer shows ATT write but no UUIDS?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/86576/ble-sniffer-shows-att-write-but-no-uuids</link><description>Hey, 
 
 I&amp;#39;m trying to follow a few guides on sniffing BLE connections (eg https://hackaday.com/2021/03/23/a-crash-course-on-sniffing-bluetooth-low-energy/ ) with an NRF52-DK (I have dongle and DK) and I have everything configured in a similar manner</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 16 May 2024 02:12:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/86576/ble-sniffer-shows-att-write-but-no-uuids" /><item><title>RE: BLE Sniffer shows ATT write but no UUIDS?</title><link>https://devzone.nordicsemi.com/thread/484594?ContentTypeID=1</link><pubDate>Thu, 16 May 2024 02:12:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e064af91-81a6-4ed0-890a-fc7ed9038920</guid><dc:creator>bao008</dc:creator><description>&lt;p&gt;I have also encountered this problem. My 52832 is connected to BLE4.0, and the MTU is 23B. How did you solve it? Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Sniffer shows ATT write but no UUIDS?</title><link>https://devzone.nordicsemi.com/thread/361782?ContentTypeID=1</link><pubDate>Tue, 05 Apr 2022 09:33:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:660bafc4-971d-48fb-8996-4a81022390b4</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;The sniffer will typically only show what is on-air, and the UUID is not sent on-air during normal write, read and notifications. However I do believe that if during the same connection there was a database discovery prior, the sniffer software may be able to find which UUID the handle belong to, and display it alongside the handle.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Sniffer shows ATT write but no UUIDS?</title><link>https://devzone.nordicsemi.com/thread/361608?ContentTypeID=1</link><pubDate>Mon, 04 Apr 2022 17:22:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d1f6db67-20cd-4f5e-8323-139b4650e9dc</guid><dc:creator>AndrewMohawk</dc:creator><description>&lt;p&gt;Hi Kenneth,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I am not following how this would relate to why I dont see the UUIDs. If you look at this guide here:&amp;nbsp;&lt;a href="https://daniellethurow.com/blog/2021/9/22/using-adafruits-bluetooth-sniffer"&gt;https://daniellethurow.com/blog/2021/9/22/using-adafruits-bluetooth-sniffer&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;You see the following screenshot (and is similar across many other guides as well):&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1649092927164v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Sniffer shows ATT write but no UUIDS?</title><link>https://devzone.nordicsemi.com/thread/361511?ContentTypeID=1</link><pubDate>Mon, 04 Apr 2022 12:31:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3e3e4a66-37a3-4361-940e-efc8f93c928d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;The GATT database server will have a lot of services and characteristics with different UUID&amp;#39;s. Typically when a peer is doing a database discovery it will receive all the UUID&amp;#39;s with a unique 16-bit handle for each &amp;quot;entry&amp;quot; in the GATT database, the handle is typically an incrementally ordered value for each service and characteristic in the GATT database. All communication (write, read, notifications) will be done using the 16-bit handle, this according to BT specifications.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>