Checklist
Is your feature request related to a problem? Please describe.
Still a work in progess on my side. but i already wanted to share this idea with others.
Im trying to show the graphic of the app into home assitant (currently by using https://github.com/ExperienceLovelace/ha-floorplan, but im open for better solutions)
to show the correct image at the dashboard (all electric/hybrid, and mono/duo) it would be nice if the current vars in the code can be exposed as an entity or state.
(there is also a difference in image for the v1 and v2 unit, but i don't know if the json specify it if it is a v2, (otherwise a manual switch on the intergration setting mght be good)
Describe the solution you'd like
code currently using
#floorplan {
padding: 10px;
}
svg, svg * {
vector-effect: non-scaling-stroke !important;
pointer-events: all !important;
}
image[id*="quatt."].quatt-show{
display: inline;
}
image[id*="quatt."]{
display: none;
}
title: Quatt
path: quatt
icon: mdi:floor-plan
type: panel
cards:
- type: custom:floorplan-card
full_height: true
config:
image: /local/floorplan/examples/quatt/quatt.svg
stylesheet: /local/floorplan/examples/quatt/quatt.css
defaults:
hover_action: hover-info
tap_action: more-info
rules:
- name: Images
entities:
- entity: sensor.heatpump_hp2_workingmode
element: quatt.houseallev2duo
state_action:
service: floorplan.class_set
service_data: "${(entity.state === \"0\") ? \"quatt-show\" : \"quatt-hide\"}"
Describe alternatives you've considered
.
Additional context
This is still work in progress, if you see no good in it, you can close the issue
Checklist
Is your feature request related to a problem? Please describe.
Still a work in progess on my side. but i already wanted to share this idea with others.
Im trying to show the graphic of the app into home assitant (currently by using https://github.com/ExperienceLovelace/ha-floorplan, but im open for better solutions)
to show the correct image at the dashboard (all electric/hybrid, and mono/duo) it would be nice if the current vars in the code can be exposed as an entity or state.
(there is also a difference in image for the v1 and v2 unit, but i don't know if the json specify it if it is a v2, (otherwise a manual switch on the intergration setting mght be good)
Describe the solution you'd like
code currently using
Describe alternatives you've considered
.
Additional context
This is still work in progress, if you see no good in it, you can close the issue