Two button multi functional - remote

Configuration Frontend
, ,
1

Hi!
I have boiler which have remote with 2 buttons (Up/Down)
By pressing down - i enable function to - change temperature (up/down)

  • After few seconds in wents back to state - where i can enable function.
    By pressing up - i enable function to control - water temperature. (up/down)
  • After few seconds in wents back to state - where i can enable function.

I have copied signals from remote with broadlink rm4 and signals are equal for each button, so all the logic is in the boiler - which makes little bit hard to figure out - how to recreate remote in home assistant.

Idea was:

Create two switches (Control water temperature and Control room temperature)

  • By clicking one of the in lovelance panel enables either (water temperature control or room temperature control) which is - input_number type.

When i start change water/room temperature i need to disable both switches so for few seconds i`m unable to do anything else as - chosen function, after few seconds - enables both switches and disables the input_number entities (for water, room)

The main problemes are:

  • disable other entities and timer reseting(when changing input_number values)…

Basically - i think Node Red would be not a solution for it? Or would be? Or maybe i need to add some functions to lovelance?

Any suggestions? What you would focus on if You need to do this kind of task?

Thank You.

2

It doesn’t seem to hard to do. But you won’t be able to “set” a temperature.
You don’t know what the boiler is set to, so changing temperatures is blind and relies on that HA is keeping track of it.
If someone uses the manual remote then you will not have correct state.

But I would build a script, either in node red or HA.
One for water and one for room.

Create two helper numbers with the current temperature.

In Lovelace add the number and the script in a card.

Then in the scripts first send the up or down depending on the function (water or room) then loop the number of presses needed to go to the desired temperature and fire the IR each time in the loop.

3

Thanks for advice! Will give a try!
In this configuration if everything will be good - the batteries from remote will be removed! :slight_smile:

4

I think something like this could work.

sequence:
  - choose:
      - conditions:
          - condition: template
            value_template: >-
              {{ (states('input_number.water_set') | int) <
              (states('input_number.water') |int) }}
        sequence:
          - service: remote.send_command
            data:
              device: boiler
              command: set_to_water_function
          - repeat:
              until:
                - condition: template
                  value_template: >-
                    {{ (states('input_number.water_set') | int) ==
                    (states('input_number.water') |int) }}
              sequence:
                - service: remote.send_command
                  data:
                    device: boiler
                    command: send_down_command
                - service: input_number.decrement
                  target:
                    entity_id: input_number.water
    default: []

This only covers when you have set the temperature lower than what the temperature currently is so it would have to be expanded in the same way for up, and one more for room.

You also have make sure they take equal steps when a remote down is sent between the input number and the actual boiler temp.
Perhaps you need to use input_number.set instead with a yaml template

5

this post is really helpful for me..

6

Take note that I just edited the yaml because the previous would have gone in a endless loop (I think)