Adaptive popup not working
Describe the bug When I wan't to click on the card, light or media_player, the action keep default (turn on, off or play/off)
To Reproduce Steps to reproduce the behavior:
N/A
Expected behavior Installing Lovelace UI via HACS
Screenshots N/A
Additional context Runing v1.1.0 and state-switch of course in v1.9.3
Hi @Drealine
can you share your configuration. Have you set the ulm_custom_actions?
Add these variables to your card:
ulm_card_tap_action: "adaptive"
ulm_card_name_action: "adaptive"
ulm_card_icon_action: "adaptive"
I follow all lines in the GitHub page of Adaptive page. It work with the version 1.0.1 which is the first vision of this feature
There could also be another problem.
In the last release the popups have been refactored. For your popup configuration use an entity entry under your card config instead the ulm_popup_light_entity variable
I did some tests and the adaptive dashboard works fine:
Use the following configuration on the card:
- view_layout:
grid-area: "card1"
type: "custom:button-card"
template: "card_light"
entity: light.light_bedroom_1
variables:
ulm_name_tap_action: "adaptive"
ulm_input_select_option: light1
ulm_input_select: input_select.minimalist_ui
For the popup configuration:
states:
# Devices
## Lights
light1:
type: "custom:button-card"
template: "popup_light_brightness"
entity: light.light_bedroom_1
Hi @matrixx567,
I just stumbled across this issue as well. For me the problem was, that in the docs and in the samples provided in the popup.yaml it still shows this:
states:
## Lights
light 1:
type: "custom:button-card"
template: "popup_light_brightness"
variables: # <--
ulm_popup_light_entity: "<your_entity>" # <--
while it only works for me using your sample:
states:
## Lights
light 1:
type: "custom:button-card"
template: "popup_light_brightness"
entity: "<your_entity>" # <--
Using the ulm_popup_light_entity there is a ButtonCardJSTemplateError showing up in the adaptive popup area.
Thank you, this was the same issue for me as well. It seems like there was no info about breaking changes to 1.1.0 and the docs haven't been updated accordingly that the variable has been replaced by the entity now.
@matrixx567 , thank you, it work like a charm in v1.1.0 with your example. If I understand, there are some breaking changes which is not documented at the moment ?
Thank you again :)