Maintenance - We're moving to another version tagging (vX.X.X)

Possibly breaking changes

• ha-floorplan will now match images on basis of the browsers window size, not the desktop width size. If you face any problems after upgrading ha-floorplan, you can enforce the old logics by adding use_screen_width: true on config.image. See more in the documentation. ⚠️IMPORTANT ⚠️ : If you end up using the use_screen_width: true option, in order to fix your solution, remember to submit it here. We're planning to remove it again in the future, if no-body submits any issues, after a period of time.

Please check release note from v1.0.46.

---

From now on, versions will be tagged with vX.X.X. This is a maintenance release, and does not include any new features. Also from now on, you'll find floorplan.js as assets to each release.

What's Changed

• Update feature_request.md by @exetico in #475
• Update Minimal Mistakes and relates ressources by @exetico in #476
• Maintenance/gh actions by @exetico in #477
• Update and clean-up packages by @exetico in #478
• Maintenance/gh_workflow_with_build_and_node_bump by @exetico in #479

Full Changelog: 1.0.46...v1.0.47

Find best image based on window.innerWidth

What's Changed

• Bump cookie and express by @dependabot in #468
• Bump rexml from 3.3.6 to 3.3.9 in /docs by @dependabot in #471
• Feat/control image width logics by @exetico in #470

Possibly breaking changes

• ha-floorplan will now match images on basis of the browsers window size, not the desktop width size. If you face any problems after upgrading ha-floorplan, you can enforce the old logics by adding use_screen_width: true on config.image. See more in the documentation. ⚠️IMPORTANT ⚠️ : If you end up using the use_screen_width: true option, in order to fix your solution, remember to submit it here. We're planning to remove it again in the future, if no-body submits any issues, after a period of time.

Full Changelog: 1.0.45...1.0.46

New "action" service to make more dynamic rules

What's Changed

• Implement "action" support in "execute" to make more dynamic rules by @exetico in #456
• Feat/support important in set style by @exetico in #457
• Do not add * as target by @exetico in #464

New features

• We're now exposing a action function, which can be used in your JavaScript code. Use it to call things like style_set, but also Home Assistant sevices, just like you'd done it with the action keyword in YAML. Check the documentation for more
• It's now possible to use the !important decorator in CSS. I'll not recommend it, but it works, if you'd ever need it.

Full Changelog: 1.0.44...1.0.45-beta.1

1.0.45-beta.1

What's Changed

• Implement "action" support in "execute" to make more dynamic rules by @exetico in #456
• Feat/support important in set style by @exetico in #457
• Do not add * as target by @exetico in #464

New features

• We're now exposing a action function, which can be used in your JavaScript code. Use it to call things like style_set, but also Home Assistant sevices, just like you'd done it with the action keyword in YAML. Check the documentation for more
• It's now possible to use the !important decorator in CSS. I'll not recommend it, but it works, if you'd ever need it.

Full Changelog: 1.0.44...1.0.45-beta.1

Support for browsers like "WallPanel" on light Android-devices

What's Changed

• Bugfix/handle simple browser support replacechildren by @exetico in #450

🐛 As part of cleaning up a few things in my Home Assistant solution, I noticed that one of my limited "dumb" smart-displays didn't support the replaceChildren function. It's now patched, so it's possible to use the default browser on a device like the Lenovo Smart Clock, and a browser like WallPanel.

Full Changelog: 1.0.43...1.0.44

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

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

Hotfix: Bring back description in HACS

What's Changed

• Kindly see release notes for version 1.0.41. This is a hotfix release, to make a few changes on how our repo acts with HACS.

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.

Full Changelog: 1.0.41...1.0.42

Evaluate navigation_path in `navigation` action

What's Changed

• We're now evaluating the navigation_path key in the navigation 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

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.

Full Changelog: 1.0.40...1.0.41

Bug-fixes for clipPath SVG Element

What's Changed

• Bugfix so clipPaths doesn't trigger errors once we try and call the getBBox on each SVG element
• Version Bump

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.

New Contributors

• @OzGav made their first contribution in #371

Full Changelog: 1.0.39...1.0.40

Improve text_set multi-line and single-line logics

Release notes

Our floorplan.text_set service will now work as it did before version 1.0.37, if there's no new-lines provided. If the user provides a \n or a escaped ones, we'll handle it as a multi-line, and replace the tspan element, and only preserve the style attribute. A dataset-key called ha_floorplan_notice on the text element will inform the user about the impact of new-line characters in the text-value. Escaped ones are included, cause that's how we receive a value like servicedata: 'Two\n', if it's added though the Home Assistant GUI editor, as mentioned in #356.

What's Changed

• setText use cur. tspan or cr. multiple if \n #357 by @exetico in #369

Full Changelog: 1.0.38...1.0.39