Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible feature requests and general questions #129

Open
sddgit opened this issue Jan 20, 2022 · 0 comments
Open

Possible feature requests and general questions #129

sddgit opened this issue Jan 20, 2022 · 0 comments

Comments

@sddgit
Copy link

sddgit commented Jan 20, 2022

Hi. Hope it’s OK to post all this here. I’m enjoying using this card. It’s by far the simplest way to get simple, predictable layouts designed. Thank you. I have a few points, and hope you can find some time to address them:

  1. I can’t get haptic feedback to work. My layout starts with
type: custom:homekit-card
home: true
rules: >
  {% if states('sensor.salinity_whole_number') | float > 5000 %} <li>Salinity
  {{states('sensor.salinity_whole_number')}} is out of range</li> {% endif %}
tileHoldAnimation: true
useTemperature: true
statePositionTop: false
haptic: success

But a single tap on a button seems to get no feedback. A long press does.

  1. The icons and text on Apple Homekit buttons seem to be transparent, so they change their shade depending on the background. Those on this card don’t do that, even though they have transparency in their styling. Can this be addressed somehow?
  2. On an iPad Mini, if I split the screen so 2/3rds are available for the card, still only 3 buttons are shown in a row, when there seems to be plenty of space for more. Any ideas if that can be changed?
  3. When I use home:true, there is always quite a lot of wasted space before the buttons (even after specifying --min-header-height: 5px;) even if no rules are triggered. Is this by design? And if I use a smallish space like this, will it expand if lots of rules are triggered?
  4. Is it possible to get the temperature in the green circle on a climate card to include a decimal place?
  5. I find the lime green of that temperature circle makes the white digits quite hard to read. Can that be change somehow?
  6. Try as I might, and after reading lots of examples, I can’t get a conditionalClass` to work. My latest incarnation is
      - entity: sensor.orp_whole_number
        name: ORP
        conditionalClass: |
          [[[
            if (states[‘’sensor.orp_whole_number’’].state > 300)
              return "redtile";
            else
              return "";
          ]]]

But that just makes the whole view go blank! Are you able to give me any pointers here?

I’m really sorry for the long list, but hope you can help me out a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant