Nilon123456789
Nilon123456789
It the address from the advertisement that is detected as 00:00:00:00:00 even tho the advertisement address is not 00:00:00:00:00. Since I can detect it correctly with my Mac
> RPA that resolves to 00:00:00:00:00:00 I don't think so, since on my Mac I can clearly get the MAC address of my device broadcast. I will look to get...
Here is the dump. [hcidump.log](https://github.com/bluez/bluez/files/13890955/hcidump.log)
I don't know if it has something to do with it. But I can't seem to be able to enable the `LE 2M` as an entry. I tried enabling it...
I did a wireshark capture using the [nrf sniffer tool ](https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le/). You can clearly see the MAC address of the device (f0:ca:f0:ca:01:d5) [capture.pcapng.zip](https://github.com/bluez/bluez/files/13924141/capture.pcapng.zip)
So I can not read/receive extended advertisement packet using bleak?
Is there a way to fix the issue? Do we need to downgrade BlueZ to an earlier version?
The device is sending a MAC address since I can see it on MacOS
I'm able to get RTT logs with the version `0.34.3`. However, I still can not flash.
Here is the output of the `pyocd erase --mass` followed by the output of the flash. ```log erase --mass -t nrf52833 -v 0002821 I Target type is nrf52833 [board] 0002870...