I play with pca10040 and the light-switch example from SDK for Mesh v1.0.1.Everything works but I wonder why the advertising signalsare not seen by nRF-Connect Scan.
As I used SDK for Mesh v1.0.0 (but with MtConnect05) I could seethe advertising.
My questions:1. Why is the advertising packets are not detected anymore?2. How could I detect them from a Rasperry Pi3 and Android?
Hi, if you're using Android 8 or newer it disregards packets that contain errors, for example extra 0s at the end of an advertisement packet. You could try on an older phone if that's the case.
You may also use nRF Connect for desktop to check if your device is advertising and with what data exactly.
thanks for your answer. My phone is on Android 7.0. I can detect the advertising signals with another pca10040 but it would be nice to detect it from my phone or (better) from a Raspberry Pi.
Bluetooth Mesh uses Advertising Data types (AD types) in the advertising packet that has been assigned for the Mesh Profile Specification. For devices that do not have support for Bluetooth Mesh those AD types are unknown, and it looks like some systems may choose not to relay the advertising packet to applications in such cases.
There is very little change from version 1.0.0 to version 1.0.1, and none that should affect advertising. That means you probably see exactly the same both for v1.0.0 and v1.0.1 if you use the same device for scanning. I.e. it all probably depends on how the device handles advertising packets that are formatted in an unknown way.
I do have a couple of questions back. For what purpose are you detecting the advertising packets from an rPi3 or Android device? Perhaps we might have some other suggestions for how to achieve your end goals here.
I'll add some support for mesh in the next release.
Records won't be unknown EIRs anymore.