`on_value` for more widgets

[nagyrobi]

`on_value` for more widgets

[nielsnl68]

true. for other sensors atc the on_value can be useful indeed.

[nielsnl68]

I was just thinking when i was playing with the button on_click event.
Would it be nice to have the "homeassistant.service" build into the widgets directly.
so you have for example:

     - btn:
            checkable: true
            id: btn_toggle_swicth
            widgets:
              - label:
                  id: lbl_btn_apa_lampa
                  align: center
                  text_color: 0xFFFFFF
                  symbol: CLOSE
            homeassistant.service:
               entity_id: light.to_be_toggled
               send: light.turn_off
               receive:
                  state:
                      checked: !lambda return x;

        - dropdown:
            x: 80
            y: 180
            width: 105
            id: dropdown_id
            options:
              - Dry food
              - Wet food
              - Semi-moist
            homeassistant.service:
               entity_id: light.to_be_toggled
               send: 
                  action: light.turn_off
                  option: !lambda return (n.c_str());
               receive:
                  value: !lambda return x;

[nagyrobi]

receive?

[nielsnl68]

Yes, that would be like a short way of:

binary_sensor:
- platform: homeassistant
  publish_initial_state: true
  id: "light_totom"
  entity_id: light.woonkamer_kleuren_totom_light_1
  on_state:
    - lvgl.widget.update:
        id: lv_button0
        state:
          checked: !lambda return x;

[nagyrobi]

But that's exclusive to homeassistant.service, right? Still need on_value for regular esphome automations...

[nagyrobi]

Was thinking about this homeassistant.service and I think we still need the binary sensor though, to get the initial state of the entity from HA, to display it before calling the service.

[nagyrobi]

Ran into a use case with a switch:

              - switch:
                  id: swi_klima
                  x: 45
                  y: 68
                  align: TOP_MID
                  width: 70 #75
                  height: 40
                  on_release:
                    - if:
                        condition:
                          lambda: return lv_obj_get_state(id(swi_klima)) & LV_STATE_CHECKED;
                        then:
                          - homeassistant.service:
                              service: climate.set_hvac_mode
                              data:
                                hvac_mode: !lambda |-
                                  if (id(bs_climate_heat_mode).state == true) {
                                      return "heat";
                                  } else {
                                      return "cool";
                                  }
                                entity_id: climate.haloszoba_klima
                        else:
                          - homeassistant.service:
                              service: climate.turn_off
                              data:
                                entity_id: climate.haloszoba_klima

We could just use x here instead of lv_obj_get_state(id(swi_klima)) & LV_STATE_CHECKED in an on_value trigger.

Not sure if things like on_turn_on and on_turn_off or more LVGL-specialised on_check and on_uncheck would be worth it.

[nagyrobi]

Works with all event triggers now.