This mostly just adds logging, but also rolls in some changes that were achieved through Eli and Max's debugging work. The log file should be configurable by changing the value in /etc/rfidlock/config.json, but I haven't tested that yet.
I've tested this on the Raspberry Pi and everything works correctly.
One major point to note:
When the RFID tags are read, 8 characters, the fourth to the eleventh are read which contain the hexadecimal form of the number printed on the tag. This string of 8 characters is then md5 hashed and stored in base64 encoding. If using the decimal form to obtain the hash, the decimal form must be first converted to hexadecimal and padded with leading zeroes to reach a length of 8 before being md5 hashed.
Also, for future reference of those deploying this code, the repository can be pulled from the internet by the server, then pushed to the client
This mostly just adds logging, but also rolls in some changes that were achieved through Eli and Max's debugging work. The log file should be configurable by changing the value in /etc/rfidlock/config.json, but I haven't tested that yet.
I've tested this on the Raspberry Pi and everything works correctly.
One major point to note: When the RFID tags are read, 8 characters, the fourth to the eleventh are read which contain the hexadecimal form of the number printed on the tag. This string of 8 characters is then md5 hashed and stored in base64 encoding. If using the decimal form to obtain the hash, the decimal form must be first converted to hexadecimal and padded with leading zeroes to reach a length of 8 before being md5 hashed.
Also, for future reference of those deploying this code, the repository can be pulled from the internet by the server, then pushed to the client