Boring update, but good code-decisions

Hi

TL;DR: Press update. There's not much related to the user-experience.

We're moving the project in a direction with even better code. Or, at least... optimised as mush as possible 😄 . I'm not here to rate the quality, or the overall optimisation of the project. 🙈

We're still working on the option pages. I really hope that's it's ready in a few weeks. But kindly use our Discussions-area, if you need any help or feedback. It's always great to see questions there. That helps us to move the project in a good direction - and other people are able to find shared configs and options by searching on Google and so. The existing Home Assistant Community are a great please, too. But splitting up questions and other things, are greatly improving our overview, and (hopefully) services even better data for Google's data-scrapers 🤖 🔍 .

---

Changes

1. We've moved to a sval-solution, instead or using libs where eval was in use. See the eval-helper-file, if that's in your interest.
2. Better handling of touchstart, to prevent the following console-warning:
   

Rules without SVG-elements, Common-functions and more

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 ...

Define target SVG-text element(s) in `text_set`-service

It's now possible to define which SVG text-element(s) to update, in the text_set-service.

No debouncing

For more information, see #41 (comment).

Allow multiple SVG-elements (Array)

Hi all

Only small changes has been implemented.

---

#28 - Use array of svg elements | 098f8a6

  # Set both back doors on one sensor
  - entity: binary_sensor.back_doors
    elements:
      - binary_sensor.patio
      - binary_sensor.laundry
    state_action:
      action: call-service
      service: floorplan.class_set
      service_data:
        class: "door-${entity.state}"

---

For questions, kindly use the Discussions area. Also, please check the docs before asking. Where's still things waiting to be done, but we're doing our best to get everything waiting.

Thanks you for spending your time with the ha-floorplan team 🥳

Let's get started - it can be found in HACS

Hi all

We're happy to push the first non-pre release to you guys. Please find more information about ha-floorplan in our documentation. The Discussions-function are also enabled on our repository, if you need any help.

If you're new to ha-floorplan, please visit our quick start-guide for more information. Our module are added in HACS, so it's very easy to get started. You'll also find a few examples in our documentation.

We wish you all a happy new year, and a great floorplanning experience 🥳

Good things come to those who wait

We're not 100% ready for "the public", and the documentation are still lacking many important details. But you're able to test things out, if you like to do so. Please don't ask about how to use each function, before the docs are ready for the public, too :-)

Stay turned, and thank you for using ha-floorplan 🎆

Pre Beta - We're almost ready

We're almost ready - but you can switch now, and give us your valuable feedback.

We're now very close to the first release of the new TypeScript-based version of the solution. A few things are still needed to be done, but it's already ready to be tested by "the public". All things are working in this version, and there's lots of improvements.

⚠️ Please note that changes will be made, before we're jumping to version 1.0. Therefore, kindly follow our repository, so you always know that's going on.

If you're facing any issues, please create a issue with good details about your problem. We'll do our best, to help you out 🧑‍🔧

More details about the new TypeScript based version, will be added for release 1.0.

🐛