Hendrik,
I made them myself - feel free to use them 
max_mode.svg: 
max_mode-automatic.svg: 
max_mode-manual.svg: 
3 Likes
I have something to contribute. I want to keep basic configuration in cfg files, and the example thing definition in the documentation throws up warnings in the log. I found the following syntax to be working without warnings in the logs.
Bridge max:bridge:JEQ0341220 "MAX! Cube LAN Gateway" [ ipAddress="192.168.189.23", serialNumber="JEQ0341220"] {
Thing ecoswitch JEQ0301258 "Eco Taster" [ serialNumber="JEQ0301258" ]
Thing shuttercontact JEQ0318859 "Fenster Badezimmer Sensor" [ serialNumber="JEQ0318859" ]
Thing shuttercontact JEQ0318809 "Balkontür Schlafzimmer Sensor" [ serialNumber="JEQ0318809" ]
Thing shuttercontact JEQ0320423 "Balkontür Wohnzimmer Sensor" [ serialNumber="JEQ0320423" ]
Thing thermostat JEQ0424354 "Heizkörperregler Kinderzimmer" [ serialNumber="JEQ0424354" ]
Thing thermostat JEQ0424374 "Heizkörperregler Wohnzimmer Klein" [ serialNumber="JEQ0424374" ]
Thing thermostat JEQ0424309 "Heizkörperregler Schlafzimmer" [ serialNumber="JEQ0424309" ]
Thing thermostat JEQ0424424 "Heizkörperregler Badezimmer" [ serialNumber="JEQ0424424" ]
Thing thermostat JEQ0424464 "Heizkörperregler Wohnzimmer Gross" [ serialNumber="JEQ0424464" ]
Thing wallthermostat IEQ0492172 "Wandthermostat Schlafzimmer" [ serialNumber="IEQ0492172" ]
Thing wallthermostat JEQ0654349 "Temperatur Balkon" [ serialNumber="JEQ0654349" ]
Thing wallthermostat JEQ0656854 "Wandthermostat Wohnzimmer" [ serialNumber="JEQ0656854" ]
Thing wallthermostat NEQ0086617 "Wandthermostat Kinderzimmer" [ serialNumber="NEQ0086617" ]
}
2 Likes
Continuing the discussion from MAX! system installation and configuration walktrough:
Hi Pekka,
Thank for this great tutorial!
I’m looking for a heating system room-by-room and Max seems the ideal candidate. And cheap 
As I understand Max is made for homes with central heating, but in my case I have to turn on the boiler.
Is it possible to use OH and adapt Max to my needs?
I was thinking of using a rule like that
rule "valve to boiler"
when
Item maxValve01 changed
then
if (maxValve01.state == ON) {
switchBoiler.sendCommand(ON)
}
else
if (maxValve01.state == OFF) {
switchBoiler.sendCommand(OFF)
}
end
to give a command to a relay that turns on the boiler.
Note: I think is important to use valve state (on/off or open/close) and not a thermostat temperature value.
Has anyone already tried it or seem good this way?
Thank you
Stefan
I don’t know if that works, but it might.
I would refrain from using Max!, as it is a one-purpose-system. I’d rather recommend momematic from the same vendor, much more flexible.
You could by using the valve valve. If the max system thinks it is cold, it starts opening valves. That would be your cue to switch on the boiler. Please note that max doesn’t have a switch for that
Hi all,
short @Pekka: is this working for all MAX! thermostats (Basic, normal, +)?
I am currently looking for the right thermostat and MAX! seems to be the best from price performance point of view.
Kindly,
Woogi
@Woogi, yes, this is for the Max! system.
However, I would recommend to choose the (more expensive) Homematic. I have the feeling that that system is more supported by the vendor, eq3 - and you haveone system when it comes to other devices.
thanks for your reply. So it works for all MAX! Thermostats (Basic, normal and the + Version). Great.
Is a deeper support needed by the vendor which explains the need to buy the double price higher homematic system?
Well, with homematic you have all options, while Max! is just a heating control…
A great tutorial! Thanks for your work! I like the way you’re managing all the components.
I’ve stared with OpenHab a few days ago and i’m wondering if there is any magic behind the scenes or what is the best practice to handle the logic.
Do i have to bind all components “the manufacturer way” and then “add” them to OpenHab or do i add all components unconfigured as things and handle the logic with rules?
You set the temperature for the living room only to the wallthermostat, but i can’t see anything in the configurations above which could be responsible for delegating this to the radiator thermostats and i wonder if you paired the wallthermostat with the two radiator thermostats with the learning mode outside openHab or if you have any rules which handle this.
I asked myself the same question. Have you already found a solution?
You configure the Max! system like it’s standalone, and after that you add it to OpenHab.
What you set the wall thermostat’s temperature, it gets inherited to the heating thermostats by Max!, so you only need to set one temperature for the whole room.
Thank you very much for your extremely helpful walkthrough!
However, it left me with a question regarding this:
According to the docs:
Sending a command to a Group causes the command to be sent to all Group members.
So I’ve tried to do it this way, and it seems to work perfectly well:
// Temperatur absenken
gMaxAutoTemp.sendCommand(11)]
gMaxAutoMode.sendCommand("MANUAL")]
This appears much simpler to me. Have I overlooked something?
I had some reasons for not doing it that way - however, I don’ remember them. So maybe I was wrong, or someone else may point us to the reasons…
Regarding setup of the cube itself:
The max cube has an own program to control.
How is the best way to disable that in the web interface of the cube?
Why would you like to do that?
the cube itself has a “week program” in factory default.
So the “week program” of the cube overwrites the last setpoints from openhab eventually.
The thermostats have a week program which is written by the cube, yes. That is exactly what you want: Use OpenHAB to set the current temperature to a new value, without disturbing your schedule.
If you want to get rid of the weekly schedule, set the thermostats into manual mode as decribed above (Section "Usage in rules).
Thx!
I afraid that but I found it a bit strange to see allways manual mode on the display.
Someone could try to press the auto button on the thermostat.
But I’ ll do that manual now.