Configurable property to update with track

[nagyrobi]

to be able to update not just "val" but anything else

[nagyrobi]

For #7

[dgomes]

Thanks for this PR :)

I was actually planning in having the possibility to link entities to various properties:

      - obj: "p1b3" #This is a checkbox
        text: {{ state_attr('automation.rise_and_shine', 'friendly_name') }}
        val: {{ state('automation.rise_and_shine') }}

[nagyrobi]

Ok I was just trying to do something :-)

[dgomes]

Highly appreciated! :)

[nagyrobi]

I would give it a shot if you'd point me into the right direction on how to expand the template into a result variable.

[dgomes]

I always find it easier to look into existing components that already support the feature I want to implement and learn from their implementations.

Here is a very simple component that uses templates: https://github.com/home-assistant/core/blob/0e98bc5ea23cd15ecdc17a8318250b4a8fbe9478/homeassistant/components/rest_command/__init__.py

[dgomes]

Major refactor yesterday, please have a look

[nagyrobi]

Nice, I see the # TODO support more then "val" at async_listen_state_changes.
Wonder if I add the template to variable resolver above in __init__ would that be enough or should it be pushed down in async_listen_state_changes to receive updates regularly?

[dgomes]

I'm afraid that will not be enough, tonight I might have some extra time to try and address this

[nagyrobi]

I think to add a configurable, optional val_factor parameter to the obj section which would be useful to address this.
The arc in hasp-lvgl can only handle integers, so you need to set it to move between 150 and 300, and divide by factor 10 to obtain decimal values to set a target temperature in Home Assistant between 15.0 and 30.0 degrees.

• But you need to multiply back with 10 when you update the val of the arc.
• And you need not to multiply with anything when updating other properties like value_str.

So val_factor parameter would be only involved in reading (divison) and setting (multiplication) of the val property.
Of course only makes sense for numeric values.

[dgomes]

a1f5704 implements this

[dgomes]

you can type any conversion you wish into the template to set the hasp objective property, now I'll work on the event side

[dgomes]

Done in 4795760
event service call can now use variables (MQTT messages key/values) in their service templates

[nagyrobi]

event service call can now use variables (MQTT messages key/values) in their service templates

What's the syntax? For MQTT message sent by the plate: {"event":"changed","val":110} how do I extract the val?

To achieve something like this:

        event:
          "changed":
            service: climate.set_temperature
            data_template:
              entity_id: climate.futes
              temperature: "{{ val / 10 }}"

[dgomes]

temperature: "{{ val | int / 10 }}"

[dgomes]

also you don't need "data_template" it's just "data"... you can test the service call in developer-tools/server and then copy & paste to the configuration.yaml

[nagyrobi]

Excellent.
try:
{"obj":"arc","id":3,"x":20,"y":75,"w":200,"h":200,"min":120,"max":460,"border_side":0,"type":0,"rotation":0,"start_angle":135,"end_angle":45,"start_angle1":135,"end_angle1":45,"value_font":28,"value_color":"#2C3E50","adjustable":"true"}

and

      - obj: "p2b3"
        properties:
          "val": "{{ state_attr('climate.climate1','temperature') * 10 | int }}" 
          "value_str": "{{ state_attr('climate.climate1','temperature') }}" 
        event:
          "changed":
            service: climate.set_temperature
            data:
              entity_id: climate.climate1
              temperature: "{{ val | int / 10 }}"

[dgomes]

does it work or not ?

You should join the hasp-lvgl discord ;)

[nagyrobi]

it works but it needs some throttling

[dgomes]

can't do much from HA side... if the events are generated, they are being processed

[nagyrobi]

There's a race causing this:
https://user-images.githubusercontent.com/1550668/112021864-05640a00-8b32-11eb-80f0-20a17051770c.mp4

I think what happens is:

• I drag the arc, object changed
• plate sends an MQTT
• HA gets it as event -> component adjusts the entity
• entity has changed -> component sends MQTT
• plate gets it as update command -> adjusts the arc, object changed
• and goto line 1 again....

So what should be done perhaps is to avoid setting the val property, when the update of the component was triggered by a val change from the same device/object...