-
Notifications
You must be signed in to change notification settings - Fork 24
Support for IVT Aero series #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
if there is possibility to obtain access token without going into their API website, then sure, go for it and add PR to bosch-library. |
It is not possible to obtain a token without going through their website, but once that process is completed once, the refresh token can be used to get a new access token when it's expired. So the library can accept a token just like takes a password for the existing gateways. The token refresh part can live either here, or in the home assistant component. Maybe it makes more sense there because the token needs to be stored long term. |
Hi team / maintainers, I would like to inquire about the current status regarding the integration of the Bosch K30RF WiFi module with Home Assistant. I have a Bosch Heat Pump that uses this module for connectivity and I am keen to integrate it into my Home Assistant setup. My main questions are:
|
I have not worked on this for over a month now, integration of the API into this client library was a bit tricky. If I get it working, my assumption is that the K30RF module would expose a similar enough API that it could use the same system. What's you level of Python skills @jannikloehr? Would you be able to connect and query the API for your heat pump if you got some Python scripts? |
The IVT Aero heat pump series connects to the Bosch cloud API (https://pointt-api.bosch-thermotechnology.com/pointt-api/api/v1), similar to the K30 RF wifi module discussed in bosch-thermostat/home-assistant-bosch-custom-component#335. Unlike the local HTTP and MQTT integrations supported today, this access method requires an OAuth authentication flow, which provides access and refresh tokens.
Although this approach differs from existing local integrations, the data structures returned appear to be similar, making it a potential fit for integration into this package. I have successfully connected to the API and can both read and write data, though the available data is somewhat limited, it's really stripped down to only allow what's used in the ‘IVT Anywhere II’ mobile app.
I'll publish a PR once I've got the sensors mapped up and can read and write it through the client, but writing now just to check that it makes a good fit? I'm looking at this part first because I want to integrate it into the home assistant component next.
The text was updated successfully, but these errors were encountered: