Skip to content

Conversation

silamon
Copy link
Contributor

@silamon silamon commented Aug 7, 2025

Proposed change

Basicly this, in a very much proof of concept form:
image

Only support added to numeric_state trigger at this moment
The code gets more complex, but we should work on this by making utility functions to handle entities, state, action names and such in the different triggers and conditions to make it more acceptable.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example configuration

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue or discussion:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

@bramkragten
Copy link
Member

I'm not sure we should put this in at this point. The idea is that more of these translation will be provided by integrations in the future. As integrations will be able to register triggers and conditions.

We should probably first figure out how we are going to handle those, before adding more features to this.

@silamon silamon marked this pull request as draft August 7, 2025 13:07
@wendevlin
Copy link
Contributor

So should we keep this PR open then?

@silamon silamon closed this Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants