Esp8622 as a access controller connected to a Wiegand26 RFI
Posted: Thu Feb 18, 2016 7:03 amHi
I am new here and to esp8266 (haven't even bought hardware yet) so be gentle:-)
I am thinking of using an esp8622 as a access controller connected to a Wiegand26 RFID reader and a relay to activate a door latch. I have found infomation about the wiegand26 and esp8266 with NodeMCU (http://www.esp8266.nu/index.php/RFID). My question is how to validate the RFID tag in a smart way.
I am planning to build multiple units, since I live on a farm and we have many exterior doors located around the permisses. I would like to limit each user (RFID tag) to only have access to specific doors. This advocates a central user database. Hence the id could be sent to a server (MQTT?) and validated, then a true/false value is returned to open the door or not. The downside is that a server shut down locks every door:-(
I therefore considered instead to download the id-list with access to the specific esp8266 and do the validation within the esp8266 itself. If the central user database is updated the access list in the esp8266's should be re-downloaded.
Is this even possible? Any thoughts?
There are probably security concerns, but I am planning to keep it local.
I am new here and to esp8266 (haven't even bought hardware yet) so be gentle:-)
I am thinking of using an esp8622 as a access controller connected to a Wiegand26 RFID reader and a relay to activate a door latch. I have found infomation about the wiegand26 and esp8266 with NodeMCU (http://www.esp8266.nu/index.php/RFID). My question is how to validate the RFID tag in a smart way.
I am planning to build multiple units, since I live on a farm and we have many exterior doors located around the permisses. I would like to limit each user (RFID tag) to only have access to specific doors. This advocates a central user database. Hence the id could be sent to a server (MQTT?) and validated, then a true/false value is returned to open the door or not. The downside is that a server shut down locks every door:-(
I therefore considered instead to download the id-list with access to the specific esp8266 and do the validation within the esp8266 itself. If the central user database is updated the access list in the esp8266's should be re-downloaded.
Is this even possible? Any thoughts?
There are probably security concerns, but I am planning to keep it local.