Home Assistant release:
0.61.1
Python release:
Unknown
Component/platform:
eQ-3 MAX! Cube thermostat
Description of problem:
An error occurs when changing temperature for MaxCube thermostat, using either arrow buttons in GUI or using an automation.
Expected:
Temperature can be changed; was possible in previous releases.
Problem-relevant configuration.yaml entries and steps to reproduce:
maxcube:
host: 192.168.1.209
Traceback (if applicable):

Additional info:
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Issue still exists on 0.66.0
Same here, issue still exists on 0.66.1.
I get this error when changing from manual to auto mode.
2018-04-07 23:25:27 ERROR (MainThread) [homeassistant.core] Error executing service <ServiceCall climate.set_operation_mode: operation_mode=auto, entity_id=['climate.gang_og_hk_gang']>
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/core.py", line 1002, in _event_to_service_call
await service_handler.func(service_call)
File "/usr/lib/python3.6/site-packages/homeassistant/components/climate/__init__.py", line 392, in async_operation_set_service
await climate.async_set_operation_mode(operation_mode)
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.6/site-packages/homeassistant/components/climate/maxcube.py", line 138, in set_operation_mode
self._cubehandle.cube.set_mode(device, mode)
File "/usr/lib/python3.6/site-packages/maxcube/cube.py", line 253, in set_mode
self.set_temperature_mode(thermostat, thermostat.target_temperature, mode)
File "/usr/lib/python3.6/site-packages/maxcube/cube.py", line 270, in set_temperature_mode
command = 's:' + base64.b64encode(bytearray.fromhex(byte_cmd)).decode('utf-8') + '\r\n'
ValueError: non-hexadecimal number found in fromhex() arg at position 21
not working in 0.76.2
when changing temperature of one thermostat, others on the same cube change?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
I have the same problem as eswjm1981 on HassOS 1.13. i have got 4 thermostats in three rooms.. the two in the living room work just fine but when I change the temperature for the one in the office or in the bedroom the other one changes as well.. I really don鈥檛 know why.. i will try to reset the max cube and install it again maybe this helps but I鈥檓 pretty sure it has worked in the past.
Just to confirm: still exists on 0.91.3. Integration is unstable and in some cases, the multiple thermostats are being updated when the temperature of one of them is changed.
@BastianPoe think you could debug this?
Has there been a recent firmware update of the cube?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
when changing temperature of one thermostat, others on the same cube change?