Version: 5.0.rc1_2411011120
@Break
Could you update the blueprint and enable Presence Away Mode?
@Ohana_Means_family
I recommend to update to the latest stable release not dev version?
What happened to your thermostat errors? Did you find a solution?
now its working 
thanks
1 Like
This is the information on my thermostat, so it is also marketed as a “Tuya”, among other things. If I have understood it, would the aggressive mode make sense? If so how did you configure it?
White-label: Essentials 120112, Tuya GTZ02, Revolt NX-4911, Unitec 30946, Tesla Smart TSL-TRV-GS361A, Nedis ZBHTR10WT, TCP Smart TBUWTRV, Brennenstuhl HT CZ 01, Appartme APRM-04-001
Great news, Thanks.
I have 8 Sonoff TRVZB with z2m.
Just tell me if you need a beta tester.
Regarding valve positioning:
The TRVZB have a high hysteresis of -1.3 degrees to +0.5 degrees.
This could be avoided by always setting the entities valve_closing_degree & valve_opening_degree inverted at the same time:
valve_closing_degree = 100 - valve_opening_degree
This would make the “running_state” entity controlled by the TRVZB itself obsolete, as “idle” and “heat” are now in the same valve position
the name remains. Do I now have to set everything up again???
No, I can’t find the error
No, just switch to yaml mode and delete the _dev in the blueprint path. No need to complain…
I’m not complaining. I was just surprised that the labelling is different now. My mistake.
So, with the new version, both TRVs should be calibrated with the thermometer?
apparently something went wrong
Quick question now that there is a v5 that is so fundamentally different from v4, does the AHC Data template binary sensor need revising? I would imagine there are maybe some additional entities?
Also, does the AHC Latest Version sensor also need to revised for the new blueprint path?
Thanks
Yes, you can find the links below the import blueprint button in the first post of this thread.
With ha 2024.11 blueprints for template sensors got introduced. but they are way limited atm, also I found an major issue which needs to be fixed first and they are not UI ready for the moment.
1 Like
Thanks a bunch. It seems that your hint regarding proximity did the trick. Removed it and all was fine as far as I can tell. I will keep an eye on it but it looks good for now.
1 Like
how do i get notified when ahc is updated?
@panhans any thoughts on this? The scheduler adjustments are working fine when I set one scheduler, but not when using the selector?
Are you still on v4. I think I’d fixed this in v5.
I have a problem with the window open detection. I have created a binary group. If a certain number of windows are open, all TRVs should lock. The only problem is that when I open one, all TRVs close.
You could force the binary sensor group to be on if all of your windows are open.
If this option is not set the group turns on when at least only one window is opened.
If you want to check the group for a certain number to be open it needs a custom binary template sensor for that purpose.
Something like this:
{{ state_attr('binary_sensor.YOUR_GROUP','entity_id') | expand | selectattr('state','eq','on') | list | count >= 2 }}
Ok, did you double check the window entities in your blueprint settings? Only the group should be set as window.