Presense sensor not working in combination with Proximity Sensor

[hfvdv]

My Setup is as follows:

• Defined location tracker for when i am home or not
• Defined a Proximity zone
• Defined a Presence Sensor
• AC used for coolling and heating
• CV used for heating

When the proximity zone ( home ) has status ARRIVED, Location tracker is HOME and Presence sensor is off ( or changes to off ) the AC and Radiator are not turned off. When i remove the proximity zone it is working as expected.

H

[panhans]

Hi, thanks for reporting.

I will check this soon. Atm I refactor everything and need to sort some things firs. If I can recreate that issue all will be fine. Maybe I need a trace log.

BR

[panhans]

Hey, so I checked this case. Yes, atm it heats if state is arrived. It makes sense if someone uses proximity only. I will change this to make status arrived only kicking in when no scheduling and presence sensor is defined. I will add this to the refactored version. This gonna replace v4 and v3 this week.

[panhans]

https://github.com/panhans/HomeAssistant/commit/479d3d72459e5e2bb039eb150af35e151a2bd4c4

[hfvdv]

it was my understanding the proximity sensor could be used to for example say if my car is within 50 km of my house with the status direction of travel being towards my bouse to activate the heating. in other words pre heat my house so its nice and warm when i come home. If i then enter my living room its nice and ready. However then the presence goes off and the proximity status is also arrived then the heating should go off again.

open to any other options to preheat the house dynanically based on some sort of geofencing

H

On Mon, 5 Feb 2024 at 08:33, panhans @.***> wrote:

Hey, so I checked this case. Yes, atm it heats if state is arrived. It makes sense if someone uses proximity only. I will change this to make status arrived only kicking in when no scheduling and presence sensor is defined. I will add this to the refactored version https://github.com/panhans/HomeAssistant/blob/dev_v4/blueprints/automation/panhans/heating_control_v4_ref.yaml. This gonna replace v4 and v3 this week.

— Reply to this email directly, view it on GitHub https://github.com/panhans/HomeAssistant/issues/57#issuecomment-1926378747, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3AUYCBKPYFN77KSFFZFI4TYSCDL7AVCNFSM6AAAAABCUOZWTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRWGM3TQNZUG4 . You are receiving this because you authored the thread.Message ID: @.***>

[panhans]

Yes, in the latest update your room should heat up when state of proximity is TOWARDS. If state changed to ARRIVED is has no impact anymore if you defined a scheduler or a presence sensor. I recently updated the v4 version with my refactored one. Feel free to test and report.

[hfvdv]

Great. Will definitely test and share my findings. The other thing i noticed ( unsure if i need to raise a feature request or and an issue ) is that:

• when using my Airco using Midea as a device it is correctly set to heat. Using override to turn off when not needed anymore as i don't want that for my Airco.
• when using the same Airco using the Tado integration it defaults to cool. What would be great is to be able to indicate if the device need to use heat or cool mode.

H

[panhans]

Yes, thats planned if the current release candidate is ready for final. The active hvac mode selection is already on my list.

Planned features are listed in here in the initial post:

https://community.home-assistant.io/t/advanced-heating-control/469873

[hfvdv]

Great

just tested 4.0_rc2

the proximity entitity selector is only allowing for selecting of zones and not the proximity sensor itself

H

On 9 Feb 2024, at 13:11, panhans @.***> wrote:

Yes, thats planned if the current release candidate is ready for final. The active hvac mode selection is already on my list.

Planned features are listed in here in the initial post:

https://community.home-assistant.io/t/advanced-heating-control/469873

— Reply to this email directly, view it on GitHub https://github.com/panhans/HomeAssistant/issues/57#issuecomment-1935819378, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3AUYCHSWT4UAKEVGKQPGUDYSYG7XAVCNFSM6AAAAABCUOZWTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVHAYTSMZXHA. You are receiving this because you authored the thread.

[panhans]

Yes, there was a breaking change in latest home assistant release 2024.02

You have to delete your old entity and create a new service in the ui. The old proximity integration is deprecated now.

[hfvdv]

I did that.

However only zone. entities are shown. proximity. devices are not selectable. Currently on 2024.2.0

On 9 Feb 2024, at 20:26, panhans @.***> wrote:

Yes, there was a breaking change in latest home assistant release 2024.02

You have to delete your old entity and create a new service in the ui. The old proximity integration is deprecated now.

— Reply to this email directly, view it on GitHub https://github.com/panhans/HomeAssistant/issues/57#issuecomment-1936482696, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3AUYCFSBGWCEGA2DTY55QLYSZZ5FAVCNFSM6AAAAABCUOZWTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWGQ4DENRZGY. You are receiving this because you authored the thread.

[panhans]

You can delete your proximity entity. There are only sensors now. They will be selected dynamically by the zone you defined in your proximity service and the person you set in blueprint settings.

[hfvdv]

Aha I see. That might explain. I was using my car as device tracker as that is more reliable then my phone. Will do some more testing HSent from my iPhoneOn 9 Feb 2024, at 20:42, panhans @.***> wrote: You have to can delete your proximity entity. There are only sensors now. They will be selected dynamically by the zone you defined in your proximity service and the person you set in blueprint settings.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[panhans]

Could you add your car to your person entity in settings?

[hfvdv]

I can givee it a try however its a shared faility car. the interesing use case for me would be that if no one is home and the car is hearing toward the house the assumption is that some will be home soon and i need to pre-heat or cool the house.

i also noticed that when my presence sensor is off it sets the thermostat to 30. In teh graph below:

• I was away between say 18.00 and 20.00 Thermosetat went to 30
• we came home around 20.00 and were in the living room until about 10.00 ( thermostat correctly went to 22
• during the nights its been at 30 while presence is off ( and car is home but not moving )

H



On 9 Feb 2024, at 21:32, panhans @.***> wrote:

Could you add your car to your person entity in settings?

— Reply to this email directly, view it on GitHub https://github.com/panhans/HomeAssistant/issues/57#issuecomment-1936563906, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3AUYCGMFC2UZTDNM2UQKH3YS2BUDAVCNFSM6AAAAABCUOZWTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWGU3DGOJQGY. You are receiving this because you authored the thread.

[panhans]

Ok, I will think about it. Its not that easy with the new integration to select everything right.

Did the behavior you described happen with the current release candidate or with the "old" version. If it's the current could you pick the trace log of your automation when temperature changes to 30? But did you use such great values in your automation. Seems like this is the maximum. It just will be set if you enable force max temperature or you set such a high or higher comfort / eco temperature.

[panhans]

I recently pushed an update. Now you can select a proximity device. This should work like before when selecting the proximity entity. Feel free to test and give feedback.