Closed aretakisv closed 4 years ago
Hi, the node will operate the status only when receives a new temperature value so you have to make sure that the new value is coming regular to this node.
you can find this in documentation
Inputs This controller accepts one main input which has to have topic as "currentTemp" and payload needs to be a float The entire control is not functional until this message is received The heater status is recalculated when this message received, or when the user is changing the target temperature.
so, schedule will not work if there is no regular temperature (currentTemp) update?
yes will not work you have to make sure that is getting at least a value on regular bases
I want to avoid having timeouts and send value out, because if there is a bug will not have any control on it, will keep send value and can look randomly.
In fact you are the second person that is asking for this behavior. You know!?!? I think I will set a ticket as a new feature. But don't expected to soon .... I've started to refactor this and I would like to finish the refactoring. After that I will see if I can set something that can be configured to work like that.
It seems like scheduling is not currently working. Heater Is not posting payloads to change temperature. And this leads to a stuck thermostat
Running Version 2.0.2 of palette and nodered is 1.0.4 based on node 12 Docker image: 1.0.4-12-minimal-arm64v8
my subflow is:
I am using input from Zwave2mqtt and outputing to zwave2mqtt The flow has some comparisons in order to avoid an "endless loop" of setting and receiving temperature, which will drain the batteries and increase Zwave traffic.
At my latest attempts instead of using just Env Variable for the schedule, I also inject it some seconds after startup/deployment.