ExperienceLovelace/ha-floorplan 1.0.17

Rules without SVG-elements, Common-functions and more

on GitHub

Hi all

There's been a few small changes, which are published with release 1.0.17.

I'm sure I forgot something... But here's a quick wrap-up.

Create rules, which should not map to a SVG element

Simply use entity: null, if you don't want ha-floorplan to map to a SVG-element.

  rules:
    - entity: sensor.ring_salon_battery
      element: null

That way, you can watch for state changes for one entity, but update some other SVG element. In other words, it lets you disable auto-mapping of our entity_id <-> element_id-mapping.

Custom/Common-function? Yes!

This needs a bit more words, and will be added to our Options-page in the official docs - we know... It's taking longer than we expected, but it's "on the way". Check out #48 for more details. You'lll find more details in this answer.

If you're using it the right way, common functions can be very powerfull, and take your ha-floorplan to the next level. Please share your ideas with the community.

Are your common functions getting way to complex - or would you like to share them like Home Assistant Blueprints? Fell free to create a ticket with a feature-request, and include your common function. If it's good for generic use, I guess we can migrate it to our solution, and find a (good) way of showing each of them down the line.

Colors and gradients

Our light example are updated. See more in #51 ...