Electrolux2mqtt

Bridges connected Electrolux, AEG, Frigidaire, and +home appliances to your MQTT broker using Home Assistant-style discovery so they appear automatically in…

  • Home Automation
  • Tools & Utilities
Bridges connected Electrolux, AEG, Frigidaire, and +home appliances to your MQTT broker using Home Assistant-style discovery so they appear automatically in Home Assistant, Jeedom, or any MQTT Discovery consumer. Entities are derived from each appliance's declared capabilities, covering programs, states, temperatures, alerts, and settings across ovens, hobs, hoods, fridges, dishwashers, washers, dryers, and more. State changes arrive via Server-Sent Events push with a 15-minute re-read safety net. Verified against 14 appliance families from the official Electrolux SDK.

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.

48/100 Fair

Maintained
79last commit 36 days ago
Popular
102 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 22 days ago

GitHub stars
2
Open issues
0
Last commit
2026-10-16
License
MIT
Activity
stale

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

Resources & Compatibility

Requirements not published yet.

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

First-install notes

  • Setup requirements Requires API credentials from the official Electrolux Group developer portal and a running MQTT broker with discovery support. No local API or Matter integration exists for these appliances; all communication goes through the cloud API. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does the bridge talk to the appliance directly on my network?

No, Electrolux appliances have no local API or Matter integration, so the bridge communicates through the Electrolux cloud API.

Will command subscriptions disappear after an MQTT disconnect?

No, discovery, states, and command subscriptions are replayed on every MQTT reconnection, so commands are not silently ignored after a broker disconnect.

Do I lose access after a container restart because Electrolux rotates refresh tokens?

No, the bridge persists the current token pair, so restarting the container does not leave you locked out with a spent token.

Can I use it for monitoring only without control entities?

Yes, a read-only mode exposes appliance states without exposing any commands.

How often does the bridge poll the Electrolux API?

State changes are pushed over Server-Sent Events, with one full re-read every 15 minutes by default that can be configured or disabled.

If I turn off an appliance in the Electrolux app, will Home Assistant state always update?

One user reports Home Assistant can still show an Electrolux air conditioner in cooling mode after it is turned off via the Electrolux app or physical controls.

Answers sourced from community.home-assistant.io, github.com

Community

Collected 48 days ago - public community threads