Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Platforms/components blocking start from finishing #6973

Closed
balloob opened this issue Apr 7, 2017 · 55 comments
Closed

Platforms/components blocking start from finishing #6973

balloob opened this issue Apr 7, 2017 · 55 comments

Comments

@balloob
Copy link
Member

balloob commented Apr 7, 2017

Home Assistant will trigger a warning when a platform/component is taking too long to start. This issue will be a catch all to find them.

@balloob
Copy link
Member Author

balloob commented Apr 9, 2017

Yeah, I have a fix ready. It's the discovery component that is messing it up. 0.42.1 should be up soon. Thanks for reporting!

@arychj
Copy link
Contributor

arychj commented Apr 9, 2017

binary_sensor, sensor.time_date, zwave, calendar, notify, google, media_player.sonos, remote, twilio, websocket_api, automation, remote.harmony, binary_sensor.zwave, conversation, group, ifttt, script, zone, emulated_hue, logbook, switch.template, http, switch.zwave, shell_command, sensor, input_slider, updater, switch.wake_on_lan, api, media_player.plex, calendar.google, sensor.template, light.hue, sensor.darksky, mqtt, alexa, recorder, sensor.google_travel_time, frontend, device_tracker, sensor.command_line, sensor.speedtest, input_boolean, light, history, media_player, sun, switch, sensor.plex

@dale3h
Copy link
Member

dale3h commented Apr 9, 2017

Sample 1

binary_sensor.xiaomi, switch.digitalloggers, switch.broadlink, alarm_control_panel.manual, sensor.wunderground, sensor.yr, frontend, switch.xiaomi, binary_sensor.template, notify, api, history, light.hue, remote.harmony, xiaomi, sensor.apcupsd, sensor.ios, input_slider, switch, remote, sensor.darksky, zone, notify.ios, switch.template, cover, camera, light.xiaomi, ecobee, media_player.plex, lock.zwave, lock, sensor.time_date, config.group, panel_iframe, ios, media_player.cast, logger, input_boolean, alarm_control_panel, binary_sensor.mqtt, sensor.mqtt, input_select, climate.ecobee, sensor.xiaomi, device_tracker, config.core, media_player, mqtt, script, switch.command_line, ffmpeg, config, logbook, sensor.template, automation, updater, binary_sensor, shell_command, light.flux_led, tts, climate, zwave, camera.mjpeg, http, config.zwave, sensor.ecobee, cover.mqtt, light.limitlessled, binary_sensor.zwave, sensor.zwave, websocket_api, zeroconf, sensor.plex, recorder, binary_sensor.ecobee, light, sensor, switch.mqtt, sun, influxdb, switch.zwave, group, apcupsd, alert

Sample 2

input_boolean, sensor.ios, ecobee, shell_command, binary_sensor.template, binary_sensor, cover, sensor.xiaomi, config.core, ffmpeg, sensor.wunderground, alarm_control_panel, tts, camera.mjpeg, sensor.darksky, sensor.plex, lock.zwave, remote.harmony, switch.command_line, group, sensor, alarm_control_panel.manual, script, history, switch.mqtt, media_player, mqtt, sensor.ecobee, frontend, automation, sensor.apcupsd, binary_sensor.ecobee, binary_sensor.mqtt, cover.mqtt, api, config, logger, media_player.cast, light.hue, config.group, switch.digitalloggers, updater, sun, light.flux_led, xiaomi, device_tracker, switch.xiaomi, sensor.zwave, sensor.yr, input_select, recorder, alert, websocket_api, input_slider, config.zwave, switch.template, light.limitlessled, binary_sensor.xiaomi, ios, switch.broadlink, climate, zone, zwave, http, panel_iframe, logbook, influxdb, light.xiaomi, notify.ios, switch.zwave, lock, apcupsd, switch, remote, sensor.template, zeroconf, camera, light, sensor.mqtt, notify, binary_sensor.zwave, climate.ecobee,
media_player.plex, sensor.time_date

Edit: Do I win an award for most loaded components in a production environment? 😂

@bieniu
Copy link
Member

bieniu commented Apr 9, 2017

HA 0.42.2
zeroconf, config.zwave, shell_command, xiaomi, zwave, sensor.darksky, device_tracker, recorder, sensor.speedtest, updater, sensor.systemmonitor, sensor.google_travel_time, climate.zwave, script, binary_sensor, input_select, http, sensor.template, binary_sensor.trend, config, frontend, binary_sensor.xiaomi, logger, mqtt, config.group, climate, input_boolean, switch.xiaomi, sensor.command_line, scene.homeassistant, zone, config.core, switch, switch.wake_on_lan, sensor.xiaomi, websocket_api, notify, light.yeelight, light, sun, sensor, sensor.statistics, scene, media_player, automation, media_player.denonavr, api, light.xiaomi, group, history, logbook

@balloob
Copy link
Member Author

balloob commented Apr 9, 2017

Discovery was the culprit. We have fixed that in the recent release 0.42.1. I've deleted all the comments containing discovery to clean up this issue.

@ZyberSE
Copy link

ZyberSE commented Apr 9, 2017

I'm seeing this in 0.42.0:

sensor.speedtest, logger, media_player.samsungtv, frontend, sensor.darksky, ios, sensor, sensor.ios, mqtt, media_player, switch.zwave, media_player.plex, sensor.template, notify.ios, config.group, sensor.netatmo, binary_sensor.netatmo, device_tracker, tts, sun, http, notify, camera.generic, climate, light, light.hue, input_slider, config.zwave, alarm_control_panel, api, camera, zone, config, logbook, updater, automation, sensor.time_date, netatmo, climate.netatmo, history, recorder, binary_sensor, binary_sensor.command_line, camera.netatmo, shell_command, switch, websocket_api, input_boolean, discovery, alarm_control_panel.manual, zwave, zeroconf, binary_sensor.zwave, alert, group, config.core, script, sensor.zwave

@jladefoged
Copy link

jladefoged commented Apr 9, 2017

0.42.0:

logbook, device_tracker, sun, sensor.google_travel_time, switch.zwave, panel_iframe, light.lifx, media_player.squeezebox, updater, media_player.kodi, media_player, config.core, sensor.miflora, light, camera, config, zwave, frontend, automation, recorder, script, history, switch.template, websocket_api, sensor.wunderground, shell_command, binary_sensor.zwave, binary_sensor, alarm_control_panel.manual, config.zwave, camera.synology, sensor, switch, alarm_control_panel, http, notify, sensor.template, zone, group, sensor.transmission, config.group, camera.generic, switch.wake_on_lan, api, sensor.zwave

@MartinHjelmare
Copy link
Member

Remember to post your version of home assistant when you post to this issue.

@ZyberSE
Copy link

ZyberSE commented Apr 9, 2017

Just updated to 0.42.2 and still sees this:

tts, switch, input_slider, updater, script, camera, discovery, sun, config.group, http, config.zwave, logger, alarm_control_panel, config, binary_sensor.netatmo, sensor.darksky, media_player.plex, websocket_api, binary_sensor.zwave, sensor.time_date, sensor.speedtest, alert, light.hue, ios, sensor.template, alarm_control_panel.manual, zone, device_tracker, climate, config.core, sensor.zwave, media_player, switch.zwave, sensor, zeroconf, api, camera.generic, frontend, notify.ios, sensor.ios, media_player.samsungtv, input_boolean, history, group, binary_sensor, binary_sensor.command_line, shell_command, logbook, sensor.netatmo, light, climate.netatmo, notify, camera.netatmo, zwave, recorder, automation, mqtt, netatmo

@syphernl
Copy link
Contributor

syphernl commented Apr 9, 2017

My 0.42.2 shows the following:

sensor.darksky, light, group, calendar.google, proximity, panel_iframe, sensor.mqtt, binary_sensor, sensor.buienradar, sensor.ring, sensor.dsmr, mqtt, websocket_api, media_player.webostv, switch.zwave, media_player.kodi, notify, zone, scene, automation, calendar, updater, camera.generic, ring, sensor, sensor.template, sensor.nzbget, frontend, input_boolean, sensor.time_date, alarm_control_panel.manual, media_player, alarm_control_panel, device_tracker, script, sensor.sonarr, config.zwave, google, api, config, sensor.systemmonitor, zwave, discovery, scene.homeassistant, light.hue, sensor.google_travel_time, switch, logbook, sensor.zwave, media_player.universal, recorder, binary_sensor.workday, binary_sensor.ring, media_player.onkyo, alert, binary_sensor.zwave, http, camera, tts, rest_command, config.core, switch.wake_on_lan, sun, config.group, history

@DeadpoolPancakes
Copy link

0.42.2

light.limitlessled, sensor, discovery, recorder, panel_iframe, wemo, logbook, sensor.torque, sensor.mqtt, binary_sensor, sensor.statistics, switch, camera, media_player.cast, tts, conversation, zone, camera.mjpeg, device_sun_light_trigger, automation, switch.flux, notify, sensor.google_travel_time, sensor.fitbit, switch.broadlink, updater, light, media_player.plex, history, sun, switch.orvibo, device_tracker, sensor.broadlink, scene.homeassistant, http, config.core, config.group, sensor.plex, sensor.systemmonitor, switch.wake_on_lan, media_player, switch.command_line, android_ip_webcam, sensor.android_ip_webcam, sensor.moon, group, websocket_api, emulated_hue, sensor.api_streams, sensor.pi_hole, shell_command, api, sensor.speedtest, sensor.darksky, binary_sensor.iss, frontend, script, config, scene, ifttt, sensor.dht, mqtt, media_player.kodi, alexa

@dap35
Copy link

dap35 commented Apr 9, 2017

0.42.2

switch.zwave, device_tracker, zwave, sensor, binary_sensor, light.zwave, frontend, automation, group, logbook, input_boolean, light, history, switch, updater, binary_sensor.zwave, discovery, websocket_api, http, sun, recorder, sensor.zwave, zone, api

@andyshilton
Copy link

I got this too so I hope this helps (thanks for the great work though - I love HASS)

0.42.2

zone, climate.nest, tts, input_boolean, scene.homeassistant, camera.nest, binary_sensor.nest, logbook, sensor, scene, group, websocket_api, shell_command, rfxtrx, sensor.nest, config.zwave, script, config.core, camera, switch, binary_sensor.zwave, http, conversation, notify, automation, frontend, mqtt, discovery, input_slider, device_tracker, sensor.time_date, zwave, updater, switch.broadlink, sensor.zwave, api, nest, binary_sensor, climate, recorder, sun, switch.rfxtrx, history, config, sensor.template, config.group, switch.zwave

@ChefsSlaad
Copy link

ChefsSlaad commented Apr 9, 2017 via email

@dcrypt3d
Copy link
Contributor

dcrypt3d commented Apr 9, 2017

sensor.speedtest, media_player, zeroconf, input_slider, mqtt, http, script, sensor.command_line, binary_sensor.zwave, api, sensor.ecobee, alexa, weblink, updater, sensor.darksky, zone, sensor.statistics, zwave, binary_sensor, lock.zwave, ios, sensor.wunderground, camera.generic, cover, logbook, config, sensor.apcupsd, scene, media_player.mpd, config.core, alarm_control_panel, discovery, sensor.zwave, sensor.google_travel_time, notify.ios, lock, device_tracker, cover.myq, switch, sensor.min_max, light.zwave, sensor.systemmonitor, automation, ecobee, websocket_api, config.zwave, ifttt, switch.zwave, climate, camera, input_boolean, config.group, climate.ecobee, sensor.rest, emulated_hue, logger, media_player.snapcast, camera.foscam, sensor.template, history, remote, media_player.kodi, sensor.ios, switch.command_line, switch.template, shell_command, notify, group, switch.tplink, proximity, sensor.sabnzbd, sensor.mqtt_room, recorder, alarm_control_panel.manual, apcupsd, scene.homeassistant, frontend, remote.harmony, light, sun, binary_sensor.ecobee, sensor, input_select

@tbrasser
Copy link

tbrasser commented Apr 9, 2017

Using the most recent homeassistant/home-assistant:dev Docker image, 0.42.0.dev0

influxdb, alarm_control_panel.manual, recorder, alarm_control_panel, zeroconf, sun, input_select, sensor.plex, switch, config.zwave, media_player.universal, sensor.darksky, config.group, sensor, camera, switch.zwave, zone, history, media_player.kodi, conversation, sensor.haveibeenpwned, light.limitlessled, weblink, media_player.plex, notify, remote, light, sensor.nzbget, tts, logbook, camera.generic, frontend, input_boolean, ifttt, http, config.core, remote.harmony, switch.flux, sensor.template, sensor.sonarr, api, sensor.zwave, group, emulated_hue, config, automation, websocket_api, media_player.onkyo, sensor.min_max, media_player.cast, zwave, media_player, device_tracker, light.hyperion, input_slider

Maybe relevant:
17-04-09 16:37:39 WARNING (MainThread) [homeassistant.setup] Setup of remote is taking over 10 seconds.
17-04-09 16:37:39 WARNING (MainThread) [homeassistant.setup] Setup of media_player is taking over 10 seconds.
17-04-09 16:37:40 WARNING (MainThread) [homeassistant.components.remote] Setup of platform harmony is taking over 10 seconds.
17-04-09 16:37:40 WARNING (MainThread) [homeassistant.components.media_player] Setup of platform cast is taking over 10 seconds.

@stu-gott
Copy link
Contributor

stu-gott commented Apr 9, 2017

Seeing this message on 0.42.2 as well:

http, binary_sensor.nest, media_player.sonos, group, automation, binary_sensor.zwave, climate, media_player, sensor.wunderground, sensor.nest, switch, api, binary_sensor.mqtt, script, discovery, device_tracker, lock, sensor.zwave, switch.zwave, sensor.kira, binary_sensor.template, wemo, tts, sun, binary_sensor, history, sensor.mqtt, updater, zone, input_boolean, camera, climate.nest, lock.zwave, calendar.google, websocket_api, google, camera.nest, light.zwave, shell_command, zwave, mqtt, sensor.template, switch.wemo, light, kira, input_slider, calendar, nest, recorder, notify, binary_sensor.flic, sensor, frontend

Kira is an unreleased (yet) custom platform I've written that has code in the remote and sensor platforms. It's never been a problem in previous versions but pointing that out it as @tbrasser noted delays related to the remote platform.

@itswag7
Copy link

itswag7 commented Apr 9, 2017

Seeing this on 42.2.

weblink, alarm_control_panel, script, sensor.yweather, sensor.ecobee, lock.wink, device_tracker, discovery, camera.mjpeg, http, scene.wink, light.wink, notify, binary_sensor.wink, sensor.plex, fan, api, binary_sensor.zwave, binary_sensor, sensor.speedtest, media_player, camera, climate.wink, zone, climate, recorder, sensor.template, cover, scene, fan.wink, sensor.darksky, history, binary_sensor.ecobee, ecobee, sensor.google_travel_time, automation, sensor, lock, sensor.wink, sensor.sabnzbd, sensor.systemmonitor, switch, websocket_api, group, sun, frontend, camera.generic, cover.wink, alarm_control_panel.wink, sensor.zwave, light, zwave, switch.wink, logbook, emulated_hue, mqtt, climate.ecobee, media_player.plex, wink

@olegunnardahle
Copy link

V 0.42.2
17-04-09 16:51:55 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at http://bit.ly/2ogP58T : binary_sensor, sensor.speedtest, config, logbook, frontend, climate.generic_thermostat, history, config.group, config.zwave, light, notify, tts, remote.harmony, binary_sensor.zwave, recorder, remote, scene, automation, input_boolean, scene.homeassistant, http, websocket_api, sensor.yr, updater, media_player.apple_tv, switch, config.core, switch.zwave, media_player, api, climate, conversation, sensor.template, light.hue, light.zwave, zwave, sensor.zwave, sensor, media_player.sonos, group, sensor.systemmonitor, sun, media_player.cast

@hokus15
Copy link

hokus15 commented Apr 9, 2017

v 0.42.2
input_boolean, zone, binary_sensor.command_line, sensor.netatmo, sensor.efergy, climate, sensor.template, logger, api, switch.template, http, camera, config, updater, group, calendar, config.zwave, logbook, camera.generic, panel_iframe, sensor, apiai, sensor.nut, sensor.bitcoin, sensor.google_travel_time, discovery, binary_sensor.template, switch.zwave, websocket_api, netatmo, camera.foscam, mqtt, frontend, sensor.fitbit, ifttt, sensor.systemmonitor, sensor.speedtest, switch, switch.mqtt, device_tracker, tts, sensor.history_stats, notify, binary_sensor.zwave, input_slider, binary_sensor.netatmo, config.core, sensor.snmp, history, calendar.google, config.group, binary_sensor, binary_sensor.mqtt, recorder, google, climate.netatmo, sensor.zwave, sun, zwave, conversation, shell_command, sensor.mqtt, switch.command_line, camera.netatmo, automation

@bobnwk
Copy link
Contributor

bobnwk commented Apr 9, 2017

v.0.42.2
config.group, google, ifttt, android_ip_webcam, config.core, climate.nest, camera, recorder, panel_iframe, sensor.android_ip_webcam, scene, sensor.broadlink, sensor.command_line, websocket_api, sensor.nest, switch, sensor.template, logbook, conversation, zone, script, nest, sensor.darksky, calendar, updater, logger, light.limitlessled, sensor.time_date, climate, camera.generic, sensor.google_travel_time, media_player.cast, camera.mjpeg, proximity, sensor.speedtest, switch.wake_on_lan, sun, frontend, binary_sensor.nest, input_slider, media_player, camera.nest, api, history, http, device_tracker, binary_sensor, input_boolean, notify, input_select, sensor.systemmonitor, mqtt, light, automation, group, tts, config, switch.broadlink, sensor, scene.homeassistant, calendar.google, discovery

@balloob
Copy link
Member Author

balloob commented Apr 9, 2017

lol okay, I'm going to remove that warning, this is too much info to keep track off. Thanks for all the help everyone.

@JudgeDreddKLC
Copy link
Contributor

@balloob how about setting up a SQL server with error-reporting, hass could be configured with automatic error submissions (opt-in), and we can then data-mine this stuff. I can help by setting up the server and writing the SQL code.

@JudgeDreddKLC
Copy link
Contributor

climate, history, ecobee, ring, zwave, config.zwave, switch, frontend, recorder, light, config, tts, isy994, sensor.zwave, climate.ecobee, http, binary_sensor, cover.isy994, lock.isy994, automation, cover, updater, binary_sensor.zwave, sensor.yr, switch.zwave, sensor, binary_sensor.isy994, lock.zwave, conversation, logbook, sun, sensor.ecobee, config.core, group, websocket_api, light.zwave, config.group, switch.isy994, lock, sensor.template, binary_sensor.ecobee, light.isy994, fan.isy994, fan, api, sensor.isy994

@mchinery
Copy link

v42.2
17-04-10 08:21:01 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at http://bit.ly/2ogP58T : media_player.plex, config.zwave, http, switch.zwave, alarm_control_panel.manual, discovery, media_player, config.group, ifttt, camera.nest, tts, device_tracker, history, joaoapps_join, sensor.darksky, nest, sensor, alarm_control_panel, sensor.template, notify, sensor.systemmonitor, remote, climate, logbook, emulated_hue, api, group, conversation, sun, remote.harmony, sensor.nest, media_player.roku, script, zwave, binary_sensor.zwave, binary_sensor.nest, recorder, input_select, camera.mjpeg, sensor.zwave, frontend, switch, camera, websocket_api, updater, automation, media_player.panasonic_viera, input_boolean, binary_sensor, mqtt, zone, config.core, climate.nest, config

@mihalski
Copy link

HA 0.42.2

light, zwave, api, config, device_tracker, media_player, mqtt, sensor.mqtt, sun, panel_iframe, tts, media_player.yamaha, history, sensor.statistics, binary_sensor.mqtt, zone, influxdb, updater, recorder, binary_sensor.zwave, binary_sensor, frontend, config.zwave, websocket_api, light.lifxtest, group, http, remote, switch, logbook, automation, switch.mqtt, config.group, sensor, config.core, media_player.plex, sensor.template, sensor.zwave, conversation, remote.harmony

@LaStrada
Copy link
Member

HA 0.42.2

scene, shell_command, binary_sensor.workday, binary_sensor, camera.generic, device_tracker, history, light.zwave, rfxtrx, sensor, zeroconf, input_slider, notify.ios, zone, alarm_control_panel, sensor.systemmonitor, switch.zwave, mqtt, light, sun, input_boolean, recorder, zwave, sensor.yr, alarm_control_panel.manual, light.hue, ios, api, sensor.moon, http, automation, binary_sensor.zwave, notify, discovery, frontend, group, tts, sensor.google_travel_time, sensor.command_line, sensor.rfxtrx, climate, updater, climate.generic_thermostat, sensor.zwave, switch, camera, websocket_api, scene.homeassistant

@Vertikar
Copy link

HA 0.42.2

api, zone, camera.generic, group, switch, recorder, input_boolean, config, websocket_api, sensor.waqi, http, sensor.wunderground, sensor.bom, notify, light.lifx, sensor.yr, sun, automation, config.core, sensor, device_tracker, sensor.rest, binary_sensor, binary_sensor.hikvision, sensor.nest, logbook, light.xiaomi, sensor.google_travel_time, sensor.fastdotcom, climate.nest, camera, discovery, xiaomi, nest, sensor.xiaomi, sensor.ecobee, climate, binary_sensor.ecobee, sensor.darksky, camera.nest, sensor.sabnzbd, conversation, switch.xiaomi, ecobee, history, binary_sensor.nest, light, influxdb, sensor.openweathermap, binary_sensor.xiaomi, climate.ecobee, sensor.speedtest, config.group, updater, frontend, sensor.statistics, sensor.command_line

@cycl0psg
Copy link

cycl0psg commented Apr 28, 2017

HA 0.43.2:

media_player.kodi

17-04-28 20:51:56 WARNING (MainThread) [homeassistant.setup] Setup of media_player is taking over 10 seconds.
17-04-28 20:51:56 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.kodi
17-04-28 20:52:01 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/home/hass/hass/deps/jsonrpc_websocket/jsonrpc.py", line 42, in send_message
    response = yield from pending_message.wait(self._timeout)
  File "/home/hass/hass/deps/jsonrpc_websocket/jsonrpc.py", line 118, in wait
    return self._response
  File "/usr/local/lib/python3.4/dist-packages/async_timeout/__init__.py", line 46, in __exit__
    raise asyncio.TimeoutError from None
concurrent.futures._base.TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
    result = coro.throw(exc)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity_component.py", line 361, in async_process_entity
    new_entity, self, update_before_add=update_before_add
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity_component.py", line 189, in async_add_entity
    yield from entity.async_update()
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/media_player/kodi.py", line 373, in async_update
    ))['item']
  File "/home/hass/hass/deps/jsonrpc_websocket/jsonrpc.py", line 48, in send_message
    raise TransportError('Transport Error', message, exc)
jsonrpc_base.jsonrpc.TransportError: ("Error calling method 'Player.GetItem': Transport Error", TimeoutError())

@Bray90820
Copy link

Bray90820 commented May 17, 2017

I am receiving the 10 second error on 0.44.1 while using harmony

aaron@server:/$ hass --open-ui
Config directory: /home/aaron/.homeassistant
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_off>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_on>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=toggle>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=stop>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=restart>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=check_config>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=reload_core_config>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=persistent_notification, service=create>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.bootstrap] Home Assistant core initialized
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.loader] Loaded history from homeassistant.components.history
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.loader] Loaded http from homeassistant.components.http
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.loader] Loaded api from homeassistant.components.api
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.loader] Loaded introduction from homeassistant.components.introduction
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.setup] Setting up introduction
2017-05-17 18:52:20 INFO (Thread-4) [homeassistant.components.introduction] 

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        Hello, and welcome to Home Assistant!

        We'll hope that we can make all your dreams come true.

        Here are some resources to get started:

         - Configuring Home Assistant:
           https://home-assistant.io/getting-started/configuration/

         - Available components:
           https://home-assistant.io/components/

         - Troubleshooting your configuration:
           https://home-assistant.io/getting-started/troubleshooting-configuration/

         - Getting help:
           https://home-assistant.io/help/

        This message is generated by the introduction component. You can
        disable it in configuration.yaml.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=introduction>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.setup] Setting up http
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=http>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=websocket_api>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.setup] Setting up api
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.setup] Setting up recorder
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=api>
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.setup] Setting up frontend
2017-05-17 18:52:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=frontend>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=recorder>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up history
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=history>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded group from homeassistant.components.group
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up group
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded updater from homeassistant.components.updater
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded sensor.yr from homeassistant.components.sensor.yr
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up sensor
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded sun from homeassistant.components.sun
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded tts from homeassistant.components.tts
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded tts.google from homeassistant.components.tts.google
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded conversation from homeassistant.components.conversation
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded remote from homeassistant.components.remote
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded remote.harmony from homeassistant.components.remote.harmony
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up remote
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded config from homeassistant.components.config
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up updater
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=group, service=set_visibility>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=group, service=reload>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=group>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up logbook
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up config
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=updater>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=logbook, service=log>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded config.core from homeassistant.components.config.core
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.core>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded config.hassbian from homeassistant.components.config.hassbian
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.loader] Loaded config.group from homeassistant.components.config.group
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.group>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up sun
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=logbook>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up tts
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up conversation
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state sun.sun=above_horizon; next_rising=2017-05-18T10:30:58+00:00, next_midnight=2017-05-18T05:50:37+00:00, next_dawn=2017-05-18T09:58:50+00:00, next_dusk=2017-05-18T01:41:13+00:00, next_setting=2017-05-18T01:09:12+00:00, elevation=0, azimuth=0, next_noon=2017-05-18T17:50:34+00:00, friendly_name=Sun @ 2017-05-17T18:52:21.395039-05:00>, entity_id=sun.sun, old_state=None>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=sun>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=conversation, service=process>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.setup] Setting up discovery
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=discovery>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=conversation>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.yr
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state sensor.yr_symbol=unknown; friendly_name=yr Symbol, attribution=Weather forecast from yr.no, delivered by the Norwegian Meteorological Institute and the NRK., entity_picture=//api.met.no/weatherapi/weathericon/1.1/?symbol=None;content_type=image/png @ 2017-05-17T18:52:21.454108-05:00>, entity_id=sensor.yr_symbol, old_state=None>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.components.remote] Setting up remote.harmony
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=tts, service=google_say>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=tts, service=clear_cache>
2017-05-17 18:52:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=tts>
2017-05-17 18:52:22 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state sensor.yr_symbol=5; friendly_name=yr Symbol, attribution=Weather forecast from yr.no, delivered by the Norwegian Meteorological Institute and the NRK., entity_picture=//api.met.no/weatherapi/weathericon/1.1/?symbol=5;content_type=image/png @ 2017-05-17T18:52:22.228254-05:00>, entity_id=sensor.yr_symbol, old_state=<state sensor.yr_symbol=unknown; friendly_name=yr Symbol, attribution=Weather forecast from yr.no, delivered by the Norwegian Meteorological Institute and the NRK., entity_picture=//api.met.no/weatherapi/weathericon/1.1/?symbol=None;content_type=image/png @ 2017-05-17T18:52:21.454108-05:00>>
2017-05-17 18:52:22 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=sensor>
2017-05-17 18:52:31 WARNING (MainThread) [homeassistant.setup] Setup of remote is taking over 10 seconds.
2017-05-17 18:52:31 WARNING (MainThread) [homeassistant.components.remote] Setup of platform harmony is taking over 10 seconds.

@pappajohan
Copy link

Hi!

On 0.47.0 after trying to get rid of some errors which I believe comes from Telldus live someone told me to try a restart after setting my dimmers to 75%.

I always thought those errors came from "WARNING (Thread-10) [homeassistant.components.tellduslive] Unidentified device type (methods: 0)".

Well, the old errors disappeared and immediately after the warning above I got;
2017-06-20 11:30:21 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at http://bit.ly/2ogP58T : binary_sensor.template, switch, group, scene.homeassistant, http, input_boolean, device_tracker, zeroconf, media_player, notify, automation, recorder, websocket_api, google, frontend, calendar.google, binary_sensor, history, ios, sensor.ios, sensor.yr, scene, tellduslive, calendar, config.automation, tts, media_player.apple_tv, zone, config.group, notify.ios, config.core, sensor, sun, logbook, media_player.cast, updater, api, config, input_select

I haven't actually checked if everything is working, but I'm just as happy as ever with this amazing software!

Kind regards,
/Johan

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@balloob
Copy link
Member Author

balloob commented Sep 5, 2017

Still relevant and referenced in Hass.

@kjetilpp
Copy link

0.53.0
lock.volvooncall, config.core, config.group, volvooncall, zone, switch.rfxtrx, config, sensor.zwave, binary_sensor.zwave, http, ifttt, device_tracker, light.tradfri, logbook, api, switch.zwave, binary_sensor.verisure, sensor.yr, ios, sensor.volvooncall, notify, notify.ios, camera, sensor.ios, switch, camera.verisure, light, lock.verisure, camera.generic, group, history, tradfri, lock, script, sensor.rfxtrx, sensor, recorder, frontend, tellduslive, alarm_control_panel.verisure, binary_sensor.volvooncall, rfxtrx, tts, switch.verisure, zeroconf, sun, automation, sensor.verisure, config.automation, config.customize, binary_sensor, alarm_control_panel, websocket_api, config.zwave, alarm_control_panel.manual, updater, input_boolean, config.script, zwave, switch.volvooncall, verisure, hassio

@balloob
Copy link
Member Author

balloob commented Sep 14, 2017

Which components / platforms were reported from taking a long time to load?

@Spartan-II-117
Copy link
Contributor

media_player.pioneer, media_player.cast

@jeliasson
Copy link

0.54.0
ifttt, media_player.cast, sensor.vasttrafik, notify, sensor.darksky, config.customize, updater, sensor.time_date, logger, recorder, frontend, zone, api, script, sensor, config.core, http, media_player.plex, config.automation, automation, media_player.apple_tv, tellduslive, logbook, tts, sun, sensor.yr, config.script, sensor.rest, websocket_api, shell_command, apple_tv, group, binary_sensor.flic, history, config, light, remote, remote.apple_tv, media_player, light.hue, conversation, binary_sensor, config.group, media_player.sonos, device_tracker

@andrey-git
Copy link
Contributor

When hass is installing a package all components will take a long time to load (at least on rpi)

@balloob
Copy link
Member Author

balloob commented Oct 16, 2017

Requirements are installed before the timer starts running: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/setup.py#L166-L183 . That being said, it will probably require a bunch of CPU.

@tboyce021
Copy link
Contributor

tboyce021 commented Oct 17, 2017

Harmony is taking more than a minute for me on 55.2:

ERROR (MainThread) [homeassistant.components.remote] Setup of platform harmony is taking longer than 60 seconds. Startup will proceed without waiting any longer

It still works though, so the configuration is correct.

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@mstrchris83
Copy link

Hi,

I'm on HA 0.89.2 using the official Docker image on my QNAP NAS and for the past several days I've been seeing the following message in my log.

2019-03-18 22:08:04 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at http://bit.ly/2ogP58T : upnp, scene, switch.command_line, custom_updater, lovelace, sensor.yr, panel_iframe, websocket_api, cover.esphome, onboarding, input_number, sensor.asuswrt, input_text, alert, light, discovery, binary_sensor.tod, media_player.plex, climate.wink, person, script, scene.homeassistant, config.entity_registry, rest_command, binary_sensor.august, cover.wink, logger, config.core, light.group, august, switch.zha, esphome, shopping_list, config, scene.wink, camera.ffmpeg, sensor.google_geocode, binary_sensor.wink, cloud, binary_sensor.ffmpeg_motion, tts, lock.zwave, history_graph, media_player.alexa_media, zeroconf, binary_sensor.mqtt, config.script, weather, media_player.samsungtv, sensor.google_travel_time, light.wink, sensor.history_stats, zwave, geo_location, config.auth_provider_homeassistant, notify.html5, fan, switch.wink, updater, fan.zwave, recorder, sensor.mqtt_room, remote.harmony, lock.august, switch, sensor.darksky, cast, camera.mjpeg, config.auth, switch.zwave, camera.local_file, binary_sensor.zwave, fan.zha, conversation, sensor.zha, weather.darksky, lock.wink, config.area_registry, device_tracker, proximity, alarm_control_panel.wink, fan.esphome, cover, water_heater.wink, shell_command, notify.pushover, geo_location.geo_json_events, config.device_registry, calendar.google, automation, light.switch, alexa_media, ifttt, system_log, customizer, light.esphome, fan.wink, sensor.statistics, camera.august, sensor.esphome, config.group, http, history, sensor.speedtestdotnet, sensor.ups, light.flux_led, camera, notify, switch.template, cover.zwave, light.zwave, binary_sensor, binary_sensor.template, notify.smtp, camera.generic, input_boolean, map, sensor, remote, sensor.zwave, light.tuya, config.zwave, zone, speedtestdotnet, water_heater, zha, python_script, mqtt, sensor.command_line, sensor.systemmonitor, system_health, binary_sensor.zha, config.automation, wink, climate.zwave, notify.group, binary_sensor.esphome, notify.file, frontend, emulated_hue, alarm_control_panel, climate, logbook, sun, webhook, config.customize, sensor.season, calendar, asuswrt, variable, sensor.wink, binary_sensor.bayesian, sensor.time_date, sensor.moon, sensor.plex, config.config_entries, auth, sensor.template, light.zha, google, media_player.cast, ffmpeg, sensor.mold_indicator, api, group, media_player, weblink, lock, sensor.mqtt, tuya, binary_sensor.ffmpeg_noise, input_select, switch.esphome

@awarecan
Copy link
Contributor

@mstrchris83 did you have any other warning in your log, such as Setup platform/component is taking longer than xx seconds

@Adminiuga
Copy link
Contributor

@mstrchris83 Please try the latest HA version and reopen if the issue still persists.

@home-assistant home-assistant locked as resolved and limited conversation to collaborators May 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests