Feature request: 2022 NFC Reader: More supported tags? Mifare classic?

[ORelio]

Hi,

What are supported tags for 2022 NFC reader besides Zstamps? I'm currently not sure of the benefit of the new NFC card compared to the original one. Would it be possible to add some common iso14443 tags such as Mifare classic?

After reading #408, it seems like common tags such as mifare classic are not handled, but I thought handling more tag types was the point of the new NFC reader, as stated here:

Nous avons donc conçu une carte NFC pour permettre au possesseur de Nabaztag première génération de bénéficier des nouvelles fonctionnalités autour des tags NFC (il n'y avait pas de cartes RFID sur les premiers Nabaztag) et au possesseur de Nabaztag:tag (la seconde génération, vous suivez ?) de remplacer la carte RFID actuelle pour lire un plus grand nombre de format de tags NFC (carte Navigo par exemple) tout en étant compatible avec les Ztamps.
https://fr.ulule.com/l-eternel-retour-du-nabaztag/

English translation of the quote above:

We therefore designed an NFC card to allow the owner of the first generation Nabaztag to benefit from the new functionalities around NFC tags (there were no RFID cards on the first Nabaztags) and the owner of Nabaztag:tag (the second generation, are you following?) to replace the current RFID card to read a larger number of NFC tag formats (Navigo card for example) while being compatible with Ztamps.

It seems like the main issue with supporting more tags is about writing to the tags, quoting @pguyot:

We definitely do not want to write Navigo cards. [...] Mifare Classic cards are encrypted with a proprietary protocol [...] URL is too long as it embeds the API key and it does not fit ST25 512 bits RFID tags sold by Violet
#408 (comment)

Since writing to the tags seems difficult, why not just store a local configuration file mapping tag UID to desired action? This way, no need to write to the tag. The NFC configuration page already shows the UID for the tags I tried. Also, I think such configuration file already exists for webhook URLs since the field is empty when scanning a webhook tag on another rabbit, whicjh means the rabbit itself stores the URL, not the tag.

Is your feature request related to a problem? Please describe.
I'd like to use the tag already present on my keychain (vigik badge) but mifare classic tags are not handled.
Additionally, sourcing adequate ztamp tags is harder and more expensive than modern tags.

Describe the solution you'd like
I'd like support for mifare classic tags as they are cheap and widespread compared to zstamps.
You can easily buy cheap mifare classic tags in various forms such as sticker, badge, keychain, etc.
I would not mind if configuration is stored on the rabbit instead of the tag, as I could configure each individual rabbit.

Describe alternatives you've considered
Adding an additional zstamp tag on my keychain, but it's less convenient and fragile as I only have them as stickers.

Additional context
See #408 and https://fr.ulule.com/l-eternel-retour-du-nabaztag/.

Thanks for your work on this project! 👏

[ORelio]

Got tired of waiting for an answer, so I wrote the following service to circumvent the issue, as suggested by @pguyot in issue #408:

https://github.com/ORelio/Rabbit-RFID

Basically, it listens for rfid events in nabd, and maps tag IDs to actions using a configuration file, for example calling a Webhook URL. Thanks for writing a clear documentation for nabd!

Note: My understanding of the codebase is still too limited to integrate with Web-UI or replace existing code. Nabaztag are great, too bad this repository has gone inactive.