Previous Topic

Next Topic

Book Contents

Book Index
Management via HDM Web Console (Deprecated)

This Page shows a short "how-to" use the Bosch IoT Gateway Software Home Connect module.

In the sample bellow we create a Home Connect Application (that would be used by the Home Connect module). For serverUrl we configure the test backend (test server with simulated Home Connect appliances),

Steps

First it has to be decided what Home Connect App should be used by the Home Connect module and to what backend server should it connect to.

  1. Go to the developer section of the Home Connect website.
  2. Login / create account.

    Newly created accounts initially have basic rights - generally it allows read-only access, only monitoring.

    There is an option on the web site to upgrade to advance level that unlocks additional access right - settings and controls (excluding oven).

    Full access is allowed only to partner accounts. This level is granted by BSH (Home Connect) developers, contacting them outside of the web side.

    More info about the right is available here.

  3. Go to "My Applications".
  4. Hit the "Create new application" on top.

mbs_homeconnect_user_mgmtweb

  1. Hit "Create Application".

mbs_homeconnect_user_mgmtweb2

  1. Start the Bosch IoT Gateway Software runtime.
  2. Set system property "mbs.homeconnect.adapter.autoAddAppliance" to "true"

    fw>$set mbs.homeconnect.adapter.autoAddAppliance=true

  3. Install the Home Connect module bundles (as described in the Setup Guide section).
  4. Open "http://<server>/system/console/configMgr" and open the "Home Connect Configuration"
  5. Enter Client API key and Client redirect url from the already created Home Connect Appliaction (step 4.); select the Home Connect backend server (by default its the test server with simulated devices), then hit Save.

mbs_homeconnect_user_mgmtweb3_v90

If Client API key belongs to a developer account that does not have the full set of access rights (partner account), the "Authorization Scope" property should be adjusted too. The user should delete the values that he/she does not have access to.

  1. Go to "http://<server>/system/console/hdm". In the list of HDM Devices there should be the Home Connect Controller Device that is waiting to be initialized.

mbs_homeconnect_user_mgmtweb4_v90

  1. Open the Home Connect controller Device. Initially its Authorization status should be status=NOT_INITIALIZED

mbs_homeconnect_user_mgmtweb5_v90

  1. Enter the Home Connect credentials username and password (if test backend is chosen enter any username / password - could be non-valid user credentials) and trigger the "login" operation. Device should become ONLINE with Authorization status stats=AUTHORIZED.

mbs_homeconnect_user_mgmtweb6_v90

  1. Go back to "http://<server>/system/console/hdm" - Home Connect module should already have pulled all available Home Connect appliances against the current configuration (backend server , home connect user) and created HDM Devices for each Home Connect Appliance.

    (If test server is chosen, all simulated Home Connect Appliances are pulled from test server and HDM Devices Are created)

mbs_homeconnect_user_mgmtweb7_v90

  1. If connected to the test backend with simulated Home Connect appliances- HDM Devices can be tested with the help of the Home Connect Simulator.