Liebherr2mqtt

Bridges connected Liebherr fridges and freezers (SmartDeviceBox) to your MQTT broker, using Home Assistant style discovery.

  • Home Automation
  • Tools & Utilities
Bridges connected Liebherr fridges and freezers (SmartDeviceBox) to your MQTT broker, using Home Assistant style discovery. The appliance then shows up on its own in Jeedom, Home Assistant, or any other MQTT Discovery consumer: temperature, setpoint, SuperCool, SuperFrost, Party Mode, Night Mode, presentation light, ice maker, HydroBreeze, BioFresh-Plus and auto door - whichever your own appliance actually exposes. Multi-zone appliances get one entity per zone. REAL TIME, NO POLLING: State changes arrive as a push over Server-Sent Events, so the Liebherr cloud is never polled in a loop. That avoids the API rate limits and the IP blocks people have run into. The bridge is built on pyliebherrhomeapi, the library behind the official Home Assistant integration.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

40/100 Fair

Maintained
68last commit 77 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 21 days ago

GitHub stars
0
Open issues
0
Last commit
2026-09-05
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (ripleyXLR8/liebherr2mqtt)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Installation Deploy as a Docker container or via the Unraid Community Applications template (search 'liebherr2mqtt'). Enter your Liebherr SmartDeviceBox API key in the UI; all other settings are exposed as form fields. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does the bridge continuously poll the Liebherr cloud?

No. It receives state changes over Server-Sent Events, and a full re-read every 15 minutes is only an optional safety net that can be configured or disabled.

How do I connect it to my Liebherr appliance?

Deploy the Docker container or the Unraid Community Applications template, then enter your Liebherr SmartDeviceBox API key in the UI. Other settings are exposed as form fields.

What happens when the MQTT broker reconnects?

The bridge replays discovery, states, and command subscriptions on every MQTT reconnection. This avoids losing command subscriptions after a non-persistent broker disconnect.

Can it use the Local API instead of the Liebherr cloud?

Not for consumer SmartDeviceBox appliances. Liebherr disables the LocalAPI remotely, so the bridge uses the official SmartDevice HomeAPI.

How are appliance entities exposed to Home Assistant or Jeedom?

They appear through Home Assistant style MQTT discovery, grouped as one device with proper units, ranges, and icons. Entities are created only for controls the appliance actually declares.

What happens if the bridge container stops?

The bridge uses a Last Will so the appliance online indicator flips off by itself.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads