TG-BT5 Bluetooth tag - breaking change in latest firmware

Hello!
As per the changelog entry:
https://help.mikrotik.com/docs/spaces/UM/pages/215351328/MikroTik+Bluetooth+TG-BT5-XX+tag+changelog

Include ad flags field in all advertisements.
New “octets” are now displayed in front of the payload. We will update the “format” guide shortly.

“020106” will be added now in front of the payloads. Those octets represent “flags” field:
https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/CSS_v11/out/en/supplement-to-the-bluetooth-core-specification/data-types-specification.html
which simply “indicate” that the flags fields “length” is “02”, type is “01” and data is “06” (which, frankly, only tells surrounding devices that it is “LE” and “discoverable”).

You can, simply, interpretate those octets as a new “static” octets that you do not have to “pay attention” to. There is not much useful information in those.
We’ve made the decision to add the “flags” field because other vendor scanners might not pick up the payload (drop it) if the “advertisement” does have this field in it.

Unfortunately, you will have to rewrite scripts (if you use them to collect Bluetooth information from the tags). If the script is used to “pick” specific “octets” from within the Bluetooth payload, they have to be shifted slightly by 3 octets.