-
Notifications
You must be signed in to change notification settings - Fork 7
Allow access to the space via HMS if a member forgets their RFID card #52
Comments
Everything we need to implement this is already in gatekeeper firmware and the DB tables. It would just need the HMS front need to generate the correct DB record and show the pin to the user. More important thing we need to look at is any security issues around this. 'RepRap' Matt
|
Seems a pretty reasonable feature to add to me. However, I think James is/was working on a feature that would allow members to register new RFID cards themselves on Gatekeeper - which would involve giving them a PIN which can be used to register a card. As for your second plan, that's trickier and a lot more interesting. I think for that to work, HMS would need to be able to send MQTT messages, which at present it can't. However, James has written some MQTT/PHP stuff before (e.g. MQTT twitter bot), so it's definitely doable, and may find uses elsewhere. Daniel |
Possibly restrict to members who have activated at least 1 RFID card (this ensures that they have visited the space and talked to a member admin at least once). |
This is just a thought I had when I was in the city centre recently and wanted to pop into the hackspace but I had left my RFID card at home but it is equally valid if a member loses or damages their RFID card. We could implement a feature in HMS which generates a one time passcode that allow a member to unlock the door via the gatekeeper keypad.
This feature would require changes to the gatekeeper code which I know is a vital system and would need to be thoroughly tested to allow this to work.
Considerations
Alternative Approach
If we can rely on the fact that the member has a smart phone or other device connected to the HSNOTTS wifi do we even need to bother with the passcode? We could allow the member to unlock the door directly from HMS as long as they are connected to the HSNOTTS wifi. This would probably mean fewer (if any) changes to the gatekeeper code and saves the need to generate a passcode.
These are just some thoughts, I'm not expecting "yes lets go ahead an implement this" but I thought I'd get my ideas documented for future reference.
The text was updated successfully, but these errors were encountered: