Once the iRFiD plugin installed and the first RFiD tag associated, What's happen if you try to create a new plugin instance and try to associate it with a second RFiD tag? (I've a Benext keypad but no RFiD tag to make this test)
I dont think it will work, unless it is possible to change the plugin itself. Because i am guessing it is the plugin itself that sets the UID + the RFiD tag code it read.
This is what i read in the BENEXT manual for the keypad.
After sending a User Code Set, including a unique User Identifier (UID), the in-use state (0x01) and the Tag code or keypad sequence using ASCII codes, the Tag Reader will accept the codes and notify any other device using the Alarm command class.
This other device can be configured using the Association command class and is typically the same controller or Gateway. When a tag or code is not known to the Tag Reader, it will send an unsolicited report to the devices in its association group with the UID 0x00. The value in this message can be used to configure new tags.
So if i understand what happens is, is that the TAG READER plugin, listens to the KEYPAD device instance in vera. as you point the plugin to that device #nr.
When you press "HOME" on the keypad and swipe the tag, the keypad dont recognise the tag, sends the code to the device in vera with the UID 0x00, the TAG READER plugin trigger the device to program in code slot #1 with UID "Code 1 ()" and the TAG?s unique code.
So i am guessing basically the plugin itself has to be rewritten to send another UID and code slot. OR even better if the plugin were proper it would query the device for the next empty code slot. As the diagram in the attached PDF shows on page 10 diagram of the manual here.http://www.benext.eu/en/products/tag-reader/
(pdf is to large and i cant compress it to attach)
The _iRFiD device can input codes and will fill codes from 1 and upwards infact all the way up to 255 basically. Shouldnt the same work with RFiD tags?
I dont have the vera luup skills myself to make a proper plugin unfortunately.
Zipato fully support this device, there you can add as many tags as you wish basically, just as i mention above you can send a UID + code with the command. So i think it is first veras support for the device. secondly the plugin which is kind of a "fix" for lack of support for the RFID part of the device. Which isnt quite doing what it could do.
I am looking at the luup script of I_iRFiD.xml atm but i dont quite understand how it takes code slot #1 and sends UID "Code 1 ()".
I ill put some time into it this weekend again, getting jelly brain atm
Been at it for 8 hours with short dinner break.