Thanks for your feedback! I could recreate and fix that issue. I will release a new version soon.
Hey,
a new version just released. Just reimport the blueprint. Feel free to report some feedback.
Thanks everyone for testing, reporting and debugging!
Version: 2.10
3 Likes
I do have the same issue. Even though I have a schedule running and presence true, it always sets the minimum temperature.
Trace log: https://controlc.com/1001bc26
1 Like
Hi, did you check your version? This issue should be fixed with version 2.10.
I had a look into your trace and in my eyes everthing is fine.
Here is the trigger. Your occupancy sensor switched to off (to_state). At the end you can see it waits for 360 seconds:
"trigger": {
"platform": "template",
"entity_id": "binary_sensor.bm_wohnzimmer_occupancy",
"from_state": {
"entity_id": "binary_sensor.bm_wohnzimmer_occupancy",
"state": "on",
"attributes": {
"device_class": "motion",
"friendly_name": "BM-Wohnzimmer Bewegung"
},
"last_changed": "2023-10-17T19:28:31.697014+00:00",
"last_updated": "2023-10-17T19:28:31.697014+00:00",
"context": {
"id": "01HCZHRXEHVWWM676HWQYPTQCK",
"parent_id": null,
"user_id": null
}
},
"to_state": {
"entity_id": "binary_sensor.bm_wohnzimmer_occupancy",
"state": "off",
"attributes": {
"device_class": "motion",
"friendly_name": "BM-Wohnzimmer Bewegung"
},
"last_changed": "2023-10-17T19:31:31.703745+00:00",
"last_updated": "2023-10-17T19:31:31.703745+00:00",
"context": {
"id": "01HCZHYD7QBJE6SGQ3D092GHVB",
"parent_id": null,
"user_id": null
}
},
"id": "20",
"idx": "20",
"alias": null,
"for": {
"__type": "<class 'datetime.timedelta'>",
"total_seconds": 360
},
"description": "binary_sensor.bm_wohnzimmer_occupancy via template"
}
Here is a configuration part. Your presence reaction time is set to 6 minutes. This is the 360 seconds mentioned above. There is no presence detected. You have a time window of 4 hours and in this time window there was no occupancy for 6 minutes. So the TRVs will set to your minimum temperature.
"presence_reaction_time": 6,
"presence_detected": false,
"presence_time_window": 4,
"is_presence_time_window": true,
"temperatur": 17,
I assume, the presence detection does not work properly:
The presence detector is on but the automation sets to minimum temperature.
1 Like
Perhaps this is a misunderstanding. The presence detection with the time window is only for early shutdown. If you want the whole automation to run based on a presence sensor, then create an empty scheduler and select your presence sensor in the party mode. You can leave the other fields empty.
I will extend the FAQ and change the naming and descriptions.
But let’s say the scheduler will turn off at 22:30 and the time window is set to 4h hours, then it should work between 18:30 and 22:30 - correct?
But it doesn’t in my case as the presence sensor jumps between on and off, but the minimum temperature is to be set.
1 Like
Hi
I have started using your heating template and everything works as expected, I just have the problem that it always switches the TRVs to the heating state (for my TRVs this means that they are always fully open, regardless of the room temperature and my request for its value). I have failed to ensure that the “Auto” state is triggered (regulates the valve opening according to temperature).
I am using a TRV Immax, based on the Tuya system. Any idea how I could force a change in the TRV settings?
Thanks
1 Like
Ah, ok. I understand what you want to achieve. For me it was just a force shut down. I heat up my room based on schedulers and after 30 minutes when no movement was detected it forces the trvs to go to minimum temperature.
You also want to have the option that in that time window the presence sensor can reactivate heating to comfort temperature, right? I would provide a test version and will add a slider for the time the presence sensor must be on before TRVs will heat up again.
The use case of that is, that you maybe just forget something in your room and just want enter it for some seconds. For that time no heating is needed.
Is that fine for you?
2 Likes
I also use some tuya based TRVs. This automation only sets the TRVs to heat or to off.
After I replaced some batteries of my TRV it was also in auto mode. I had to disable it manually. I think there was shown a flame symbol. After disabling it there only was a wifi symbol and the current target temperature. In that state it can be controlled only manually or in this case by home assistant.
Be sure there is no other automation or integration that sets it to auto mode. Check the logbook to see if something in the home assistant is responsible or maybe a bridge or another app.
Yes exactly!
1 Like
Да, именно внешний датчик - может правильно анализировать, температуру в помещении.
Thanks for this blueprint.
Could you add the domain group to persons?
And the link to this thread in the blueprint doesn’t work.
1 Like
Thanks for your feedback. Here is a test version for you. If it fit your needs I will add it to the main version.
Which mdi icon is this?
Sry for the late reply. Here is a test version. There is a new boolean switch to activate heating again if presence is recognized in the time window. Waiting for your feedback. Thanks!
Hi and thanks for great blueprint and all your continued work.
I’ve tested version 2.11_presence_detection_b1 it appears that if the ‘Presence reaction time’ is set to Zero, heating does not resume from off to on state when presence is detected however heating is turned off when no presence is detected when ‘Presence reaction time’ is set to Zero. Increasing this to minimum of 1 seems to fix this, I will however continue to test.
To avoid issues later you might want to amend blueprint to fix the resume state if ‘Presence reaction time’ is Zero or set slider so that Zero is not allowed - however it is probably worth noting that this issue might be unique to me.
Using Tado heating system and TRVs via the HomeKit integration.
Aqara P1 Motion Sensor (occupancy entity) via ZHA
Thanks again Sean.
I think it works, but unfortunately it does not set the comfort temperature if “Presence activates heating” is enabled. It always stays at the eco temperature.
Edit: okay, similar problem as @sourdistorne has described: with 10 min as presence reaction time it has stayed at Eco temp, however with 1 min reaction time, it seemed to set the comfort temp, I do not know why.
There seems to be a problem with setting up the comfort temp again and/or presence detection: