RE: rc522 not reading id from PICC compliant with ISO/IEC 14443-4 cards

[Philip Knowles]

Phones deliberately give a different ID every time as a security feature

 

Sent from Mail for Windows

 

From: FransOv
Sent: 06 August 2022 09:58
To: TasmotaUsers
Subject: rc522 not reading id from PICC compliant with ISO/IEC 14443-4 cards

 

I have an rfid reader MFRC522 to switch on/off the office alarm system. Works fine, but I would like to use my phone instead of the supplied Mifare 1KB tags. The reader detects the phone, successfully identifies the type of nfc chip but does not read the ID as I get a different value on every read.

The result is like:

"RC522":{"UID":"083CDA4A","Type":"PICC compliant with ISO/IEC 14443-4"}

 

 I tried with other cards such as the Dutch public transportation card (MiFare 4KB): ID read OK, my driver license: same result as my phone and my bank card: card not detected.

 

Anyone know How to get the rc522 to read the id of the PICC compliant with ISO/IEC 14443-4 cards?

--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/45cc43dd-12e1-434f-883b-48932732b104n%40googlegroups.com.

 

[Frans Overkleeft]

Thank you for the info. I was reading on and found some articles that explained that the changing uid was  by design and therefore that basing access control on the uid of nfc tags is a bad idea. That's why I withdrew my question.

Frans Overkleeft
Diessenseweg 24
5081 AJ Hilvarenbeek
tel.: +31 (13) 505 1841
mob.: +31 (6) 5322 3860
email: frans.ov...@overkleeft.nl

---

From: Philip Knowles <knowles...@gmail.com>
Sent: Saturday, August 6, 2022 5:15:28 PM
To: FransOv <frans.ove...@gmail.com>; TasmotaUsers <sonof...@googlegroups.com>
Subject: RE: rc522 not reading id from PICC compliant with ISO/IEC 14443-4 cards