ExperienceLovelace/ha-floorplan 1.0.43

Evaluate `navigation_path` and `url_path` in the `navigate` and `url` action

on GitHub

What's Changed

• We're now evaluating the navigation_path key in the navigate action, and the url_path in the url action, allowing the user to use a reference like element.id in the navigation_path, just like we evaluate post of all other ha-floorplan actions. We also added support for the navigation_replace boolean, which is part of the the standard lovelace actions. See more details about navigation_replace here.
• Version Bump
• Fixed README-render in HACS

Here's a quick summary on how to use the navigation action.

tap_action:
  action: navigate
  navigation_path: |
    > const target = "/default-overview/alarm#" + element.id;
    console.log(element.id, "target", target);
    return target;

And also the simple way of doing so:

tap_action:
  action: navigate
  navigation_path: '/default-overview/alarm#${element.id}'

I'm aware of the Cannot find '*' in Home Assistant entities error, if you try and use the * key for the entity, like described in our docs. I'll fix this in the future, but no-one has mentioned this - and it has been in the codebase for a while. See #385.

Please note that 1.0.42 was a hot-fix release, and navigation_path evaluation was added in 1.0.41. Therefore, the compare link are between 1.0.40 and 1.0.43.

Full Changelog: 1.0.40...1.0.43