Just one question please, instead of using a seperate temperature sensor here I would like to use the temperature sensor of the TRV, is this possible because the only entity I can think about is the ālocal_temperatureā but I canāt find it back as an entity in the MQTT listing but in Z2M the status shows this
First of all thanks for a great blueprint sharing. I have a question. Iām using Winter mode for general enable of all my heating thermostats during winter/heating season. Is it possible to add another Input_boolean for controling some of thermostats, as I want to control few thermostats that depends on another input_boolean.
@bojke
I think this is for the most users a bit confusing and hard to realize with the possibilities of jinja and yaml code. Couldnāt you just clone your automation, remove the climates you donāt want for the other input boolean and just set it?
Hi,
I just updated to the current v5.x version and migrated all of my automations from the v4.x version. I basically opened the old automation twice and changed to the new blueprint while copying over the settings from the old one in the other tab. Long story short I have 2 rooms which would require a guest mode to be turned on to run at the comfort temperature. This worked fine with the v4.x version and I checked that guest mode is not set (turned off) but with the new blueprint the rooms were heating up anyways although they should not. Did something change here with the pure guest mode or am I missing something?
I guess itās your proximity sensor, right? It got handled like a person now. So when youāre home comfort heating is set.
Did you use proximity in this configuration? If yes it could be that in v4 the comfort was only set if someone is on way home. But if home it has no impact anymore?
But maybe you could go a step further and share just a trace log. Thanks!
You mean, I should not set a proximity sensor at all? The way it used to work was when the guest at home mode was turned on it used the scheduler and heated the room accordingly. If disabled the room remained at the eco temperature. So if I understand you correctly, not setting the proximity sensor would do the trick?
I think Iāve fixed this now, but I wonāt know for sure until nobody is at home again. Iāve now got the target temperature in all rooms reacting in the same way and in the way I want them too.
Itās quite easy to miss a setting when your creating as many automations as I have.
Unfortunately, the calibration of the second TRV does not work. It retains the internal temperature measured on the TRV. The TRV is set to external. Aqara TRV.
Thank you for your answer,
I have now set to heating, as my thermostat now shows me the manual mode, furthermore I have not made any changes except for opening.
Do you have any beginnerās tips for optimizing the thermostats?
Greetings
@Break
Could you share your current configuration in yaml?
@Ohana_Means_family
Are you on the latest stable? Looks like youāre using still the dev version. Did you also check if the calibration entity has external in itās id? No other entity of this thermostat should have this keyword in its id.
@cgott82
Not really. I own some Tuya TRVs and now Sonoff. My Tuyas needs aggressive mode. The Sonoff TRVs are working fine without any tweak. It depends as always.