Can not include floorplan.yaml #20

gillman99 · 2021-01-17T13:27:39Z

gillman99
Jan 17, 2021

exetico,
Thank you for your help in getting the panel working but when I copy your code into the raw editor I get an error on !include. Here's what I have in my editor:

title: Floorplan
icon: 'mdi:floor-plan'
panel: true
cards:
- type: vertical-stack
  cards:
  - type: horizontal-stack
    cards:
    - config: !include /local/floorplan/floorplan.yaml
      type: 'custom:floorplan-card'
      full_height: true

Here's the error message:

Attached is my floorplan.yaml:

  name: Mark Floorplan
  image: /local/floorplan/house2.svg
  stylesheet: /local/floorplan/floorplan.css

  groups:

    - name: Lights
      entities:
         - light.caseta_r_wireless_in_wall_dimmer_2
         - light.caseta_r_wireless_in_wall_dimmer_3
         - light.caseta_r_wireless_in_wall_dimmer_4
         - light.caseta_r_wireless_in_wall_dimmer_5
      states:
        - state: 'on'
          class: 'light-on'
        - state: 'off'
          class: 'light-off'
      action:
        domain: homeassistant
        service: toggle

Any idea what's causing the error in !include?

Answered by vajonam

Jan 23, 2021

home assistant Lovelace yaml

  - type: 'custom:floorplan-card'
    title: Main Floor
    full_height: true
    config: /local/floorplan/floorplan.yaml?v=2

yaml

full_height: false
image: /local/floorplan/floorplan.svg?v=2
stylesheet: /local/floorplan/home.css
# log_level: debug
console_log_level: debug
defaults:
  hover_action: more-info
  state_action:
    action: call-service
    service: floorplan.class_set
    service_data: "button-${entity.state}"
  tap_action:
    action: call-service
    service: homeassistant.toggle
rules:
  - entity: light.shower_lamp
    element: light.caseta_r_wireless_in_wall_dimmer_3
    state_action:
      action: call-service
      service: floorplan.class_…

View full answer

exetico · 2021-01-17T18:16:23Z

exetico
Jan 17, 2021
Maintainer

Maybe due to www vs. local.

I've created a folder for all my Floorplan-files, which are called /lovelace. Could you try that?

Another think could be the use of / in the front, but I'm not 100% sure (I'm om my phone right now)...

2 replies

gillman99 Jan 17, 2021
Author

Exetico,
By /lovelace, should I put that in root, under config, someplace else?

exetico Jan 17, 2021
Maintainer

Normally the HA-root are the folder where your configuration.yaml are saved :-) And yes, lovelace should be created in the same folder as your configuration.yaml-file.

--- /home/yoga/homeassistant -----------------------------------
    8.8 GiB [##########]  home-assistant_v2.db                  
    7.6 MiB [          ] /www
    4.0 MiB [          ] /custom_components
  284.0 KiB [          ] /themes
  112.0 KiB [          ] /lovelace
   68.0 KiB [          ] /packages
   44.0 KiB [          ]  ui-lovelace.yaml
   24.0 KiB [          ]  configuration.yaml

Here's an example with some of my files :-)

My YAML are located in configuration.yaml:

  - title: Floorplan
    icon: 'mdi:floor-plan'
    panel: true
    cards:
      - type: vertical-stack
        cards:
          - type: horizontal-stack  
            cards:
              - config: !include lovelace/floorplan/_config-floorplan1.yaml
                type: 'custom:floorplan-card'
                full_height: true

And the configs are located within the lovelace-folder.

!include are a bit hard to get use to, but you'll get there :-)

Your floorplan1.yaml should have a formatting like this:

image: /local/floorplan/floorplan1.svg?v=1.1.14
#log_level: error
rules: <!-- Rules goes here -->
id: floorplan1

But, you're asking for general HA-support. It's not really anything related to floorplan - but I know it's kinda relevant, to get a better overview of your floorplan-configs :-)

gillman99 · 2021-01-17T19:15:17Z

gillman99
Jan 17, 2021
Author

One more thing Exotico, this error is happening when I'm trying to save the code in the raw configuration editor and not when I'm trying to run anything. I think it's complaining about !include since save most likely doesn't resolve the path of what's being included.

1 reply

exetico Jan 17, 2021
Maintainer

Oh, fair. Maybe the include are making some validations in the GUI. which I'm not use to in the raw-editing way :-) I hope you'll get it to work, one way or another. Please share the solution here, if the above guidance are not the right answer for you.

gillman99 · 2021-01-17T20:16:54Z

gillman99
Jan 17, 2021
Author

I went a different approach to get past this !include issue and am not including floorplan.yaml from my raw configuration editor yaml. Below is a screenshot of the SVG file:

Now a screenshot of the Home Assistant view:

I added some code to modify the icon of the 1 light when it is turned on or off per the demo. Why does it size so large and not keep the same size as the light_off/on.svg file I imported into Inkscape? Here's my yaml:

title: Floorplan2
panel: true
groups:
- name: Lights
  entities:
  - light.caseta_r_wireless_in_wall_dimmer_2
  - light.caseta_r_wireless_in_wall_dimmer_3
  - light.caseta_r_wireless_in_wall_dimmer_4
  - light.caseta_r_wireless_in_wall_dimmer_5
    states:
  - state: 'on'
    class: light-on
  - state: 'off'
    class: light-off
    action:
    service: toggle
    cards:
- type: 'custom:floorplan-card'
  full_height: true
  config:
  image: /local/floorplan/house2.svg?v=1.1.14
  stylesheet: /local/floorplan/floorplan.css
  defaults:
  hover_action: hover-info
  rules:
  - entity: light.caseta_r_wireless_in_wall_dimmer_5
  element: light.caseta_r_wireless_in_wall_dimmer_5
  state_action:
  action: call-service
  service: floorplan.image_set
  service_data: '/local/custom_ui/images/light_${entity.state}.svg'
  tap_action: toggle
  - entity: light.caseta_r_wireless_in_wall_dimmer_5
  element: light.caseta_r_wireless_in_wall_dimmer_5.button
  state_action:
  action: call-service
  service: floorplan.class_set
  service_data: 'button-${entity.state}'
  tap_action:
  action: call-service
  service: homeassistant.toggle

Also included my css file
floorplan.txt

Can anyone help with why my icon does not size correctly with the above code?

4 replies

exetico Jan 17, 2021
Maintainer

Please create another topic for that part. It's much better to have one thread for each topic (That's why I'm asking people to use the discussion here, instead of our mega-thread on the HA-community forum).

Also, you must have done something wierd here. I've not seen anything like that before. Maybe you've make an error in the SVG; or something like that? Try and use the "Inspect" option in your browser, and see why the size is changed. Maybe it due to other CSS-rules, which are conflicing. I can't find any good reason for it, so something must be a conflict or so. Are you facing the same issue, while using the sample SVG file?

And oh, if you're trying to ask for help, it's much better to try and get it to work - or at least give "Thanks" in return, now that I'm spending time on helping you, the best I can, instead of just jumping to another topic 👍 Thanks!

gillman99 Jan 17, 2021
Author

Exetico,
I'm very appreciative of your assistance. Been constantly working on this for the last 5 hours or so and have different options going in parallel to see if I can get one of them to work. I'll start another thread for the sizing issue and have looked at inspect but not sure what to look for in there. I'm a noob so learning as I go.

Again, very thankful for your assistance and guidance you've provided so far.
Mark

exetico Jan 17, 2021
Maintainer

Thanks Mark. I'm sorry if that was a bit too aggressive ❤️😁

Please share the SVG, too.

vajonam Jan 21, 2021

Now a screenshot of the Home Assistant view:

This is most likely due the the transform that inkscape added to your imported SVG object, when set a new class to it you need to set the transform as well, or your can move and size the object and then select clear transform in inkscape.

gillman99 · 2021-01-17T21:14:04Z

gillman99
Jan 17, 2021
Author

Tobias, No problem. How do I upload .svg file since it’s not one of the supported formats for gitHub discussions? Mark

…

On Jan 17, 2021, at 3:11 PM, Tobias Nordahl Kristensen ***@***.***> wrote: Thanks Mark. I'm sorry if that was a bit too aggressive ❤️😁 Please share the SVG, too. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASK3KRX7RWB6OG3KR4XTDTTS2NHB7ANCNFSM4WGDOOEA>.

1 reply

exetico Jan 18, 2021
Maintainer

It's up to you. Just one of the major upload-services. Mega or so, is fine.

gillman99 · 2021-01-19T13:56:08Z

gillman99
Jan 19, 2021
Author

Thanks. I’ll give this a shot.

…

On Jan 18, 2021, at 1:31 PM, Tobias Nordahl Kristensen ***@***.***> wrote: It's up to you. Just one of the major upload-services. Mega or so, is fine. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASK3KRVX4XZXGZHYFUJAY7LS2SD7PANCNFSM4WGDOOEA>.

0 replies

vajonam · 2021-01-21T20:29:36Z

vajonam
Jan 21, 2021

AFAIK you dont need the !include in here just point the yaml file with the config.

This is what I have. I am using a grid, but you can see all the configs are in each of the mainfloor.yaml secondfloor.yaml and basment.yaml

type: vertical-stack
cards:
  - type: grid
    columns: 2
    cards:
      - type: 'custom:floorplan-card'
        full_height: false
        config: /local/floorplan/mainfloor.yaml
      - type: 'custom:floorplan-card'
        full_height: false
        config: /local/floorplan/secondfloor.yaml
      - type: 'custom:floorplan-card'
        full_height: false
        config: /local/floorplan/basement.yaml

0 replies

gillman99 · 2021-01-21T21:38:26Z

gillman99
Jan 21, 2021
Author

Thank you. Everything is functionally working but it is not changing the icon color to yellow when the light is switched on. Can you look at the css code and help me figure out why the icons are not changing to yellow?

I have modified my card language to be as follows:

title: Floorplan3
panel: true
cards:
- type: 'custom:floorplan-card'
  full_height: true
  config: /local/floorplan/floorplan.yaml

floorplan.yaml
name: Marks Floorplan
image: /local/floorplan/floorplan.svg
stylesheet: /local/floorplan/floorplan.css

  groups:
    - name: Lights
      entities:
         - light.caseta_r_wireless_in_wall_dimmer_2
         - light.caseta_r_wireless_in_wall_dimmer_3
         - light.caseta_r_wireless_in_wall_dimmer_4
         - light.caseta_r_wireless_in_wall_dimmer_5
         - light.driveway_lights
      states:
        - state: 'on'
          class: 'light-on'
        - state: 'off'
          class: 'light-off'
      action:
        domain: homeassistant
        service: toggle

  last_motion_entity: sensor.template_last_motion
  last_motion_class: last-motion
  defaults:
    hover_action: hover-info
  rules:
    - entity: light.caseta_r_wireless_in_wall_dimmer_5
      element: light.caseta_r_wireless_in_wall_dimmer_5
      tap_action: toggle
    - entity: light.caseta_r_wireless_in_wall_dimmer_4
      element: light.caseta_r_wireless_in_wall_dimmer_4
      tap_action: toggle
    - entity: light.caseta_r_wireless_in_wall_dimmer_3         
      element: light.caseta_r_wireless_in_wall_dimmer_3
      tap_action: toggle
    - entity: light.caseta_r_wireless_in_wall_dimmer_2
      element: light.caseta_r_wireless_in_wall_dimmer_2
      tap_action: toggle
    - entity: light.driveway_lights
      element: light.driveway_lights
      tap_action: toggle

And floorplan.css
/* SVG shapes */
svg, svg * {
vector-effect: non-scaling-size !important;
pointer-events: all !important;
}

/* SVG size */

#floorplan {
padding: 10px;
}

#floorplan > svg {
max-width: 700px;
}

/* SVG elements */

svg * {
vector-effect: non-scaling-stroke !important;
}

/* Hover over */

.floorplan-shape:hover,
g.floorplan-hover > :not(text):hover,
g.floorplan-click > :not(text):hover,
g.floorplan-long-click > :not(text):hover,
:not(text).floorplan-hover:hover,
:not(text).floorplan-click:hover,
:not(text).floorplan-long-click:hover {
stroke: #03A9F4 !important;
stroke-width: 1px !important;
stroke-opacity: 1 !important;
}

/* Animation */

.spinning {
animation-name: spin;
animation-duration: 5s;
animation-iteration-count: infinite;
animation-timing-function: linear;
transform-origin: 50% 50%;
transform-box: fill-box;
}

@Keyframes spin {
from {
transform: rotate(0deg);
}
to {
transform: rotate(360deg);
}
}

/* Binary sensors */

.binary-sensor-on {
fill: #F9D27C !important;
}

.binary-sensor-off {
fill: #7CB1F9 !important;
transition: fill 5s ease;
}

/* Buttons */

.button-on rect {
fill: #1ABA92 !important;
}

.button-off rect {
fill: #d32f2f !important;
}

.button-on tspan,
.button-off tspan {
fill: white !important;
}

/* Light */

.light-off {
fill: #000000 !important;
}

.light-on {
fill: #FFFF00 !important;
}

3 replies

vajonam Jan 22, 2021

Can you do an inspect using chrome on the floorplan, specifically on the bulb. on mine I have rect that I change the color on.

does it show the class="light-off" or something like mine above I use button-off, you can than manually change it see if actually changes.

gillman99 Jan 22, 2021
Author

Vajonam, thanks for your help. I am not seeing the class=light-off on inspect. I've attached the inspect code below. Not sure why it's not getting my class from the floorplan.yaml file. It is creating 2 new classes which I believe are defined in the css above.

vajonam Jan 22, 2021

First off I have just been using this for a few days.

  - entity: light.cresha_blah
    element: light.cresha_blah
    state_action:
      action: call-service
      service: floorplan.class_set
      service_data: "light-${entity.state}"
    tap_action:
      action: call-service
      service: homeassistant.toggle

Try that.

This is how I toggle. I dont have a groups: section I have it all in the rules section. Since the docs are still being worked on I am not sure what the groups: config does..

gillman99 · 2021-01-22T15:06:20Z

gillman99
Jan 22, 2021
Author

I will give this a try and let you know how it goes. Thanks.

…

On Jan 22, 2021, at 9:00 AM, vajonam ***@***.***> wrote: First off I have just been using this for a few days. - entity: light.cresha_blah element: light.cresha_blah state_action: action: call-service service: floorplan.class_set service_data: "light-${entity.state}" tap_action: action: call-service service: homeassistant.toggle Try that. This is how I toggle. I dont have a groups: section I have it all in the rules section. Since the docs are still being worked on I am not sure what the groups: config does.. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASK3KRW6HE6BAGWD2AXYTMTS3GHIJANCNFSM4WGDOOEA>.

7 replies

gillman99 Jan 22, 2021
Author

vajonam,
removing the groups section and using this in my floorplan.yaml file I can now see the class light-on and light-off. But the icon does not change colors based on the fill command in the floorplan.css file.

    - entity: light.caseta_r_wireless_in_wall_dimmer_5
      element: light.caseta_r_wireless_in_wall_dimmer_5
      state_action:
        action: call-service
        service: floorplan.class_set
        service_data: "light-${entity.state}"
      tap_action:
        action: call-service
        service: homeassistant.toggle

I've tried the template in your last recommendation but that leaves me with an icon that's not the same size as the icon in my floorplan.svg file. I haven't spent time trying to debug that.

In Inspect, I can see the class change from light-on to light-off when I click it but icon always stays black. Any ideas?

vajonam Jan 22, 2021

Not sure which icon you are changing, if its just an outline you will have to set the stroke: #ff0000 as well as fill, My recommendation is that you can do all the test in the chrome inspector. you can right click on the bulb click inspect change the class or in the class edit the css on the right pane and see what you need to send in order to change it, and then modify the css accordingly.

gillman99 Jan 22, 2021
Author

Sorry to keep bugging you with basic questions and I appreciate your help. I've attached a screenshot so you can see what I'm seeing. I see the class light-off change to light-on and change to yellow when I click the light, but it stays dark. Further up I see in element a fill that always stays RGB(0,0,0) but it's crossed out which i'm not sure what that means.

I'm not able to manually edit any of the fields in inspect to change the color. Not to say there's not a way I just don't know how.

vajonam Jan 22, 2021

for whatever reason your css is "commented out" see the /* */ tags.

also have look at https://developers.google.com/web/tools/chrome-devtools/css/overrides#:~:text=The%20first%20thing%20to%20do,this%20concept%20is%20called%20Specificity.

vajonam Jan 22, 2021

also maybe the floorplan-hover class is interfering as well?

gillman99 · 2021-01-22T16:53:45Z

gillman99
Jan 22, 2021
Author

Thank you Vajonam. I'll review the google doc and spend more time playing with this. I'm sure I'll come back with more questions but hopefully they'll be more intelligent questions.
Thanks for your help.

0 replies

gillman99 · 2021-01-22T23:41:54Z

gillman99
Jan 22, 2021
Author

Vajonam,
I went back and used pretty much the exact same code and light icons as the example. Everything is functional and the icon changes from clear to yellow when the light is turned on. I'm attaching my new yaml, css and svg files. You can see from the image below that the light icon I'm playing with (the clear one) is not sized or placed in the same place as floorplan.svg puts it. I've been playing around with inspect and not sure why the icon is not coming in sized or placed correctly. I appreciate your help earlier and thought you may have some ideas.

floorplan.svg

Screenshot of HA

Floorplan.yaml:
defaults:
hover_action: hover-info
tap_action: more-info

  rules:
    - entity: light.caseta_r_wireless_in_wall_dimmer_5
      element: light.caseta_r_wireless_in_wall_dimmer_5
      state_action:
        action: call-service
        service: floorplan.image_set
        service_data: /local/floorplan/light_${entity.state}.svg
      tap_action:
        action: toggle

    - entity: light.caseta_r_wireless_in_wall_dimmer_5
      element: light.caseta_r_wireless_in_wall_dimmer_5.button
      state_action:
        action: call-service
        service: floorplan.class_set
        service_data: 'button-${entity.state}'
      tap_action:
        action: call-service
        service: homeassistant.toggle

floorplan.svg.zip
floorplan.css.zip
light_off.svg.zip
light_on.svg.zip

0 replies

vajonam · 2021-01-22T23:45:14Z

vajonam
Jan 22, 2021

Remove the image set call and just change colours. If you want to make it hidden set the opacity or visibility. I am not sure which order the rules are fired. Not sure if they can be predicted. You assuming the order of the rules right?

…

On Fri, Jan 22, 2021 at 6:42 PM gillman99 ***@***.***> wrote: Vajonam, I went back and used pretty much the exact same code and light icons as the example. Everything is functional and the icon changes from clear to yellow when the light is turned on. I'm attaching my new yaml, css and svg files. You can see from the image below that the light icon I'm playing with (the clear one) is not sized or placed in the same place as floorplan.svg puts it. I've been playing around with inspect and not sure why the icon is not coming in sized or placed correctly. I appreciate your help earlier and thought you may have some ideas. *floorplan.svg* [image: Screen Shot 2021-01-22 at 5 38 46 PM] <https://user-images.githubusercontent.com/76920134/105560160-b0924780-5cd8-11eb-80d2-aacb4b2fb59b.png> *Screenshot of HA* [image: Screen Shot 2021-01-22 at 5 39 22 PM] <https://user-images.githubusercontent.com/76920134/105560193-c6077180-5cd8-11eb-894f-cf02ecf73cda.png> Floorplan.yaml: defaults: hover_action: hover-info tap_action: more-info rules: - entity: light.caseta_r_wireless_in_wall_dimmer_5 element: light.caseta_r_wireless_in_wall_dimmer_5 state_action: action: call-service service: floorplan.image_set service_data: /local/floorplan/light_${entity.state}.svg tap_action: action: toggle - entity: light.caseta_r_wireless_in_wall_dimmer_5 element: light.caseta_r_wireless_in_wall_dimmer_5.button state_action: action: call-service service: floorplan.class_set service_data: 'button-${entity.state}' tap_action: action: call-service service: homeassistant.toggle floorplan.svg.zip <https://github.com/ExperienceLovelace/ha-floorplan/files/5859189/floorplan.svg.zip> floorplan.css.zip <https://github.com/ExperienceLovelace/ha-floorplan/files/5859190/floorplan.css.zip> light_off.svg.zip <https://github.com/ExperienceLovelace/ha-floorplan/files/5859194/light_off.svg.zip> light_on.svg.zip <https://github.com/ExperienceLovelace/ha-floorplan/files/5859195/light_on.svg.zip> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFHNISUZ2RI74IST7KWZ3S3IEM7ANCNFSM4WGDOOEA> .

0 replies

gillman99 · 2021-01-23T00:04:39Z

gillman99
Jan 23, 2021
Author

What is the best way to change the color? Is it done in yaml or css? Can you send me command?

0 replies

vajonam · 2021-01-23T00:07:28Z

vajonam
Jan 23, 2021

I change the colour by setting the class but I think you can set style as well but set class is a clean way to do it Basically what your saying in the yaml that based on the state change the class to something that includes the entity state like foo-(on) or foo-(off)

…

On Fri, Jan 22, 2021 at 7:04 PM gillman99 ***@***.***> wrote: What is the best way to change the color? Is it done in yaml or css? Can you send me command? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFHNL27RRKBMEF5LYL26LS3IHCHANCNFSM4WGDOOEA> .

1 reply

vajonam Jan 23, 2021

Here is what I suggest. That you put all the lights bulbs etc on on SVG. Then you assign the object names correct into the SVG. Then in the css you create 2 classes on for -on state and -off state. The off state will have the fill black and the on state will have fill as yellow. No need to switch between svg. I try out your svgs and let you know

vajonam · 2021-01-23T00:37:37Z

vajonam
Jan 23, 2021

home assistant Lovelace yaml

  - type: 'custom:floorplan-card'
    title: Main Floor
    full_height: true
    config: /local/floorplan/floorplan.yaml?v=2

yaml

full_height: false
image: /local/floorplan/floorplan.svg?v=2
stylesheet: /local/floorplan/home.css
# log_level: debug
console_log_level: debug
defaults:
  hover_action: more-info
  state_action:
    action: call-service
    service: floorplan.class_set
    service_data: "button-${entity.state}"
  tap_action:
    action: call-service
    service: homeassistant.toggle
rules:
  - entity: light.shower_lamp
    element: light.caseta_r_wireless_in_wall_dimmer_3
    state_action:
      action: call-service
      service: floorplan.class_set
      service_data: "button-${entity.state}"

svg

just use the floorplan.svg

css

.button-on  {
  fill: rgb(245 255 0)  !important;
}

.button-off {
  fill: #494949 !important;
  /* transition: fill 1.5s ease; */
}

result

1 reply

vajonam Jan 23, 2021

hope this helps

gillman99 · 2021-01-23T00:39:42Z

gillman99
Jan 23, 2021
Author

Thanks. Giving it a shot now. Let you know how it goes. Mark

…

On Jan 22, 2021, at 6:39 PM, vajonam ***@***.***> wrote: hope this helps — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASK3KRUI7HR4CLEWSPNIUFLS3ILCTANCNFSM4WGDOOEA>.

0 replies

gillman99 · 2021-01-23T00:59:48Z

gillman99
Jan 23, 2021
Author

Vajonam, This is working perfectly now! Thank you so much for your help. Mark

…

On Jan 22, 2021, at 6:39 PM, vajonam ***@***.***> wrote: hope this helps — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASK3KRUI7HR4CLEWSPNIUFLS3ILCTANCNFSM4WGDOOEA>.

0 replies

vajonam · 2021-01-23T01:01:46Z

vajonam
Jan 23, 2021

No worries. Remember chrome inspector is your friend.

…

On Fri, Jan 22, 2021 at 8:00 PM gillman99 ***@***.***> wrote: Vajonam, This is working perfectly now! Thank you so much for your help. Mark > On Jan 22, 2021, at 6:39 PM, vajonam ***@***.***> wrote: > > > hope this helps > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub < #20 (reply in thread)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ASK3KRUI7HR4CLEWSPNIUFLS3ILCTANCNFSM4WGDOOEA >. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFHNPTCN64M3TTFX6NPBDS3INRDANCNFSM4WGDOOEA> .

0 replies

Can not include floorplan.yaml #20

home assistant Lovelace yaml

yaml

Replies: 17 comments · 20 replies

exetico Jan 17, 2021 Maintainer

gillman99 Jan 17, 2021 Author

exetico Jan 17, 2021 Maintainer

gillman99 Jan 17, 2021 Author

exetico Jan 17, 2021 Maintainer

gillman99 Jan 17, 2021 Author

exetico Jan 17, 2021 Maintainer

gillman99 Jan 17, 2021 Author

exetico Jan 17, 2021 Maintainer

gillman99 Jan 17, 2021 Author

exetico Jan 18, 2021 Maintainer

gillman99 Jan 19, 2021 Author

gillman99 Jan 21, 2021 Author

gillman99 Jan 22, 2021 Author

gillman99 Jan 22, 2021 Author

gillman99 Jan 22, 2021 Author

gillman99 Jan 22, 2021 Author

gillman99 Jan 22, 2021 Author

gillman99 Jan 22, 2021 Author

gillman99 Jan 23, 2021 Author

home assistant Lovelace yaml

yaml

svg

css

result

gillman99 Jan 23, 2021 Author

gillman99 Jan 23, 2021 Author

Replies: 17 comments 20 replies

exetico
Jan 17, 2021
Maintainer

gillman99 Jan 17, 2021
Author

exetico Jan 17, 2021
Maintainer

gillman99
Jan 17, 2021
Author

exetico Jan 17, 2021
Maintainer

gillman99
Jan 17, 2021
Author

exetico Jan 17, 2021
Maintainer

gillman99 Jan 17, 2021
Author

exetico Jan 17, 2021
Maintainer

gillman99
Jan 17, 2021
Author

exetico Jan 18, 2021
Maintainer

gillman99
Jan 19, 2021
Author

gillman99
Jan 21, 2021
Author

gillman99 Jan 22, 2021
Author

gillman99
Jan 22, 2021
Author

gillman99 Jan 22, 2021
Author

gillman99 Jan 22, 2021
Author

gillman99
Jan 22, 2021
Author

gillman99
Jan 22, 2021
Author

gillman99
Jan 23, 2021
Author

gillman99
Jan 23, 2021
Author

gillman99
Jan 23, 2021
Author