I have a Weissgauff dishwasher that only talks to the HolaBrain phone app. No local API, no Matter, no HomeKit. So I wrote an integration for it, and it grew to cover the rest of the family.
Repo: holabrain-ha Version 0.14.0, MIT, install via HACS as a custom repository.
WHAT IT IS
HolaBrain is a Midea OEM platform. The cloud behind it is dollin.net, and you will still run into the Dollin name here and there. Same thing. Appliances ship under several brands, Weissgauff among them.
The integration talks to that cloud. There is no local control path.
DEVICE SCOPE
Six categories are modelled. Dishwasher is confirmed on real hardware. Washing machine, oven, air conditioner, water heater and ceiling lamp are built from the cloud API but nobody has checked them against an actual appliance yet.
Air conditioners map to climate, water heaters to water_heater, lamps to light. Dishwashers, washers and ovens have no native platform in HA, so they turn into a set of sensors, switches, selects, numbers and buttons.
READ THIS BEFORE YOU INSTALL
The cloud allows one session per account. Last login wins. When Home Assistant makes a request, your phone app gets kicked out, and when the app logs back in, HA loses the session. There is no way to share it.
So the integration makes you pick a side. Two modes, one click to switch:
-
Cooperative (the default). HA never spends an account request on its own initiative. Status arrives over the cloud push channel, which authenticates with its own certificate and does not touch the session. Your phone app keeps working.
-
Exclusive. HA acts as the primary client. It polls, refreshes consumption after a cycle, and takes the session back when something else grabs it. Expect the app to be signed out a lot.
Your own actions always go through in either mode. Sending a command, pressing refresh, scanning for new appliances. The idea is to stop the integration from taking the session, not to stop you.
WHAT ELSE IT DOES
Readings that stopped meaning anything now read as unknown instead of showing stale numbers. A dishwasher sitting idle for two days used to report a programme and a remaining time left over from its last cycle, and automations happily fired on that. Every category now has a state machine, and every reading declares which states it makes sense in.
Water and electricity come from the cloud’s own aggregation, already in kWh and litres, with proper device classes. They drop straight into the energy and water dashboards. The appliance also reports raw lifetime counters, but nothing documents their scale, so I left them out.
Entities are gated by what your specific model advertises. A control the appliance would refuse never shows up. A command it would reject gets refused with a reason instead of failing quietly.
An appliance from a category I have not modelled still appears as a device, with one disabled diagnostic sensor per status field. Raw key names, no units, nothing writable. Turn on whatever you recognise.
There is an optional sidebar panel, off by default, plus a Lovelace card built from the same components. UI in English, Russian, Belarusian, Kazakh and Uzbek.
LIMITS, HONESTLY
Cloud only. Internet goes down, nothing works.
You cannot add a new appliance from Home Assistant. Putting one into pairing mode wipes its Wi-Fi settings and drops it off the network, so the chain breaks before it starts. I hit that wall and wrote it up. Set the appliance up in the phone app, then HA picks it up on the next scan.
Only the dishwasher is confirmed on hardware. The other five create entities, but a reading may be wrong or a control may be ignored.
Regions. The cloud runs eu and us. An account lives in one of them and does not exist in the other. I tested on eu. If you are on us, expect rough edges. The product catalogue is region specific too, so what you can even add differs.
Requires Home Assistant 2025.3 or newer. Entity names and ids may still shift while this is 0.x.
WHAT IS NOT COVERED
The cloud knows fourteen appliance types. Six are the ones above. The other eight (fridge, air purifier, water purifier, gas and central heating water heaters, energy manager, commercial AC, air fryer) run on a different protocol family. Their commands are encoded on the client with a per model codec instead of being sent as plain JSON.
That is a separate chunk of work, and I own none of those appliances, so I am not going to write it blind.
LOOKING FOR TESTERS
If you have any HolaBrain appliance other than a dishwasher, I would like to hear from you. A washing machine or an oven especially, since both are modelled but unverified. There is an issue form that feeds a hardware compatibility list, and diagnostics with account and appliance identifiers stripped out.
Not affiliated with the appliance manufacturer or the cloud operator.