[max] Can not change temperature via openHAB

gnilebein · January 22, 2024, 3:20pm

Hello,

I have the problem that I can no longer change the temperature of my thermostats via openHAB and the Max Cube.

openHAB accepts the change, a short time later the message appears that the data is being sent to the Max Cube. Before that, however, the temperature already jumps back.

The debug log shows this very well:

2024-01-22 15:57:57.859 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'maxSetTempGaesteWC' received command 23.0
2024-01-22 15:57:57.861 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'maxSetTempGaesteWC' predicted to become 23.0
2024-01-22 15:57:57.862 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'maxSetTempGaesteWC' changed from 19 to 23.0
2024-01-22 15:57:57.865 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Command queued id 158 (MKF0028830-set_temp:23.0).

…

2024-01-22 15:58:16.861 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'maxSetTempGaesteWC' changed from 23.0 to 19
2024-01-22 15:58:16.758 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Sending request #86 to MAX! Cube
2024-01-22 15:58:16.838 [DEBUG] [b.binding.max.internal.device.Device] - Device 1a9c92 (Thermostat): Actual Temperature : 21.9
2024-01-22 15:58:16.839 [DEBUG] [b.binding.max.internal.device.Device] - Device 10f1f7 (Thermostat): Actual Temperature : 23.6
2024-01-22 15:58:16.839 [DEBUG] [b.binding.max.internal.device.Device] - Device 11a512 (Thermostat): Actual Temperature : 20.5
2024-01-22 15:58:16.839 [DEBUG] [b.binding.max.internal.device.Device] - Device 11a480 (Thermostat): Actual Temperature : 23.2
2024-01-22 15:58:16.840 [DEBUG] [b.binding.max.internal.device.Device] - Device 0f73c9 (Thermostat+): Actual Temperature : 21.7
2024-01-22 15:58:16.840 [DEBUG] [b.binding.max.internal.device.Device] - Device 05b2c4 (Thermostat): Actual Temperature : 21.3
2024-01-22 15:58:16.840 [DEBUG] [b.binding.max.internal.device.Device] - Device 10f211 (Thermostat): Actual Temperature : 22.4
2024-01-22 15:58:16.841 [DEBUG] [x.internal.handler.MaxDevicesHandler] - Updating states of Thermostat Fenster (OEQ1740386) id: max:thermostat:MKF0026302:OEQ1740386
2024-01-22 15:58:16.843 [DEBUG] [x.internal.handler.MaxDevicesHandler] - Updating states of Thermostat Fenster (MKF0025858) id: max:thermostat:MKF0026302:MKF0025858
2024-01-22 15:58:16.846 [DEBUG] [x.internal.handler.MaxDevicesHandler] - Updating states of Thermostat Fenster (MKF0028830) id: max:thermostat:MKF0026302:MKF0028830
2024-01-22 15:58:16.848 [DEBUG] [x.internal.handler.MaxDevicesHandler] - Updating states of Thermostat Balkon (MKF0028927) id: max:thermostat:MKF0026302:MKF0028927
2024-01-22 15:58:16.850 [DEBUG] [x.internal.handler.MaxDevicesHandler] - Updating states of Thermostat+ Heizung (LEQ1074357) id: max:thermostatplus:MKF0026302:LEQ1074357
2024-01-22 15:58:16.852 [DEBUG] [x.internal.handler.MaxDevicesHandler] - Updating states of Thermostat Esstisch (JEQ0434275) id: max:thermostat:MKF0026302:JEQ0434275

Changing the temperature via the Max software works without any problems.

OH Version: openhab/openhab:4.1.1-debian (Docker)
Binding Version: 4.1.1
Max Cube Config:
- refreshInterval: 29 (tried 30 and 60)
- ntpServer1: de.pool.ntp.org
- ntpServer2: ntp.homematic.com
- port: 62910
- exclusive: true
- maxRequestsPerConnection: 1000

Best regards and thanks

marcel_verpaalen · January 28, 2024, 9:47pm

There can be a bit of delay

The command is queued, but it may take some time before the thermostat actually report back the new state. So there can be few refreshes which flip back to the old value, and once the thermostats reports the new state it will flip to the new

2024-01-22 15:57:57.865 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Command queued id 158 (MKF0028830-set_temp:23.0).

gnilebein · February 1, 2024, 10:55am

Thank you for your answer. But I don’t think that’s the case.

Here is a log file when I change the mode. Here the command is transmitted within a very short time. The whole thing happens within two seconds.

2024-02-01 11:48:59.289 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Command queued id 135 (LEQ1074357-mode:AUTOMATIC).
2024-02-01 11:48:59.289 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Command id: 135, channelUID: max:thermostatplus:MKF0026302:LEQ1074357:mode, command: AUTOMATIC, cubeCommand: null, serialNumber: LEQ1074357, key: LEQ1074357-mode, commandText: AUTOMATIC sent to MAX! Cube at IP: 192.168.112.99
2024-02-01 11:48:59.290 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Sending request #698 to MAX! Cube
2024-02-01 11:48:59.290 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - Write string to Max! Cube 192.168.112.99: s:AARAAAAAD3PJBgA=
2024-02-01 11:48:59.504 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - message block: 'S:07,0,31'
2024-02-01 11:48:59.505 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - === S Message === 
2024-02-01 11:48:59.505 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - 	RAW : 07,0,31
2024-02-01 11:48:59.505 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - 	DutyCycle         : 7
2024-02-01 11:48:59.505 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - 	Command Discarded : false
2024-02-01 11:48:59.505 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - 	FreeMemorySlots   : 49
2024-02-01 11:48:59.506 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - S message. Duty Cycle: 7, Free Memory Slots: 49
2024-02-01 11:48:59.506 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - Command id: 135, channelUID: max:thermostatplus:MKF0026302:LEQ1074357:mode, command: AUTOMATIC, cubeCommand: null, serialNumber: LEQ1074357, key: LEQ1074357-mode, commandText: AUTOMATIC completed for MAX! Cube at IP: 192.168.112.99
2024-02-01 11:49:13.637 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'maxValveBad' changed from 100 to 0
2024-02-01 11:49:13.577 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Sending request #699 to MAX! Cube
2024-02-01 11:49:13.577 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - Write string to Max! Cube 192.168.112.99: l:
2024-02-01 11:49:13.605 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - message block: 'L:CxqckgkSGAAKAAAACxDx9wkSGAAoAAAACxGlEgkSGCkmAAAACxGkgAkSGAEoANcACw9zyQkSGAAiAAAACwWyxAkSGCIoAAAACxDyEQkSGAAKAAAA'
2024-02-01 11:49:13.605 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - === L Message === 
2024-02-01 11:49:13.605 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - 	RAW: CxqckgkSGAAKAAAACxDx9wkSGAAoAAAACxGlEgkSGCkmAAAACxGkgAkSGAEoANcACw9zyQkSGAAiAAAACwWyxAkSGCIoAAAACxDyEQkSGAAKAAAA

And the log file when changing the temperature resets the temperature to the original value after 12 seconds, and only then does communication with the Cube take place:

2024-02-01 11:47:34.236 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'maxSetTempKinderzimmerY' received command 11.5
2024-02-01 11:47:34.243 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'maxSetTempKinderzimmerY' predicted to become 11.5
2024-02-01 11:47:34.243 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'maxSetTempKinderzimmerY' changed from 5 to 11.5
2024-02-01 11:47:34.251 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Command queued id 134 (MKF0025817-set_temp:11.5).
2024-02-01 11:47:46.335 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'maxSetTempKinderzimmerY' changed from 11.5 to 5
2024-02-01 11:47:46.220 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Sending request #695 to MAX! Cube
2024-02-01 11:47:46.220 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - Write string to Max! Cube 192.168.112.99: l:
2024-02-01 11:47:46.302 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - message block: 'L:CxqckgkSGAAKAAAACxDx9wkSGAAoAAAACxGlEgkSGCkmAAAACxGkgAkSGAEoANcACw9zyQkSG2QiAN0ACwWyxAkSGCIoAAAACxDyEQkSGAAKAAAA'
2024-02-01 11:47:46.302 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - === L Message === 
2024-02-01 11:47:46.303 [TRACE] [nternal.handler.MaxCubeBridgeHandler] - 	RAW: CxqckgkSGAAKAAAACxDx9wkSGAAoAAAACxGlEgkSGCkmAAAACxGkgAkSGAEoANcACw9zyQkSG2QiAN0ACwWyxAkSGCIoAAAACxDyEQkSGAAKAAAA