agroszer
(AdamG)
September 3, 2025, 7:43am
1
Hi,
Upgraded HASS from 2024.12 to 2025.8, some sensor values display went crazy despite precision set to a single digit.
For example 2 calculated helpers, sensor.temp_avg_mb2 is fine sensor.hum_avg_mb3 is not.
I have also sensors acting as such
Tried settings precision to default/custom 99.9 to no avail…
Also weird that sensor readings seem to be all 99.9 precision
what’s wrong?
tom_l
September 3, 2025, 7:54am
2
What card is that?
See the 2025.7 release notes topic. 2025.7: That's the question - #11 by karwosts
If it is a template sensor you can do this: 2025.7: That's the question - #58 by abmantis
agroszer
(AdamG)
September 3, 2025, 11:27am
3
config is like:
views:
- title: Home
cards:
- type: vertical-stack
cards:
...
- type: entities
entities:
- entity: sensor.esp_03_1_room_temp
type: custom:multiple-entity-row
name: 3
show_state: false
icon: mdi:numeric-3-box-outline
entities:
- entity: calendar.mb3
name: guest
state_color: true
icon: mdi:account
- entity: switch.power_mb3
name: power
icon: true
state_color: true
- entity: switch.esp_03_6_power
name: bojler
icon: true
state_color: true
- entity: climate.c630bcb0
name: AC
styles:
font-weight: bold
- entity: climate.c630bcb0
attribute: temperature
name: Down
- entity: climate.c630bdf9
name: AC
styles:
font-weight: bold
- entity: climate.c630bdf9
attribute: temperature
name: Up
- entity: sensor.temp_avg_mb3
name: Temp
- entity: sensor.hum_avg_mb3
name: Hum
agroszer
(AdamG)
September 3, 2025, 11:28am
4
Mindbogging is that some work some not, no idea why.
Sounds like multiple-entity-row makes my life miserable, but why randomly?
tom_l
September 3, 2025, 11:54am
5
agroszer:
no idea why.
I gave you two links that explain why.
agroszer
(AdamG)
September 6, 2025, 9:04am
6
Looks like multiple-entity-row 's format: precision1 was the solution.
Thank you
jayjay
(JJ)
January 12, 2026, 10:33am
7
Still stuck with this problem, I know I can use round=true or with a number, and yes I know I can set a default precision, but in some cases all this will not work, example with a mini-graph card:
type: custom:button-card
aspect_ratio: 1/1
icon: mdi:home
entity: sensor.t_huiskamer
name: huiskamer
size: 30%
custom_fields:
graph:
card:
type: custom:mini-graph-card
entities:
- sensor.t_huiskamer
show:
icon: false
name: false
state: false
line_width: 5
hu: |
[[[
return `<ha-icon
icon="mdi:water-percent:"
style="width:14px;color: skyblue;">
</ha-icon><span style="color: var(--text-color-sensor);">${states['sensor.h_huiskamer'].state}%</span>`
]]]
temp: |
[[[
return `<ha-icon
icon="mdi:thermometer:"
style="width:14px;color:var(--accent-color);">
</ha-icon><span>${entity.state}°C</span>`
]]]
styles:
custom_fields:
graph:
- overflow: unset
card:
- overflow: unset
- width: 120px
- height: 110px
- font-size: 12px
grid:
- grid-template-areas: "\"n i\" \"temp hu\" \"graph graph\""
- grid-template-columns: 50% 50%
- grid-template-rows: 1fr 1fr 1fr
- overflow: unset
name:
- font-size: 12px
- color: rgb(107,148,237)
state:
- font-size: 10px
- color: rgb(107,148,237)
tom_l
January 12, 2026, 10:51am
8
Then you need to report that to the developer of the third party card.
jayjay
(JJ)
January 12, 2026, 11:29am
9
Thank you Tom, had not thought about this, cause it was in so many different cards and and representations of values, many of which I could repair with a simple round statement in the retrieval of the entity.state or value expression.
But you see no other option to adapt the code line:
</ha-icon><span>${entity.state}°C</span>`
in another way? Cause as said there are more cards affected like this one!
And it looks terrible, I disabled several pages from my front end to not see all of these.