# Liebherr2mqtt

Liebherr2mqtt is a bridge that connects Liebherr fridges and freezers with a SmartDeviceBox to an MQTT broker using Home Assistant-style discovery. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/2985/liebherr2mqtt

## Description

Liebherr2mqtt is a bridge that connects Liebherr fridges and freezers with a SmartDeviceBox to an MQTT broker using Home Assistant-style discovery. The appliance appears directly in Jeedom, Home Assistant, or any other MQTT Discovery consumer, exposing temperature, setpoints, SuperCool, SuperFrost, Party Mode, Night Mode, presentation light, ice maker, HydroBreeze, BioFresh-Plus, and auto door where supported. Multi-zone appliances get one entity per zone. State changes arrive in real time over Server-Sent Events, so the Liebherr cloud is not polled in a loop, avoiding API rate limits and IP blocks. The bridge is built on pyliebherrhomeapi, the library behind the official Home Assistant integration.

## Platform availability

Available on 1 of 10 platforms: Unraid.

## Health score

40/100 (Fair), based on 3 of 4 factors.
- Maintained: 68 (last commit 77 days ago)
- Popular: 0 (0 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- Unraid: https://ca.unraid.net/apps/liebherr2mqtt-1ldlh0x1oubv39?q=liebherr2mqtt
- GitHub: https://github.com/ripleyXLR8/liebherr2mqtt

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/2985/liebherr2mqtt), the self-hosted and open-source app directory.
