-
|
Hello, In OpenCCU I have just one group with one thermostat (HmIP-eTRV-2) programmed with one profile - all weekdays with temperature set to 21. I wanted to test Away mode action, so in HA I triggered "homematicip_local.enable_away_mode_by_duration" and set time to one hour and temperature to 18. OpenCCU and thermostat perfectly reflected this change, and I could see that away mode is active and temperature is set to 18 (from 21) with given duration. Also in HA integration "temperature" attribute of climate device has been set to 18 (from 21). After duration time passed, in OpenCCU (and in thermostat) temperature returned to previous (21) and away mode has been disabled. And this is expected. Unfortunately, what is not expected, HA integration didn't observe this change and in climate device I still can see "temperature" attribute set to 18 (should be 21 know). So, after using "away" mode action, looks like integration is not receiving updates from OpenCCU, but still it works other way. I can set temperature to 21 in HA, it returns to 18, but OpenCCU and thermostat is aware of this new change (received it). Looks like communication OpenCCU -> integration is somehow broken. After integration reload solves this issue. Is this a bug or maybe I did something wrong? Please help. Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
From an integration perspective, this sounds good at first, because only one command is sent to the CCU, and the further execution then also takes place there. From the integration side, no further commands are sent. When the away mode is deactivated, the CCU should then send updating events. However, this doesn't seem to be happening. |
Beta Was this translation helpful? Give feedback.
-
|
In the mean time I did another test, same scenario, away mode activated by action, and this time it worked flawlessly. After duration time, integration has been fully updated. Maybe it was some kind of anomaly? Hard to say (nothing in logs). Now, I'll do test you mentioned and let you know ASAP. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, your scenario also works good. So, perfect! Maybe it was just some anomally. I'll keep observing. Sorry for bothering you, |
Beta Was this translation helpful? Give feedback.
From an integration perspective, this sounds good at first, because only one command is sent to the CCU, and the further execution then also takes place there. From the integration side, no further commands are sent. When the away mode is deactivated, the CCU should then send updating events. However, this doesn't seem to be happening.
Please try testing it again and activate the away mode via the CCU web interface. What happens then?