Question about scheduler card. I am planning to configure my heating system with a temperature sensor and a trv in each room. The idea is the temp sensor will control if the valve opens/closes based on the temperature, and then the trv sends a signal to the thermostat to swich on/off
I want to add an scheduler to the equation, and i am wondering how it would work all together
I would like to set a room to 20 from 07.00am to 05.00pm, and to 16 for the rest of the day.
My understanding is i should configure in the scheduler card as an entity the temperature sensor and not the trv, correct?
Also, for the automation i want to create, which is, when the temp sensor is lower than {{expected_temp}}, start the radiator, can this value be read from the scheduler? It is, will it be 16 at 09.00pm and 20 at 11.00am for example?
Does your TRV support external temp sensor?
If not then you will need to trick the TRV to not turn off early.
Most of the times the TRV will report a higher temperature than your sensor due to the closeness to the radiator.
You can trick it by setting up a generic thermostat that uses the set_temperature of the TRV and the external temperature sensor.
Then you need to make sure the temperature you set in the scheduler or generic thermostat+ a few degrees are sent to the TRV.
Or if you turn the knob on the TRV minus a few degrees.
It does become complicated which is why I eventually settled for actuators instead since they don’t have any logic and no temperature sensor.
They just do as they are told.
But regarding your question with the schedule, you could try it.
Just create a schedule and write some topic/message and set up an automation to test it.
Use the trace to figure out what is available