eQ-3 MAX! Cube
homebridge-platform-maxcube · v2.0.15
Adds eQ-3 MAX! Cube radiator and wall thermostats and window contacts to HomeKit.
What it says it supports
Brands
- eQ-3
- ELV
- MAX!
Devices it names
- MAX! Cube
- radiator thermostats
- wall thermostats
- window contacts
Shows up in Apple Home as from its README
Sensor readings in its code
What people report
Controls eQ-3 MAX! Cube thermostats and window contacts; Cube cannot be shared with other software and needs restarts.
- Partly works2
| Device | Status | What they said | Source |
|---|---|---|---|
| eQ-3 MAX! Cube thermostats | Partly works | Cube cannot be accessed by multiple backends; error setting temperature, needs restartsSaved copyFhem also communicates with the thermostats over the cube. And yes, the cube sucks sometimes, so i connected it to a hue controlled outlet, to restart it when its not responding. Von meinem iPad gesendet Am 25.02.2021 um 19:03 schrieb Normen Hansen : 🤷♂️ I have to restart the cube regularly no matter what software I use to control it - I guess switching to some open source 868MHz controller would be better overall. I think FHEM also has this kind of support for the EQ3 thermostats., You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or … Excerpt saved from GitHub on 2026-10-22. | Issue #38 · 2021-02 |
| eQ-3 MAX! window contacts | Partly works | Names not shown in HomeKit for one userSaved copyHallo, ich habe heute meine Homebridge inklusive dem "homebridge-platform-maxcube"-Plugin neu installiert. Dabei ist mir aufgefallen, dass die Namen der Thermostate und der Fenster-Kontakte nicht in Homekit übernommen werden, obwohl Homebridge die Namen richtig vom Cube übernimmt (sie werden in den Logs auch richtig angezeigt). Ich nehme an, dass liegt daran, dass keine Klammern oder Sonderzeichen in Namen mehr erlaubt sind. Das führt dazu, dass die Namen bei allen Geräten auf "Thermostat" und "Kontaktsensor", also quasi auf die Standardbezeichnungen zurückgesetzt werden. Ist dieser Fehler … Excerpt saved from GitHub on 2026-10-22. | Issue #30 · 2020-05 |
Gathered from the plugin’s GitHub issues, pull requests, discussions, wiki and docs, and from r/homebridge. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local
Direct to MAX! Cube on LAN
You’ll need
- MAX! Cube
Compatibility
| Verified by Homebridge | Yes |
|---|---|
| Homebridge versions | >=0.4.10 |
| Homebridge 2.0 | No |
| Node.js | >=6.0.0 |
| Settings in Homebridge UI | Yes |
| Matter | No |
| Platform name | MaxCubePlatform |
| License | MIT |
Community signals
| Downloads a week | 2 |
|---|---|
| Downloads a month | 32 |
| GitHub stars | 14 |
| Open issues | 2 |
| Closed issues | 42 |
| Last code push | 2023-12-22 |
| Latest version | 2.0.15 (2022-06-24) |
| First published | 2017-03-12 |
| Releases | 49 |
In ReReHome
Whatever this plugin publishes reaches Apple Home as a normal HomeKit accessory behind your Homebridge bridge, so ReReHome shows and controls it like any other.
Bridges get their own settings page listing the accessories behind them.
Caveats from the README
- Cannot run alongside Max! software without toggling Max! Link
- 868 MHz broadcast limit
HomeKit services in its code
Found by scanning the published npm package. A plugin can register a service only for some devices.
- ContactSensor
- Switch
- Thermostat
