BLE Xiaomi sniffer not working more about mpyeasy HOT 6 CLOSED

Second beta published. memoryview is now converted to other types.
https://github.com/enesbcs/mpyeasy/releases/tag/1.0.004

from mpyeasy.

Is working now stable again since yesterday evening. Will tell you...

from mpyeasy.

Interesting. It looks like that "def decode_xiaomi(buf)" function tries to reach an index behind the buffer... can you narrow this error to a type of device? Lywsd02/Lywsd03/ATC... or what can be the one, who are sending smaller packages?
This function is the same as the RPIEasy version - although micropython works a bit differently.

from mpyeasy.

Have removed all devices, enabled FlowerCare only - same result (after reboot)
Have removed all devices, enabled LYWSD02 only - same result (after reboot)
Have removed all devices, enabled CGG1 only - same result (after reboot)

Same also after power on/off, tested again with LYWSD02.

LYWSD02 with connection will work (if all sniffing devices disabled)

What I have seen, if I disable all "sniffing devices" and have only the system available (or additional BLE device with connection (LYWSD02) ) - still the scan process will be started until reboot.

from mpyeasy.

Have removed all devices, enabled FlowerCare only - same result (after reboot)
Have removed all devices, enabled LYWSD02 only - same result (after reboot)
Have removed all devices, enabled CGG1 only - same result (after reboot)

I have no idea. In the next release, buffer content will be printed.

What I have seen, if I disable all "sniffing devices" and have only the system available (or additional BLE device with connection (LYWSD02) ) - still the scan process will be started until reboot.

Scan process will never stop if started, it is by design. Different tasks do not check each other to know if it is the last one running.

from mpyeasy.

13:47:25.120 -> decode xiaomi error memoryview index out of rangescan pause

The problem is that i was used micropython 1.12 on my development device, and compiled against micropython 1.13... for a reason a few API changed in between.. and now memoryview type returnes some places, which is a major headache to me, as behaving differently compared bytes, bytearray or simple arrays.

from mpyeasy.