-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moes BRT-100-TRV didnt update local_temperature after local_temperature_calibration is set #9486
Comments
confirm, I've the same problem. local_temperature_calibration has no effect, after hours too. |
Same problem. Two BRT-100-TRV |
Any hints how to fix this? |
A workaround to calibrate from an external temperature sensor is to ignore the local_temperature_calibration. |
@IvanUpa how are you using this temperature difference then? |
I can't say for sure why this works. As if, if you do not touch TRV, then "local_temperature" is returned without correction. |
But "tvr" Not touched is the Problem, as soon as the tvr wake up from sleep state the Temperature ist correctly updated, so my idea is to fix this in z2m if the calibration is set, update the current temp with it internal in z2m if a event direcly from the device is fired Override the current temp. if everythig is correct the current temp dosent changed. |
btw the calibration isn't reported to HA and i don't know why. other tvr works great. but i think the "instand" intern Update with the current Temperature and calibration should be done on any Thermostats |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
The problem is relevant. |
Проблема актуальна. |
i have the same issue
@IvanUpa |
@mrybas |
It is a big problem if you are using an external temperature sensor. It is not updating the latest temperature after the calibration. So home assistant is not able to know what is the latest temperature on trv. and that makes the external sensor usage meaningless. Probably it is going to work if you are going to make a calibration setting once every hour. But if you want to make calibration settings once every 5 minutes you will broke the trv system. Update: I fixed my problems. I stopped using trv's temperature control and i created new virtual climate devices by 'generic_thermostat' and i used boolean inputs and external temperature sensors on that virtual climate devices. Created a script which sets the real brt climate devices to 5 degree and 35 degree according the position of boolean switch's on/off state. So i used my real trv's like a switch based water heater in that way. At the end of the day, my whole house has a perfect heating system now. The only negative point is; im not able to use brt's smart positioning feature. Now its always %100 or %0. At least i have a system that is more sensitive to temperature changes and works healthier. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Problem still exists |
Are there any solution for this or returning is the only option? |
Could you please share your script and settings of 'generic_thermostat'? |
having the same problem with the local temperature calibration setting and also the update of the local temperature seems very slow back to z2m |
Please show your configuration of the created new virtual climate device. |
sorry for the delay. in configuration yaml i added a virtual trv.
for sync between virtual and real trv i used 2 automation.
second automation might not be necessary but its effective on problems created by first automation
if you have multiple trv's like mine. create multiple from the 'first automation' and generic_thermostat virtual climate for each. 1 secondary automation will be enough for all (every hour fixer) i used this for 6 months and works perfectly. |
If local_temperature_calibration is set, local_temperature should be updated instandly with the new value.
The text was updated successfully, but these errors were encountered: