With 113.1 sensor template error fine in developer tools, in sensor is unavailable

Configuration
1

Have thios sensor sionce long time, now it gives error with new 113.1
How to fix?

In template is working, so code is still valid I think. The sensor is unavailable


- platform: template

    sensors:

        potenza_generale_totale:

            friendly_name: "Potenza generale totale"

            unit_of_measurement: 'W'

            value_template: '{{ states("sensor.potenza_generale_interno_1") |float + states("sensor.potenza_generale_interno_2") | float + states("sensor.potenza_generale_interno_3") | float + states("sensor.potenza_generale_interno_4") | float }}'
2

I even restarted HASS, all 4 sensors of the sum are numeric (no unknown or unavaiulable state).

{{ states(“sensor.potenza_generale_interno_1”) |float + states(“sensor.potenza_generale_interno_2”) | float + states(“sensor.potenza_generale_interno_3”) | float + states(“sensor.potenza_generale_interno_4”) | float }}

in deveoper tools template gives the correct value.

But the sensor is unavailable … evben after a restart. ???

3

I can’t see anything wrong with it. Does the state change if you use the update entity service in the developer tools?

If so you could try listing the four entity id’s in the sensor so the template knows what to monitor for updates.

4

Hi, I do not understand …" Does the state change if you use the update entity service in the developer tools?" ?

I put
{{ states(“sensor.potenza_generale_interno_1”) |float + states(“sensor.potenza_generale_interno_2”) | float + states(“sensor.potenza_generale_interno_3”) | float + states(“sensor.potenza_generale_interno_4”) | float }

in developer tools on the left, and automatically on the right I have the value (which is a correct numeric value 1.387.00 in the picture)

Cattura
Cattura1402×407 40.2 KB

But if I go to the
Configuration
Entities
I get the Entity, sensor.potenza_generale_totale it has the state Unavailable

Cattura

Please note that was perfectly working for weeks now, problem started this morning (not sure if related to the update to 113.1 or not)

5

how you do that? Like this? I can try … but why was working before not now


- platform: template

    sensors:

        potenza_generale_totale:

            friendly_name: "Potenza generale totale"

            unit_of_measurement: 'W'

            entity_id: 

              - sensor.potenza_generale_interno_1

              - sensor.potenza_generale_interno_2

              - sensor.potenza_generale_interno_3

              - sensor.potenza_generale_interno_4

            value_template: '{{ states("sensor.potenza_generale_interno_1") | float + states("sensor.potenza_generale_interno_2") | float + states("sensor.potenza_generale_interno_3") | float + states("sensor.potenza_generale_interno_4") | float }}'
6

This:

Screenshot_2020-07-29 Developer Tools - Home Assistant
Screenshot_2020-07-29 Developer Tools - Home Assistant555×555 23.6 KB

:man_shrugging:

7

Yes it updated it… Mmmhhh hope do not need to make an automation for that

8

Adding all four of the entities to the sensor should do it. It will update when any of them change.

It’s a fairly simple template. Home assistant should be able to extract the entities to monitor automatically. The fact that it isn’t happening could mean an issue has been introduced. Is it only this template you are having trouble with?

I explicitly list all my entities in my template sensors so am not a good comparison test .

9

So far yes

10

Did adding all four entities fix the issue?

11

it did at the beginning. Now upgrading from 113.1 to .3 have again the same issue. To fix, I have to call the homeassistant upgrade entity

12

Are there any errors in the home assistant system log (configuration / logs)?

13

Checked, none that I noticed