Vusion.nfc.txt
What i expected to happen
I wanted to add my ESL tag as a target in Targeted Payloads so I could send it a custom image, either via NFC Tag Scan or barcode entry.
What actually happened
Neither identification method works for this tag:
NFC Tag Scan doesn't recognize it
Barcode entry doesn't work either — the barcode printed on this tag doesn't match the format the app expects
As a result I can't create a target entry at all, regardless of which display profile I'd pick — I'm fully blocked, not just missing an image profile.
Tag details
Model: SES-imagotag / VUSION 2.2" BWR GL340 — FCC ID 2ACQM-EDG2-0220-A
Resolution: 212×104 px
Active display area: 48.6 × 23.8 mm
Color: black/white (no accent color)
NFC chip: NTAG I2C Plus 1K, UID D024C54A
IFETEL: RCPSEED19-1896C
Questions
Is there a manual/fallback way to add a target without NFC or barcode (e.g. a broadcast or diagnostic mode), for cases like this where identification fails?
Would adding this model's NFC UID pattern and/or barcode format to the recognition tables be feasible? Happy to provide more scans/photos if useful.
Flipper firmware: Official firmware, latest release channel
Vusion.nfc.txt
What i expected to happen
I wanted to add my ESL tag as a target in Targeted Payloads so I could send it a custom image, either via NFC Tag Scan or barcode entry.
What actually happened
Neither identification method works for this tag:
NFC Tag Scan doesn't recognize it
Barcode entry doesn't work either — the barcode printed on this tag doesn't match the format the app expects
As a result I can't create a target entry at all, regardless of which display profile I'd pick — I'm fully blocked, not just missing an image profile.
Tag details
Model: SES-imagotag / VUSION 2.2" BWR GL340 — FCC ID 2ACQM-EDG2-0220-A
Resolution: 212×104 px
Active display area: 48.6 × 23.8 mm
Color: black/white (no accent color)
NFC chip: NTAG I2C Plus 1K, UID D024C54A
IFETEL: RCPSEED19-1896C
Questions
Is there a manual/fallback way to add a target without NFC or barcode (e.g. a broadcast or diagnostic mode), for cases like this where identification fails?
Would adding this model's NFC UID pattern and/or barcode format to the recognition tables be feasible? Happy to provide more scans/photos if useful.
Flipper firmware: Official firmware, latest release channel