Homeconnect

Control and monitor Bosch, Siemens, NEFF and Gaggenau home appliances through the official Home Connect cloud API — dishwashers, washers, dryers, ovens, hobs, hoods, fridges, freezers, coffee makers, cleaning robots and more.

Every value arrives in a form you can use directly: on/off as a boolean, a fixed choice as a readable name, a measurement as a number with its unit and limits. Updates arrive live through a single event stream, and programs can be selected, configured and started from ioBroker.

Requirements

• Node.js >= 22
• js-controller >= 7.2.5
• Admin >= 8.2.0
• A free Home Connect developer account, for a Client ID and a Client Secret

Getting your Home Connect credentials

Three things belong together: your normal Home Connect account (the one of the Home Connect app, where your appliances are paired), a developer account linked to it, and an application registered in the developer account. The settings page shows the same steps as a checklist, with buttons for creating the developer account, registering the application and opening your applications.

1. Create a free developer account at developer.home-connect.com. As Default Home Connect Account for Testing enter the e-mail address of your Home Connect app account — exactly as in the app, in lower case. This links the two accounts; without it the sign-in is refused.
2. Register an application: any Application ID, OAuth Flow Device Flow (the adapter runs on a server without a browser; the flow cannot be changed later), Success Redirect empty, One Time Token Mode off.
3. Wait 15 to 60 minutes — a new or edited application only becomes active at Home Connect after that.
4. Copy the Client ID (64 characters) and the Client Secret into the adapter settings and save.

Signing in

After saving the credentials the adapter requests a sign-in link. The settings panel shows it together with the code to confirm. Open the link, sign in with your Home Connect account and approve the access — the adapter picks the approval up on its own within a few seconds and stores the login encrypted. The notification only points you to the settings: the code changes every five minutes, and the panel always shows the current one.

While the link waits, it renews itself every five minutes. If nobody confirms one for an hour, the adapter stops asking Home Connect for new links; Request a new sign-in link in the panel starts again, and so does a restart. Reset sign-in forgets the login and starts a new sign-in — for example to switch to another Home Connect account. The Test connection button asks Home Connect directly: it reports how many appliances your account lists and how many of them are connected right now, and whether live updates are running.

You sign in once. The adapter refreshes its access by itself; a new sign-in is only needed when the access is revoked in your Home Connect account, when Home Connect refuses the application (disabled, deleted, new secret), or when the ioBroker data moved to another system — the stored login cannot be read there, and the log says so.

When Home Connect refuses the sign-in, the panel shows what it answered and what to do; auth.lastError keeps the answer (see Troubleshooting).

The object tree

Each appliance gets one folder. Its name is the appliance's model and the last four characters of its own Home Connect number (for example sx87tx02ce-5775) — unchangeable, and different for two appliances of the same model, which neither the app name nor the E-number from the type plate is. The appliance name from the app stays visible as the folder's display name and follows it live. Should two appliances of one model end in the same four characters, the second one gets its whole number.

Below each appliance — which channels an appliance gets depends on its type; fridges, freezers and wine coolers have no programs:

At instance level, info.devicesTotal, info.devicesOnline and info.devicesAllOnline summarise the account, info.connection is green when the adapter is signed in and live updates are running, and auth.lastError holds Home Connect's answer to a refused sign-in (empty while signed in, Unknown while nothing was asked yet).

Where the data points come from:

• Status, settings, programs, options and commands are what the appliance itself reports to Home Connect — the adapter creates exactly those. options holds only what you choose for a program; values the appliance reports while a program runs (remaining time, progress, forecasts, process phase) are under run.
• Events are the exception. Home Connect has no way to ask which events an appliance can send — an event only arrives at the moment it happens. So the adapter creates every known event of the appliance type in advance, from its own catalogue: you can build a script on "salt empty" today instead of waiting months for the salt to run out. An appliance may therefore have event data points it never uses; an event the catalogue does not know is added the first time the appliance sends it.

Two properties are worth knowing:

• Every data point exists from the first read of the connected appliance on — the events of the appliance type even from the first start, and the options of all its programs, not only of the one currently selected.
• No data point ever disappears. A switched-off appliance reports far less to the cloud, but that never means it lost a capability. Only an appliance you remove from your Home Connect account loses its folder. (Exception: a statistics channel named program<number> moves to the program's name once the adapter has learned it or its program table names the number; recordings, aliases, rooms and functions move along.)

Operating appliances

• A setting: write the value into the data point under settings. "true", 1 and true all work — the adapter converts to the data point's type before sending.
• Start a program: pick it in programs.selectedProgram, set the options you want under options, then set programs.start to true. The adapter sends the selected options with the start; if the appliance refuses that combination, it retries once with the program's defaults.
• Stop a program: set programs.stop to true.
• A command: set the button under commands to true; it falls back to false by itself.

A written value counts as done (ack) once the appliance reports it back. If the appliance refuses it, the data point returns to the appliance's real value.

Home Connect only accepts remote operation when the appliance allows it — most machines need Remote Start enabled on the appliance itself, and many refuse a change while a program is running. status.remoteControlActive and status.remoteControlStartAllowed tell you what the appliance currently permits.

Data point names and descriptions

The adapter's own names come first: it names the events, the common status values and settings, the program options and its own structure in eleven languages. Where it has no name of its own, it uses the localized name Home Connect sends in your ioBroker system language, and as a last resort a readable name derived from the id. The description explains what a data point means, never repeats the manufacturer's key, and stays empty where the adapter has nothing to explain.

Names and descriptions belong to the adapter: an update brings existing installations along, so a tree from an older version does not keep old labels. If you want your own naming, use aliases or your own data points under 0_userdata.

Updating from 1.x

Version 2.0 replaces the raw data tree of the community releases up to 1.6.x with a readable one per appliance. Example: homeconnect.0.012345678901234567.status.BSH_Common_Status_DoorState becomes homeconnect.0.kg49nsbbf-4567.status.doorOpen — the device folder is named by the model and the last four characters of the appliance's own number.

The update takes care of the tree itself: your login and Client ID are kept, and rooms, functions and aliases move to the datapoint that takes the old one's place as soon as the appliance has been read once. A recording setting moves along only on a tree that also carries a room, function or alias, and only where exactly one new datapoint of the same value type replaces the old one. Where the type changed (a door text became yes/no) or one old datapoint became several (operation state → operation state + program running), the new datapoint starts without a recording — enable it again there. The log counts the room/function entries and aliases carried and the datapoints with a room or alias that had no counterpart.

What you have to do:

1. Make a backup before the update. Going back to 1.x is not supported — the old tree is removed once it has been handed over, and 1.x cannot read the login 2.0 stores encrypted.
2. Adjust your scripts and visualizations to the new IDs. The table lists, for the last part of every old ID, the datapoint that replaces it (below the new device folder). Rows marked (decoded) are new datapoints read from the old raw value; rooms, functions, aliases and recordings of the old raw datapoint are not carried to them.

Updating from 1.7 – 1.23

The device folders were named after the app name (up to 1.12) or the E-number from the type plate (1.13 – 1.23, sx87tx02ce-60), which names the model only. With this version every folder moves once to the model and the appliance's own number (sx87tx02ce-5775). Values, recording settings, rooms, functions and aliases move along, and recorded history continues in its old series. Scripts and visualizations that use the old IDs must be updated.

The running program, the doors and the totals have their own channels now: status.remainingProgramTime → run.remainingProgramTime (likewise elapsed time, progress, phase, forecasts and recommendations), status.doorOpen → doors.door, status.doorLocked → doors.doorLocked, status.programAllCountCompleted → counters.programAllCountCompleted (likewise every total). An event or compartment door of a 2.0 test build that was a channel of its own (events.programFinished.active, doors.freezer.open) becomes a plain datapoint again (events.programFinished, doors.freezer). The last run is part of the history: lastRun.start → history.latest.start (likewise end, how it ended and the consumption); where the history already had the program and the duration, those stay and the two from lastRun go. Values, recordings, aliases, rooms and functions move along.

Rate limits

Home Connect grants 1000 requests per day per application and account, at most 50 per minute, and blocks for ten minutes after ten failed requests in a row. The adapter is built around that: it uses one persistent event stream instead of polling, remembers program definitions permanently, sends at most 50 requests per minute (so the first start after an update or with a new appliance reads for a few minutes), puts your commands before waiting reads, and pauses on its own after a rate-limit answer — the log names the limit and how long Home Connect blocks. There is nothing to configure — but a second application of your own using the same credentials shares the same budget.

Troubleshooting

Diagnostics report

When an appliance does not do what it should, open the instance settings, tab Expert, pick the appliance and download its diagnostics report. It holds what Home Connect answered for this appliance (also a fresh read of its status, settings and programs while it is connected), the events of the live stream, the appliance's datapoints with their values and the adapter's recent log lines. Attach the file to an issue with the form Report a device — the card links to it.

The report is made only when you ask for it, stays in memory until the download and writes nothing. Serial numbers, the names you gave your appliances and your sign-in data stand in it as placeholders.

Support

Questions, bug reports and ideas: github.com/iobroker-community-adapters/ioBroker.homeconnect.

Changelog

2.0.0-alpha.0 (2026-10-21)

• (krobipd) Changed: complete rewrite with a new object tree and new datapoint IDs — breaking for existing scripts and visualizations
• (krobipd) Changed: readable values with units and labels in the user's language
• (krobipd) New: program history and the consumption of the last run as readable datapoints
• (krobipd) Changed: the adapter requires js-controller 7.2.5 and Admin 8.2.0 or newer now
• (krobipd) New: sign-in panel in the instance settings with a connection test and a reset of the login
• (krobipd) Improved: an update from 1.x keeps rooms, functions, aliases and the Home Connect sign-in
• (krobipd) Fixed: the object database no longer grows with every value change (#387), and the start stays within the Home Connect request limits (#327, #58)
• (krobipd) New: diagnostics report on the Expert tab, with a 'Report a device' issue form for it

1.6.1 (2026-05-12)

• (TA2k) Login/Refresh flow improved

1.6.0 (2026-05-11)

• (copilot) Adapter requires node.js >= 22 now
• (copilot) Adapter requires admin >= 7.7.22 now
• (Lucky-ESA) Fixed adapter crash if URI is empty
• (Lucky-ESA) Save remaining time in active folder
• (Lucky-ESA) Device monitoring starts only after the adapter has started (this may take up to 2 minutes)

1.5.2 (2025-12-14)

• (Lucky-ESA) Rate limit of 50 requests per minute intercepted at adapter startup
• (Lucky-ESA) Added custom request

1.5.1 (2025-09-20)

• (Lucky-ESA) Fixed: Name of the objects are deleted

License

The MIT License (MIT)

Copyright (c) 2019-2026 TA2k tombox2020@gmail.com
Copyright (c) 2024-2026 iobroker-community-adapters iobroker-community-adapters@gmx.de
Copyright (c) 2026 krobi krobi@power-dreams.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.