I was told better to use a helpers though at first I was trying in one Automation but now its better even harder with what to do really. Also hard for me to explain it all and how the lamp is behaving! I have two sets of light one are Leds the other Beside lamp and I want both to run like sunset sunrise. but then after this th exchanging of the light colour only on the lamp so the other will turn on as normal when I used the motion sensor I have setup to detect me when I stick my hand out to go to my mobile, this triggers the Leds to come on!
I’m also no good on Yaml only to copy and past into it or try to change the code a little if I feel its right and I have backed up.
Not at all sure where I would put this code your showing me. I been side tracked due to a shed coming to be thinking on this! Takes me ages to get my head around to knowing what to try.
Too many variables really but should be easy is maybe I should start again with a new lamp and keep it off the other things I already have setup! Then is one fails the other will work as normal Also any excuse for a new Lamp
Not sure what a Binary helper is on or off is? never used it before!
@Bart_Huitsing Love the idea of the radial chart and im playing about with Measureit as suggested though it appears to measure in seconds … what scale is this graoh using as right now the % are not what they should be
Based on the initial dashboard by @CaptainSweatpants I created a single Lovelace card which basically holds all the current information in one mini graph. I decided to share it as it might be of value to others.
For the trend I would have loved to use built-in icons in the state mapping (or just refer to the current icon of the trend sensor instead of including the trend sensor as an entity with a state mapping) but afaik this is not possible: hence I used unicode arrows that also show well on my iOS devices (which is not as obvious as one would expect).
No, it shouldn’t as it applies to the second entity only. This way I don’t print a graph for the glucose trend, but I do use the state_map on it to translate the sensor values to an arrow (you did notice the trend arrow in the upper right of the graph, didn’t you?)
For those using nightscout trend sensor, the names are different, for example instead of rising_slightly it shoes FortyfiveUp. Hence I changed the map part to
I removed that entry (probably after you copied it) as the state map of the mini graph card cannot be defined per entity. As a consequence adding “unknown” to the state map resulted in spikes in the glucose value graph.
I don’t know if this is the place to ask, but I have been using a nice view on my glucose values for a while now. Ever since 2025.6.x it is not working very good anymore (also not on 2025.7.00.bx).
It used to show the current value, but now it either shows the value with a lot of decimals after the comma, or it shows n/a.
I have tried to alter some code myself, but can’t seem to figure it out.
The sensor sensor.dexcom_user_glucose_value has the correct value. I can also see the color change based on the value, but the value itself doesn’t show.
Just a guess. Change: <span>${(states['sensor.dexcom_user_glucose_value'].state)} mmol/L</span>
to: <span>${parseFloat(states['sensor.dexcom_user_glucose_value'].state).toFixed(2)} mmol/L</span>
This would change 11.166666666666667 to 11.17
What is your display? This looks like well written YAML.
This is with your suggestion included. The strange thing is when I change mmol to something completely else, it doesn’t show. I’ll try and put into a clear dashboard to see if that helps.
–
other dashboard didn’t help, so it is in the card. I changed the mmol, but that’s part of the IMG: block. Doesn’t hold the actual value.
Cool! With your code I’ve edit the last IMG block and added the rounding to all parts. Now it is nicely rounded. Thanks a lot!
I don’t fully understand what you mean by the display question. I already posted the screenshot multiple times. So I assume you don’t mean that, but what then?