I'll ask one of the developers if they can take a look at this for you.
1 of 1 people found this helpful
If you set permission as Authenticated Read the stack will check that link is encrypted before replying to the Read request. Either client or server can initiate security. On the peripheral side you can call
lesmp_sendSecurityRequest(); at the time connection is established. On the central side you can do
lesmp_startPairing which will perform pairing if needed and will initiate encryption procedure.
could you help me understand?
Do you mean that the reason is unneeded encryption?
I saw the conn-up and bonded message with hello-sensor board and mobile phone.
When I try to read the characteristic on mobile screen, authenticated-read type was not available for read.
After I changed the characteristic from authenticated read to read, then I could read the characteristic.