serbanb11/homecom_alt

So apparently bosh does some weird shit with its way of using cursors. 0 is not the first one you have to call it without it and then go the the next. So now it starts without the next get attribute. and then collects all the data. In the meanwhile i found out that in the easycontroll app you can select an unit for gas, so i implemented this enpoint Since using `asyncio` caused multiple simultaneous token refreshes, which led to errors, I implemented an `asyncio.Lock`. This lock ensu...

Enhance energy history APIs and improve async data retrieval

this pr fixes the issue for https://github.com/serbanb11/bosch-homecom-hass/issues/101 The issue was that not all devices have energy history :)

While testing the energy data, I noticed that the information was not updating as expected. Upon further investigation, I found that the /history endpoint only returns the earliest entries by default. I discovered that the total number of entries can be retrieved via /historyEntries. Using this, I was able to collect the full history of the previous day. I have updated the /history endpoint function so that it now retrieves the latest entry by default. You can still specify a particular en...

After reviewing the available endpoints, I identified the relevant ones for controlling the heating mode and temperature: * `userMode` * `temperatureHeatingSetpoint` ## User Modes There are two available `userMode` values: * `manual` * `clock` You can: * Retrieve the current mode via `GET /userMode` * Update the mode via `PUT /userMode` with: ```json { "value": "manual" } ``` or ```json { "value": "clock" } ``` ## Temperature ...