[RELEASE] Home Connect Integration - Control Bosch, Siemens, Thermador and more

Home Connect Integration - Complete Rewrite with Enhanced Features

I'm excited to announce the initial release of Home Connect Integration v3 for Hubitat. This is a complete rewrite of the Home Connect integration, building on the excellent foundation laid by the original author Rfg81.

What's New in v3?

This isn't just an update—it's a ground-up redesign with significant improvements:

Architecture & Reliability

Three-Component Architecture

The integration uses a clean separation of concerns across three components:

  • Stream Driver: Handles the Server-Sent Events (SSE) connection to Home Connect's event stream. This persistent connection receives real-time updates about your appliances' status, ensuring immediate notification of cycle completions, errors, and state changes without polling.
  • Parent App: Manages OAuth authentication and device discovery. This is your control center for authorizing with Home Connect, discovering new appliances, and managing which devices are added to your Hubitat hub.
  • Child Drivers: Dedicated drivers for each appliance type (currently Dishwasher, with more coming soon). Each child driver translates Home Connect's API data into Hubitat attributes and commands, providing appliance-specific capabilities and controls.

This modular design makes the integration more maintainable, easier to debug, and allows for independent updates to individual components without affecting the entire system.

New OAuth Implementation

The OAuth flow has been completely redesigned to address common authentication issues:

  • Stateless validation eliminates race conditions and timing issues people experienced previously (the two browser workaround)
  • Improved error handling with clear, actionable error messages that help you quickly identify and fix configuration issues

The result should be a more reliable authentication experience that "just works" - especially important when setting up the integration for the first time or re-authorizing after token expiration.

Enhanced Features

  • Four-button notification system:
    • Button 1: Cycle complete notifications
    • Buttons 2-3: Maintenance alerts (e.g., salt/rinse aid low)
    • Button 4: Error notifications
  • Delayed program start support for cost optimization (start during off-peak electricity hours)
  • Node-RED compatibility through JSON state attributes

Current Support

  • Dishwasher (fully implemented with all programs and options)
  • Additional appliance types coming soon!

Installation Options

Option 1: New Installation (No Existing Home Connect Setup)

If you've never used Home Connect with Hubitat before, follow these steps:

Step 1: Create Home Connect Developer Account

  1. Go to Home Connect Developer Portal
  2. Sign up for a developer account (free)
  3. Create a new application with these settings:
  • Application ID: Choose a unique name (e.g., hubitat-yourname)
  • OAuth Redirect URI: Leave blank for now (we'll add this in Step 4)
  • Success Redirect: Leave blank for now (we'll add this in Step 4)
  1. Note your Client ID and Client Secret - you'll need these next

Step 2: Install the Integration

Option A: Via Hubitat Package Manager (Recommended)

  1. Open Hubitat Package Manager
  2. Search for "Home Connect Integration v3"
  3. Click Install
  4. HPM will install all three components and automatically launch the app configuration screen

Option B: Manual Installation

  1. Go to Drivers Code and create a new driver
  1. Create another new driver
  1. Go to Apps Code and create a new app
  1. Click the OAuth button and enable OAuth for the app
  2. Go to Apps and click Add User App
  3. Select "Home Connect Integration v3" from the list

Step 3: Initial App Configuration

  1. In the app configuration screen:
  • Enter your Client ID from Step 1
  • Enter your Client Secret from Step 1
  • Select your Region (US or EU)
  • Set Debug Level (recommend "Info" for initial setup)
  • Click Next
  1. The app will now display your unique registration URIs (these include your app-id)
  2. Copy both URIs - you'll need them for the next step
  3. Do NOT click "Authorize" yet - we need to add these URIs to Home Connect first

Step 4: Configure Home Connect with Your URI

  1. Return to your Home Connect Developer Portal
  2. Open the application you created in Step 1
  3. In the Redirect URI field, paste the full URI shown in the Hubitat app (this is the complete URI that includes your app-id)
  4. Save your Home Connect application settings

Step 5: Authorize & Discover Devices

  1. Return to the Hubitat app configuration
  2. Click "Authorize with Home Connect"
  3. Log in with your Home Connect account credentials
  4. Grant permissions to the integration
  5. After successful authorization, return to the app and click "Discover Devices"
  6. Your appliances will appear - select the ones you want to add
  7. Click Done to create the devices

Option 2: Side-by-Side Installation (Test Alongside Existing Integration)

If you're currently using the original Home Connect driver and want to test v3 before fully committing:

Step 1: Install v3 Integration

Option A: Via Hubitat Package Manager (Recommended)

  1. Open Hubitat Package Manager
  2. Search for "Home Connect Integration v3"
  3. Click Install
  4. HPM will install all three components and automatically launch the app configuration screen

Option B: Manual Installation

  1. Go to Drivers Code and create a new driver
  1. Create another new driver
  1. Go to Apps Code and create a new app
  1. Click the OAuth button and enable OAuth for the app
  2. Go to Apps and click Add User App
  3. Select "Home Connect Integration v3" from the list

Step 2: Initial Configuration to Get URI

  1. In the app configuration screen:
  • Enter the same Client ID and Client Secret from your existing integration
  • Select your Region (same as your existing integration)
  • Set Debug Level (recommend "Info" for initial setup)
  • Click Next
  1. The app will display your v3-specific Redirect URI
  2. Copy the Redirect URI (it will have a different app-id than your original integration)
  3. Do NOT click "Authorize" yet - we need to add this URI to Home Connect first

Step 3: Add Second Redirect URI to Home Connect

  1. Go to your Home Connect Developer Portal
  2. Open your existing application
  3. Check the "Add additional redirect URIs" checkbox
  4. Add the new v3 Redirect URI from Step 2 (don't replace the existing one - you'll now have two URIs listed)
  5. Save the application settings

Step 4: Authorize & Create Test Devices

  1. Return to the v3 app in Hubitat
  2. Click "Authorize with Home Connect"
  3. Log in and grant permissions
  4. After successful authorization, click "Discover Devices" and select your appliances
  5. Click Done
  6. Note: v3 devices will have a HC3- prefix (e.g., HC3-Dishwasher) to distinguish them from your original devices

Step 5: Testing & Migration

  • Both integrations will work simultaneously
  • Test v3 features with the new devices
  • Update your rules/dashboards to use v3 devices when ready
  • Once satisfied, you can remove the original integration and its devices

Key Differences from Original

  • Better OAuth handling: Cleaner error messages, more reliable authentication
  • Enhanced notifications: Four-button system for different alert types
  • Improved state management: JSON attributes for easier Node-RED integration
  • Comprehensive logging: Easier troubleshooting with detailed debug options
  • Program mapping: Supports both technical and friendly program names
  • Maintenance tracking: Salt, rinse aid, and other consumable alerts

Troubleshooting Tips

  • OAuth errors: If you see "missing or invalid request parameters," double-check your redirect URIs in the Home Connect Developer Portal
  • Enable debug logging in the app settings if you encounter issues
  • Check the Stream Driver logs for SSE connection statusly

What's Next?

I'm actively working on support for additional appliances:

  • Ovens
  • Coffee makers
  • Refrigerators
  • Washers/Dryers
  • And more!

Credits

A huge thank you to Rfg81 for creating the original Home Connect integration. This project wouldn't exist without that foundational work. Version 3 builds on those concepts while addressing limitations and adding modern features requested by the community.

Support & Feedback

Please report any issues, feature requests, or questions in this thread. Include debug logs when reporting problems—they're incredibly helpful for troubleshooting!


Installation Links:

Looking forward to your feedback and helping you get your Home Connect appliances working smoothly with Hubitat

8 Likes

Thanks for all the work (past/present/future :wink: ) on this, Craig! Really appreciate you stepping up to provide this integration to the community!

This installed w/out issue for me.

Wow, your timing is impeccable as the boss (aka, wife) just bought an entire new set of Thermador appliances for our kitchen.

1 Like

I have only tested this on my Bosch dishwasher so it will be interesting to see if the dishwasher works for you. I am in the process of building a test harness for their simulator so I can build the drivers for the other appliance classes I don't have. Hopefully I will get it working this week.

1 Like

Happy to be your beta tester. We got Thermador dishwasher, oven, stove, and fridge/freezer, as well as a warming drawer. Install date is 2-3 weeks out. I also run Home Assistant so I can do some side-by-side testing as well, if that's helpful.

1 Like

I have a Bosch 500 hood on @rfg81 's original driver. When I get some time I'll definitely try yours out. Thanx for picking up the mantle. And thanx to @rfg81 for all his work that he did on this in the first place. I think I put the issue about Home Connect out there in 2021 and he dug out some github code he found and modified it for hubitat. The community devs here are the shiat!

3 Likes

I have the simulator running and just created a coffee maker driver becuase... you know... coffee :). I'll come back to it tomorrow and will prioritize the devices you guys called out as the next batch.

3 Likes

Actually the one thing I've never really needed to smartify. (I have a Breville grind and brew) I just set it up the night before and the 1st person downstairs hit's the button...lol

@craigde: just tried to install the new Home Connect V3 but got a error message (see shot below). Any ideas? Just did an update without any problems for an installed app

Using the latest HPM release 1.9.7. Not sure if this is an HPM or Github issue? Just noticed, that I installed another community app without any issues via HPM yesterday.

Thanks

Update:
Just compared the installation link stated at the end of the thread with the link in my error message.

Installation Links:


HPM Link in error message:

Looks like there is a difference after the /...../hubitat-homeconnect-v3/main/packagde.......

in one link there is an additional path (main), which is missing in the other link.

Could this be the reason for the issue?

Same error when I tested installing from HPM on my test hub.

Doh! Missed a comma in the json when I updated the HPM file to include the coffee maker. Its fixed now. Thanks for the heads up.

2 Likes

Still no go here. I had some time so I tried installing again. Four times with Chrome and once with Edge still yields the same error. I even deleted and reinstalled the application between one of the Chrome tries. The redirect was correct as well as the client and secret. While waiting I checked all 3 each time. It's just odd. I'm sure it's something on this end. I also double checked to make sure Oauth was also enabled. I'm stumped.

Did you enable debug logging and capture the logs?

also can you share a screenshot of your Home Connect developer config with the client secret redacted.

I didn't capture any logs but I do know that the HE side entries are 100% correct. They match the same format as the old integration and I painstakingly made sure that the data copied matched.

For fun I tried Firefox and waited the entire 30 minutes for the same results.

Being no one else had this issue it's something here. I'm going to create a new developer account and try that.

I sent you a private message. No go with new developer account.

1 Like

After messages back and forth with Craig, and him adding additional logging, we have a solution to the authentication issue. It was because I was trying to authenticate using my mobile. As soon as I tried authenticating with the netbook it worked the first time.

I did all of this using OpenVPN so the verdict, at least for me, is OpenVPN isn't an issue, at least on the Linux PC, but my Motorola on Android 15 is.

It wasn't the browser, as I tried Chrome, Edge (whose base is Chrome) and Firefox and none of them would authenticate on mobile. Maybe the mobile on my home network but definitely not mobile over openVPN.

Now time to actually play.

Thanks @craigde for all of the work that you have done. It is much appreciated.

1 Like

So the "AHA!" is that authenticating from your Moto/Android 15 was the blocker, and the solution was to use your Netbook instead.

Kudos for tracking things down! :slight_smile: Have fun playing. Particularly interested in the delayed start option, I'd like to set up a button to enable delayed start for 9:01pm (cheaper electricity, or so says my thrifty wife), but I haven't had time due to her office remodel and all associated effects on furniture locations and networking gear connections/locations. :slight_smile:

Well, we aren't done yet. It said it authenticated and everything was connected but the home connect V3 app isn't listed anywhere on the hub. Something didn't finish right.

I think I'm going to quit for now and wait until I'm back on the home network. Too many variables. LOL

We know that it connects and that's important.

1 Like

The very first time I set up v3, the app was present after authorization, but the dishwasher device didn't appear. I went back into the app and basically "nexted" through the screens and then the dishwasher device appeared.

Just mentioning in case that's helpful for @craigde in the troubleshooting process.

2 Likes