you need to put your climate entity in ‘climate.YOUR_THERMOSTAT’
No, it does not exist. Therefore, I want to use the custom integration but I am not sure what custom integration are you talking about?
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.
nop
If it were possible, I would not have written here with them
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.
…even found the link where I got the manual from:
https://hejdom.pl/images/pdf/Siterwell-ZigBee-Radiator-Thermostat-GS361A-H04-User-Manual.pdf
Hope this helps you or someone…
Did you tried to set the calibration delta to 0 and the timeout to e.g. 2s?
Do you think it should work like this?
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.
I fixed the calibration for the aqaras 11 days ago. Here are the post related to that topic. Maybe it helps.
I recommend to create a AHC template sensor (described in the first post). There you can always find the timestamp of the last calibration.
I don’t understand.
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.
It worked with the simple new addition
I also tried the latest version, but my “max. offset for tharget temp. is 2 degrees”-problem remains.
Can I simply adjust the threshold somewhere in the code?
Have a look at line 2444 (what a luck ). I gonna make this editable in the next release.
Hm I am having heating_control.yaml version 4.3.14 (says so in the file) with 2262 lines. That’s odd!
Could you give me a significant string or the entire line, so I could just search for it?
Just substitute the 2 and -2 from line 2444-2447 with your max offset or delete 2444-2448 for the whole range.
//EDIT: Have a look here.
Hi, first of all : Great Work and thanks for sharing! I have a question concerning configuration/Schedule.
I want my Bedroom/Office to be
- 21° between 7am and 6pm (Schedule + Static Comfort Temperature)
- 17° when away(People)
- 18.5° between 8pm and 7am (Schedule + ? Temperature)
What would be the intended way to handle different temperatures for different schedules? Thanks for your support!
- Create a schedule and enable it from 7am to 6pm.
- Set Static Comfort to 21° (no additional entity needed)
- Set Static Eco to 17°C (no additional entity needed)
- Setup your persons
- Add this to heating adjustments
- time: "20:00"
eco: "18.5"
- time: "07:00"
eco: "17"
Thanks a lot! Would it also be possible to allow switch entities for presence detection? I dont have any presence detection devices but in my office example I could imagine using the state of the shelly plug which powers my pc as an indicator. PC on = I am in the room. Or could this already be done another way?
You can create a helper (binary_sensor / threshold) sensor for this purpose.
Set the upper limit to for example 10, select the power entity of your shelly plug, give it a name and set it as you presence sensor.