Combine Max! schedule with external contact sensors

---

It changes the color to grey and after 20 seconds back to white. The setting seems to be kept.

@saxnpaule
Okay, so it basically works.

Try installing a small delay. For example: when fenster-kinderzimmer is opened set mode of max-thermostat-kinderzimmer to "manu" and set temp of max-thermostat-kinderzimmer to 4.5 after 10 seconds

But as I said, this rule works for me.

Maybe there’s a problem connecting to the cube. I’ve had that before. Restarting the cube helped.

I restarted the cube several times during the last days.
I try the delay.

I also get several connection errors every night between 4 and 5. “cube is busy” or ECONNRESET.

But this seems to have no impact because everything works still fine the next morning.

Cube has no internet access by firewall rule in the router.

@saxnpaule I’m sorry, then I have no idea anymore…

@SaxnPaule

The MAX Plus thermostats have no advantage when you have the cube.
These are only designed for stand-alone operation. The cube or pimatic is responsible for scheduling.

My recommendation for your problem is to switch to maxcul
and make the schedule with pimatic.

I have been using the cube with max-plugin for a long time, but i did the schedule with pimatic.
This had two disadvantages.

• delay due to polling mechanism
• and connection losses

The cube allows only one simultaneous connection. (MaxSoftware/pimatic)

That’s why I switched to the maxcul solution and flashed my cube.
This works properly. see here But there is no way back!

And since yesterday the maxcul plugin also supports wall thermostats, fake devices and
pairing devices together. (v1.0.0)

@kosta said in Combine Max! schedule with external contact sensors:

The MAX Plus thermostats have no advantage when you have the cube.
These are only designed for stand-alone operation. The cube or pimatic is responsible for scheduling.

I am not sure this is correct. My understanding is that Max Plus add means for directly programming the thermostat via the control panel. Another new feature is the childlock which has been added to avoid accidental reprogramming or state change. In turn, when the childlock is active it is no longer possible to switch to manual mode.

See also
https://www.elv.de/topic/unterschiede-zum-alten-heizkoerperthermostat-ohne-plus.html

Regarding the “cube is busy” problem I am not sure whether this is due to poor connection handling on the plugin side or the cube itself cause the problem. @kosta Did you ever look into this issue?

@SaxnPaule Getting back to the original problem, make sure the childlock is disabled.

Yes, the schedule is “flashed” to the thermostat it self.
Childlock is deactivated in my case.

Yesterday the “window open” case worked well for me with the delay. I will monitor it some additional days.

But another case occured. I pressed the “boost” button at the thermostat and the countdown started 600, 599, 598, …
When I looked again after two or three minutes, the thermostat was back on auto mode with setpoint to the comfy temp. There are no other rules defined in pimatic than window open/close. And the “update” rule that changes the setpoint every 10 minutes by plus/minus 1°

@mwittig What about the device variables (comfy, vac, eco)? Could you make them accessible via action?

I think I know whats going wrong.

The update rule crashes the whole logic.

For example pimatic seems not to recognize when the thermostat is on boost mode. Then the rule is triggered and changes the setpoint by 1°. That kills the boost mode.
If pimatic would know about it, I could check it via rule and only update when it’s not active.

The rule is needed to get the temperature measured by the thermostat. As it is only published on changes.

@saxnpaule said in Combine Max! schedule with external contact sensors:

If pimatic would know about it, I could check it via rule and only update when it’s not active.

In my case, Pimatic detects the boost mode, even if it is activated by the thermostat. It may take a few seconds. Simply query the variable $max-thermostat-kinderzimmer.mode (‘manu’, ‘auto’ or ‘boost’).

Well, okay. Does it also detect the “window open” mode? This is absolutely necessary. If not, the schedule would be activated although the window is open.
It would also be great if the “window open” mode could be triggered by rule instead setting the thermostat to manu and 5°

@saxnpaule
I don’t understand. The Max! window contacts are detected by the cube and the temperature is automatically reduced to a preset value when the window is open. If other contacts are used, it is not possible to use the cube but must be done with a rule via Pimatic.

@saxnpaule said in Combine Max! schedule with external contact sensors:

What about the device variables (comfy, vac, eco)? Could you make them accessible via action?

Sorry, I can’t do that as I don’t have a device to test with at the moment. Feel free to submit a PR on the matter.

@wajowi said in Combine Max! schedule with external contact sensors:

@saxnpaule
I don’t understand. The Max! window contacts are detected by the cube and the temperature is automatically reduced to a preset value when the window is open. If other contacts are used, it is not possible to use the cube but must be done with a rule via Pimatic.

Yes, and thats the case. The Max! contacts are hugh and ugly. I use Kerui D026.

I have a rule and set the cube to manu mode and 5° when the window is opened. But after x minutes the “update rule” destroys the setting.

I think I need to tune the update rule to store and restore all available variables.

@mwittig You are right.
The MAX plus has a programming interface via the control panel, but I think that with a central management this doesn’t play a big role. A normal childlock is also available with the normal thermostat. The plus has a “extended” childlock.

I haven’t made a more detailed analysis about the connection issue. I think it’s on the cube side.

@SaxnPaule
my suggestion for the cul firmware was primarily for the possibility to send a fake window open message to a thermostat.
i use also gs-iwds07 contact sensors

After three weeks of testing I don’t know how to move on.

At the moment I only use the manu mode at the thermostat. The Pi is able to receive all updates, thats fine. But I’m not able at all to trigger any changes at the Pi.

When I change the temperature in pimatic, the item turns grey and after several seconds, it changes back to white (black in default theme) and has the old temperature again. At the termostat nothing happened.

The thermostat is in manual mode and child lock is disabled. Do you have any ideas?

Same behavior with the other buttons (auto, comfy, eco, boost).

I also had some problems with the max cube but most of the time it works fine.
Restart the cube and make sure that you don’t have any other connections to the MAX cube (App, PC software, Cloud?) as it really can only handle one client.

I already did. And I also set everything to factory defaults. The connection must be fine, because reading the values works fine at every time.