Feature request: link event and properties between objects directly about openhasp-custom-component

[nagyrobi]

Perhaps making the plate key optional, defaulting from the context to the current plate. So you only need to specify it if the object is on a different plate.

[nagyrobi]

We need some kind of templates to be able to make it more universal. In the example above, we set the text property of an object based on the val property of another object.

[dgomes]

The proposed solution would require a complete rewrite of the template engine...

I'm thinking about:

 - obj: "p3b30"  # tab dots
    event:
      "changed":
        - service: openhasp.update
          data:
            plate: openhasp.openhasp_plate_6fe4fc
            property: p3b26.text
            value: >
              {% if val == 0 %}
              {{ "#000000 \u2022# #909090 \u2022# #909090 \u2022#" | e }}
              {%-elif val == 1 %}
              {{ "#909090 \u2022# #000000 \u2022# #909090 \u2022#" | e }}
              {%-elif val == 2 %}
              {{ "#909090 \u2022# #909090 \u2022# #000000 \u2022#" | e }}
              {% endif %}

[dgomes]

Service really requires the plate….

…

On 12 Jun 2021, at 14:13, nagyrobi ***@***.***> wrote:  Perhaps making the plate key optional, defaulting from the context to the current plate. So you only need to specify it if the object is on a different plate. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[nagyrobi]

Service really requires the plate

Sure, when outside the CC, in an automation. But when you parse it in your own code, you can substitute it (if none then self.plate etc.)

[dgomes]

Services are called using async_call_from_config (it reads directly from the yaml the service call)

I would need to patch the yaml file before calling... and would be confusing because we would have a service call in yaml that is different from the normal service call...

[nagyrobi]

I see

[dgomes]

If we can do without templates maybe something like:

bindings:
p3b30.text: p3b26.text

And the cc would sync the two properties

[nagyrobi]

Well actually if you pull in the command service, that can already fulfill your logic the way it is - if it's not possible to make it more compact/efficient.

[nagyrobi]

This could be partially solved with #63 .