FR: support for adding RFID tags

[RichieB2B]

As previously requested in #333

This endpoint writes a new RFID tag:

POST /api/v1/config/auth/standalonelist HTTP/1.1

{"RfidTokenUid":"0123456789ABCD","RfidTokenDescription":"My Charge Card"}

This endpoint returns the list of tags:

GET /api/v1/config/auth/standalonelist HTTP/1.1

{
	"Tokens" : 
	[
		{
			"RfidTokenDescription" : "My Charge Card",
			"RfidTokenUid" : "0123456789ABCD"
		}
	]
}

Removing a single tag:

DELETE /api/v1/config/auth/standalonelist/0123456789ABCD HTTP/1.1

There is a working PR for this feature in #349

[frenck]

The problem with exposing management functions like these is that they affect volatile memory (flash), which has a limited lifespan caused by the number of write cycles. Exposing this through (for example an Home Assistant integration, or script that tries basically to make time-based access or similar) that could potentially write to it frequently (or even periodically) would risk wearing out the charger's storage prematurely.

This is an actual concern raised by the Peblar engineers themselves, which has honestly withheld me from exposing everything the API technically offers.

../Frenck

                       

Blogging my personal ramblings at frenck.dev

[RichieB2B]

Personally I don't see a scenario where someone would write so many RFID tags that it can wear out a flash chip.

Would adding a warning or "are you sure" step be sufficient to address these concerns?

[frenck]

Personally I don't see a scenario where someone would write so many RFID tags that it can wear out a flash chip.

I'm not sure what you relation ship with Peblar is (maybe you designed their harware, I don't know...), but... if they raise this as a concern in their early communications, I take it seriously. Unless you have more technical details that I'm lacking; I suggest to take them seriously.

../Frenck

                       

[RichieB2B]

I am just a simple Peblar end user. Flash chips typically support a minimum of 10.000 write cycles per cell. I can understand Peblar trying to protect their fragile hardware but it sounds a bit overcautious to me. Granted, writing repeatedly to non-volatile memory on purpose could cause permanent damage. IMHO any safeguards to prevent this should be built into the product, not an API library or cli tool.