You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Im new to BT but I read through the whole repo and issues to get more informations how BT is working with HmIP (ccu3).
Some discussions and Issues lead me to this setup for a normal room:
HmIP-eTRV-2
a cheap ewelink window/door sensor
a cheap temp sensor for outside measurement
On creation of the BT-entity for this room I made this configuration:
Target Temperature Based
no calibration
the homematic option
In my logs i found information about using the "switch mode auto and heat" but also I find discussions about this option to not use it with homematic devices. I tried both and cant see a difference.
Also I set the "HmIP-eTRV-2" to mode "manual" instead of "auto" (to not use the week programs) in raspberrymatic.
Every time I use the BT "climate.my_room" entity to change the temp, the device will be set to the given temp in the ccu3. But also it switches directly to "auto"-mode. So the week plans are active immediately.
If i set the temp in the homematic entity (climate.hmip_etrv_2_my_room) the mode will be stay at "manu"-mode in the ccu3.
I tried also the BT UI card but the mode will every time switched to "auto"-mode in the ccu3.
For now I have no ideas to fix this behavior. Also Im not sure if its really a problem?
Generally I can see slightly higher temps in my rooms as with the original ccu3 week plans but i see also a better or "faster" temp increase (what is an improvement for me).
Any ideas or suggestions for the configuratoin?
Any clarifications for the usage of HmIP devices (especially the TRVs)?
Thanks in advance :)
*edit:
BT Version 1.7.0
HA Version 2025.10.1
Homematic(IP) local 1.88.1
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Im new to BT but I read through the whole repo and issues to get more informations how BT is working with HmIP (ccu3).
Some discussions and Issues lead me to this setup for a normal room:
On creation of the BT-entity for this room I made this configuration:
In my logs i found information about using the "switch mode auto and heat" but also I find discussions about this option to not use it with homematic devices. I tried both and cant see a difference.
Also I set the "HmIP-eTRV-2" to mode "manual" instead of "auto" (to not use the week programs) in raspberrymatic.
Every time I use the BT "climate.my_room" entity to change the temp, the device will be set to the given temp in the ccu3. But also it switches directly to "auto"-mode. So the week plans are active immediately.
If i set the temp in the homematic entity (climate.hmip_etrv_2_my_room) the mode will be stay at "manu"-mode in the ccu3.
I tried also the BT UI card but the mode will every time switched to "auto"-mode in the ccu3.
For now I have no ideas to fix this behavior. Also Im not sure if its really a problem?
Generally I can see slightly higher temps in my rooms as with the original ccu3 week plans but i see also a better or "faster" temp increase (what is an improvement for me).
Any ideas or suggestions for the configuratoin?
Any clarifications for the usage of HmIP devices (especially the TRVs)?
Thanks in advance :)
*edit:
BT Version 1.7.0
HA Version 2025.10.1
Homematic(IP) local 1.88.1
Beta Was this translation helpful? Give feedback.
All reactions