Closed accountgit closed 1 year ago
I managed to make it work assigning a uuid in the sensor like:
sensors:
site1_energy_bill_hourly:
unique_id : 87dba62e-51b4-435e-b294-f58332d73ace
friendly_name: bill energy hour site1
value_template: '{{ states("sensor.site1_energy_hourly") | float * states("sensor.pvpc") | float }}'
unit_of_measurement: '€'
icon_template: hass:currency-eur
and in developer tools -> statistics -> search for the sensor -> settings and change the display resolution to something different (like 0,0000).
The problem
I have some tasmota devices, all added without problem in HA and created a couple of utility_meter entities related to it:
The pvpc sensor came from Spain electricity hourly pricing (PVPC) integration.
When the value of any of the bill float values (XXXX_energy_bill_hourly or XXXXXX_energy_bill_monthly) it's under 1 (0.XXXXXXXXX) the entites are displayed correctly in the lovelace cards related to it , but I think that at the moment that any of the values goes over 1 in browser console log appears the message
and that specific variable doesn't appear in the card.
The values are saved in HA because I can see them in history of the values from "History" option and I can see them being received from the websocket in the network tab of the browser, but it's failing to parse them on the frontend. I tried changing the value of the template to use the format using "%.8f" but continues happening the same.
I'm using: Home Assistant 2023.5.4 Supervisor 2023.04.1 Operating System 10.2 Frontend 20230503.3 - latest
A value that is appearing is: "s":"0.02427397" and one that it's missing in the card is: "s":"1.117355880000000000000"
What version of Home Assistant Core has the issue?
core-2023.5.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response