Input Bool -> binary sensor bit status not changing

@Doranagun wrote:

setting up a boolinputs.yaml file
contents are only…

input_boolean:
# used by NodeRed Home/Away for a few humans.
  home_occupied:
     name: "Is Someone Home"


binary_sensor:
  - platform: template
    sensors:
      is_someone_home:
        friendly_name: "Home In Use"
        value_template: >-
           "{ is_state('input_boolean.home_occupied', 'on') }"

input bool toggles with NodeRed using turn_on or turn_off.
Binary sensor does not update.

Whoever wrote node red needs their head examined for some of the idiosyncrasies of it…
A true/false pair on an event state that outputs…

Input Device - True…
Evaluation Comparison - True
Evaluates True…
Output True = True…
Output False = Null.

Input Device - False
Evaluation comparison is False.
Evaluates False… (whaaat?)
Output True - Null
Output False - False. (WHAT!?)

This should evaluate is TRUE, output true should go high, false should go low.
Da hell? NEVER should it output Null. if the eval is True (regardless of the values the evaluation uses). The reason behind that would be dual state actions. If your evaluation is true, then the true output goes high and false goes low. if the eval is not true then true goes low and false goes high. this is basic freaking logic… who the hell wants a null value… causes annoying issues with basic gate logic… a false in node red is still a true for a gate… The false logic is even more scatterbrained.

Posts: 4

Participants: 2

Read full topic