But the 0,1 instead of 0 is expected behavious of the Sonoff thermostats?
No it’s fine. The with external configuration the value will be updated at least every 20 min.
Oh My God. For the first time ever, all my thermostat temps are 100% aligned with external Thermometer readings. This is what I wanted from the very beginning, I spent so many hours working on this and one keyword mentioned by you fixes everything.
I suggest you add that a bit more explicitely to the guidance at the beginning of this thread, maybe that spares someone else some time?
As always, you have been so helpful! How do you have time for a proper job when we steal all of your time with our stupid problems?
One man’s opinion @Raffe…
Experience from fresh eyes that just went thru startup would be great.
Take a shot at making an edit suggestion…
Yeah, I see two places for clarification:
-
Inside the Blueprint itself. It does refer the need for a targeted key-word for internal calibration, but completely omits the same for external. In my naivity, I had assumed this means you switch calibration off when going to external temp:
-
At he very beginning, there is this box about changes to v5.5. Adding the below bullet point would help:
- using calibration by external temperature be sure the calibration entity contains the word “external” or “external_temperature_input” and not calibration.
I have proximity set to 1000 (meters). I was 80 000 meters away 
So pretty sure it’s not working?
I can test it this evening. You can watch the proximity entity in your history or dev tools if it’s working properly. If yes, a trace log of the automation run would be helpful.
//EDIT: @Unhumanje Just update the blueprint. A small piece was missing.
Thank you! I’ve removed all devices/people from the ‘Persons & Devices’ section, i’ve enabled proximity at 1000 (meters), and I’ve enabled “off if nobody home”. This is on top of my active comfort/eco schedule. Will report back how it goes!
Just for my sanity, based on what you said before, is the expected behaviour now:
- If at home & within schedule - comfort
- If not home, but in proximity zone - regardless of schedule - eco (this is where I’m not sure how the proximity range aligns)
- If outside of proximity zone - off ?
Home + schedule on → comfort
Home + schedule off → eco
Outside proximity zone → off
Inside Proximity Zone and Towards Home → comfort, else off
1 Like
Is there a way to disable any adjustment?
E.g. I want to preheat my bath, before I get up, so it’s comfy in there.
So I added
- time: "06:00"
comfort: "30"
days: ['Mon','Tue','Wed','Thu','Fri']
- time: "08:30"
days: ['Mon','Tue','Wed','Thu','Fri']
would that be working, when the second time block simply doesn’t have any temperature?
What this do is setting the comfort temperature to 30° at 6:00. I think your schedule is on at this point? You also can force the mode to comfort. The 2nd entry will do nothing. The comfort temperature will stay on 30°.
What should happen at 08:30?
Oh I thought I could just override the comfort temp to 30 and revert to whatever it was set to on 08.30.
But if it simply set’s the temperature, I might have to get creative for this behavior
Hmm… I don’t know. I’ve never tested this. Just try it but don’t forget to disable Sync Adjustments With Entities in your settings. Forget this feature got introduced with the latest version. xD
1 Like
Sadly I don’t think it works. But it also set’s the comfort entity anyway, even though the Sync Adjustments With Entities is off
It actually works, but for that you need to also disable Temperature Tweaks > Physical Temperature Change / Sync. Only then will it not override the Comfort Temperature Entity
Hi,
I’m using latest version (5.5.6) and I see some weird behavior. I have a radiator Comet COZB0001 (Eurotronic COZB0001 control via MQTT | Zigbee2MQTT) which supports 2 TRV modes (1 aka manual and 2 aka auto) and I can set the valve position when it is on 1. So I have set first the eco mode to be off but I see that it goes to Auto HVAC. Additional when it get triggered by the conform temp. it goes to Heat HVAC (as I set it in HAVC settings) but the valve position remains to 0. The keyword I set it to “valve_position” (entity id: number.living_room_radiator_valve_position), timeout default (20min).
The radiator itself when it is on Auto/eco is still slightly warm but on the Heat is goes more which someone is says normal but I’m not sure where is the valve.
Any help?
Yes, maybe it needs a modifier in the adjustments to disable the physical sync feature temporarily. This shouldn’t happen. I will test it and fix it if I can.
Did you see the state of your valve positioning entity or is it write only? Try to decrease the timeout, but with a temperature change the valve position will be forced regarding the timeout.
1 Like
I’m not sure what you mean with state or write only, so I can provide screenshots
Changes to position yesterday to 11 and 147 where manual to test if works. I also try to play with the temperature difference but didn’t help.
Could you reimport the blueprint and test again. Didn’t know there where valve positioning entities with values up to 255. This should now work with your entity, also with negative values if there are implentations like that.
1 Like
Hello. I recently started using the excellent Blueprint. My situation is as follows. The air conditioning system is my primary heating source, and I use infrared ceiling heating as a secondary heating system. The air conditioning is efficient and the infrared heating provides comfort.
How can I control the air conditioning so that it is the main heating system (up to approx. 1° below the target temperature) and the infrared only comes on at the end to take over the rest? If the delta is greater again, the air conditioning should switch back on.
Does this type of control work with this Blueprint?
Many thanks in advance.