So, is it possible to use assist in adding tasks to a todo list? I know that there’s already an intent for adding to a shopping list, but I couldn’t get it to work.
hi, without more info, it is going to be impossible for anyone to help. Generally at a minimum folks will need to know what type of hardware you are using, what type of installation you have on that hardware, and will also ask what was in your logs from when it was claiming it was updating
I just noticed what I believe to be a bug with the new Tile card features but thought I’d post here before reporting on Github incase it’s user error…
If I create a new Tile card for an entity, in this case one of my motion sensors, the UI lets me add ‘features’ such as ‘last triggered’, however if I put that exact same entity in a Tile card wrapped in a Grid card, the UI says that the entity has no available features.
In order to get those ‘features’ shown when using Tile in Grid, I had to add them in YAML mode.
is worked after i remove something from configuration.yaml
Thanks
1 Like
It’s a bug : Use strict comparison for above condition in conditional card by piitaya · Pull Request #18560 · home-assistant/frontend · GitHub
Thanks for reporting!
2 Likes
The ha-slider has been migrated to material 3 library because the previous one was unmaintained and deprecated : https://github.com/home-assistant/frontend/pull/18168
You should be able to theme the new one using these variables : Material Web - Sliders. It’s not officially supported but it should work.
2 Likes
Thank you Paul.
how were you able to diagnose this as the issue? I’m having trouble upgrading so I’m wondering if I might have a similar issue with a custom integration but not sure how I would go about verifying this.
What did you have to remove from your configuration?
Hey Stephen, noted that this release had added Fitbit integration without manually adding so removed all my Fitbit references…
1 Like
It seems this update broke my DSMR integration (5B version in Belgium).
I still can see all of my electricity entities are fine, but my gas-consumption isn’t working anymore.
Rollback to 2023.10.5 fixes this.
Ok, so I was wrong about this being Grid card problem, at least that I can’t seem to reproduce that issue, however I am finding that the ‘features’ option does not work via the UI.
Yet I can add the ‘features’ with YAML.
Since that ha-slider migration the below code stopped working and I corrected it with the new parameters, everything works except for the “pointer-events: none;”
Old code:
card_mod:
style:
hui-generic-entity-row:
$: |
:host {
--paper-slider-active-color: var(--disabled-text-color);
--paper-slider-knob-color: var(--disabled-text-color);
--paper-slider-container-color: var(--disabled-text-color);
--paper-item-icon-color: var(--disabled-text-color);
color: var(--disabled-text-color);
pointer-events: none;
}
New code:
card_mod:
style:
hui-generic-entity-row:
$: |
:host {
--md-slider-active-track-color: var(--disabled-text-color);
--md-slider-inactive-track-color: var(--disabled-text-color);
--md-slider-handle-color: var(--disabled-text-color);
--paper-item-icon-color: var(--disabled-text-color);
color: var(--disabled-text-color);
pointer-events: none;
}
Can somebody enlighten me how should the “pointer-events: none” be handled? Thanks
HI Paul,
Been trying to figure out all changed variables there, but run into a bit of problem with that 
current theme variables are:
paper-slider-knob-color
paper-slider-knob-start-color
paper-slider-pin-color
paper-slider-active-color
paper-slider-container-color
paper-slider-secondary-color
paper-slider-disabled-active-color
paper-slider-disabled-secondary-color
paper-slider-bar-color
and I can not find the direct replacement for all of these in the doc you linked as that only lists:
--md-slider-active-track-color
--md-slider-active-track-shape
--md-slider-inactive-track-color
--md-slider-inactive-track-shape
--md-slider-handle-color
--md-slider-handle-shape
would appreciate it if you could find a moment to help and create a direct replacement instruction for those?
This is fixed in the 2023.11.2 update. Thank you!
I use this GitHub - j-a-n/lovelace-wallpanel: 🖼️ Wall panel mode and photo screensaver for your Home Assistant Dashboards in my old IPad with guided access and it is great!
You have all tokens list in the code using the « all token » link in the page I provided (below the table). Just prefix them with —md-slider-.
Also, these variables are not officially supported by HA and will never be because we don’t want to be stuck with a library. So it can (will certainly) break in the future.
thanks I didnt spot that before
md-slider-active-track-color: green
md-slider-inactive-track-color: yellow
md-slider-focus-handle-color: black
md-slider-pressed-handle-color: white
md-slider-handle-color: pink
md-slider-hover-handle-color: orange
md-slider-handle-shadow-color: red
md-slider-label-container-color: grey
md-slider-label-text-color: purple
seem to be working. However, I can not find the correct variables for the slider container itself as they are nit mentioned in that linked page?
that doesnt sound really user-friendly… why make the move now then…
it’s not supported and will certainly break again.
As theming is supposed to be the way the endusers can/should customize their frontend (opposed to using all custom cards), why not make that theming more robust going forward?
Material etc controls imho are not a part of HA, they tend to be changed/upgraded/…, HA should not provide a persistent “proxy” theme CSS variables. This is completely up to users to maintain their styles. Sad but true.
We will not move away from Material. So theorically it should continue to work.
But if Material developers change the variables or deprecate the library (like they did for the previous slider), it will break 
That’s why we don’t officially support it.
1 Like