Some Elements are not showing up in Lovelace

Farnsworth · December 24, 2020, 9:37am

Hey there and Merry Christmas everyone!

I have a weird problem - some elements are not showing up in Lovelace…
This is pretty much a complete fresh install of HA, so I don’t know what I could have done wrong

Here’s a picture:

As you can see, only the “month” and “year” values are displayed - all three are configured the same way in the yaml:

########
# AC01 #
########

### Täglich
  ac_01_day_energy_draw:
    source: sensor.plug_on_off_07_pwr_power
    cycle: daily

### Monatlich

  ac_01_month_energy_draw:
    source: sensor.plug_on_off_07_pwr_power
    cycle: monthly

### Jährlich

  ac_01_year_energy_draw:
    source: sensor.plug_on_off_07_pwr_power
    cycle: yearly

And all three actually have values:

this shows only the ac_01_day_energy_draw entity`, sou you can see, that there is a value for this sensor

What could be the issue here?

EDIT: I just realized, it says ‘W’ instead of ‘kWh’ … why?!

Burningstone · December 24, 2020, 11:43am

Did you restart after the changes and refreshed your browser cache?

Farnsworth · December 24, 2020, 11:48am

Ok, I set up everything completely from scratch now. The weird thing is, now the utility_meter shows up in Lovelace, UNTIL the value is greater than 0

yeah - I connected it to the wrong sensor at first ( source: sensor.plug_on_off_07_pwr_power instead of source: sensor.plug_on_off_07_pwr_energy - this issue is now solved

Burningstone · December 24, 2020, 11:51am

Do you get any errors under Developer Tools -> Logs?

With showing up until the value is above 0,do you mean the line disappears completely or does it say unavailable?

Farnsworth · December 24, 2020, 11:55am

I’ll have a look

the whole entity is gone in Lovelace (like in the forst picture, where only two of the three utility_meters are shown)

I can still go to ~~Settings~~ Configuration → Entities → sensor.ac_01_day_energy_draw and open it, which shows the correct values (second picture)

Farnsworth · December 24, 2020, 12:00pm

this does not exist … you meant Supervisor → System → Supervisor?!

everything green there

in the Core Logs, there are a couple of errors, but they are related to the telegram integration, which I doubt have yn connection to this issue

Burningstone · December 24, 2020, 12:03pm

Ou, sorry about that, I meant, Configuration -> Logs (it was under Developer Tools for a long time).

If you go to Developer Tools -> States, what’s the state of the sensor there?

Farnsworth · December 24, 2020, 12:05pm

2020-12-24 13:02:40 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

2020-12-24 13:02:43 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for thermal_comfort which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

2020-12-24 13:02:53 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved

Traceback (most recent call last):

File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 130, in async_init

result = await self._async_handle_step(

File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 213, in _async_handle_step

result: Dict = await getattr(flow, method)(user_input)

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 318, in async_step_discovery

return await self.async_step_pick_implementation()

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 243, in async_step_pick_implementation

return await self.async_step_auth()

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 267, in async_step_auth

url = await self.flow_impl.async_generate_authorize_url(self.flow_id)

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 147, in async_generate_authorize_url

redirect_uri = self.redirect_uri

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 131, in redirect_uri

raise RuntimeError(“No current request in context”)

RuntimeError: No current request in context

2020-12-24 13:02:53 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved

Traceback (most recent call last):

File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 130, in async_init

result = await self._async_handle_step(

File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 213, in _async_handle_step

result: Dict = await getattr(flow, method)(user_input)

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 318, in async_step_discovery

return await self.async_step_pick_implementation()

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 243, in async_step_pick_implementation

return await self.async_step_auth()

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 267, in async_step_auth

url = await self.flow_impl.async_generate_authorize_url(self.flow_id)

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 147, in async_generate_authorize_url

redirect_uri = self.redirect_uri

File “/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py”, line 131, in redirect_uri

raise RuntimeError(“No current request in context”)

RuntimeError: No current request in context

2020-12-24 13:02:54 ERROR (updater) [telegram.ext.updater] Error while getting Updates: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running (409)

2020-12-24 13:04:01 ERROR (updater) [telegram.ext.updater] Error while getting Updates: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running (409)

Farnsworth · December 24, 2020, 12:06pm

no idea what all this means xD

Also, I did try to disable these addons and restart HA - no change

Burningstone · December 24, 2020, 12:08pm

The errors are not related to this sensor.

Farnsworth · December 24, 2020, 12:10pm

hmm thanks anyway ^^

Burningstone · December 24, 2020, 12:14pm

So the entity shows up as you would like it and then it disappears when the value goes above 0? I can’t replicate this on my system, my entity stays there,no matter what the value is.

Again, what state do you see under Developer Tools -> States when the entity is showing up and what do you see when it disappears?

Farnsworth · December 24, 2020, 12:23pm

everything seems to be as it should

different entity - same problem

Lovelace:

Burningstone · December 24, 2020, 12:27pm

And if you press save, refresh the browser cache and restart HA it still doesn’t show up?

Farnsworth · December 24, 2020, 12:28pm

Just did all of that - still not there

Burningstone · December 24, 2020, 12:31pm

What if you try removing entity: before the entity like this:

entities:
  - sensor.xxxxy

Farnsworth · December 24, 2020, 12:35pm

same thing…

I just realized something completely different - maybe it’s connected… after restarting HA, many stored values are reset to 0 - this applies to input_numbers but also this utility_meter … what the hell is going on here?

Farnsworth · December 26, 2020, 6:46pm

Ok, I figured out the problem - at least I think so…

I did do some calculations which resulted in numbers with a LOT of decimal places - if I round the end result the utility meter receives to 3 places (and manually calibrate it), they show up again.

Strangely enough, the history graph did not have any problems showing the values

Anyways - rounding the numbers to 3 decimal places is a workaround - not ideal for tiny loads, like single LED bulbs though