Just wanted to note that I recently connected my Bosch Dishwasher to HE via HA & HADB and the connection was simple/easy. Connection is to the Home Connect API which supports a number of brands, including Bosch, Siemens, Gaggenau, Neff, Thermador, Balay, Constructa, Pitsos, and Profilo.
After I brought the dishwasher into HE via HADB, a power device (switch) was created in HE/HADB, but only after I used HA to turn the washer on/off. (I did re-intialize HADB in HE, but that didn't add the dishwasher power switch.) No other HADB devices were created at that point. It seemed like more devices appeared in HADB>HE as I used them on the dishwasher or in HA. E.g., the door status appeared in HE (as a contact sensor) after I opened and closed the door on the dishwasher, and the Stop Program option (as a button) appeared after I used the "Stop Program" button on the Bosch Dishwasher device on Home Assistant.
Current HE devices under the HE HADB device parent:
HE HADB Bosch devices a day later: As @672southmain confirmed, devices populate as features/controls are accessed:
There is also a python connector to Home Connect that @Alan_F posted about as well that I haven't looked into that yet. IIRC it's local. Probably a little more work, too.
Thanks for posting this. I'm going to check out the NodeRED integration, as I already have that running and, so far, I've managed to avoid adding HA to the mix.
@danabw I've been using the hubitat community Bosch integration for several years now. Been working well. @rfg81 was very kind to me in initially writing the integration for my Bosch stove Hood and it really took off for him. It's something that is still really appreciated.,,,
Yes, the community integration was the first integration I installed. I actually prefer to use the community integration as I'm trying to reduce my dependence on secondary hubs/devices (in this case running HA on a Pi for this topic's integration). However, the community Home Connect integration is no longer supported so that is a concern, and it's cloud-based so all of those potential issues we know so well.
The Python integration is fully local, but also requires a Pi to run on, so it's going against my "de-complicate my home" goals.
Really wish that Home Connect was Homekit compatible, then I'd bring it in via the new Homekit capability on the hub.
My dishwasher is integrated into my life by my need for clean dishes... I'm sure (hope) you will understand the need to downplay the need for making things smart when it is not necessary.... If not, you should try emptying the dishwasher more often...
But if there is a Fisher and Paykel integration.... I may reconsider my assessment...
I've hardly even looked at the python option yet...so at this point.
But the setup guide for it does say this...sounds like it grabs what it needs to command the device locally and won't be running commands through the cloud:
I was able to get the NodeRED Home Connect integration up and running without too much drama. Won't have a dishwasher to connect to it for a few weeks though.
The python project looks like it publishes device state via MQTT and accepts commands via MQTT, which is how they connect it to HA. If no one beats me to it, I might take a LLM-assisted shot at creating an app and driver to integrate that to Hubitat.
I actually prefer to use the community integration as I'm trying to reduce my dependence on secondary hubs/devices (in this case running HA on a Pi for this topic's integration). However, the community Home Connect integration is no longer supported so that is a concern, and it's cloud-based so all of those potential issues we know so well.
