MAX! Binding

This is the binding for the eQ-3 MAX! Home Solution. This binding allows you to integrate, view and control the MAX! Thermostats in the Openhab environment

Supported Things

This binding support 6 different things types

Thing Type Description
bridge Bridge This is the MAX! Cube LAN gateway
thermostat Thing This is for the MAX! Heating Thermostat. This is also used for the powerplug switch “Zwischenstecker-Schaltaktor”.
thermostatplus Thing This is for the MAX! Heating Thermostat+. This is the type that can hold the program by itself
wallthermostat Thing MAX! Wall Thermostat.
ecoswitch Thing MAX! Ecoswitch.
shuttercontact Thing MAX! Shuttercontact / Window Contact.

Generally one does not have to worry about the thing types as they are automatically defined. If for any reason you need to manually define the Things and you are not exactly sure what type of thermostat you have, you can choose thermostat for both the thermostat and thermostat+, this will not affect their working.


The discovery process for the MAX! binding works in 2 steps. When the binding is started or when manually triggered, the network is queried for the existence of a MAX! Cube lan gateway. When the Cube is found, it will become available in the discovery inbox. Periodically the network is queried again for a Cube.

Once the Cube is available in Openhab, all the devices connected to it are discovered and added to the discovery inbox. No scan is needed to trigger this.

Binding Configuration

In the Openhab2 version of this binding there are no binding wide settings. All the configuration settings are now per MAX! Cube, hence in case you have multiple Cubes, they can run with alternative settings.

Thing Configuration

All the things are identified by their Serial number, hence this is mandatory. The Cube (bridge thing) also requires the IP address to be defined. All other configuration is optional.

Note that several configuration options are automatically populated. Later versions of the binding may allow you to update this information. These properties can be found in the Device Settings section of parameters.


Depending on the thing it supports different Channels

Channel Type ID Item Type Description
mode String This channel indicates the mode of a thermostat
battery_low Switch This channel indicates if the device battery is low
set_temp Number This channel indicates the sets temperature of a thermostat.
actual_temp Number This channel indicates the measured temperature of a thermostat. see below for more details
valve Number This channel indicates the valve opening in %. Note this is an advaned setting, normally not visible
contact_state Contact This channel indicates the contact state for a shutterswitch
free_mem Number This channel indicates the free available memory on the cube to hold send commands. Note this is an advanced setting, normally not visible
duty_cycle Number This channel indicates the duty cycle (due to regulatory compliance reasons the cube is allowed only to send for a limited time. Duty cycle indicates how much of the available time is consumed) Note this is an advanced setting, normally not visible.

Full Example

In most cases no Things need to be defined manually. In case your Cube can’t be discovered you need a max:bridge definition incl the right IP address of the Cube. Only in exceptional cases you would need to define the thermostats etc.


Bridge max:bridge:KEQ0565026 [ ipAddress="", serialNumber="KEQ0565026" ] {
    Thing max:thermostat:KEQ0565026:KEQ0565123 [ serialNumber="KEQ0565123" ]


Group gMAX 			"MAX Heating" 	<temperature>	[ "home-group" ]

Switch maxBattery "Battery Low" (gMAX) {channel="max:thermostat:KEQ0565026:KEQ0648949:battery_low"}
String maxMode    "Thermostat Mode Setting" (gMAX) {channel="max:thermostat:KEQ0565026:KEQ0648949:mode"}
Number maxActual  "Actual measured room temperature  [%.1f �C]" (gMAX) {channel="max:thermostat:KEQ0565026:KEQ0648949:actual_temp"}
Number maxSetTemp "Thermostat temperature setpoint [%.1f �C]"  (gMAX) {channel="max:thermostat:KEQ0565026:KEQ0648949:set_temp"}


sitemap demo label="Main Menu"
	Frame label="MAX Heating System" {
			Switch  item=maxMode  icon="climate" mappings=[AUTOMATIC=AUTOMATIC, MANUAL=MANUAL, BOOST=BOOST]
			Setpoint item=maxSetTemp minValue=4.5 maxValue=32 step=0.5 icon="temperature"
			Text item=maxActual  icon="temperature"
			Switch  item=maxBattery

Actual Temperature Update

Please be aware that the actual temperature measure for thermostats is only updated after the valve moved position or the thermostats mode has changed. Hence the temperature you see may be hours old. In that case you can update the temperature by changing the mode, wait approx. 2 minutes and change the mode back. There is an experimental mode that does this automatically. This can be enabled by showing the “advanced settings”(e.g. in Habmin UI. Than the “Actual Temperature Refresh Rate” can be set. Minimum refresh rate once/10 minutes, recommended 60min to avoid excessive battery drain.

New Device Inclusion

When clicking the discovery button for MAX! devices manually in the UI, you will start New Device Inclusion mode for 60s. During this time holding the boost button on your device will link it to the Cube.

Device configuration

In the Configuration Parameters section of the device things you can update some of the device configuration parameters. Currently the following parameters can be updated:

  • name Name of the thermostat stored in the Cube (also used by the eq3 software).

Cube device configurable parameters

  • ntpServer1 The hostname for NTP Server 1 used by the Cube to get the time
  • ntpServer2 The hostname for NTP Server 2 used by the Cube to get the time

Action Buttons (visible in Habmin)

In the Habmin thing configuration screen several action buttons are available to trigger special actions on the Cube

  • Reset Cube Configuration. This resets the MAX! Cube room and device information. Devices will need to be included again! To use this button you need to enable ‘Advanced settings’

  • Restart Cube, triggers the reboot of a Cube. This can be used if a Cube became unresponsive to commands or no connection can be made. (e.g. if you tried to connect to the Cube with multiple applications at the same time)

On the MAX! devices you can trigger the following action

  • Delete Device from Cube. Deletes the device from the MAX! Cube. Device will need to be included again! To use this button you need to enable ‘Advanced settings’

Note: In PaperUI there are no action buttons. You can trigger these actions changing from ‘No Action’ in the dropdown to the action value.