Sensibo Rate Limits

Sensibo rate limits the API but does not publish a fixed numeric request cap. When a client exceeds the limit the API returns HTTP 429. Sensibo's guidance is that sending an `Accept-Encoding: gzip` header raises the effective limit, which implies limiting is influenced by response payload volume as well as request count - so clients should request only the fields they need (via the `fields` parameter) and accept gzip. Historical measurements are capped at seven days per request regardless of rate. Practical integrations poll measurements on the order of tens of seconds to a few minutes rather than continuously, since Sensibo devices report to the cloud on an interval and there is no push/streaming API to subscribe to.