This is a known bug/limitation of iOS devices with a slider.
Luckily the next release will introduce a fix to this problem.
For more info check-out this PR: Added/Fixed: The Light Slider can now be dragged! by AndyVRD Ā· Pull Request #732 Ā· UI-Lovelace-Minimalist/UI Ā· GitHub
1 Like
Hi, Iām loving this dashboard and have everything working great, however I have never been able to launch any popups. Iāve installed on pre-requisites and set up the variables on my cards yet on the iOS app and Chrome Desktop I have never been able to trigger one pop up. Iāve even removed and reinstalled Minimalist UI but still nothing. Can anyone help? My console output is below if that shows any redflags?
simple-weather-card.js:1 Uncaught (in promise) TypeError: Cannot convert undefined or null to object
at Function.getPrototypeOf (<anonymous>)
at Object.<anonymous> (simple-weather-card.js:1:1186)
at t (simple-weather-card.js:1:110)
at simple-weather-card.js:1:902
at simple-weather-card.js:1:911
lovelace-card-mod.js:5 Card-mod is loaded as a module
button-card.js:421 BUTTON-CARD Version 3.4.1
mini-media-player.js:1 Uncaught (in promise) TypeError: Class extends value undefined is not a constructor or null
at Object.<anonymous> (mini-media-player.js:1:113685)
at b (mini-media-player.js:1:48176)
at Module.<anonymous> (mini-media-player.js:1:145964)
at b (mini-media-player.js:1:48176)
at mini-media-player.js:1:48984
at mini-media-player.js:1:48995
at mini-media-player.js:1:47910
at mini-media-player.js:1:47975
at mini-media-player.js:1:174730
my-cards.js:318 ---- MY-SLIDER ---- Version 2.0.3
my-cards.js:488 ---- MY-FOOTER ---- Version 0.0.3
my-cards.js:556 ---- MY-CARDS ---- Version 1.0.5
lovelace-auto-entities.js:172 AUTO-ENTITIES 1.11.0 IS INSTALLED
mini-graph-card.js:1 MINI-GRAPH-CARD 0.11.0-dev.5
light-entity-card.js:9211 LIGHT-ENTITY-CARD Version 4.5.0
lovelace-card-mod.js:5 CARD-MOD 3.1.4 IS INSTALLED
0:1 Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "light-entity-card-editor" has already been used with this registry
mini-graph-card-bundle.js?hacstag=1512800620110:1 MINI-GRAPH-CARD 0.11.0
0:1 Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "mini-graph-card" has already been used with this registry
scheduler-card.js?hacstag=286270157234:1850 SCHEDULER-CARD Version: v2.3.4
button-card.js?hacstag=146194325342:425 BUTTON-CARD Version 3.4.2
browser_mod.js:145 BROWSER_MOD 1.5.3 IS INSTALLED DeviceID: 39fae3b6-9ebbee15
I am having an issue with Welcome Scenes Card - UI Lovelace Minimalist
even if I put nav_path under an entity it goes to auto-entities and does not navigate, anyone has an example usage with navigation?
Does anyone know if it is possible to have the thermostat popup with tap_action, rather than hold? I want to remove the ability to turn on and off the thermostat by tapping on the initial thermostat card
I am working on it Ability to customize actions by schumijo Ā· Pull Request #721 Ā· UI-Lovelace-Minimalist/UI Ā· GitHub
Amazing! Thanks!
Hi all wonderful community!
Quick question for you
I did this:
using this code:
- type: entities
entities:
- type: "custom:auto-entities"
card:
type: "grid"
columns: 2
square: false
card_param: "cards"
sort:
numberic: True
filter:
include:
- entity_id: "sensor.*_battery*"
options:
type: "custom:button-card"
template: "card_battery"
variables:
ulm_card_battery_battery_state_entity_id: "this.entity_id"
ulm_card_battery_battery_level_danger: 30
ulm_card_battery_battery_level_warning: 50
I want to do the same for some sensors using the bar card:
But when I try to do it, i get this result insteadā¦
This is the code Iāve used:
- type: "entities"
entities:
- type: "custom:auto-entities"
card:
type: "grid"
columns: 2
square: false
card_param: "cards"
filter:
include:
- entity_id: "sensor.shelly_*_power"
options:
type: "custom:button-card"
template: "custom_card_bar_card"
variables:
ulm_custom_card_bar_card_entity: "this.entity_id"
ulm_custom_card_bar_card_color: "var(--google-green)"
ulm_custom_card_bar_card_min: 1
ulm_custom_card_bar_card_max: 1000
Any hints of what iām doing wrong?
maybe @Mukund
BR
2 Likes
Hi All,
Just wanted to pop in and thank all of you for an amazing theme and all the ideas and contributions. I started with Mushroom, but got frustrated pretty quick, so went back to YAML. This was more work then I planned, especially since I keep changing my mind once I see it. It is still very much a work in progress and once the family gives feedback will require more work I am sure. I have learnt to love the custom cards and once you have a basic understanding, they are super powerful.
3 Likes
Hi,
I think that card is not optimized to use with the line but only with the entity in the variables.:
entity: your.entity
This is added by auto-entities.
To remove the icon and text of the top layer you could add some additional lines:
- type: "custom:auto-entities"
card:
type: "grid"
columns: 2
square: false
card_param: "cards"
filter:
include:
- entity_id: "sensor.shelly_*_power"
options:
type: "custom:button-card"
template: "custom_card_bar_card"
show_icon: false
show_name: false
show_label: false
variables:
ulm_custom_card_bar_card_entity: "this.entity_id"
ulm_custom_card_bar_card_color: "var(--google-green)"
ulm_custom_card_bar_card_min: 1
ulm_custom_card_bar_card_max: 1000
3 Likes
That worked perfectly!
just leaving trails here for someone like me who has been trying to figure this outā¦ at some point during my install my profile reverted themesā¦
so to fix it, went to my profile (bottom left, clicking on my picture) on the devices displaying black and white and had to select the minimalist uiā¦
1 Like
Worked like a charm! Thanks!
Hi all - thanks for all of your great work, very happy with how my dashboard has turned out.
Hoping someone can help with the custom card card_input_datetime. Is anyone using this card? I have had a search and spent some time trying to understand it and struggling.
When I use this, the increment and decrement seem to convert my input_datetime to strange numbers. Looking at the template, I can see that the
entity.attributes.timestamp
is converted, and subtracted by different values (e.g. 4500).
I modified this to try to understand how it was all pieces together and changed the first button to - 600 (decrement) and the third to + 600 (increment). This then increased and decreased the time value by 10 minutes, but every second click converted the hour between 24 hours!
Is there something up with my setup, or is there some incompatibility with the card_input_datetime?
Hi! When I create a new room yaml and add it as
!include views/living_room.yaml
then I get a new view through the navbar and also I can navigate there. However I donāt want it to be visible in the navbar. I only want to go to the room.yaml when I select that room in the main home.yaml view. How do I make that?
Hi to all, is possible to Add a notification icon to chips card? Like this? Thanks 
Add visible: [] to the view as shown in the screenshot below. This will make it visible to no users. @Adnan_Hossain
1 Like
I wonder if there are ways to re-use yaml config files.
Most of my rooms have lights
some type of other devices in a form of switch or fan
and some sensors. mostly motion or window/door
this is an example of a room
icon: mdi:silverware-fork-knife
path: "dining-room"
cards:
- type: "custom:button-card"
template: chip_back
variables:
ulm_chip_back_path: /ui-lovelace-minimalist/home
- type: "custom:button-card"
template: card_title
name: Dining Room
- type: "custom:button-card"
template: card_title
label: Lights
- type: custom:auto-entities
card:
type: grid
columns: 2
square: false
card_param: cards
filter:
include:
- domain: light
area: Dining Room
options:
type: "custom:button-card"
template: card_light_slider_collapse
variables:
ulm_card_light_enable_slider: true
ulm_card_light_enable_collapse: true
- domain: switch
area: Dining Room
entity_id: /^.*light.*$/
options:
type: "custom:button-card"
template: card_light_slider_collapse
variables:
ulm_card_light_enable_slider: true
ulm_card_light_enable_collapse: true
- type: "custom:button-card"
template: card_title
label: Other Devices
- type: custom:auto-entities
card:
type: grid
columns: 2
square: false
card_param: cards
filter:
include:
- domain: switch
area: Dining Room
options:
type: "custom:button-card"
template: card_binary_sensor
variables:
- ulm_card_binary_sensor_alert: false
show_last_changed: true
- domain: fan
area: Dining Room
options:
type: "custom:button-card"
template: card_binary_sensor
variables:
- ulm_card_binary_sensor_alert: false
show_last_changed: true
- type: "custom:button-card"
template: card_title
label: "Sensors"
- type: custom:auto-entities
card:
type: grid
columns: 2
square: false
card_param: cards
filter:
include:
- attributes:
device_class: motion
area: Dining Room
options:
type: "custom:button-card"
template: card_binary_sensor
variables:
- ulm_card_binary_sensor_alert: false
show_last_changed: true
- attributes:
device_class: moving
area: Dining Room
options:
type: "custom:button-card"
template: card_binary_sensor
variables:
- ulm_card_binary_sensor_alert: false
show_last_changed: true
sort:
method: name
The only difference between this and my Baby Room for is the literally the name of the area.
would be so cool if I could find a way to ātemplatizeā the yaml and re-use it.
Another thing that would be impressive would be if I could also find a way to not display the title card if there were no auto entities.
Any ETA on 0.0.10? Been pretty quiet with updates lately