I did what you asked. Somehome 3 traces were created shortly after another so I uploaded them all here:
Hi,
I need some help in debugging the Proximity, as seen below, I have set it up at 8 in the blueprint (i think 8000 it the correct number I need to use) but my issue, is that it triggers with 8 and i use meters as setup, and here you can see 9361m (9km) and the automation har triggered heating. not good as I drive around at work, and it triggers every time I drive in the direction of my home (while being more them 10km away)
Please advice on what iām doing wrong?
@panhans and friends: Is(nāt) there a list of TVR Devices that work well with the AHC Blueprint (under Z2M)? As far as I understand, not all theortically suitable devices* work well?!
Thanks to @LvS21 I knew and saw that Avatto ME167 works fine, but does ME168, too? Would it be nice to have a link to suitable devices in the first post?
_* Does someone know how to better filter the above linked device list for TVR? The expose ālocal_temperature_calibrationā e.g. canāt be chosen ); A Pity there is no category like āProduct categoryā
Hi Dennis,
Its a liitle Offtopic but i have exact the same configuration as you have. I also want to use thecalibration feature from this blueprint, but it doesnt work for me. For now i have another automation to set the the temperature from external sensor to TRV, but it would be great to have only one automation.
Might be related to the Firmware Update of the TRVs 0.0.0_1030 at least there is a similar issue mentioned for the dedicated blueprint here: [Z2M] Aqara TRV E1 link external temperature sensor - #50 by ThWoell.
Tested the script, but step 6 doesnāt seem to work and the climate stays off, so it looks like something with the scene doesnāt work.
1 Like
@DenisLanz Navigate to the device overview, open your climate entity and there you can find the number entitiy for calibration. If you set this to a random value it should be set or result in that error youāve mentioned before.
Just have a look into the description of the proximity distance option. "Hint: Unit depends on the setup of your integration. Seems your unit is m not km. So you have to set the distance to 8000.
So in my experience there is no goat in terms of thermostats. Each of them have some issues. Most TUYA thermostats work well, but can only fully open or close. DECT thermostats only update every 15 min and some have no native calibration posibility. Aqara was very loud to me. Popp thermostats should work well but doesnāt have hvac mode off so you just can set them to its minimal target temperature. For Tado you should use a the custom integration for calibration. Donāt know how Sonoff works but from that what they look like it seems they are also branded TUYAs. Wonder if someone here is going with Bosch.
I try to summarize some facts from the feedback Iāve got. But it can be that this isnāt the current state.
Ok, for me (test and productive environment) and other users it works well. Could I ask what thermostats youāve got? I will add an option to disable the scene based feature. So you can force the automation to do the window detection the old way.
@MUC13 Could you add entities for comfort and eco temperature? This is essential for the physical change feature since the automation itself is stateless and needs the helpers to store and synchronize the temperature for all thermostats also if there is just one in your configuration. Itās a little tricky but a need because there is still a bug in HA to figure out where the target change comes from.
1 Like
Thanks.
but when itās set at 8 meters, and it trigger when iām 9km away, then something must be wrong, or do I understand it wrong? I understand that when iām 8000 meters away, direction towards for more then 2 min, then set comfort.
8000 meters is the radius around your home. If someone whoās defined in your proximity entity is outside this radius comfort temperature should never be set. But if someone is in this circle so distance is less than 8000 meters comfort heating kicks in when this person is moving towards your home for 2 minutes.
The thermostats are Honeywell Evohome HR92.
Thanks for adding the option to force the old behavior! This was working fine for me already quite some time.
1 Like
Thanks. iāll test again tomorrow, but the test today, at 8 m and me 9km away set off comfort heating.
1 Like
Another question: After you run the script. Did you had a look into the trace? Was there an error / exclamation mark at the last step?
That did the trick! Works perfectly now. Thank you for the great help!
1 Like
Nope, works well. As I said doing it manually works as expected. Looked at the blueprint code but couldnāt find where you set the Payload external for the sensor or the external_temperature_inputeither. But Iāve never build something complex for Homeassistant before.
Could you navigate to dev tools.
Paste this into the template editor and edit you thermostat:
{% set valve = 'climate.YOUR_AQARA_THERMOSTAT' %}
{{ device_entities(device_id(valve)) | expand | selectattr('domain','in','number') | map(attribute='entity_id') | list }}
Could you share the output on the right?
Sure thing:
Result
Result type: list
[
"number.thermostat_office_l0_away_preset_temperature",
"number.thermostat_office_l0_external_temperature_input"
]
This template listens for the following state changed events:
Entity: binary_sensor.thermostat_office_l0_calibrated
Entity: binary_sensor.thermostat_office_l0_setup
Entity: binary_sensor.thermostat_office_l0_valve_alarm
Entity: binary_sensor.thermostat_office_l0_window_open
Entity: button.thermostat_office_l0_calibrate
Entity: climate.thermostat_office_l0
Entity: number.thermostat_office_l0_away_preset_temperature
Entity: number.thermostat_office_l0_external_temperature_input
Entity: select.thermostat_office_l0_calibrate
Entity: select.thermostat_office_l0_sensor
Entity: sensor.thermostat_office_l0_battery
Entity: sensor.thermostat_office_l0_device_temperature
Entity: sensor.thermostat_office_l0_power_outage_count
Entity: switch.thermostat_office_l0_child_lock
Entity: switch.thermostat_office_l0_schedule
Entity: switch.thermostat_office_l0_valve_detection
Entity: switch.thermostat_office_l0_window_detection
Entity: text.thermostat_office_l0_schedule_settings
Entity: update.thermostat_office_l0
Nope, same but now Iām pretty sure that the blueprint setās the away_preset_temperature property to the desired external temperature instead of the external_temperature_input is that intentional?
Yes, the new version filters for external so the away_preset_temperature is ignored. You have to wait some time or trigger the calibration by manipulate the value of the external temperature sensor by setting its state in dev tools or by hold it in your hands for example.