Documentation

[vrelk]

While this is still heavily a work in progress, can we get some extra documentation, such as Airtable format?

While I know it isn't complete, and is missing fields to be added later, here is what I have worked out for anyone wishing to try it.
Note: Make the Devices table first.

Table: Devices
    Fields:
        Name: Single line text

Table: Tags
    Fields:
        UID: Single line text
        Name: Single line text
        Enabled: Checkbox
        Devices: Link to another record
            Table To Link: Devices
            Allow linking to multiple records: Enabled
            Limit record selection to a view: Default/Disabled

Note: For anyone that also runs a local nginx webserver, this should help you get around the HTTPS issue by creating an HTTP version of it.

server {
    listen 80;
    listen [::]:80;

    server_name airtable.example.com;
    
    location / {
        proxy_set_header Host api.airtable.com;
        proxy_ssl_verify off;
        proxy_pass_request_headers on;
        proxy_pass https://api.airtable.com;
    }
}

[iBobik]

Hello,
I stopped development on this, but kept it in repository so someone can take care of it if it makes sence.

I used this database: https://airtable.com/invite/l?inviteId=invTyk0Vs5j4osCW1&inviteToken=32d7ad898dea8c476786018beb716bbd107b70ca61fd3d5883dc47a15baed1a2

Thank you for proxy config, could be useful for someone.

---

Btw, I am working on a Django app for managing multiple controllers:
Wireframe.pdf

If you are interested in joining, let me know.

[vrelk]

Unfortunately I'm not a Python person. If you are working on that app, what are you planning on using as a controller if you stopped this project? I like the idea that the heavy lifting is done elsewhere over bogging down the system like the main esp-rfid project This isn't really the kinda of thing you want to have to wonder if it's going to work or not (I don't use it for a house or anything, just something that can be a PITA to get into if it breaks). (Honestly, for my purposes I'd be happy with this one as-is if it supported pin entry. I'm just unsure how to do that.)

I don't see it in that screenshot, or in this project, but pins. Would like to see pins (mainly independent, but also an option to enter a pin after scanning a fob). Something to add down the to-do list maybe.

[iBobik]

This project is still based on esp-rfid-py - it just sync tags databases between server and door controllers, so they will work when network is broken. I do not plan to implement PINs, but I can implement it for you commercialy. Jan Pobořil https://honza.poboril.cz/

…

13. 9. 2020 v 3:52, Controller Vrelk ***@***.***>:  Unfortunately I'm not a Python person. If you are working on that app, what are you planning on using as a controller if you stopped this project? I like the idea that the heavy lifting is done elsewhere over bogging down the system like the main esp-rfid project This isn't really the kinda of thing you want to have to wonder if it's going to work or not (I don't use it for a house or anything, just something that can be a PITA to get into if it breaks). (Honestly, for my purposes I'd be happy with this one as-is if it supported pin entry. I'm just unsure how to do that.) I don't see it in that screenshot, or in this project, but pins. Would like to see pins (mainly independent, but also an option to enter a pin after scanning a fob). Something to add down the to-do list maybe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.