# Receive Numerics with BLE **URL:** \ **Category:** Questions about Thunkable X\ **Created:** [May 11, 2021, 9:29pm UTC](https://community.thunkable.com/t/receive-numerics-with-ble/1277173 "2021-05-11T21:29:06Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [April 13, 2022, 4:57am UTC](https://community.thunkable.com/t/receive-numerics-with-ble/1277173/8 "2022-04-13T04:57:27Z")
When you say “unreadable”… what is the exact Hex you are seeing? I spent some time learning to parse hex codes here: > [@A brick wall that i've smacked into with hex codes](https://community.thunkable.com/t/a-brick-wall-that-ive-smacked-into-with-hex-codes/1068428/13): > > Right but you’re not getting 0x0FA0 from a physical device/sensor, are you? You’re getting a value like 41 0C 0F A0, right, according to the updated “Reading Real-Time Data” link you posted? Just trying to understand the starting and ending points. Because if you have a device that gives you 0x0FA0, that’s going to be a different set of steps in Thunkable compared to the steps you’d need if you’re given 41 0C 0F A0. By the way, the 0x0FA0 is just the last four digits of 41 0C 0F A0. If you join… But as far as your question about converting letter to integers, I’m not sure how to do that. I doubt it’s difficult but I’m not at my computer so I can’t work on a demo at the moment. --- _[View the full topic](https://community.thunkable.com/t/receive-numerics-with-ble/1277173)._