2022.6: Gaining new insights!

KennethLavrsen · June 27, 2022, 5:40pm

I run an Odroid N2+ (Home assistant Blue) also and I also see more and more of these 10 seconds warnings.

I am not sure the startup is that much longer. We are just beeing spammed by these 10 second warnings which appear to be pointless.

arganto · June 27, 2022, 5:45pm

BTW: When was the change, since when I cannot scroll e.g. entity list (and some other lists) anymore on desktop Chrome, etc. with cursor and page keys, and via mouse fast scrolling wheel only a few lines after which I have to wait for some time to be able to scroll in the next few lines and since I don’t have a scrollbar anymore, etc.?

Or is this only an error on my devices and I can locally get rid of this anyhow?

This is really not good anymore. And I wonder, why this is not the case e.g. on ipad safari. There I can still scroll smoothly and fast through the whole lists.

erkr · June 27, 2022, 6:39pm

Except a longer startup time, I didn’t see any side effects

sashadeg · June 28, 2022, 4:11pm

Thank you! your answer helped me!

Speezle · June 28, 2022, 6:46pm

Hi All,

After updating to core-2022.6.7 my device trackers from the companion app’s (3 off them) won’t update device tracker state in homeassistant anymore. can’t see any errors in the logs niether the companion logs

Anyone with the same issue?

Regards,
Danny

Duke_box · June 28, 2022, 7:04pm

I Agree,

No difference in start up time.
Just loads of warnings!!!

nickrout · June 28, 2022, 8:31pm

No issue here using the android companion app.

maxym · June 28, 2022, 9:09pm

mqtt lights configured with use of new format stuck in unavailable state after using Reload feature if they have availability configured
HA restart helps (until next reload)

Interesting, that other entity types (at least sensors and covers) don’t manifest this issue.

github.com/home-assistant/core

Availability option breaks light entity (new format)

opened 08:03PM - 26 Jun 22 UTC

michalk-k

integration: mqtt

### The problem When reloading manually configured MQTT entities, MQTT light en…tities which: * are declared using a new format (mqtt: domain) * have availability set (regardless of new or old way) get stuck with an unavailable state. Such a state doesn't change even by changes in tracked MQTT topic. Worth to mention that HA restart causes all entities to recover. Granted, those with availability set, require a minute or so more after restart is confirmed by UI. The code below configures 4 entities. All do use the same settings and MQTT topics. Two of them are using the old format, and another two are using the new format. Each pair has one entity with and without availability option (suffixes av and nav respectively). To reproduce: 1. add those entities to the HA 2. restart HA to confirm all entities are available 3. go to Developer Tools / YAML 4. Reload manually configured MQTT entities The result: 3 of them are available, while `test_mqtt_av` is not available. This test case is deterministic and confirmed with every light entity I reconfigured in order to use the new format. Other domains like sensors or covers seem to be free of this bug. But worth checking all possible domains. ![image](https://user-images.githubusercontent.com/7868445/175831867-e27cef23-848f-4eb6-91e0-684b79193437.png) ### What version of Home Assistant Core has the issue? core-2022.6.7 ### 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 MQTT Light ### Link to integration documentation on our website https://www.home-assistant.io/integrations/light.mqtt/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml mqtt: light: - name: "test_mqtt_av" command_topic: "shellies/light-bathroom/relay/0/command" state_topic: "shellies/light-bathroom/relay/0" availability_topic: "shellies/light-bathroom/online" qos: 1 retain: false payload_on: "on" payload_off: "off" payload_available: "true" payload_not_available: "false" optimistic: false - name: "test_mqtt_nav" command_topic: "shellies/light-bathroom/relay/0/command" state_topic: "shellies/light-bathroom/relay/0" #availability_topic: "shellies/light-bathroom/online" qos: 1 retain: false payload_on: "on" payload_off: "off" #payload_available: "true" #payload_not_available: "false" optimistic: false light: - name: "test_light_av" platform: "mqtt" command_topic: "shellies/light-bathroom/relay/0/command" state_topic: "shellies/light-bathroom/relay/0" availability_topic: "shellies/light-bathroom/online" qos: 1 retain: false payload_on: "on" payload_off: "off" payload_available: "true" payload_not_available: "false" optimistic: false - name: "test_light_nav" platform: "mqtt" command_topic: "shellies/light-bathroom/relay/0/command" state_topic: "shellies/light-bathroom/relay/0" #availability_topic: "shellies/light-bathroom/online" qos: 1 retain: false payload_on: "on" payload_off: "off" payload_available: "true" payload_not_available: "false" optimistic: false ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

erkr · June 29, 2022, 1:47pm

Since core 2022.6.7 my startup increased significant.
On core 2022.6.6 and before, only the fritzbox was slow ( ca 60 sec) and all other integrations where below 30 sec.
Now ca 5 integrations, including supervisor, are above the 30 seconds:

Further more, before the last update only incidentally a 10 seconds warning popped up. Now it’s structurally a whole list:

There must be a change in this latest core version that i.e. increased the time to create entities or something like that

AJStubbsy · June 29, 2022, 1:53pm

I had this problem (or at least a similar one, since I’m not sure it was that update that caused the problem). The Companion App location sensors became disabled. You can find a the solution here HA app- phone never leaves home - #2 by dshokouhi

bdraco · June 29, 2022, 1:59pm

I don’t see anything that changed in core between 2022.6.6 and 2022.6.7 that would explain the increase. In fact there were only integration changes between the versions and no core changes:

arganto · June 29, 2022, 2:33pm

I have this as well. If it was since 2022.6.7 or already with 2022.6.whatever, I cannot say anmyore

Setup of sensor platform dwd_weather_warnings is taking over 10 seconds.
28. Juni 2022, 20:24:26 – (WARNUNG) Sensor - Die Nachricht ist zum ersten Mal um 28. Juni 2022, 20:24:06 aufgetreten und erscheint 6 mal
Setup of binary_sensor platform homematic is taking over 10 seconds.
28. Juni 2022, 20:24:26 – (WARNUNG) Binärsensor
Setup of switch platform rest is taking over 10 seconds.
28. Juni 2022, 20:24:16 – (WARNUNG) Homematic (benutzerdefinierte Integration) - Die Nachricht ist zum ersten Mal um 28. Juni 2022, 20:24:16 aufgetreten und erscheint 21 mal
Setup of input_boolean is taking over 10 seconds.
28. Juni 2022, 20:24:07 – (WARNUNG) /usr/local/lib/python3.9/asyncio/events.py - Die Nachricht ist zum ersten Mal um 28. Juni 2022, 20:24:07 aufgetreten und erscheint 8 mal

etc. etc. Sometimes with “start cannot be finisehd, please report [list of all integrations] to the developers”

KennethLavrsen · June 29, 2022, 4:19pm

A few point releases ago I had usually 4 of 10 second pointless warnings.

Now I have something like this

2022-06-29 18:03:02 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.
2022-06-29 18:03:02 WARNING (MainThread) [homeassistant.setup] Setup of input_button is taking over 10 seconds.
2022-06-29 18:03:02 WARNING (MainThread) [homeassistant.setup] Setup of zone is taking over 10 seconds.
2022-06-29 18:03:02 WARNING (MainThread) [homeassistant.components.scene] Setup of scene platform homeassistant is taking over 10 seconds.
2022-06-29 18:03:02 WARNING (MainThread) [homeassistant.setup] Setup of input_text is taking over 10 seconds.
2022-06-29 18:03:03 WARNING (MainThread) [homeassistant.setup] Setup of input_datetime is taking over 10 seconds.
2022-06-29 18:03:03 WARNING (MainThread) [homeassistant.setup] Setup of timer is taking over 10 seconds.
2022-06-29 18:03:03 WARNING (MainThread) [homeassistant.setup] Setup of counter is taking over 10 seconds.
2022-06-29 18:03:03 WARNING (MainThread) [homeassistant.setup] Setup of input_number is taking over 10 seconds.
2022-06-29 18:03:03 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds.

Why all these 10 seconds. Just a few months ago there were none of these. Instead there were the up to 100 IOS app errors. I actually remember that the release that fixed the IOS error log bug was the same that started the 10 seconds warnings.

There is also a problem with the way the logs are displayed in the browser. It happens often that the front end code fails to load the cache but keeps on displaying a cached version. And it is in the browser because another computer will not show same problem at same time. Only fix is to open developer tools and do a hard reload with cache flush. Not even control F5 solves the problem

erkr · June 29, 2022, 5:46pm

found this related issue: https://github.com/home-assistant/core/issues/73863

Kertz1954 · June 29, 2022, 7:22pm

This will take more than 10 seconds to read !!

Home Assistant Beta Release Notes 2022.7

tom_l · June 29, 2022, 10:01pm

Reminder: Please only discuss the beta release in the Discord beta channel.

gdreelin · July 3, 2022, 1:00am

For some reason this is occurring on the header of Home Assistant but I can not seem to find where the configures for that header comes from. I have tried to remove theme but did the same. Anyone have any ideas why the header would keep adding the word “My” to it over and over?

SawKyrom · July 16, 2022, 11:50pm

Not having luck with !include_dir_merge_named suggestion. Any thoughts?

mqtt: 
  sensor: !include_dir_merge_named mqtt/sensors/
  binary_sensor: !include_dir_merge_named mqtt/binary_sensors/

returns “nvalid config for [mqtt]: [Sensor] is an invalid option for [mqtt]. Check: mqtt->mqtt->sensor->0->Sensor. (See /config/configuration.yaml, line 120).”

Sensors are formated in yaml files as such:

sensor:
  - name: "SMLReaderManufacturer"
    state_topic: "homeassistant/sensor/smartmeter/sensor/1/obis/1-0:96.50.1/1/value"

or as follows for binary files

binary_sensor:
  - name: "SMLReaderManufacturer"
    state_topic: "homeassistant/sensor/smartmeter/sensor/1/obis/1-0:96.50.1/1/value"

tom_l · July 17, 2022, 5:54am

mqtt: 
  sensor: !include_dir_merge_list mqtt/sensors/
  binary_sensor: !include_dir_merge_list mqtt/binary_sensors/

sensor files in mqtt/sensors/

- name: "SMLReaderManufacturer"
  state_topic: "homeassistant/sensor/smartmeter/sensor/1/obis/1-0:96.50.1/1/value"

binary sensor files mqtt/binary_sensors/

- name: "SMLReaderManufacturer"
  state_topic: "homeassistant/sensor/smartmeter/sensor/1/obis/1-0:96.50.1/1/value"

SawKyrom · July 17, 2022, 3:36pm

Thanks Tom! Love this community.