-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
Comments
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! |
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 |
Sample 1binary_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 2input_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, Edit: Do I win an award for most loaded components in a production environment? 😂 |
HA 0.42.2 |
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. |
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 |
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 |
Remember to post your version of home assistant when you post to this issue. |
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 |
My 0.42.2 shows the following:
|
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 |
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 |
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 |
Updates to 42.2 but the error hasn't changed
…On Sun, Apr 9, 2017, 14:10 Andy Shilton ***@***.***> wrote:
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
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6973 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOho_3CsjsR4ivBwQPty4QiQRJ4B3-WKks5ruMrOgaJpZM4M3FMu>
.
|
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 |
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: |
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. |
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 |
V 0.42.2 |
v 0.42.2 |
v.0.42.2 |
lol okay, I'm going to remove that warning, this is too much info to keep track off. Thanks for all the help everyone. |
@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. |
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 |
v42.2 |
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 |
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 |
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 |
HA 0.43.2: media_player.kodi
|
I am receiving the 10 second error on 0.44.1 while using harmony
|
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; I haven't actually checked if everything is working, but I'm just as happy as ever with this amazing software! Kind regards, |
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 👍 |
Still relevant and referenced in Hass. |
0.53.0 |
Which components / platforms were reported from taking a long time to load? |
media_player.pioneer, media_player.cast |
0.54.0 |
When hass is installing a package all components will take a long time to load (at least on rpi) |
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. |
Harmony is taking more than a minute for me on 55.2:
It still works though, so the configuration is correct. |
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 👍 |
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 👍 |
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 👍 |
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 |
@mstrchris83 did you have any other warning in your log, such as Setup platform/component is taking longer than xx seconds |
@mstrchris83 Please try the latest HA version and reopen if the issue still persists. |
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.
The text was updated successfully, but these errors were encountered: