chore: Update readme

Author: nickknissen

README.md

@@ -9,14 +9,14 @@
 
 _Integration to integrate with [monta][monta]._
 
-**This integration will set up the following platforms.**
+**This integration sets up the following:**
 
-Platform | Description
+Platform | Entities
 -- | --
-`binary_sensor` | Show something `True` or `False`.
-`sensor` | Show info from Monta API.
-`switch` | Switch something `True` or `False`.
-`services` | `start_charging` and `stop_charging``
+`binary_sensor` | Cable Plugged In
+`sensor` | Charge point Visibility, Type, State, Last meter reading (kWh), Last Charge (with attributes), Personal Wallet amount, Latest Wallet Transactions
+`switch` | Charger Start/Stop
+`services` | `start_charging` and `stop_charging`
 
 ## Installation
 
@@ -59,6 +59,52 @@ Client id and secret are obtained from https://portal2.monta.app/applications.
 
 <!---->
 
+## Rate limiting and update cadence
+- The integration respects Monta Public API rate limits and HTTP 429 responses.
+- On 429, it reads `context.rateLimitResponse.resetsIn` from the response JSON body and backs off accordingly. It does not rely on `Retry-After` or other rate-limit headers.
+- To reduce bursts:
+  - Charge points are fetched at setup and cached, then refreshed infrequently (default every 60 minutes).
+  - Wallet and transactions refresh every 5 minutes by default.
+  - Charges (latency-sensitive) refresh every 30 seconds, staggered across multiple charge points to stay well under quota.
+- When backing off due to a 429, you will see an INFO log and the coordinator temporarily increases its update interval (capped at 5 minutes) and then recovers automatically.
+
+## Entities and services
+
+- Charge point sensors
+  - Visibility: `public` or `private`
+  - Type: `ac` or `dc`
+  - State: charger state (enum)
+  - Last meter reading: cumulative energy (kWh)
+  - Last Charge: exposes latest charge state; attributes include timestamps like `startedAt`, `stoppedAt`, etc.
+- Wallet sensors
+  - Personal Wallet amount (with `credit` attribute when available)
+  - Latest Wallet Transactions: attributes include a parsed list of recent transactions
+- Binary sensors
+  - Cable Plugged In
+- Switches
+  - Start/Stop charging
+- Services
+  - `monta.start_charging` and `monta.stop_charging`
+    - Both accept a `charge_point_id` (select your charger device in the UI Service call dialog to populate it)
+
+## Development
+
+- Quick test: `scripts/develop` launches HA with this integration and local `config/`.
+- Setup tooling: `scripts/setup` installs Python deps (HA, Ruff, etc.).
+- Lint: `scripts/lint` runs Ruff checks and autofixes style.
+- In HA UI, add the Monta integration and supply Client ID/Secret.
+- Validate that entities appear and update; watch logs for any rate-limit backoff messages.
+
+## Troubleshooting
+
+- 429 Too Many Requests
+  - The integration automatically backs off based on Monta’s `resetsIn` hint and resumes normal cadence afterward.
+  - You may see: `Rate limited by API. Backing off update interval to …` in logs.
+- Authentication
+  - If credentials are invalid or tokens expire, HA will surface a config entry auth error; reconfigure the integration.
+- Privacy
+  - Access/refresh tokens are stored using HA’s Storage (`.storage/`) and sensitive fields are redacted from logs.
+
 ## Contributions are welcome!
 
 If you want to contribute to this please read the [Contribution guidelines](CONTRIBUTING.md)