Possible Bug?

[OzGav]

Chrome devtools says I am running version 1.0.17

Everything was working OK. However after MUCH trial and error if I have either of the following in my ui-lovelace

            - entities:
                - binary_sensor.rumpus_light_on
              name: Virtual Lights
              state_action:
                service: floorplan.class_set
                service_data: 
                  class: '${(entity.state === "on") ? "light-on" : "light-off"}'
                  
            - entities:
                - sensor.ultrasonic_sensor_2
              name: Tank Quantity Text
              state_action:
                service: floorplan.text_set
                service_data: '${entity.state != "unavailable" ? Math.ceil((2.2 - (entity.state - 0.17)) / 2.2 * 100) + "%" : "UNK %"}'

then I get this error:

floorplan.js?v=14:137 Uncaught (in promise) TypeError: Cannot read property 'svgElement' of undefined
    at HTMLElement.callFloorplanService (floorplan.js?v=14:137)
    at HTMLElement.callService (floorplan.js?v=14:137)
    at HTMLElement.handleActions (floorplan.js?v=14:137)
    at HTMLElement.<anonymous> (floorplan.js?v=14:137)
    at Generator.next (<anonymous>)
    at floorplan.js?v=14:61
    at new Promise (<anonymous>)
    at v (floorplan.js?v=14:61)
    at HTMLElement.handleEntity (floorplan.js?v=14:137)
    at HTMLElement.<anonymous> (floorplan.js?v=14:137)

I tried to rollback to 1.0.14 but nothing I tried had the version label change so I am not sure if that was successful. I have rebooted with 1.0.17 again.

Note that those two excerpts from my ui-lovelace.yaml were from two different floorplans (I run three in fact). If I remove those everything seems to be working OK.

Ideas?

[OzGav]

OK I hate it when 15mins later I have a thought!

The issue is those two entities did not appear in the SVG. So on the one hand they highlighted some things to fix in my ui-lovelace.yaml but on the other hand it appears the recent update is intolerant of that situation. FYI.

[exetico]

Hi. Great you figured it out. Please help other, by sharing the correct solution, too. It's great so people don't end up copying the broken code.

Yes, that's a thing.. :-)

[OzGav]

For the first one the entity is no longer used so that code was redundant and I just removed it. For the second one the entity name had changed and I didn’t realise so I just needed to fix that up.

[pkozul]

Hi @OzGav

Going back to the original state of things, if you were to enable warnings in the floorplan logs:

  log_level: warn

Would you then see the following in the log panel, below your floorplan image?

2/15/2021, 9:46:17 AM WARNING CONFIG Cannot find element 'binary_sensor.garage_old' in SVG file

In any case, we will add some guard code to ensure that actions (i.e. setting classes, styles, etc.) are not applied to missing SVG elements. This will be in the next version.

[OzGav]

Thanks Petar. I had forgotten about that! When I turned that on there were three more entities that could not be found but they were not causing a crash. The only difference I can see is that they are part of a list of entities so perhaps the crash was occurring because in my two above they were the only entity and since they were missing there was effectively no entity for that rule.