an entity row cannot call a service. You need to use a service row.
type: entities
entities:
- type: call-service
action_name: Hall
service: hue.hue_activate_scene
service_data:
group_name: Living Room
scene_name: Bright
- entity: light.other
Just an FYI you can’t mix and match any old configuration. Seems like you just pieced a bunch of things together that you thought would work without consulting the docs.
The docs themselves do a pretty good job at letting you know what’s available for configuration.
For example in the entities card, the available configuration fields are defined in configuration variables section of the docs.
meaning, at the top level, the only valid attributes for an entities card is:
type: entities
entities:
title:
show_header_toggle:
theme:
Any field outside of that is not valid. Now the next section of those docs is called ‘Options for Entities’. This covers all items that can be placed into the entities field.
You’ll notice in that section, the only available attributes are:
- entity:
type:
name:
icon:
secondary_info:
format:
Notice how tap_action
is not an option. Now take a look at your configuration.
type: entities
entities:
- entity: light.hall
name: Hall
tap_action: #<------------------ USING TAP ACTION AS A FIELD.
action: call-service
service: hue.hue_activate_scene
service_data:
group_name: Living Room
scene_name: Bright
- entity: light.other
Ultimately the reason your configuration isn’t working is because lovelace is completely ignoring your extra fields and only using the ones that it cares about. Which is essentially this:
type: entities
entities:
- entity: light.hall
name: Hall
- entity: light.other
The last section is called Special Row Elements. This section contains anything else that you can place into the entities row. This is where the docs are alittle lacking. They don’t really mention that these rows go in the entities section. Either way, they do.
So with that being said, the special row that you should use (that I stated above) is the call service element.