This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

PyACI showing wrong unprovisioned UUID

Hi @ll,

I have the following problem:

There are three unprovisioned devices with UUIDs containing a 0x0A byte but the scanner within the pyaci script shows 0x00 instead.

Device Print:

BLE Sniffer:

PyACI:

I verified this using a BLE sniffer and also by implementing an Android code-snipped that scans for unprovisioned mesh beacons.

As you can see both, the device and the ble scanner say it's a 0x0A but the python console says it's a 0x00. This is the for all devices with UUIDs containing 0x0A.

Is this a problem in the python script or the serial example?

I'm using Mesh SDK version 2.0.0 but it's still the same in version 2.1.0.

Thank you in advance for the information!

Bye
Andrej

Parents Reply
  • Ok just found out that it's the SerProxy I have to use to forward my Windows-Serial-Port to Linux over ethernet because otherwise I'm getting these annoying Timeout issues for the serial example and serial dfu does not work at all.

    But by now I can use my Android-App for scanning or verifying the UUID.

    It would be great if your toolchain and scripts would be fully supported and tested under Linux.

    Thank you for your time and support.

    Bye
    Andrej

Children
No Data
Related