Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot get entity attributes card to work :(

See original GitHub issue

Hello everyone! I’ve been trying for a couple of days without success get this useful custom card to work.

I want to create a cart just for the vacuum, but I get this:

This is my code:

- type: entities
  title: Aspirador
  show_header_toggle: no
  entities:
    - switch.aspirador
    - sensor.xiaomi_status
    - sensor.xiaomi_battery_level
    - input_select.estados_de_succao
    - input_select.zonas_de_aspiracao
    - type: custom:entity-attributes-card
      entity: vacuum.aspirador
      attributes:
        - key: vacuum.aspirador.do_not_disturb
          name: "Não perturbe"
        - key: vacuum.aspirador.cleaning_time
          name: "Tempo limpando"
        - key: vacuum.aspirador.cleaned_area
          name: "Área limpa"
        - key: vacuum.aspirador.main_brush_left
          name: "Escova principal"
        - key: vacuum.aspirador.side_brush_left
          name: "Escova lateral"
        - key: vacuum.aspirador.filter_left
          name: "Filtro"

Here is the list of all attributes:

status: Charging
battery_level: 100
battery_icon: mdi:battery-charging-100
fan_speed: Balanced
fan_speed_list: Quiet,Balanced,Turbo,Max
do_not_disturb: off
do_not_disturb_start: 22:00:00
do_not_disturb_end: 08:00:00
cleaning_time: 2
cleaned_area: 2
cleaning_count: 39
total_cleaned_area: 222
total_cleaning_time: 302
main_brush_left: 294
side_brush_left: 194
filter_left: 144
friendly_name: Aspirador
supported_features: 2047

Did I miss something here?

Thanks a lot!

Issue Analytics

State:
Created 5 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

ASchneiderBRcommented, Jul 14, 2018

Thanks @ciotlosm! I will enable HTTPS ASAP, had many problem with HomeBridge but now using HomeKit native and am about to migrate do HassOS. Thanks for your time! It helped a great deal sir. Cheers!

1reaction

ciotlosmcommented, Jul 13, 2018

It seems the problem is with Lovelace and people running Home Assistant on HTTP. Lovelace uses a service worker and Chrome specifically blocks some things for the service worker if it’s not using TLS (HTTPS).

If you want to run HTTP you must call your home assistant either from localhost, or from something with .local or use HTTPS