Did you apply the credential template to the reader?
Go to Templates-->Device Templates-->Then select the reader that you are using.
About half way down the page you will see a list of available templates on the left and the templates that the reader is using for cards on the right. Select your new Template and ADD it to the reader.
To solve this kind of issue, I try to create a credential with the correct number of bits that really receive the reader....
EX: with a KeyscanCard of 36bits a made a simply credential of 36bits and the "reader decode failed" change for ": Lookup Error Badge id ..."
Then you must match the parameters of the credential with code received (number of bit for Id code, facily code, binary, when start and stop the Id code, Most significant bit order...Etc...) You can search and see how change the Badge Id received....
Keyscan 36 bits:
Card Id 16bits, encoding binary bits 19 a 34 en “Most significant bit Order”
Facility 8 bits, encoding binary bits 11 a 18 en “Most significant bit Order”
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...