Newbie assistance neededā¦
Trying to combine multiple styling components but am obviously wrong with the syntax
(no errors returned but only the first styling component works; background-color).
They work individually though.
Iāve checked the guide but couldnāt figure it out.
what am I missing?
Thank you!
Maybe I donāt read something, but my mushroom animation doesnāt work . I just copy/paste your code, install card-mod plugin via HACS but itās doesnāt workā¦ for example with the basic fan animation :
Does anybody know how to minimize the delay between clicking the up or down arrow on a mushroom number card and the actual update of the input number value ? Iāve already tried to lower the values of āmush-slider-tresholdā and āmush-input-number-debounceā with card-mod and in my theme but the delay of approximately 2 seconds wonāt change.
Iām trying to use custom:mushroom-select-card as an overlay to a custom:button-card.
Essentially, I just want the select-option part to be visible once the card is clicked, the rest should be transparent.
Iām pretty close to the result (see code below) but two issues remain:
1- can the ābottom barā be hidden / made transparent?
2- is it possible to custom size the clickable zone so it covers the full card (see gray zone when cursor hovers the card)? Iāve tried changing the font size hoping it would expand the zone but it doesnāt.
i had to set the position to absolute for the dropdown, so it may not work well in grids. but since its already in a layout card, perhaps it will, who knows!
Amazing. Thanks for the extra mile. Glad you like the use case =)
This will be a great building block for my dashboard. Thank you!
Just to improve my search skills, was this documented in your guide or elsewhere?
Iām using mushroom-entity-buttons to highlight which rooms my vacuum should clean. I had the intention that every button would light up when I press it, but unfortunately they all light up when I press only one.
Is it possible because they all refer to the same script (but with different parameters) ?
Yes. it will be because your entity is the same script. your tap action has no bearing on what the card does. it is the fact that the script is being ran that changes the state of the entity in your card, which is the same between all cards.
I would make the amount of scripts you need for each card. they can even do identical things and you can keep your service data as is, if you like. but the scripts need to be different if you are referring to them in in this way as your entity.
The only problem is, as far as I think itās a problem, is that the script is needed to fill up a queue. With other words, more buttons can be pushed at the same time that fill the queue. Donāt know if āa script per buttonā will result in the same.
Iāll show you the script below:
jarvis_room_cleaner:
alias: Jarvis Room Cleaner
max: 20
mode: queued
fields:
room:
name: room
required: true
selector:
select:
options:
- bathroom
- bedroom
- hallway
- kitchen
- living_room
- joosarne
- bentjesse
- berging
sequence:
- choose:
- conditions:
- condition: or
conditions:
- condition: state
entity_id: vacuum.jarvis
state: cleaning
- condition: state
entity_id: vacuum.jarvis
state: error
sequence:
- wait_for_trigger:
- platform: state
entity_id: vacuum.jarvis
to: returning
- platform: state
entity_id: vacuum.jarvis
to: docked
continue_on_timeout: false
timeout: 01:30:00
- service: vacuum.send_command
target:
device_id: xxxxxxxxxxxxxxxxxxx
data_template:
command: app_segment_clean
params: >
{% set room_id = states("input_number.roborock_room_enum_" + room)
| int(0) %} {{ room_id }}
- wait_for_trigger:
- platform: state
entity_id: vacuum.jarvis
to: returning
- platform: state
entity_id: vacuum.jarvis
to: docked
continue_on_timeout: false
timeout: 01:30:00
- conditions:
- condition: or
conditions:
- condition: state
entity_id: vacuum.jarvis
state: returning
- condition: state
entity_id: vacuum.jarvis
state: docked
- condition: state
entity_id: vacuum.jarvis
state: idle
sequence:
- service: vacuum.send_command
target:
device_id: xxxxxxxxxxxxxxxxxxxx
data_template:
command: app_segment_clean
params: >
{% set room_id = states("input_number.roborock_room_enum_" + room)
| int(0) %} {{ room_id }}
- wait_for_trigger:
- platform: state
entity_id: vacuum.jarvis
to: returning
- platform: state
entity_id: vacuum.jarvis
to: docked
continue_on_timeout: false
timeout: 01:30:00
default: []
still related to the same overlay card:
not a big deal but wondering if this is also customizable;
once a selection is made, the mushroom select card stays āselectedā (greyed out) unless you click elsewhere.
Any way to hide / make this transparent as well? Thanks!
Iāve made a button-specific script to call the main script after push of the button, but all buttons are still activated, probably because of the fact that the script calls the same entity.
- type: custom:mushroom-entity-card
tap_action:
action: call-service
service: script.jarvis_bathroom
entity: script.jarvis_bathroom
type or paste code here
So, this doesnāt work and I canāt figure out why not
Perfect. Thank you!