The Home Connect protocol provides control of home appliances. It also comes with a mobile application that gives access to relevant information at any time. Home Connect provides the capability to switch appliances on and off, select programs, adjust timers, set eco modes on and of and more. The protocol provides IFTTT support for setting rules based on events.
Feature Set
The Home Connect module provides the following features and functionalities:
Support for OAuth2 standard for authorization against the HomeConnect server.
Support for HDM Devices Classes
Support for Home Connect WhiteGoods DC API.
Support for Home Connect devices
Defines a HomeConnect Driver API at driver level that communicates with and supports fully all the REST calls, including connectivity, access, appliances features as programs, options and etc of the HomeConnect REST API : https://developer.home-connect.com/
Each HomeConnect compliant appliance can be represented and visible via the HomeConnect Driver API without any restrictions or known limitations.
New HomeConnect compliant appliances can be seamlessly integrated and supported by the HomeConnect Driver API.
Easy extension of the HomeConnect Driver API with new supported appliances features & functionalities.
Compliant devices - the Home Connect module provides support for all Home Connect Smart Home connected appliances, with a subset of features as described in the feature set above.
Tested Devices - a number of production devices is fully tested with the latest release of the Bosch IoT Gateway software stack.
For a most up-to-date list of tested and compliant devices, visit Supported Devices.
Home Connect driver makes a two-seconds delay between each successive REST call. Two seconds is default value, this settings is configurable.
It is not very clear how the Home Connect server counts opened monitoring SSE channels. Upon quick restarting of the Home Connect driver bundle (or OSGi framework itself), the user may end with HTTP error 429 Too Many Requests. This may lead to an inconsistent state between the HomeDevice instance and the current state of the home appliance.
In case that SSE monitoring channel cannot be opened, the Home Connect driver will continiously retry establishing a new channel after a certain timeout.
Usually Home Connect server includes HTTP header Retry-After 600 (10 minutes) in its response. However, a retry after 10 minutes is not guaranteed to succeed either, sometimes the HomeConnect server still rejects the SSE subscription request with another 10-minute Retry-After header.
Stopping Home Connect driver bundle can take up to two minutes. This is done on purpose in order to make sure that any opened SSE channels are surely closed from the client side.
Home Connect adapter represents program options as Switches and Setpoints device items, that have getter and setter methods. The getters work well showing the values received from the Home Connect server, but some setters may failed with "Unsupported Program Option" or similar error. Home Connect bundles does not do any filtering of setter methods, they forward all the requests towards the Home Connect server. The error comes from the Home Connect server, it does not allow setting some program options through the Home Connect REST API.
