That is exactly what I did. Maybe the quirk just makes it work better that without one, I donât know. Also not important atm, because I donât really care about setting the temperature offset, since it will be too small, anyway. Setting the target temperature should do the trick, I just have to get it to workâŠ
(All motion, is group of all motion sensors and a mmwave in the living room, hence its constant on)
(AHC Stue, is the AHC sensor from the snip in OP)
(AHC tilstĂŠdevĂŠrelses tid, is the scheduler user for presence)
the issue is when normal scheduler end, and I must wait the (10 min in config) for the trvs to kick back it can take more then 10 min, and Danfoss Ally, will after a change from 23C->20C->23C, opens the valve quite a lot for the some time before reverting to normal.
I donât know if there is a way to prevent this ?
Using the quirk from the official zigpy/zha_handlers repository did not really work. It is loaded - found it in the logs - but while the device itself works, even though lacking some features, AHC gives me a warning in the logs: Your selected hvac mode auto isn't support by some of your climate entities: climate.tze200_hhrtiq0x_ts0601_thermostat This goes for"heat" and âautoâ. In the end it shouldnât matter, since all I want AHC to do is set the target-temperature, but still, itâs ugly in the logsâŠ
Also it says I should install the âuptime integrationâ. Will look into that. In the meantime I will revert to my former quirk, which btw. is from here (posted a too generic link before): GitHub - jacekk015/zha_quirks: All quirks in one place
Donât know the state of the official integration but last year calibration wasnât supported and the custom integration did it. Could you navigate to your services /action in the developer tools and have a look if tado.set_climate_temperature_offset exists?
As I said, I need the manufacturer. Just paste the code into the developer template editor and post the returned value here. There are 4 different calibration strategies depending on the manufacturer.
The manual said the exclamation mark means fault. But there is no further information.
Then this should already work. You have to set the calibration to external and youâre good to go. In the next version this is done automatically.
Oh, ok. I personally donât own a tado thermostat but there were user who had integrated them by home kit and some using the tado integration. But this should offer the calibration service. So it seems its the official one.
This looks exactly like my thermostat. I had to dig a lot to find a manual, which explains the calibration. Maybe this is your problem too.
So to calibrate the valve after installation:
Remove Batteries for 30 secs.
Insert them
Thing will flash
Press âthe button/displayâ for several seconds, until F1 appears
Release. The thing will vibrate while retracting the pin, so you can install it.
Install it. DONâT touch the button.
Press Button once. Thing will calibrate.
I have enough instructions from the TRVâs I have 10 of them at home.
It is not a valve problem but a temperature problem.
The communication between TRV and sensor is not working properly.
But I have just seen that I have 4.3.1 and there is 4.3.11
Do I now have to delete the old blueprint and download the new one and enter everything again?
Latest version is 4.3.14 Just have a look in the blueprint description and check if youâre using the latest version. Iâd provided him a test version but merged the fix in the main one.
Just try to reimport the blueprint. No need to delete your configuration. If this didnât work open the blueprint in a file editor (config/blueprints/panhans/heating_control.yaml) and paste the content of the github version into your local file. Then just reload the automation in the developer tools.
I have 10 of them at home.
Just have a look in the blueprint description and check if youâre using the latest version. Iâd provided him a test version but merged the fix in the main one.