Tinkerforge / esp32-firmware

Firmwares for ESP32 Brick and ESP32 Ethernet Brick (including firmwares for WARP/WARP2 Charger, WARP Energy Manager)
https://www.tinkerforge.com/en/doc/Hardware/Bricks/ESP32_Ethernet_Brick.html
23 stars 20 forks source link

Data Model Users - Tags - Cars #292

Open HobbyIngenieur opened 9 months ago

HobbyIngenieur commented 9 months ago

Let's see if i can get to the point in english ;-)

Looking at the data model in User- NFC-tag management, I'm missing one of the three entities: Users, Tags, Cars. Tags is obviously there. Users in my opinion could be better understood as Cars. In Terms of "Vollkostenrechnung" the (my) main interest is accumulating all charging cost to a car, not to the person who initiated charging a car. So, is Users needed at all? Sure. To authenticate - which a car can't. To be grabbed as person for returning an issued token.

To run a proper access-, key- and NFC tag-management I'd find it helpful to have something like the following: Charging a car is enabled by presenting a NFC tag to the charger. Ok. A car can have more then one NFC tag assigned (e. g. one tag at each keyring). A NFC tag is issued to a person/user, who is responsible for it. One NFC tag can have only one person responsible for it, while one person can be responsible for a number of tags.

I can imagine that this means some unpleasant changes, so for now I am happy about the exchange on my idea ;-)