core 🚀 - Platforms that do I/O inside properties

Fixed via #4219 Thanks @pvizeli
Component: Nest
Platform: Climate
Time to update (average of three): 0.474

Took a look at the python-nest platform and it is calling the nest API every X minutes it looks like (appears to be 5 minutes). So I am only seeing this issue logged once for every 5 updates.

The same code is used to update all Nest platforms so I assume this would be an issue with any of them.

w1ll1am23 on 4 Nov 2016

👍1

Reporting as requested.

I noticed this with the climate.radiotherm component. Delays vary between the two captures below. Hardware is a Radio Thermostat CT50. No idea if the time taken is being caused by the issue mentioned above, or just slow hardware. Functionality seems unaffected.

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.thermostat took 24.439 seconds. Please report platform to the developers at https://goo.gl/Nvioub
WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.thermostat took 4.149 seconds. Please report platform to the developers at https://goo.gl/Nvioub

xehn on 5 Nov 2016

👍1

Seeing this behaviour as well with the media_player.sonos component, reporting as requested:

16-11-05 19:24:31 homeassistant.helpers.entity: Updating state for media_player.kitchen took 0.537 seconds. Please report platform to the developers at https://goo.gl/Nvioub

16-11-05 19:25:32 homeassistant.helpers.entity: Updating state for media_player.kitchen took 0.399 seconds. Please report platform to the developers at https://goo.gl/Nvioub

16-11-05 19:26:11 homeassistant.helpers.entity: Updating state for media_player.kitchen took 0.314 seconds. Please report platform to the developers at https://goo.gl/Nvioub

bjw-s on 5 Nov 2016

👍3

I am also seeing this with the media_player.sonos component on HA 0.32. I am also seeing the message below which is for the sonos controller package, not sure if it is at all related to this issue.. It does not appear to be updating the component.

Nov 05 14:57:44 rpi01.home.int hass[24265]: INFO:homeassistant.util.package:Attempting install of https://github.com/SoCo/SoCo/archive/cf8c2701165562eccbf1ecc879bf7060ceb0993e.zip#SoCo==0.12

dap35 on 5 Nov 2016

👍1

Here you go - reporting per log request:

16-11-06 03:28:16 homeassistant.helpers.entity: Updating state for cover.garagedoor took 1.176 seconds. Please report platform to the developers at https://goo.gl/Nvioub

16-11-06 03:28:32 homeassistant.helpers.entity: Updating state for cover.garagedoor took 1.428 seconds. Please report platform to the developers at https://goo.gl/Nvioub

16-11-06 03:28:46 homeassistant.helpers.entity: Updating state for cover.garagedoor took 1.167 seconds. Please report platform to the developers at https://goo.gl/Nvioub

olines on 6 Nov 2016

Which platform is this?

On Sat, Nov 5, 2016, 20:56 olines [email protected] wrote:

Here you go - reporting per log request:

16-11-06 03:28:16 homeassistant.helpers.entity: Updating state for cover.garagedoor took 1.176 seconds. Please report platform to the developers at https://goo.gl/Nvioub

16-11-06 03:28:32 homeassistant.helpers.entity: Updating state for cover.garagedoor took 1.428 seconds. Please report platform to the developers at https://goo.gl/Nvioub

16-11-06 03:28:46 homeassistant.helpers.entity: Updating state for cover.garagedoor took 1.167 seconds. Please report platform to the developers at https://goo.gl/Nvioub

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/4210#issuecomment-258658865,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYJ2iIevk0Q3KCaVdLtK6aQUULeWWMLks5q7U_TgaJpZM4KpMod
.

balloob on 6 Nov 2016

I'm getting
16-11-06 01:29:01 homeassistant.helpers.entity: Updating state for climate.bedroom took 0.371 seconds. Please report platform to the developers at https://goo.gl/Nvioub

when connecting to my Honeywell thermostat API.

raccettura on 6 Nov 2016

I´m getting
homeassistant.helpers.entity: Updating state for switch.kitchen_lamp took 0.563 seconds. Please report platform to the developers at https://goo.gl/Nvioub

When trying to turn on a lamp using emulated hue

(lamp didn't turn on but I think there is an issue with emulated hue in latest version)

frelev on 6 Nov 2016

@frelev what platform is the lamp?

balloob on 6 Nov 2016

I am getting the warning on cover.garage_door - it is the "myq" platform, from: http://pastebin.com/qVszax1t

TeeSeePeeEyePea on 6 Nov 2016

@Teeseepeeeyepea that component is indeed wrong. However, it is not part of Home Assistant so you'll have to find the author and have him fix it (the get_status call should be moved to a new update method) like done here: https://github.com/home-assistant/home-assistant/pull/4244/files

balloob on 6 Nov 2016

@balloob It´s a tellstick (not Net) switch

frelev on 6 Nov 2016

👍1

I have a huge number of KNX switches and I'm getting following in the error log (truncated):

16-11-06 20:54:28 homeassistant.helpers.entity: Updating state for switch.master_bedroom_spotlights took 1.022 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:29 homeassistant.helpers.entity: Updating state for switch.bathroom_shower_spotlights took 1.002 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:30 homeassistant.helpers.entity: Updating state for switch.toilet_extractor_fan took 1.002 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:31 homeassistant.helpers.entity: Updating state for switch.toilet_spotlight took 1.002 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:32 homeassistant.helpers.entity: Updating state for switch.bathroom_spotlights took 1.002 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:33 homeassistant.helpers.entity: Updating state for switch.hallway_ff_wall_lights took 1.003 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:34 homeassistant.helpers.entity: Updating state for switch.kitchen_centre_pendant took 1.003 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:35 homeassistant.helpers.entity: Updating state for switch.rear_gate took 1.003 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:36 homeassistant.helpers.entity: Updating state for switch.master_bedroom_wardrobe_spotlights took 1.002 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:37 homeassistant.helpers.entity: Updating state for switch.external_porch_wall_light took 1.003 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:38 homeassistant.helpers.entity: Updating state for switch.external_side_wall_lights took 1.003 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:39 homeassistant.helpers.entity: Updating state for switch.av_room_exctractor_fan took 1.003 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:40 homeassistant.helpers.entity: Updating state for switch.bathroom_extractor_fan took 1.003 seconds. Please report platform to the developers at https://goo.gl/Nvioub

resoai on 6 Nov 2016

👍1

@TeeSeePeeEyePea I made submitted a pull request for https://github.com/arraylabs/myq that updates to handle multipe doors (using name from the app) as well as resolving the error here. Have a look (may need to check my fork) and let me know if you see any problems.

kylerw on 7 Nov 2016

I am seeing lots of errors for pyW215 when I am using the D-Link DSP-W215 Switch, here is one example:

16-11-07 20:27:29 homeassistant.helpers.entity: Updating state for switch.patio_audio took 1.037 seconds. Please report platform to the developers at https://goo.gl/Nvioub

MichaelMuir on 7 Nov 2016

I am getting the warning message on the dark sky weather platform

timstanley1985 on 7 Nov 2016

👍2

I'm also getting this warning for the new openweathermap component (weather platform)

homeassistant.helpers.entity: Updating state for weather.openweathermap took 0.241 seconds. Please report platform to the developers at https://goo.gl/Nvioub

bestlibre on 7 Nov 2016

I just got the message on a template sensor too:

Nov 7 20:19:01 pi2 hass[524]: WARNING:homeassistant.helpers.entity:Updating state for sensor.back_room_temp_update_timer took 0.547 seconds. Please report platform to the developers at https://goo.gl/Nvioub

- platform: template
   sensors:
     back_room_temp_update_timer:
       value_template: '{% if is_state("input_boolean.boot_delay", "off") %} {{ (as_timestamp(now()) - as_timestamp(states.sensor.back_room.last_updated)) / 60 }} {% else %} {{ 0 | int }} {% endif %}'
       entity_id: sensor.time
       unit_of_measurement: 'minutes'

timstanley1985 on 7 Nov 2016

@bestlibre could you try against #4298 ?
@MichaelMuir could you try against #4301 ?

lwis on 7 Nov 2016

No more warning after I applied the patch

bestlibre on 8 Nov 2016

Am getting the warning on the date_time platform now too

timstanley1985 on 8 Nov 2016

Just got the warning Transmission sensor platform too

timstanley1985 on 8 Nov 2016

@balloob Transmission doesn't look to be doing anything bad, maybe this is producing some misnomers?

lwis on 8 Nov 2016

@lwis I think that you might be right. I'm seeing some that just cannot be there, like template and time date.

balloob on 9 Nov 2016

Let's increase it to 0.4 seconds in 0.32.3

balloob on 9 Nov 2016

@balloob The majority of the warnings I receive are 0.5 secs plus so, at least in my case, increasing to 0.4 seconds would not stop the warnings.

I have attached my log below. sensor.time is date_time platform, the two temp_update_timers are templates and the weather sensor is dark sky

16-11-10 01:06:01 homeassistant.helpers.entity: Updating state for sensor.time took 0.553 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 01:35:01 homeassistant.helpers.entity: Updating state for sensor.front_room_temp_update_timer took 0.567 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 03:27:01 homeassistant.helpers.entity: Updating state for sensor.front_room_temp_update_timer took 0.576 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 03:54:01 homeassistant.helpers.entity: Updating state for sensor.time took 0.557 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 04:17:01 homeassistant.helpers.entity: Updating state for sensor.transmission_status took 0.536 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 05:27:01 homeassistant.helpers.entity: Updating state for sensor.weather_temperature took 0.544 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 05:47:01 homeassistant.helpers.entity: Updating state for sensor.back_room_temp_update_timer took 0.528 seconds. Please report platform to the developers at https://goo.gl/Nvioub

timstanley1985 on 10 Nov 2016

I'm receiving this warning for alarm.com. I get the alert every 30 seconds. It seems to vary between 0.66 seconds and 1.4 seconds.

16-11-10 10:30:01 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for alarm_control_panel.alarm took 1.361 seconds. Please report platform to the developers at https://goo.gl/Nvioub

16-11-10 10:30:31 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for alarm_control_panel.alarm took 0.985 seconds. Please report platform to the developers at https://goo.gl/Nvioub

nathanm412 on 10 Nov 2016

Looks like a fix is incoming but still reporting in. Running HA 32.2.

This is a Panasonic Viera TV. As I understand, Viera's have iffy-support as it is but just wanted to check in. Alert every 20-40 seconds.

16-11-10 21:46:01 homeassistant.helpers.entity: Updating state for media_player.unnamed_device took 0.245 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 21:46:20 homeassistant.helpers.entity: Updating state for media_player.unnamed_device took 0.250 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 21:46:40 homeassistant.helpers.entity: Updating state for media_player.unnamed_device took 0.257 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 21:47:00 homeassistant.helpers.entity: Updating state for media_player.unnamed_device took 0.265 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 21:47:40 homeassistant.helpers.entity: Updating state for media_player.unnamed_device took 0.274 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-10 21:47:51 homeassistant.helpers.entity: Updating state for media_player.unnamed_device took 1.095 seconds. Please report platform to the developers at https://goo.gl/Nvioub

deegs on 11 Nov 2016

👍1

Sorry for the delayed reply, unfortunately KNX issues are still there.

16-11-06 20:54:28 homeassistant.helpers.entity: Updating state for switch.master_bedroom_spotlights took 1.022 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:29 homeassistant.helpers.entity: Updating state for switch.bathroom_shower_spotlights took 1.002 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:30 homeassistant.helpers.entity: Updating state for switch.toilet_extractor_fan took 1.002 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-06 20:54:31 homeassistant.helpers.entity: Updating state for switch.toilet_spotlight took 1.002 seconds. Please report platform to the developers at https://goo.gl/Nvioub

There is also a huge delay updating value of the switch.

resoai on 12 Nov 2016

@resoai are you running 0.32.3 ?

balloob on 12 Nov 2016

@balloob yes

resoai on 12 Nov 2016

It takes about 15-20 seconds for the switch to update it's value in the UI (when switching it off)? although the actual light turns on/off immediately.

resoai on 12 Nov 2016

Sounds like we should be updating the state after we change the lights, rather than waiting for update to be called?

lwis on 13 Nov 2016

I don't think so, it used to work fine before this major async movement.

resoai on 13 Nov 2016

Upgraded to 0.32.3, no warnings for 24 hours, was getting at least half a dozen a day on 0.32.2

timstanley1985 on 13 Nov 2016

@lwis there is a different KNX address for status changes so we actually need to wait for it to send something. Besides, lights could be triggered via physical buttons. As I said, the issue only started after this major async rewrite. Also it looks like the thermostat (climate component) is not reporting temperature.

I can confirm that the actual error messages are gone. There was a weird cache bug in Google Chrome which was displaying the old page.

resoai on 13 Nov 2016

KNX Problem

I have a working KNX-based system which I am trying to control via Home-Assistant, but there is still an issue with KNX driver.

HA is not able to switch lights on and off, nothing happens.

On HA screen in the browser, it correctly reads the state of the lights, but when I try and switch a light, nothing happens.

In the log file, there is a message about the time it takes - 3.2 secs

I have attached the log file to this post.

In the log file, around 17:11:54, I switched the a light, which is reflected in the log file, but the actual light did not switch

I have also attached my configuration file for your info.

configuration_and_logfile.zip

mestafin on 20 Nov 2016

Hello! I am owning this Edimax SP-2101W smart plug. And now my home-assistant log is full of this:

16-11-22 18:46:01 homeassistant.helpers.entity: Updating state for switch.edimax_smart_plug took 0.801 seconds. Please report platform to the developers at https://goo.gl/Nvioub

I am running home-assistant on a latest gen raspberry pi.

Thanks for your awesome work, people! I'll gladly provide more information.

hendrikb on 23 Nov 2016

@hendrikb looks like the edimax switch isn't caching it's state;

https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/switch/edimax.py#L81

That should be in an update function.

lwis on 23 Nov 2016

On the media_player.yamaha platform with HA 0.33.3 I get

16-11-25 01:05:32 homeassistant.helpers.entity: Updating state for media_player.yamaha_receiver took 0.413 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-25 01:06:04 homeassistant.helpers.entity: Updating state for media_player.yamaha_receiver_zone_2 took 0.993 seconds. Please report platform to the developers at https://goo.gl/Nvioub

pilot33 on 25 Nov 2016

After recent rewrite to async KNX switches take between 12 and 25 seconds to update it's values when switching lights off. Very strange thing is that switching lights on updates very fast both via hass and via physical buttons. The actual command gets executed momentarily i.e. turn on/off without delay.

resoai on 26 Nov 2016

@sdague See previous comment. I have looked at the Yamaha component but I cannot find any I/O inside properties. Could you verify that this is not happening? (Home Assistant sometimes warns about the wrong platform)

balloob on 26 Nov 2016

@hendrikb @lwis Edimax fix is here: #4584

balloob on 26 Nov 2016

🎉1

Hi guys,
I setup Google Calendar a few days ago, and today I got these messages:

16-11-30 02:06:04 homeassistant.helpers.entity: Updating state for calendar.facebook_events took 0.433 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-30 02:06:12 homeassistant.helpers.entity: Updating state for calendar.my_first_calendar took 0.833 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-11-30 02:06:17 homeassistant.helpers.entity: Updating state for calendar.work_calendar took 0.512 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Tommatheussen on 30 Nov 2016

I still have issues with Tellstick switches in the latest DEV:
Updating state for switch.outdoor_switch took 0.828 seconds. Please report platform to the developers at https://goo.gl/Nvioub

frelev on 1 Dec 2016

I have a Yamaha RX-V775
16-12-01 20:30:31 homeassistant.helpers.entity: Updating state for media_player.yamaha_receiver took 1.113 seconds. Please report platform to the developers at https://goo.gl/Nvioub

vrishabkakade on 2 Dec 2016

I'm using the Synology DSM Sensor:
16-12-04 14:09:17 homeassistant.helpers.entity: Updating state for sensor.memory_usage_real took 1.261 seconds. Please report platform to the developers at https://goo.gl/Nvioub

jschroeck on 4 Dec 2016

👍1

I've just seen this in the logs:
16-12-04 19:12:03 homeassistant.helpers.entity: Updating state for sensor.living_room_thermostat_target took 2.590 seconds. Please report platform to the developers at https://goo.gl/Nvioub

ghost on 4 Dec 2016

@bk86a what platform is it?

balloob on 4 Dec 2016

@balloob Raspberry Pi 2 Model B + raspbian 4.4.32-v7

ghost on 4 Dec 2016

Sorry, I meant the Home Assistant platform that created sensor.living_room_thermostat_target

balloob on 5 Dec 2016

Reporting as requested:

16-12-05 11:00:37 homeassistant.helpers.entity: Updating state for media_player.plex_web_chrome took 0.698 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-12-05 11:06:01 homeassistant.helpers.entity: Updating state for sensor.pws_wind_dir took 0.494 seconds. Please report platform to the developers at https://goo.gl/Nvioub

HA is running as a Docker container in a QNAP TS-253 Pro NAS (quad-core Celeron 2.0 Ghz CPU).

pedropombeiro on 5 Dec 2016

@balloob this was Nest with the developer account approach enforced by 0.34. With 0.33 and the username and password I've never seen an error message like this.

ghost on 5 Dec 2016

Hi, although #4584 went into home assistant 0.32.4, which I got running, my Edimax smart plug still complains, like mentioned above :(

16-12-05 17:11:01 homeassistant.helpers.entity: Updating state for switch.edimax_smart_plug took 0.756 seconds. Please report platform to the developers at https://goo.gl/Nvioub

hendrikb on 5 Dec 2016

@hendrikb Edimax fix did not go out until 0.34

balloob on 6 Dec 2016

As mentioned by @bk86a the recent change to nest has started this message to appear. When I have never seen it before.

Looks like /homeassistant/components/sensor/nest.py (line 165) NestTempSensor::unit_of_measurement() is reaching out to the nest device to get the unit of measurement.

brentahughes on 9 Dec 2016

@bah2830 @bk86a I've put up a fix for Nest at #4855
@PombeirP Plex fix in #4857

Both will go out in 0.34.5 👍

balloob on 12 Dec 2016

Thanks @balloob!

pedropombeiro on 12 Dec 2016

Noticed it for the Osram Lightify platform:

16-12-11 14:18:31 homeassistant.helpers.entity: Updating state for light.a60rgbw_01 took 0.547 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-12-11 18:53:31 homeassistant.helpers.entity: Updating state for light.a60rgbw_01 took 0.527 seconds. Please report platform to the developers at https://goo.gl/Nvioub
16-12-11 19:57:31 homeassistant.helpers.entity: Updating state for light.a60rgbw_01 took 0.542 seconds. Please report platform to the developers at https://goo.gl/Nvioub

etc.

DavidMStraub on 13 Dec 2016

Interesting. @DavidMStraub, how are you running Home Assistant? Using a RPi 3 with hassbian?

balloob on 13 Dec 2016

Almost, I use a RPi 3 with raspbian and hass installed using the all-in-one installer. Running 0.34.3.

DavidMStraub on 13 Dec 2016

Do you use verbose flag ?

balloob on 14 Dec 2016

My logs are still getting filled up with these warnings, including some that you have been discounted in the opening posts. I have listed platforms below:

All weather sensors are darksky
temp_update_timers are templates
switch.coffee_machine is orvibo
There is also a group showing up which is a view I use for showing some switches, scripts and binary sensors

Hass is running on a RPi2. The RPi is headless and runs Hass pretty much exclusively.

16-12-11 11:33:01 homeassistant.helpers.entity: Updating state for sensor.weather_daily_summary took 0.541 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-11 11:44:01 homeassistant.helpers.entity: Updating state for switch.coffee_machine took 0.539 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-11 12:22:01 homeassistant.helpers.entity: Updating state for switch.coffee_machine took 0.533 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-11 12:50:01 homeassistant.helpers.entity: Updating state for sensor.front_temp_update_timer took 0.535 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-11 15:12:01 homeassistant.helpers.entity: Updating state for switch.coffee_machine took 0.535 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-11 22:43:01 homeassistant.helpers.entity: Updating state for sensor.back_temp_update_timer took 0.563 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 00:23:01 homeassistant.helpers.entity: Updating state for sensor.back_temp_update_timer took 0.548 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 00:28:01 homeassistant.helpers.entity: Updating state for sensor.weather_daily_summary took 0.555 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 01:25:01 homeassistant.helpers.entity: Updating state for sensor.front_temp_update_timer took 0.548 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 02:48:01 homeassistant.helpers.entity: Updating state for sensor.back_temp_update_timer took 0.559 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 06:52:01 homeassistant.helpers.entity: Updating state for group.scripts_view took 0.526 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 07:10:01 homeassistant.helpers.entity: Updating state for group.scripts_view took 0.560 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 16:29:01 homeassistant.helpers.entity: Updating state for sensor.weather_daily_summary took 0.546 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 16:53:01 homeassistant.helpers.entity: Updating state for sensor.weather_daily_summary took 0.536 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 18:41:01 homeassistant.helpers.entity: Updating state for switch.coffee_machine took 0.532 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 19:26:01 homeassistant.helpers.entity: Updating state for sensor.front_temp_update_timer took 0.525 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 21:30:01 homeassistant.helpers.entity: Updating state for sensor.back_temp_update_timer took 0.558 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-12 23:58:01 homeassistant.helpers.entity: Updating state for sensor.weather_daily_summary took 0.539 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 03:09:01 homeassistant.helpers.entity: Updating state for group.scripts_view took 0.542 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 04:09:01 homeassistant.helpers.entity: Updating state for sensor.back_temp_update_timer took 0.525 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 05:29:01 homeassistant.helpers.entity: Updating state for sensor.back_temp_update_timer took 0.536 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 05:35:01 homeassistant.helpers.entity: Updating state for group.scripts_view took 0.535 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 10:41:01 homeassistant.helpers.entity: Updating state for sensor.front_temp_update_timer took 0.558 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 11:34:01 homeassistant.helpers.entity: Updating state for sensor.front_temp_update_timer took 0.544 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 12:27:01 homeassistant.helpers.entity: Updating state for sensor.front_temp_update_timer took 0.536 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 12:27:22 homeassistant.components.updater: Got unexpected response: None 16-12-13 13:07:01 homeassistant.helpers.entity: Updating state for sensor.back_temp_update_timer took 0.535 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 15:15:01 homeassistant.helpers.entity: Updating state for sensor.front_temp_update_timer took 0.533 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 15:19:01 homeassistant.helpers.entity: Updating state for sensor.back_temp_update_timer took 0.595 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 19:40:01 homeassistant.helpers.entity: Updating state for sensor.front_temp_update_timer took 0.554 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 20:32:01 homeassistant.helpers.entity: Updating state for sensor.weather_daily_summary took 0.546 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 20:56:01 homeassistant.helpers.entity: Updating state for sensor.weather_daily_summary took 0.525 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-13 22:29:01 homeassistant.helpers.entity: Updating state for switch.coffee_machine took 0.539 seconds. Please report platform to the developers at https://goo.gl/Nvioub

timstanley1985 on 15 Dec 2016

@timstanley1985 we have figured out the cause and it is caused by our loggers. It will be addressed by the next release.

balloob on 16 Dec 2016

tellstick selflearning-dimmer switches. Also they're not detected as dimmers for some reason =(

16-12-25 12:29:49 homeassistant.helpers.entity: Updating state for switch.stairs took 0.835 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-25 12:29:50 homeassistant.helpers.entity: Updating state for switch.twins took 0.835 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-26 08:54:28 homeassistant.helpers.entity: Updating state for switch.hallway took 0.876 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-26 08:54:29 homeassistant.helpers.entity: Updating state for switch.sofa took 0.845 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-26 08:54:31 homeassistant.helpers.entity: Updating state for switch.stairs took 0.846 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-26 08:54:33 homeassistant.helpers.entity: Updating state for switch.twins took 0.846 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-26 09:55:15 homeassistant.helpers.entity: Updating state for switch.hallway took 0.846 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-26 09:55:17 homeassistant.helpers.entity: Updating state for switch.sofa took 0.846 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-26 09:55:19 homeassistant.helpers.entity: Updating state for switch.stairs took 0.846 seconds. Please report platform to the developers at https://goo.gl/Nvioub 16-12-26 09:55:20 homeassistant.helpers.entity: Updating state for switch.twins took 0.847 seconds. Please report platform to the developers at https://goo.gl/Nvioub

mist0706 on 26 Dec 2016

Noticed this in my logs today:

Jan 02 12:57:01 raspberrypi hass[15288]: 17-01-02 12:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Updat
ing state for sensor.power_consumption_normal took 0.581 seconds. Please report platform to the developers at https:
//goo.gl/Nvioub

My guess it might be caused by DSMR sensor as implemented by @aequitas.

jmartens on 2 Jan 2017

@jmartens the DSMR implementation should not do any IO on state read. Maybe the culprit is the module import at the beginning of the function: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/sensor/dsmr.py#L154

Do you see this message often or only during loading of HA?

@balloob do you know if it is common for imports to cause this warning message? My guess is it should not matter I import in the state property as a similar import is already done during module load. But might be i'm wrong here?

aequitas on 2 Jan 2017

I saw this in the logs when HASS has been running for a few days w/o interruption, unfortunately I have just lost the log as a config check overwrites the log of the running instance. :-(

jmartens on 2 Jan 2017

@aequitas importing should not cause any slowness as it is already in the cache.

@jmartens are you running the latest version of Home Assistant?

balloob on 3 Jan 2017

Yes I am running 0.35.3.On Jan 3, 2017 8:22 AM, Paulus Schoutsen notifications@github.com wrote:@aequitas importing should not cause any slowness as it is already in the cache.
@jmartens are you running the latest version of Home Assistant?

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.

jmartens on 3 Jan 2017

I get this warning on the latest Home Assistant version, 0.36.0. It also occurred somewhat frequently with the prior version. Yamaha RX-A710, 1.114 seconds. Yamaha RX-A830, 0.566 seconds. I'm also seeing exceptions related to asyncio and the RXV package. I've attached a brief log listing...

requests.packages.urllib3.exceptions.ProtocolError: ('Connection aborted.', BadStatusLine("''",))

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 "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 387, in _update_entity_states
    yield from update_coro
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 216, in async_update_ha_state
    yield from self.hass.loop.run_in_executor(None, self.update)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/media_player/yamaha.py", line 131, in update
    current_source = self._receiver.input
  File "/home/homeassistant/.homeassistant/deps/rxv/rxv.py", line 231, in input
    response = self._request('GET', request_text)
  File "/home/homeassistant/.homeassistant/deps/rxv/rxv.py", line 129, in _request
    headers={"Content-Type": "text/xml"}
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/sessions.py", line 535, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/sessions.py", line 488, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/sessions.py", line 609, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/adapters.py", line 473, in send
    raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', BadStatusLine("''",))
17-01-16 02:51:57 homeassistant.helpers.entity: Updating state for media_player.bedroom_receiver_zone_2 took 1.114 seconds. Please report platform to the developers at https://goo.gl/Nvioub
17-01-16 09:13:42 homeassistant.helpers.entity: Updating state for media_player.family_room_receiver_zone_2 took 0.566 seconds. Please report platform to the developers at https://goo.gl/Nvioub

n0dyjeff on 16 Jan 2017

Thanks @n0dyjeff, I have a fix for it in #5387

balloob on 17 Jan 2017

Wow, that was fast! Thanks!

n0dyjeff on 17 Jan 2017

I've just seen this last night (running HA 36.1):

17-01-19 20:55:09 homeassistant.helpers.entity: Updating state for binary_sensor.fibaro_system_fgms001_motion_sensor_sensor_92_0 took 0.558 seconds. Please report platform to the developers at https://goo.gl/Nvioub

markcarline on 20 Jan 2017

TP-Link HS100

17-01-20 21:29:56 homeassistant.helpers.entity: Updating state for switch.nightstand took 0.499 seconds. Please report platform to the developers at https://goo.gl/Nvioub

stickystyle on 21 Jan 2017

@stickystyle will be fixed in 0.37: https://github.com/home-assistant/home-assistant/pull/5589 - thanks for reporting.

balloob on 27 Jan 2017

LG WebOS TV

17-01-29 12:31:33 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.living_room_tv took 1.483 seconds. Please report platform to the developers at https://goo.gl/Nvioub

vassilis-panos on 29 Jan 2017

LIFX lights Gen3

17-01-29 12:10:19 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for light.kitchen took 1.210 seconds. Please report platform to the developers at https://goo.gl/Nvioub

vassilis-panos on 29 Jan 2017

Yamaha RX-A3050 Amplifier media_player took took 0.620 seconds, full response below.

17-01-29 23:49:09 homeassistant.helpers.entity: Updating state for media_player.yamaha_amp took 0.620 seconds. Please report platform to the developers at https://goo.gl/Nvioub
17-01-29 23:49:11 rxv: Invalid XML returned for request <YAMAHA_AV cmd="GET"><Zone_4><Volume><Mute>GetParam</Mute></Volume></Zone_4></YAMAHA_AV>: b''
Traceback (most recent call last):
  File "/home/homeassistant/.homeassistant/deps/rxv/rxv.py", line 131, in _request
    response = ET.XML(res.content)  # releases connection to the pool
  File "/usr/lib/python3.4/xml/etree/ElementTree.py", line 1326, in XML
    return parser.close()
  File "<string>", line None
xml.etree.ElementTree.ParseError: no element found: line 1, column 0
17-01-29 23:49:11 homeassistant.components.media_player: Error while setting up platform yamaha
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 151, in _async_setup_platform
    entity_platform.add_entities, discovery_info
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/media_player/yamaha.py", line 89, in setup_platform
    YamahaDevice(name, receiver, source_ignore, source_names)])
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/media_player/yamaha.py", line 108, in __init__
    self.update()
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/media_player/yamaha.py", line 125, in update
    self._muted = self._receiver.mute
  File "/home/homeassistant/.homeassistant/deps/rxv/rxv.py", line 443, in mute
    response = self._request('GET', request_text)
  File "/home/homeassistant/.homeassistant/deps/rxv/rxv.py", line 131, in _request
    response = ET.XML(res.content)  # releases connection to the pool
  File "/usr/lib/python3.4/xml/etree/ElementTree.py", line 1326, in XML
    return parser.close()
  File "<string>", line None
xml.etree.ElementTree.ParseError: no element found: line 1, column 0
17-01-29 23:49:20 homeassistant.core: Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/sensor/synologydsm.py", line 112, in run_setup
    for volume in volumes:
TypeError: 'NoneType' object is not iterable
17-01-29 23:49:25 homeassistant.helpers.entity: Updating state for media_player.yamaha_amp_zone_3 took 0.417 seconds. Please report platform to the developers at https://goo.gl/Nvioub
17-01-29 23:49:55 homeassistant.helpers.entity: Updating state for media_player.yamaha_amp_zone_2 took 0.414 seconds. Please report platform to the developers at https://goo.gl/Nvioub

gebb79 on 29 Jan 2017

Component: Danfoss Z-Wave Living Connect 014G0013
Platform: Climate

17-01-31 09:18:13 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.antresola_thermostat_heating_1_2_1 took 0.514 seconds. Please report platform to the developers at https://goo.gl/Nvioub

bieniu on 31 Jan 2017

Component: fibaro_system_fgrm222_roller_shutter_controller_2_power_7_4
Platform: sensor

janv. 31 10:56:56 hass hass[23375]: WARNING:homeassistant.helpers.entity:Updating state for sensor.fibaro_system_fgrm222_roller_shutter_controller_2_power_7_4 took 1.090 seconds. Please report platform to the developers at https://goo.gl/Nvioub

ldvc on 31 Jan 2017

17-02-04 23:16:44 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.hsm100_general_3_2 took 0.642 seconds. Please report platform to the developers at https://goo.gl/Nvioub

http://www.expresscontrols.com/pdf/EZMotion+OwnerManual.pdf

eperdeme on 5 Feb 2017

17-02-12 19:08:31 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.living_room_apple_tv took 0.510 seconds. Please report platform to the developers at https://goo.gl/Nvioub

/cc @postlund

robbiet480 on 13 Feb 2017

17-02-13 20:42:15 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.fibaro_system_fgrm222_roller_shutter_controller_2_switch_4_0 took 0.458 seconds. Please report platform to the developers at https://goo.gl/Nvioub

misterbenj34 on 13 Feb 2017

@misterbenj34 what HA version are you on?

andrey-git on 13 Feb 2017

Happened across this one going through the source: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/media_player/cmus.py#L94

emlove on 15 Feb 2017

@armills can you submit a PR to just remove that call?

balloob on 15 Feb 2017

@andrey-git I've got the last one 0.38.3
It just appears once.

misterbenj34 on 16 Feb 2017

17-02-28 18:04:44 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.aeotec_zw100_multisensor_6_sensor_2_0 took 1.453 seconds. Please report platform to the developers at https://goo.gl/Nvioub

getsmokes on 28 Feb 2017

17-03-01 17:16:42 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.aeotec_dsc06106_smart_energy_switch_interval_9_2 took 0.405 seconds. Please report platform to the developers at https://goo.gl/Nvioub

EllieRagone on 1 Mar 2017

17-03-01 17:19:59 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.household_power_meter_interval_4_2_2 took 0.683 seconds. Please report platform to the developers at https://goo.gl/Nvioub

For what it's worth, there seems to be some major problem as well as the webpage just hangs and won't actually load, and now the log is filling up with 17-03-01 17:20:56 WARNING (MainThread) [asyncio] socket.send() raised exception. messages.

EllieRagone on 1 Mar 2017

Platform: Zwave Switch
Component: fibaro_system_fgwpef_wall_plug_gen5

Updating state for switch.fibaro_system_fgwpef_wall_plug_gen5_switch_4_0 took 0.770 seconds
First time seen in 0.39.2

wootapa on 2 Mar 2017

Platform: Z-Wave Aeotec
Component: aeotec_dsc24_smart_switch_2nd_edition

17-03-03 10:34:20 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.aeotec_dsc24_smart_switch_2nd_edition_current_2_20 took 0.755 seconds. Please report platform to the developers at https://goo.gl/Nvioub

decool on 3 Mar 2017

Platform: HA 0.38.1, RPI2 (not sure about model). Raspbian Jessie Lite.
Controller: Aeon Z-Stick (Gen 5) USB (also a Telldus Duo but it controls other sensors/switches)
Sensor: Fibaro Z-wave Wall plug (Gen 5)

groups.yaml: ... garage: name: 'Garage' view: yes entities: - switch.fibaro_system_fgwpef_wall_plug_gen5_switch_2_0 ...
17-03-03 22:45:29 WARNING (Thread-4) [homeassistant.components.zwave] zwave not ready after 30 seconds, continuing anyway 17-03-03 22:45:32 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.fibaro_system_fgwpef_wall_plug_gen5_switch_2_0 took 1.061 seconds. Please report platform to the developers at https://goo.gl/Nvioub

callebokedal on 4 Mar 2017

Z-Wave should be fixed in the upcoming 0.40 release.

balloob on 4 Mar 2017

👍1

platform: samsungtv
host: 192.168.0.109
mac: f4:7b:5e:70:99:02

Samsung 55" F6300

17-03-07 12:59:49 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.samsungtv
17-03-07 12:59:49 INFO (Thread-6) [homeassistant.components.media_player.samsungtv] Samsung TV 192.168.0.109:55000 added as 'Samsung TV Remote'
17-03-07 14:28:14 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.samsungtv
17-03-07 14:28:14 INFO (Thread-10) [homeassistant.components.media_player.samsungtv] Ignoring duplicate Samsung TV 192.168.0.109:55000
17-03-07 15:51:51 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.samsung_tv_remote took 0.665 seconds. Please report platform to the developers at https://g
oo.gl/Nvioub

And about 3000 of these messages since restart

17-03-07 22:20:14 WARNING (MainThread) [homeassistant.components.media_player] Updating samsungtv media_player took longer than the scheduled update interval 0:00:10
17-03-07 22:20:25 WARNING (MainThread) [homeassistant.components.media_player] Updating samsungtv media_player took longer than the scheduled update interval 0:00:10

terrycarlin on 8 Mar 2017

😕1

Hi, have just received warning with Yahoo finance platform

timstanley1985 on 12 Mar 2017

17-03-12 17:31:52 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.yr_symbol took 0.512 seconds. Please report platform to the developers at https://goo.gl/Nvioub

not sure exactly what is meant with 'platform' , so here's both:

# Weather Prediction
sensor weather:
  - platform: yr
    monitored_conditions:
      - temperature
      - symbol
      - precipitation

and the 'platform' hass is running on is a xiaomi mini running LEDE 17.01.01,
iow. slowness could just be due to the 'platform' :)

fundef1 on 12 Mar 2017

Error message: _17-03-27 09:44:01 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.atv1 took 1.061 seconds._

Model: _Apple TV gen3_
Connectivity: _Wifi 2,4, about 5 meters, thru 1 wall._

ludeeus on 27 Mar 2017

17-03-31

16:09:38 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.light_office_on_last_30_days took 3.393 seconds. Please report platform to the developers at

I am using the ststistic sensors which seems to take information from mysql database installed also on the pi .. It takes ages to get information for this

thundergreen on 31 Mar 2017

Please post the integration that caused the warning. Just the entity id is not going to help us.

To keep this thread clean, I will remove messages that do not mention the integration.

balloob on 9 May 2017

2017-06-08 02:27:37 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.roku_5s4640042419 took 0.534 seconds.

Model: Roku stick (3600R)
Connection: Wifi (Ubiquity UniFi) appx 20 feet from AP through no walls)

justinglow on 8 Jun 2017

@justinglow fixed in 0.46.1

balloob on 9 Jun 2017

👍1

2017-06-19 01:15:59 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for lock.front_door took 0.934 seconds.

Model: Sesame Lock
Connection: Wifi + bluetooth no walls. approx. 12 feet

aetaric on 19 Jun 2017

CC @trisk ^^ see last comment. Looks like Sesame is doing I/O inside properties. Can you take a look?

balloob on 20 Jun 2017

HaveIBeenPwned sensor:

2017-07-04 21:49:21 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.breaches_REDACTEDgmailcom took 0.474 seconds.

fanaticDavid on 5 Jul 2017

2017-07-24 23:03:28 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for light.porch_light took 0.497 seconds. Please report platform to the developers at https://goo.gl/Nvioub

For a TP-Link LB100 wifi bulb.

patosullivan on 25 Jul 2017

Rachio Irrigation Controller component.
2017-08-10 16:03:01 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.backyard_2 took 1.494 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-08-10 17:20:58 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.courtyard took 1.511 seconds. Please report platform to the developers at https://goo.gl/Nvioub

JSCSJSCS on 11 Aug 2017

This is the problem:
https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/switch/rachio.py#L202
Just remove that line.

MartinHjelmare on 11 Aug 2017

Thank you Martin. As a Hass.io user, I don't think I have access to the directory where components are kept to make the change even through ssh and putty.

JSCSJSCS on 11 Aug 2017

I can make a PR, but I can't test it. But should be ok anyway I think.

MartinHjelmare on 11 Aug 2017

Arlo just started this symptom in 0.55.

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for xxxx_cam took 19.394 seconds. Please report platform to the developers at https://goo.gl/Nvioub

edif30 on 8 Oct 2017

@edif30 thanks for the report. Will be fixed in 0.55.1: https://github.com/home-assistant/home-assistant/pull/9738

balloob on 8 Oct 2017

When using the DSMR plugin, the logs stated:
WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.power_consumption took 3.108 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Atrejoe on 8 Oct 2017

Running Home Assistant 0.55.0, the haveibeenpwned platform gives me this:

2017-10-14 10:35:40 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.breaches_[redacted]gmailcom took 0.409 seconds. Please report platform to the developers at https://goo.gl/Nvioub

fanaticDavid on 14 Oct 2017

2017-10-28 22:54:52 WARNING (MainThread) [homeassistant.components.sensor] Updating miflora sensor took longer than the scheduled update interval 0:00:30

moskovskiy82 on 28 Oct 2017

Running Hassbian 1.31, HA 0.56.2, with the Toon component.

i get errors like:

2017-10-31 08:36:51 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.eet_hoek took 4.553 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-10-31 08:36:51 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:37:51 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:38:52 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:39:53 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.bank_hoek took 1.356 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-10-31 08:41:58 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:43:03 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:44:04 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.tv_hoek took 5.566 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-10-31 08:44:04 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:45:05 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:46:05 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:47:06 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:49:16 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:50:17 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:51:17 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:53:35 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:53:35 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.gas_today is taking over 10 seconds
2017-10-31 08:54:19 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:55:19 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:57:30 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.tv_hoek_today_energy is taking over 10 seconds
2017-10-31 08:58:31 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 08:59:31 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:00:32 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:01:32 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:02:32 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:03:33 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:07:15 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:08:45 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:09:46 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:10:53 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-10-31 09:10:53 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.eet_hoek_current_power is taking over 10 seconds

I guess it's because i have three zwave plugs connected to toon that don't measure power.

kurniawan77 on 31 Oct 2017

The problem is the "Updating state" ones. So bank_hoek, tv_hoek. Those are not toon. What are they?

balloob on 1 Nov 2017

Actually those are zwave switches which are connected to Toon. They are working perfect on the Toon, the only thing is that these aren't fibaro zwave switches and they don't measure power.

I have opened an issue a while ago here

kurniawan77 on 1 Nov 2017

KNX does no longer do IO inside properties...

Julius2342 on 4 Nov 2017

File sensors

2017-11-17 14:42:04 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.unni took 0.533 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-11-17 15:16:08 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.livingroom_temperature took 0.525 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2

Oreron on 17 Nov 2017

@Oreron The file sensor code looks good, I think. Could you show us the config you are using for these sensors?

tinloaf on 18 Nov 2017

platform: file
name: unni
file_path: /home/pi/filesensors/proximity_unni.json
value_template: '{{ value_json.unni }}'
platform: file
name: livingroom_temperature
file_path: /home/pi/filesensors/moteino_livingroom.json
value_template: '{{ value_json.temperature }}'
unit_of_measurement: "°C"

Oreron on 18 Nov 2017

Should I report this here? 0.58 and Arlo Component

Updating state for camera.baksidan (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 1.614 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Setup of camera is taking over 10 seconds.

Setup of platform arlo is taking over 10 seconds.

And some of those
Update of camera.vardagsrummet is taking over 10 seconds

Nicxe on 18 Nov 2017

👍1

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for weather.volkel took 0.429 seconds. Please report platform to the developers at https://goo.gl/Nvioub

configuration.yaml:

weather:
  - platform: buienradar
    name: 'volkel'
    forecast: True

kvandt on 20 Nov 2017

Running HA 0.57.3.
Please note that I'm having other issues with my HA box so it may be due to that - After a while the whole box hangs or deadlocks.

2017-11-20 20:24:40 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sun.sun took 0.783 seconds. Please report platform to the developers at https://goo.gl/Nvioub

zyberzero on 20 Nov 2017

@trisk, @balloob. The pysesame library which handles the Sesame lock will update and cache the state of the lock the first time any property on the object is accessed. As long as update_state(...) is called on the object before getting any of the properties it should be fine. Is there a mechanism to perform "async loading" for an entity like this so the state isn't used until after this first initialization?

Alternatively, you can just set the use_cached_state field to True to force it to return whatever defaults it has until it can be updated independently by the update loop.

veleek on 3 Dec 2017

@veleek there is absolutely 0 I/O allowed inside properties. Cache it all inside instance variables inside the update method.

balloob on 3 Dec 2017

@balloob I'm not the pysesame dev or anything, I just took a quick look into it to help root cause the issue to help with the fix. I can take a look at making the change myself, but I'm gonna need a few additional pointers.

Is it reasonable to do async I/O during the initial setup? Could I just call update_state(...) when the lock is first initialized, or should I just make the change to force the "cached" lookup on startup and then let it refresh normally?

If neither option works, then the changes will need to be pushed in the pysesame library.

veleek on 4 Dec 2017

Pass True as a second argument to add_devices and Home Assistant will call update before the entity is added. Then just update the update method to set variables as instance variables.

Awesome if you want to take this one on 👍

balloob on 4 Dec 2017

@veleek Thanks for reminding me. pysesame defaults to synchronous I/O when Sesame attributes are accessed, but I added the use_cached_state attribute to change this behaviour after creating the object (could also consider adding a parameter to Sesame.__init__ so there is no window in which used_cached_state is False, but that's not as convenient when using Sesame.get_sesames). I am also the author of pysesame, but haven't gotten around to updating the sesame platform yet because I don't have a system set up for testing HA development builds anymore. It should work the way you suggest.

trisk on 4 Dec 2017

2017-12-09 22:35:11 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for light.lightstrip_wardrobe (<class 'homeassistant.components.light.hue.HueLight'>) took 0.404 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Running Home Assistant 0.59.2

fanaticDavid on 11 Dec 2017

2017-12-15 22:26:00 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.groventre (<class 'homeassistant.components.binary_sensor.verisure.VerisureDoorWindowSensor'>) took 0.498 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-12-15 22:28:10 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.altandorr (<class 'homeassistant.components.binary_sensor.verisure.VerisureDoorWindowSensor'>) took 0.727 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-12-15 22:28:12 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.kaffebryggare (<class 'homeassistant.components.switch.verisure.VerisureSmartplug'>) took 0.465 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-12-15 22:28:18 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.overvaning_humidity (<class 'homeassistant.components.sensor.verisure.VerisureHygrometer'>) took 0.971 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-12-15 22:28:41 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.groventre_humidity (<class 'homeassistant.components.sensor.verisure.VerisureHygrometer'>) took 0.432 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2017-12-15 22:33:49 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.groventre_temperature (<class 'homeassistant.components.sensor.verisure.VerisureThermometer'>) took 0.540 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Running Home Assistant 0.59.2

PetterSjo on 15 Dec 2017

👍1

Sonos again...

Updating state for media_player.living_room (<class 'homeassistant.components.media_player.sonos.SonosDevice'>) took 1.077 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Running 0.60.0 via Hassbian

schmittx on 27 Dec 2017

HASS 0.60.1
Python 3.6.3

Sonos...

Sat Jan 06 2018 23:20:22 GMT-0500 (EST)

Updating state for media_player.portable () took 1.090 seconds. Please report platform to the developers at https://goo.gl/Nvioub

net4unner on 7 Jan 2018

Sonos...

Hass: 0.60.0
Updating state for media_player.kitchen () took 1.082 seconds.

mellowmerlin on 11 Jan 2018

Agreed on that Sonos problem is back. Just updated to 0.60.1

Updating state for media_player.sonos () took 0.453 seconds.

isabellaalstrom on 13 Jan 2018

Same Sonos issue here as well, 0.60.1.

Updating state for media_player.vardagsrum () took 3.609 seconds

code-to-joy on 14 Jan 2018

Sonos, 0.60.1, just after reboot.

Updating state for media_player.oficina (<class 'homeassistant.components.media_player.sonos.SonosDevice'>) took 0.445 seconds. Please report platform to the developers at https://goo.gl/Nvioub

xtianpaiva on 15 Jan 2018

Cast device on 0.61 (google home device).

2018-01-16 07:33:38 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.kitchen_speaker (<class 'homeassistant.components.media_player.cast.CastDevice'>) took 0.467 seconds. Please report platform to the developers at https://goo.gl/Nvioub

olskar on 16 Jan 2018

Wunderground on 0.61 (after restart)

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.pws_uv (<class 'homeassistant.components.sensor.wunderground.WUndergroundSensor'>) took 0.456 seconds. Please report platform to the developers at https://goo.gl/Nvioub

qrioniclabs on 17 Jan 2018

Log Details (WARNING)
Wed Jan 17 2018 12:02:24 GMT-0500 (Eastern Standard Time)

Updating state for camera.arlo3 (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 24.267 seconds. Please report platform to the developers at https://goo.gl/Nvioub

arsaboo on 17 Jan 2018

👍1

0.62
Updating state for sensor.moc_czynna_l3 (<class 'homeassistant.components.sensor.mqtt.MqttSensor'>) took 0.651 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Strange, because it's sensor purely from MQTT (mosquitto), with multiple JSON values (and it's the only one with the warning, once).

andriej on 29 Jan 2018

0.62.1, talking to Telldus Z-wave:

2018-02-03 00:06:56 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.gastrum_fonster (<class 'homeassistant.components.switch.tellduslive.TelldusLiveSwitch'>) took 4.267 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-02-03 00:06:56 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

joltcan on 3 Feb 2018

Reporting as requested.
Hass.io: 0.63.1
Australian Bureau of Meteorology (BOM) Weather Sensors in HA.

Updating state for sensor.bom_ap_relative_humidity () took 0.530 seconds. Please report platform to the developers at https://goo.gl/Nvioub
6:49 PM helpers/entity.py (WARNING)

Updating state for sensor.bom_ap_wind_direction () took 0.539 seconds. Please report platform to the developers at https://goo.gl/Nvioub
5:49 PM helpers/entity.py (WARNING)

Pre10der on 14 Feb 2018

Reporting as requested.
Hass.io: 0.63.1
2018-02-21 07:24:01 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.bathroom () took 1.147 seconds. Please report platform to the developers at https://goo.gl/Nvioub

robertw on 21 Feb 2018

Hass.io : 0.63.3

Updating state for sensor.yweather_temperature () took 0.525 seconds. Please report platform to the developers at https://goo.gl/Nvioub

07:03 helpers/entity.py (WARNING)

memodeladej on 22 Feb 2018

Sonos is hopefully fixed in 0.64, please report again if you still see this issue.

amelchio on 1 Mar 2018

I received the following warnings in the log for my Arlo Pro cameras:
Sat Mar 03 2018 11:15:15 GMT+0000 (GMT Standard Time)
Updating arlo alarm_control_panel took longer than the scheduled update interval 0:00:30

Sat Mar 03 2018 11:14:51 GMT+0000 (GMT Standard Time)
Update of camera.garage is taking over 10 seconds

Sat Mar 03 2018 11:13:11 GMT+0000 (GMT Standard Time)
Updating state for camera.garage () took 76.441 seconds.

Hass.io: 0.64.3

mooshpot on 3 Mar 2018

👍1

WARNING (MainThread) [homeassistant.components.light] Updating hue light took longer than the scheduled update interval 0:00:30

Updating state for light.dining_backlight () took 0.508 seconds. Please report platform to the developers at https://goo.gl/Nvioub

HassIO 0.65.0

zepixir on 11 Mar 2018

Log Details (WARNING)
Mon Mar 19 2018 09:41:41 GMT+0100 (CET)

Updating state for light.custom_group_for_lights () took 0.452 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Mariusthvdb on 19 Mar 2018

Continuously receiving warnings for Nest:

8-03-20 13:47:04 WARNING (MainThread) [homeassistant.components.climate] Updating nest climate took longer than the scheduled update interval 0:01:00
2018-03-20 13:47:19 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating nest binary_sensor took longer than the scheduled update interval 0:00:30
2018-03-20 13:47:28 WARNING (MainThread) [homeassistant.components.sensor] Updating nest sensor took longer than the scheduled update interval 0:00:30
2018-03-20 13:47:50 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating nest binary_sensor took longer than the scheduled update interval 0:00:30
2018-03-20 13:47:59 WARNING (MainThread) [homeassistant.components.sensor] Updating nest sensor took longer than the scheduled update interval 0:00:30

HA 0.66.0dev0

maxclaey on 20 Mar 2018

Move from #13437.

-03-24 14:11:53 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.allergy_index_forecasted_average (<class 'homeassistant.components.sensor.pollen.AllergyAverageSensor'>) took 0.544 seconds. Please report platform to the developers at https://goo.gl/Nvioub

fabaff on 26 Mar 2018

homeassistant.components.media_player.plex on a Nvidia Shield TV Pro (2017)

2018-04-05 20:47:20 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.shield_android_tv (<class 'homeassistant.components.media_player.plex.PlexClient'>) took 4.056 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-04-05 20:47:21 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1522954040.9619803, level=WARNING, message=Updating state for media_player.shield_android_tv (<class 'homeassistant.components.media_player.plex.PlexClient'>) took 4.056 seconds. Please report platform to the developers at https://goo.gl/Nvioub, exception=, source=helpers/entity.py>

martinfrancois on 5 Apr 2018

Apr 13 11:34:20 nuc hass[22184]: WARNING:homeassistant.helpers.entity:Updating state for switch.NAME ()
took 0.851 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Product: https://www.etekcity.com/product/100276

IsaacG on 13 Apr 2018

@IsaacG fixed in https://github.com/home-assistant/home-assistant/pull/13862

balloob on 14 Apr 2018

Log Details (WARNING)

Fri Apr 20 2018 05:12:04 GMT+0100 (GMT Daylight Time)

Updating state for switch.hdmi_0 () took 0.570 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Product: HDMI-CEC on RPi3

Spankythemusical on 20 Apr 2018

Log Details (WARNING)

Tue Apr 24 2018 19:09:01 GMT+0200 (CEST)

Updating state for light.couch (<class 'homeassistant.components.light.lifx.LIFXColor'>) took 0.550 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Product: LIFX A19
RPI3 running Hassbian and HASS 0.67.1

meetyourlaser on 24 Apr 2018

Component: binary_sensor
Platform: linode
Time to update (average of three): +- 0.900 seconds
Additional Information: https://github.com/home-assistant/home-assistant/issues/15007

shark711 on 17 Jun 2018

Log Details (WARNING)
Sat Jun 23 2018 18:20:58 GMT+1000 (Australian Eastern Standard Time)

Updating state for camera.arlo1 () took 50.624 seconds. Please report platform to the developers at https://goo.gl/Nvioub

jezzamine on 23 Jun 2018

👍1

Ver 0.72

2018-06-25 21:46:52 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform arlo is taking over 10 seconds.
2018-06-25 21:46:52 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Setup of platform arlo is taking over 10 seconds.
2018-06-25 21:48:20 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.tv_room (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 77.571 seconds. Pleas
e report platform to the developers at https://goo.gl/Nvioub
2018-06-25 21:48:20 WARNING (MainThread) [homeassistant.components.camera] Setup of platform ffmpeg is taking over 10 seconds.
2018-06-25 21:48:20 WARNING (MainThread) [homeassistant.components.camera] Setup of platform arlo is taking over 10 seconds.

amritgary on 26 Jun 2018

👍1

Reporting as requested, HassIO 0.72.1 on Pi2

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.ups_battery_charge (<class 'homeassistant.components.sensor.nut.NUTSensor'>) took 0.534 seconds. Please report platform to the developers at https://goo.gl/Nvioub

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.ups_battery_runtime (<class 'homeassistant.components.sensor.nut.NUTSensor'>) took 0.536 seconds. Please report platform to the developers at https://goo.gl/Nvioub

DoctorOctagonapus on 3 Jul 2018

Hey, some more appeared today. Same system.

Updating state for sensor.pihole_ads_percentage_blocked_today (<class 'homeassistant.components.sensor.pi_hole.PiHoleSensor'>) took 0.546 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Updating state for sensor.pihole_dns_queries_forwarded (<class 'homeassistant.components.sensor.pi_hole.PiHoleSensor'>) took 0.531 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Updating state for sensor.pihole_dns_unique_domains (<class 'homeassistant.components.sensor.pi_hole.PiHoleSensor'>) took 0.531 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Updating state for sensor.pihole_dns_queries_cached (<class 'homeassistant.components.sensor.pi_hole.PiHoleSensor'>) took 0.530 seconds. Please report platform to the developers at https://goo.gl/Nvioub

DoctorOctagonapus on 5 Jul 2018

Got the following for Arlo:
Updating state for camera.back_gate () took 2.636 seconds. Please report platform to the developers at https://goo.gl/Nvioub

SP410 on 7 Jul 2018

Per log request,

Updating state for light.family_room_light () took 0.607 seconds. Please report platform to the developers at https://goo.gl/Nvioub

BTLOPER on 9 Jul 2018

👍1

Updating state for camera.baksidan () took 25.984 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Nicxe on 12 Jul 2018

ARLO Pro System (1 base unit, 4 Pro Cameras and 1 Pro 2 camera)

Updating state for camera.roof () took 34.044 seconds.

mcginnie on 16 Jul 2018

Camera.Arlo

Updating state for camera.back_garden () took 1.812 seconds.

Pow377 on 20 Jul 2018

HassOS (supervisor 121)
Home Assistant 0.74.1

media_player.spotify

2018-07-25 21:57:47 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.spotify (<class 'homeassistant.components.media_player.spotify.SpotifyMediaPlayer'>) took 1.075 seconds.

ludeeus on 26 Jul 2018

Using UniFi UVC-G3 video cameras.

2018-07-28 20:35:39 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.hallway () took 0.424 seconds.

unixben on 28 Jul 2018

HassOS (supervisor 123)
Home Assistant 0.75.2

Updating state for group.group_system_stats () took 0.561 seconds.

Pre10der on 7 Aug 2018

HassOS 1.9 | Version| 125
Home Assistant 0.75.3

Updating state for camera.driveway () took 2.751 seconds.

GrandNewbien on 14 Aug 2018

Home Assistant 0.75.3

2018-08-15 11:30:28 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.back_yard (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 1.802 seconds. Please report platform to the developers at https://goo.gl/Nvioub

frekel on 15 Aug 2018

👍1

System | HassOS 1.9
Deployment | production
HASSIO Supervisor: 127
HA: 0.76.2

Updating state for weather.my_ecobee (<class 'homeassistant.components.weather.ecobee.EcobeeWeather'>) took 0.447 seconds. Please report platform to the developers at https://goo.gl/Nvioub

jamieboy05 on 24 Aug 2018

System | HassOS 1.9
Deployment | production
HASSIO Supervisor: 127
HA: 0.76.2

Updating myq cover took longer than the scheduled update interval 0:00:15

jamieboy05 on 24 Aug 2018

Mon Aug 27 2018 00:30:01 GMT+0200 (Central European Summer Time)
Updating state for light.level_5 () took 0.950 seconds. Please report platform to the developers at https://goo.gl/Nvioub
Raspberry pi 3 b => raspbian + home assistant
Linux raspberrypi 4.14.52-v7+ #1123 SMP Wed Jun 27 17:35:49 BST 2018 armv7l

Good luck!

remcoongit on 27 Aug 2018

Ver 0.76.2
Updating state for camera.side_door_cam () took 26.551 seconds. Please report platform to the developers at https://goo.gl/Nvioub

haruny on 30 Aug 2018

👍1

2018-09-03 17:42:53 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.babymonitor (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 16.011 seconds. Please report platform to the developers at https://goo.gl/Nvioub

jurgenweber on 3 Sep 2018

Reporting as requested. This is for Google Home being used as a media player:

Tue Sep 04 2018 11:45:26 GMT-0400 (Eastern Daylight Time)

Updating state for media_player.family_room_speaker (<class 'homeassistant.components.media_player.cast.CastDevice'>) took 0.475 seconds.

grantalewis on 4 Sep 2018

2018-09-07 23:24:22 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.template_weather_br_forecast_4_days_ahead (<class 'homeassistant.components.sensor.template.SensorTemplate'>) took 0.445 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Component: buienradar
Time zone: CET
HASSIO
0.77.3

farstreet on 7 Sep 2018

Reporting as requested. pihole component on hassbian 0.77.3

> Log Details (WARNING)
> Mon Sep 10 2018 12:03:40 GMT+0200 (Midden-Europese zomertijd)
> 
> Updating state for sensor.pihole_ads_blocked_today (<class 'homeassistant.components.sensor.pi_hole.PiHoleSensor'>) took 0.532 seconds. Please report platform to the developers at https://goo.gl/Nvioub

gastonbe on 10 Sep 2018

reporting as requested.

Xiaomi temperature and humidity sensor

platform: mitemp_bt
mac: '4C:xx:xx:xx:xx:xx'
name: room
force_update: false
median: 1
timeout: 60
retries: 3
monitored_conditions:

temperature
//# - humidity
//# - battery

platform: mitemp_bt
mac: '4C:xx:xx:xx:xx:xx'
name: room2
force_update: false
median: 1
timeout: 60
retries: 3
monitored_conditions:
//# - temperature

humidity
//# - battery

I am new here so I cannot be sure, but this should be the source:
https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/sensor/mitemp_bt.py

and there is a log:
2018-09-12 20:14:43 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30 2018-09-12 20:15:14 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30 2018-09-12 20:15:45 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30 2018-09-12 20:16:14 WARNING (SyncWorker_14) [homeassistant.components.sensor.mitemp_bt] Polling error 2018-09-12 20:16:15 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30 2018-09-12 20:16:24 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.obyvaci_pokoj_temperature is taking over 10 seconds 2018-09-12 20:16:46 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30 2018-09-12 20:17:17 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30

CZBios on 12 Sep 2018

Updating state for binary_sensor.verandadr (<class 'homeassistant.components.binary_sensor.verisure.VerisureDoorWindowSensor'>) took 0.606 seconds. Please report platform to the developers at https://goo.gl/Nvioub

haabe on 16 Sep 2018

Not sure if custom components should be listed here too, but it's not specifically told to not include them,

So reporting as requested:
Updating state for sensor.radarr_upcoming_media (py 'custom_components.sensor.radarr_upcoming_media.Radarr_UpcomingSensor'>) took 11.555 seconds. Please report platform to the developers at https://goo.gl/Nvioub

This is the custom component https://github.com/custom-components/sensor.radarr_upcoming_media

fortepc on 18 Sep 2018

Updating state for media_player.living_room_xbox_one () took 0.849 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Newlance on 19 Sep 2018

Version 0.78.3
AIO installer

 Sun Sep 23 2018 16:30:57 GMT+0200 (centraleuropeisk sommartid)
Updating state for camera.entre (<class 'homeassistant.components.camera.uvc.UnifiVideoCamera'>) took 1.216 seconds. Please report platform to the developers at https://goo.gl/Nvioub

kernehed on 23 Sep 2018

Updating state for sensor.bom_hobart_wind_direction () took 0.532 seconds. Please report platform to the developers at https://goo.gl/Nvioub

tomlut on 24 Sep 2018

Updating state for sensor.memory_use_percent () took 0.526 seconds. Please report platform to the developers at https://goo.gl/Nvioub

tomlut on 24 Sep 2018

Updating state for remote.cinema_lights () took 0.532 seconds. Please report platform to the developers at https://goo.gl/Nvioub

tomlut on 25 Sep 2018

Updating state for sensor.ipad_battery_level () took 0.533 seconds. Please report platform to the developers at https://goo.gl/Nvioub

tomlut on 25 Sep 2018

) took 0.423 seconds

chris195612 on 27 Sep 2018

2018-09-27 16:36:39 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for remote.xiaomi_remote () took 0.568 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Anonym-tsk on 27 Sep 2018

Updating state for sensor.nextsunrise () took 0.548 seconds. Please report platform to the developers at https://goo.gl/Nvioub

tomlut on 30 Sep 2018

Updating state for media_player.cinema_kodi () took 0.532 seconds. Please report platform to the developers at https://goo.gl/Nvioub

tomlut on 1 Oct 2018

class 'homeassistant.components.switch.tellduslive.TelldusLiveSwitch'>) took 4.191 seconds.

swetoast on 2 Oct 2018

Updating state for camera.living_room () took 2.787 seconds. Please report platform to the developers at https://goo.gl/Nvioub

ngknick on 2 Oct 2018

👍1

Version 0.79.0
AIO installer

Updating state for sensor.luftdaten_pm10 (<class 'homeassistant.components.sensor.luftdaten.LuftdatenSensor'>) took 0.498 seconds.

kernehed on 3 Oct 2018

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for X () took 0.438 seconds. Please report platform to the developers at https://goo.gl/Nvioub

tomeeka on 6 Oct 2018

Version 0.79.3

Update of alarm_control_panel.grand_ohio is taking over 10 seconds 4:02 PM util/async_.py (WARNING) Updating state for camera.living_room (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 2.691 seconds. Please report platform to the developers at https://goo.gl/Nvioub 4:00 PM helpers/entity.py (WARNING)

gnomesoup on 6 Oct 2018

👍2

0.79.3

Thu Oct 11 2018 06:30:03 GMT-0300 (hora estándar de Argentina)

Updating state for weather.openweathermap () took 0.408 seconds. Please report platform to the developers at https://goo.gl/Nvioub

pablolassalle on 11 Oct 2018

0.79.3

2018-10-12 14:32:15 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.kok () took 7.387 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-10-12 14:32:22 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.vardagsrum () took 6.998 seconds. Please report platform to the developers at https://goo.gl/Nvioub

My Arlo Alarm Panel has the state: unknown

skaker1 on 12 Oct 2018

👍1

0.80.0

018-10-13 10:51:31 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.arlo1 () took 11.035 seconds. Please report platform to the developers at https://goo.gl/Nvioub

2018-10-13 10:51:41 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.arlo3 () took 9.406 seconds. Please report platform to the developers at https://goo.gl/Nvioub

2018-10-13 10:51:50 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.arlo2 () took 9.454 seconds. Please report platform to the developers at https://goo.gl/Nvioub

(Monitored conditions signal_strength and battery_level state: unknown)

jezzamine on 13 Oct 2018

👍1

Reporting as requested:

Component: Arlo
Platform: Camera
Log Entry:
2018-10-13 14:32:51 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.nursery (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 11.901 seconds. Please report platform to the developers at https://goo.gl/Nvioub

TJohnson93 on 13 Oct 2018

👍1

Version: 0.80.1
Component: Arlo
Platform: Camera
Log Entries:
2018-10-15 13:21:31 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.3 () took 6.642 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-10-15 13:21:38 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.1 () took 7.073 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-10-15 13:22:45 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.2 () took 67.641 seconds. Please report platform to the developers at https://goo.gl/Nvioub

aneisch on 15 Oct 2018

👍1

Version: 0.80.1
Component: Arlo
Platform: Camera

I get Updating state for camera.vardagsrum (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 0.650 seconds (average).

I also get "Timer got out of sync. Resetting" every minute when arlo hub is trying to update:

2018-10-16 11:36:40 INFO (SyncWorker_11) [homeassistant.components.arlo] Updating Arlo Hub component
2018-10-16 11:36:59 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

I think that the connection to Arlo might be broken and this is causing these errors

matteskonto on 16 Oct 2018

Came here to report Arlo, was not disappointed.

hatesyourface on 16 Oct 2018

👍2

Updating state for switch.spuehlmaschine (<class 'homeassistant.components.switch.wemo.WemoSwitch'>) took 0.528 seconds. Please report platform to the developers at https://goo.gl/Nvioub

pattyland on 18 Oct 2018

Platform

media_player

Device

lg_netcast

Full warning

2018-10-19 18:25:40 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.lg_tv_remote (<class 'homeassistant.components.media_player.lg_netcast.LgTVDevice'>) took 0.647 seconds. Please report platform to the developers at https://goo.gl/Nvioub

timmo001 on 19 Oct 2018

Platform/component: light/yeelight

Updating state for light.bulb_salon_1 (<class 'homeassistant.components.light.yeelight.YeelightLight'>) took 1.381 seconds.

bieniu on 21 Oct 2018

2018-10-29 20:11:01 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.house (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 1.922 seconds. Please report platform to the developers at https://goo.gl/Nvioub

MatGriffin on 29 Oct 2018

2018-10-30 07:49:34 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.uvc_g3 () took 1.146 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Pocke01 on 30 Oct 2018

0.81.1
Tue Oct 30 2018 13:46:17 GMT+0100 (centraleuropeisk normaltid)

Updating state for camera.vardagsrum () took 1.995 seconds. Please report platform to the developers at https://goo.gl/Nvioub

skaker1 on 30 Oct 2018

0.81.4:
2018-11-03 16:06:45 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.broadlink_switch () took 0.413 seconds. Please report platform to the developers at https://goo.gl/Nvioub

jariha on 4 Nov 2018

0.81.6

Sun Nov 04 2018 15:37:53 GMT+0100 (centraleuropeisk normaltid)

Updating state for camera.kok () took 12.886 seconds. Please report platform to the developers at https://goo.gl/Nvioub

skaker1 on 4 Nov 2018

Using https://www.home-assistant.io/components/sensor.dsmr/
On (old) raspberry pi 1b with smart meter attached to serial uart port.
During restart of HomeAssistant.
Nov 05 21:11:18 raspberrypi hass[509]: 2018-11-05 21:11:18 WARNING (MainThread) homeassistant.helpers.entity] Updating state for sensor.power_tariff (<class 'homeassistant.components.sensor.dsmr.DSMREntity'>) took 0.537 seconds. Please report platform to the developers at https://goo.gl/Nvioub

JeroenvO on 5 Nov 2018

0.81.6

2018-11-07 12:11:02 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.habitica_name_mp (<class 'homeassistant.components.sensor.habitica.HabitipySensor'>) took 0.456 seconds. Please report platform to the developers at https://goo.gl/Nvioub

vorostamas on 8 Nov 2018

Home Assistant 0.82.0

Log Details (WARNING)
Fri Nov 16 2018 08:12:47 GMT-0300 (hora estándar de Argentina)

Updating state for weather.openweathermap () took 0.526 seconds. Please report platform to the developers at https://goo.gl/Nvioub

pablolassalle on 16 Nov 2018

0.82.0
2018-11-14 17:50:33 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.kok () took 23.704 seconds. Please report platform to the developers at https://goo.gl/Nvioub

skaker1 on 16 Nov 2018

👍1

Component: Climate
Platform: Hive
HA Version: 0.82.1

Fri Nov 16 2018 15:21:55 GMT+0000 (Greenwich Mean Time)

Updating state for climate.heating () took 0.420 seconds. Please report platform to the developers at https://goo.gl/Nvioub

labrunning on 16 Nov 2018

Compontent: telldus live switch
HA version: 0.82.1

Reporting as requested:
() took 0.644 seconds

tormodu on 24 Nov 2018

👍1

Component: Envisalink Alarm Control Panel
HA Version: 0.82.1

Error:
2018-11-29 16:45:07 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.front_door (<class 'homeassistant.components.binary_sensor.envisalink.EnvisalinkBinarySensor'>) took 0.520 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Apocrathia on 30 Nov 2018

Added the new Fibaro device to my configuration.yaml and restarted. Seems to some problems around it...

I run on a rasperry pi 3 and just upgraded to 0.83.2

bjorne

Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
timeout=timeout
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 638, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/local/lib/python3.6/site-packages/urllib3/util/retry.py", line 367, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/local/lib/python3.6/site-packages/urllib3/packages/six.py", line 685, in reraise
raise value.with_traceback(tb)
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 384, in _make_request
six.raise_from(e, None)
File "", line 2, in raise_from
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 380, in _make_request
httplib_response = conn.getresponse()
File "/usr/local/lib/python3.6/http/client.py", line 1331, in getresponse
response.begin()
File "/usr/local/lib/python3.6/http/client.py", line 297, in begin
version, status, reason = self._read_status()
File "/usr/local/lib/python3.6/http/client.py", line 266, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/fiblary3/common/restapi.py", line 146, in request
*kwargs)
File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 533, in request
resp = self.send(prep, *send_kwargs)
File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 646, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.6/site-packages/requests/adapters.py", line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/fiblary3/client/v4/client.py", line 259, in run
timeout=timeout)
File "/usr/local/lib/python3.6/site-packages/fiblary3/common/restapi.py", line 186, in get
return self.request('GET', url, **kwargs)
File "/usr/local/lib/python3.6/site-packages/fiblary3/common/restapi.py", line 149, in request
raise exceptions.ConnectionError(e.message)
AttributeError: 'ConnectionError' object has no attribute 'message'
2018-12-01 12:06:26 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.bion () took 3.586 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-12-01 12:06:55 WARNING (StateHandler) [fiblary3.client.v4.client] Waiting for next attempt 1 second(s)
2018-12-01 12:06:57 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.garage_ljusstyrka_680 is taking over 10 seconds
2018-12-01 12:26:19 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.hall_utanfor_sovrum_temp_hallway_722 () took 0.550 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-12-01 12:36:55 WARNING (Thread-18) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-12-01 12:36:58 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.utvecklingsrum_temperatur_546 () took 0.724 seconds. Please report platform to the developers at https://goo.gl/Nvioub

bjornesjogren on 1 Dec 2018

Raspberry Pi3
Debian Stretch
Hass 0.83.3.3

Dec 04 17:15:18 pihole hass[583]: 2018-12-04 17:15:18 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for light.lifx_329c4f () took 3.536 seconds. Please report platform to the developers at https://goo.gl/Nvioub

aelg305 on 4 Dec 2018

Reporting as requested.
Raspberry Pi 3B+
Hassio - HA version 0.83.3

Updating state for media_player.living_room_xbox_one () took 0.781 seconds. Please report platform to the developers at https://goo.gl/Nvioub

denniswham on 9 Dec 2018

Hardware: Raspberry Pi 3B+
OS: HassOS 1.13
HA: 0.83.3

Log:

2018-12-12 13:12:30 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sun.sun () took 0.458 seconds. Please report platform to the developers at https://goo.gl/Nvioub

DeviousPenguin on 12 Dec 2018

Compontent: telldus live switch
HA version: 0.82.1

Reporting as requested:
() took 0.644 seconds

Still no change in 84.1. Had this issue since "forever".

thepapamaan on 14 Dec 2018

Compontent: weather.ipma.IPMAWeather
HA version: 0.84.5

2018-12-22 22:30:15 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for weather.ipma__ovar () took 1.661 seconds. Please report platform to the developers at https://goo.gl/Nvioub

nunofmds on 22 Dec 2018

Component: camera.uvc
HA version: 0.84.6

2018-12-22 19:05:19 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.uvc_g3_dome_door (<class 'homeassistant.components.camera.uvc.UnifiVideoCamera'>) took 0.755 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-12-22 19:05:19 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.uvc_g3_dome_yard (<class 'homeassistant.components.camera.uvc.UnifiVideoCamera'>) took 0.515 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-12-22 19:05:20 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.80_ptl_mud_room (<class 'homeassistant.components.camera.uvc.UnifiVideoCamera'>) took 0.502 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-12-22 19:05:20 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.lot_835 (<class 'homeassistant.components.camera.uvc.UnifiVideoCamera'>) took 0.443 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-12-22 19:05:21 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.uvc_g3_dome_garage (<class 'homeassistant.components.camera.uvc.UnifiVideoCamera'>) took 0.676 seconds. Please report platform to the developers at https://goo.gl/Nvioub

davidu on 23 Dec 2018

👍1

Updating state for camera.owen (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 8.203 seconds. Please report platform to the developers at https://goo.gl/Nvioub
Updating state for camera.olivia (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 2.999 seconds. Please report platform to the developers at https://goo.gl/Nvioub

...

2018-12-27 15:37:24 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.olivia (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 13.177 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-12-27 15:37:32 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.owen (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 8.095 seconds. Please report platform to the developers at https://goo.gl/Nvioub

anthonysiano on 27 Dec 2018

Hassio 0.84.6
Updating state for sensor.koket_power () took 2.785 seconds. Please report platform to the developers at https://goo.gl/Nvioub
13:39 helpers/entity.py (WARNING)

Updating state for sensor.sovrummet_temperature () took 0.612 seconds. Please report platform to the developers at https://goo.gl/Nvioub
13:50 helpers/entity.py (WARNING)

askusbloodfist on 29 Dec 2018

Hassio Version: 0.84.5
Component: Arlo
Platform: Camera
Raspberry Pi 2

Update of alarm_control_panel.arlo_home is taking over 10 seconds
Updating state for camera.front_door (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 6.706 seconds. Please report platform to the developers at https://goo.gl/Nvioub

talljohnson on 29 Dec 2018

Hass Version: 0.84.6
Component: iTunes
Platform: Media Player
Raspberry Pi 3+ running Hassbian

Hi there, my system just crashed to the point that I couldn't open the UI with the following as it's last messages.. I get a lot of these kind of messages and would love to know why.

2019-01-03 22:43:36 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:00:30
2019-01-03 22:43:44 WARNING (MainThread) [homeassistant.components.sensor] Updating ios sensor took longer than the scheduled update interval 0:00:30
2019-01-03 22:43:58 WARNING (MainThread) [homeassistant.components.camera] Updating synology camera took longer than the scheduled update interval 0:00:30
2019-01-03 22:44:03 WARNING (MainThread) [homeassistant.components.media_player] Updating itunes media_player took longer than the scheduled update interval 0:00:10
2019-01-03 22:49:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.speedtest_download is taking over 10 seconds
2019-01-03 22:50:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.seans_iphone_x_battery_level is taking over 10 seconds
2019-01-03 22:50:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.itunes is taking over 10 seconds
2019-01-03 22:50:16 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.load_15m is taking over 10 seconds
2019-01-03 22:50:24 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.cp_packages_coming_today is taking over 10 seconds
2019-01-03 22:50:41 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.itunes () took 2.227 seconds. Please report platform to the developers at https://goo.gl/Nvioub

scstraus on 4 Jan 2019

Hass Version: 0.84.6
Components: weather.openweathermap, media_player.itunes, sensor.template.SensorTemplate
Platform: Media Player
Raspberry Pi 3+ running Hassbian

More Crashes... I have opened an issue at https://github.com/home-assistant/home-assistant/issues/19806

2019-01-05 17:36:48 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for weather.openweathermap () took 2.869 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-01-05 17:36:50 WARNING (MainThread) [homeassistant.helpers.entity] Update of camera.front is taking over 10 seconds
2019-01-05 17:36:50 WARNING (MainThread) [homeassistant.helpers.entity] Update of camera.back is taking over 10 seconds
2019-01-05 17:36:50 WARNING (MainThread) [homeassistant.helpers.entity] Update of camera.right is taking over 10 seconds
2019-01-05 17:36:51 WARNING (MainThread) [homeassistant.helpers.entity] Update of camera.left is taking over 10 seconds
2019-01-05 17:36:56 WARNING (MainThread) [homeassistant.helpers.entity] Update of image_processing.tensorflow_front is taking over 10 seconds
2019-01-05 17:36:57 WARNING (MainThread) [homeassistant.components.image_processing] Updating tensorflow image_processing took longer than the scheduled update interval 0:00:05
2019-01-05 17:36:59 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.itunes () took 1.012 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-01-05 17:37:02 WARNING (MainThread) [homeassistant.components.image_processing] Updating tensorflow image_processing took longer than the scheduled update interval 0:00:05
2019-01-05 17:37:11 WARNING (MainThread) [homeassistant.helpers.entity] Update of image_processing.tensorflow_back is taking over 10 seconds
2019-01-05 17:37:12 ERROR (MainThread) [homeassistant.components.image_processing] Error on receive image from entity: Unable to get image
2019-01-05 17:37:30 WARNING (MainThread) [homeassistant.components.camera] Updating synology camera took longer than the scheduled update interval 0:00:30
2019-01-05 17:37:37 WARNING (MainThread) [homeassistant.components.image_processing] Updating tensorflow image_processing took longer than the scheduled update interval 0:00:05
2019-01-05 17:38:51 WARNING (MainThread) [homeassistant.components.media_player] Updating itunes media_player took longer than the scheduled update interval 0:00:10
2019-01-05 17:38:53 WARNING (MainThread) [homeassistant.components.image_processing] Updating tensorflow image_processing took longer than the scheduled update interval 0:00:05
2019-01-05 17:39:01 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.current_rate_power_cost_per_day () took 0.924 seconds. Please report platform to the developers at https://goo.gl/Nvioub

scstraus on 5 Jan 2019

Component: ecobee
Hassio Version: 0.85.0
hass.io on a Raspberry Pi 3

Updating state for weather.home () took 0.645 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Jessev88 on 15 Jan 2019

Component: ecobee
Hassio Version: 0.85.0
hass.io on a Raspberry Pi 3

Updating state for weather.home () took 0.645 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Here the same with buienradar

hiddit on 16 Jan 2019

Reporting as requested:

Component: Arlo (Alarm System and Camera)

arch: aarch64
channel: stable
hassos: "1.13"
homeassistant: 0.85.1
hostname: hassio
machine: raspberrypi3-64
supervisor: "142"

2019-01-16 16:55:45 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.front_porch (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 3.249 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Happens periodically with all components in the Arlo platform but always on restart of HA from the above.

chipriley on 17 Jan 2019

homassistant 0.85.1
ubuntu 16.04

2019-01-18 12:33:49 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.spotify () took 1.866 seconds. Please report platform to the developers at https://goo.gl/Nvioub

jonwaland on 18 Jan 2019

Updating state for media_player.express () took 0.427 seconds. Please report platform to the developers at https://goo.gl/Nvioub

fastrack20 on 21 Jan 2019

Component: dsmr
PlatformL: sensor

hassio info
arch: armhf
channel: stable
hassos: "1.13"
homeassistant: 0.86.2
hostname: null
machine: raspberrypi3
supervisor: "142"

2019-01-27 12:06:17 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.power_production_low () took 0.805 seconds. Please report platform to the developers at

snelweg on 27 Jan 2019

Here is mine Darksky. Running on Hass.io, Raspberry Pi 2B.

Updating state for weather.dark_sky (<class 'homeassistant.components.weather.darksky.DarkSkyWeather'>) took 0.542 seconds.

naldoxable on 5 Feb 2019

0.87.0
Been doing stuff like this since 0.84.x i belive.
rasp 3b+

Updating state for sensor.outside_temperature_2 () took 0.561 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2:02 PM helpers/entity.py (WARNING)

platform tellduslive

System | HassOS 2.8
Deployment | production
Hass.io supervisor
Version | 143

gurkburk76 on 7 Feb 2019

0.87.0

Updating state for sensor.ups_battery_replaced () took 0.533 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Hass.IO on HassOS v1.13

Pre10der on 9 Feb 2019

Updating state for climate.melcloud_XXX_XXXXXX () took 6.774 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Home Assistant
0.87.0

Hostname hassio
System HassOS 2.8
Deployment production

dolenec on 10 Feb 2019

Updating state for switch.hdmi_0 () took 1.212 seconds

nbeernink on 11 Feb 2019

Updating state for media_player.transporter () took 0.549 seconds.

I've been using Squeezebox for well over a year in HA. Never had this warning before.

jladefoged on 19 Feb 2019

Updating state for climate.termostato () took 1.153 seconds. Please report platform to the developers at https://goo.gl/Nvioub

mirkochip88 on 23 Feb 2019

Log details:
Updating state for climate.trv_bedroom_heat () took 0.457 seconds. Please report platform to the developers at https://goo.gl/Nvioub

The product is a Eurotronic Spirit Z-Wave Plus TRV

vodanium on 5 Mar 2019

Updating state for sensor.nut_ups_status_data () took 0.467 seconds. Please report platform to the developers at https://goo.gl/Nvioub

It's for a Cyber Power UPS connected to a Synology DSM hosting HA

tregster on 7 Mar 2019

Date/Time of occurrence: Mon Mar 11 2019 22:45:42 GMT-0700 (Pacific Daylight Time)
Product name: UnifiVideoCamera

Execution time: 0.443 seconds

Error message: Updating state for camera.frontdoor () took 0.443 seconds. Please report platform to the developers at https://goo.gl/Nvioub

JRock30000 on 12 Mar 2019

👍1

Sonoff TH16
sensor SI7021
Fri Mar 15 2019 01:08:55 GMT-0500 (Central Daylight Time)
Updating state for sensor.bedside_temp () took 1.316 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Nighalefty on 15 Mar 2019

The climate: Maxcube integration. I once made a pull request, but was rejected as the (HA specific) API project for MaxCube should also be modified.

Script frequently takes over 10 seconds, especially when updating mulitple thermostats in a room:

2019-03-18 10:54:29 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.livingroom_2 is taking over 10 seconds
2019-03-18 11:49:23 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.livingroom is taking over 10 seconds
2019-03-18 12:24:14 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.kitchen is taking over 10 seconds
(Lately I get about 10 of these entries a day)

ekaats on 20 Mar 2019

Reporting Arlo Cams and Hub:
Arlo has always been slow since the beginning at startup and the state of the hub (Armed/Disarmed) fluctuates constantly or simply shows as unknown.

Updating state for camera.second_floor () took 2.835 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Sat Mar 30 2019 14:22:43 GMT-0400 (Eastern Daylight Time)
Update of alarm_control_panel.arlohub is taking over 10 seconds

rpitera on 30 Mar 2019

👍1

Reporting Arlo Cams and Hub:
Arlo has always been slow since the beginning at startup and the state of the hub (Armed/Disarmed) fluctuates constantly or simply shows as unknown.

Take a look at this, this works perfect and will hopefully replace the component https://github.com/twrecked/hass-aarlo

Nicxe on 31 Mar 2019

👍2

Wow, thanks for the heads up! I'll check into it.

rpitera on 31 Mar 2019

Log Details (WARNING)
Mon Apr 01 2019 11:14:01 GMT-0500 (Central Daylight Time)
Updating state for sensor.plex_recently_added () took 0.588 seconds. Please report platform to the developers at https://goo.gl/Nvioub

bbalz on 1 Apr 2019

_homeassistant.components.cloud.binary_sensor.CloudRemoteBinary_
took 14.429 seconds
Log Details (WARNING)
Wed Apr 03 2019 17:35:26 GMT-0500 (Central Daylight Time)
Updating state for binary_sensor.remote_ui () took 14.429 seconds. Please report platform to the developers at https://goo.gl/Nviou

Dino-Tech on 4 Apr 2019

👍1

Hello, I have the following message :

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for weather.openweathermap () took 3.014 seconds. Please report platform to the developers at https://goo.gl/Nvioub

HASSOS : 2.11
HASS : 0.91.0

boced66 on 5 Apr 2019

Updating state for light.color_temperature_light_1 () took 4.544 seconds. Please report platform to the developers at https://goo.gl/Nvioub

warcanoid on 8 Apr 2019

Hello,

I received the following message:

Updating state for camera.uvc_g3_micro_2 (<class 'homeassistant.components.uvc.camera.UnifiVideoCamera'>) took 2.715 seconds. Please report platform to the developers at https://goo.gl/Nvioub

HASS: 0.91.2

dancwilliams on 10 Apr 2019

Here's more. Arlo is also reporting this.

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.backyard_cam () took 3.415 seconds. Please report platform to the developers at https://goo.gl/Nvioub

haruny on 12 Apr 2019

@haruny - If you scroll up just a bit you can see a recommendation for an alternative to native Arlo support: https://github.com/twrecked/hass-aarlo. I tested it out and it's just incredibly good. I imagine this replacing the current Arlo component at some point; more stable, better features and better state reporting. Definitely check it out; @Nicxe made a great recommendation and I think you'll be really pleased with it!

rpitera on 13 Apr 2019

👍1

@rpitera amazing tip. Thank you so much

haruny on 14 Apr 2019

👍1

@haruny Thanks should really go to @Nicxe, he pointed me to it.

rpitera on 14 Apr 2019

SMHI component took 0.425 seconds

andreaswulff on 15 Apr 2019

homeassistant.components.zwave.sensor.ZWaveMultilevelSensor took 0.489 seconds

andreaswulff on 16 Apr 2019

019-04-17 21:13:16 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.upstairs () took 2.297 seconds. Please report platform to the developers at https://goo.gl/Nvioub

tmonck on 18 Apr 2019

Upgraded to 0.92.0 and got the following warning on startup.

Updating state for sensor.hass_db (<class 'homeassistant.components.sql.sensor.SQLSensor'>) took 0.538 seconds

Coolie1101 on 26 Apr 2019

Upgraded to 0.92.0 and got the following warning on startup.

Updating state for automation.battery_sensor_from_attributes (<class 'homeassistant.components.automation.AutomationEntity'>) took 0.529 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Coolie1101 on 26 Apr 2019

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.power_production () took 0.706 seconds. Please report platform to the developers at https://goo.gl/Nvioub

mverleun on 28 Apr 2019

Meross-iot + custom_component:

Log Details (WARNING)
Mon Apr 29 2019 22:54:00 GMT+0200 (Ora legale dell’Europa centrale)
Updating state for sensor.meross_18050387424708251a0234298f117d1e_current (<class 'custom_components.meross.sensor.MerossSensorEntity'>) took 0.409 seconds. Please report platform to the developers at https://goo.gl/Nvioub

gianky69 on 29 Apr 2019

2019-05-17 18:38:25 WARNING (MainThread) [homeassistant.components.media_player] Updating samsungtv media_player took longer than the scheduled update interval 0:00:10
2019-05-17 18:38:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.hall_tv is taking over 10 seconds
2019-05-17 18:39:03 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.hall_tv (<class 'homeassistant.components.samsungtv.media_player.SamsungTVDevice'>) took 0.401 seconds. Please report platform to the developers at https://goo.gl/Nvioub

arch	armv7l
dev	false
docker	false
hassio	false
os_name	Linux
python_version	3.5.3
timezone	Europe/Moscow
version	0.92.1
virtualenv	true

olegin15 on 17 May 2019

I had the following warning in my log file:

2019-05-19 11:41:13 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for group.motion_sensor_batteries (<class 'homeassistant.components.group.Group'>) took 0.891 seconds. Please report platform to the developers at https://goo.gl/Nvioub

The group contains sensors for motion sensors from Xiaomi and Dome.

RonJ103 on 20 May 2019

I had this warning in my log file:

Updating state for climate.living_room (<class 'homeassistant.components.sensibo.climate.SensiboClimate'>) took 0.511 seconds. Please report platform to the developers at https://goo.gl/Nvioub`

Quicksand10 on 23 May 2019

It seems like the Neato Vacuum component might fall into this category, too:

Log Details (WARNING)
Mon May 27 2019 15:49:09 GMT+0200 (Central European Summer Time)
Update of vacuum.kreacher is taking over 10 seconds

SeraphimSerapis on 27 May 2019

👍1

I found these logs in home-assistant.log as the last logs when my instance crashed...

2019-05-31 21:57:38 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sun.sun () took 4.528 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-05-31 21:58:07 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.kitchen_2 () took 0.406 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-05-31 21:58:27 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.sovrum () took 0.623 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-05-31 21:58:35 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.nodon_msp31xx_micro_smart_plug_previous_reading () took 2.200 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-05-31 21:58:48 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for weather.smhi_goteborg () took 0.946 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-05-31 21:59:07 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for zwave.nodon_msp31xx_micro_smart_plug () took 0.447 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-05-31 21:59:23 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.nodon_msp31xx_micro_smart_plug_interval () took 0.896 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-05-31 22:00:11 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.nodon_msp31xx_micro_smart_plug_unknown () took 1.009 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-05-31 22:03:13 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for group.default_view () took 0.995 seconds. Please report platform to the developers at https://goo.gl/Nvioub

trettiotrean on 31 May 2019

Updating state for sensor.uptime () took 0.559 seconds. Please report platform to the developers at https://goo.gl/Nvioub

gsotiriou on 29 Jun 2019

Updating state for sensor.glances_total () took 0.572 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Spankythemusical on 3 Jul 2019

2019-07-03 22:09:41 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.wohnzimmer_motion_light_level () took 0.414 seconds. Please report platform to the developers at https://goo.gl/Nvioub

wneessen on 3 Jul 2019

Updating state for camera.kitchen_camera () took 1.576 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Seannaber on 6 Jul 2019

Updating state for weather.weather () took 0.825 seconds. Please report platform to the developers at https://goo.gl/Nvioub

djtommye on 12 Jul 2019

Updating state for binary_sensor.remote_ui (<class 'homeassistant.components.cloud.binary_sensor.CloudRemoteBinary'>) took 0.437 seconds. Please report platform to the developers at https://goo.gl/Nvioub

dancwilliams on 20 Jul 2019

Updating state for media_player.living_room_xbox_one () took 0.410 seconds. Please report platform to the developers at https://goo.gl/Nvioub

djtommye on 26 Jul 2019

This is a custom component so it might not be covered, but I'm going to include it here anyway. This is the meross_cloud custom component.
```
2019-07-29 23:05:25 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.redacted1 () took 0.408 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-07-29 23:05:25 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.redacted2 () took 0.471 seconds. Please report platform to the developers at https://goo.gl/Nvioub
````

maxistviews on 30 Jul 2019

Updating state for sensor.voodi_kaal (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) took 0.721 seconds. Please report platform to the developers at https://goo.gl/Nvioub

kuradi on 3 Aug 2019

OpenWeatherMap still has issues:

Updating state for weather.openweathermap (<class 'homeassistant.components.openweathermap.weather.OpenWeatherMapWeather'>) took 0.554 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Using HA in Docker, version 0.95.4

TASSDevon on 6 Aug 2019

platform: https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/uvc

Updating state for camera.uvc_g3_flex (<class 'homeassistant.components.uvc.camera.UnifiVideoCamera'>) took 1.726 seconds. Please report platform to the developers at https://goo.gl/Nvioub

HA in Docker, 0.97.1

parberge on 10 Aug 2019

2019-08-12 21:40:12 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for zwave.id_lock_150 (<class 'homeassistant.components.zwave.node_entity.ZWaveNodeEntity'>) took 0.444 seconds. Please report platform to the developers at https://goo.gl/Nvioub

larronni on 12 Aug 2019

Updating state for binary_sensor.remote_ui (<class 'homeassistant.components.cloud.binary_sensor.CloudRemoteBinary'>) took 0.437 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Another report for this one:
2019-08-13 17:26:49 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.remote_ui () took 0.823 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Hass.io on Raspberry Pi 3B+, 0.97.2

pickerin on 14 Aug 2019

https://github.com/albertogeniola/meross-homeassistant

Updating state for switch.luz_cocina (<class 'custom_components.meross_cloud.switch.SwitchEntityWrapper'>) took 0.543 seconds. Please report platform to the developers at https://goo.gl/Nvioub

arcangelweb on 23 Aug 2019

As the instruction recommend.

Details: HASS.io 0.96.5
Integration: Xiaomi Vacuum

Updating state for vacuum.xiaomi_vacuum_cleaner (<class 'homeassistant.components.xiaomi_miio.vacuum.MiroboVacuum'>) took 0.542 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Let me know if you need anything further

mpartoglou on 24 Aug 2019

https://www.home-assistant.io/components/tuya/

Updating state for switch.AAA (<class 'homeassistant.components.tuya.switch.TuyaSwitch'>) took 1.499 seconds.

troykelly on 29 Aug 2019

Updating state for switch.00854014807d3a388ebe () took 1.067 seconds
Updating state for switch.00854014ecfabc9e8261 () took 1.051 seconds.

tmat78 on 29 Aug 2019

Tuya switch problem reported upstream here with problem analysis:
https://github.com/PaulAnnekov/tuyaha/issues/7

MartinHjelmare on 30 Aug 2019

Home Assistant 0.98.1

2019-08-30 09:27:07 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.ups_battery_charge (<class 'homeassistant.components.nut.sensor.NUTSensor'>) took 1.675 seconds. Please report platform to the developers at https://goo.gl/Nvioub

bieniu on 30 Aug 2019

Just Got this..
2019-08-30 20:52:16 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.remote_ui () took 0.432 seconds. Please report platform to the developers at https://goo.gl/Nvioub

pi 3 b+ ha 96.1

dex857 on 30 Aug 2019

Home Assistant 0.98.1 Environment Canada platform

2019-09-01 10:56:18 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for weather.calgary (<class 'homeassistant.components.environment_canada.weather.ECWeather'>) took 0.533 seconds. Please report platform to the developers at https://goo.gl/Nvioub

ve6rah on 1 Sep 2019

Home Assistant 0.98.0 on rpi3b+
Updating state for geo_location.lightning_strike_6786155 () took 1.748 seconds. Please report platform to the developers at https://goo.gl/Nvioub

SelcouthGuy on 2 Sep 2019

Updating state for camera.shop (<class 'homeassistant.components.uvc.camera.UnifiVideoCamera'>) took 1.241 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Home Assistant 0.98.1 on rpi3b+

randomstring on 2 Sep 2019

Updating state for vacuum.roborock_s50 () took 2.536 seconds. Please report platform to the developers at https://goo.gl/Nvioub

On HA 0.97.1

TASSDevon on 5 Sep 2019

I'm seeing slow responses from Netgear Arlo. I run this with 2 cameras and use the alarm panel to arm / disarm based on location. It works, but slowly and with some warnings:

2019-09-09 11:40:50 WARNING (MainThread) [homeassistant.helpers.entity] Update of alarm_control_panel.haarlem is taking over 10 seconds
2019-09-09 11:43:37 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.front_door () took 34.405 seconds. Please report platform to the developers at https://goo.gl/Nvioub

rvleij on 9 Sep 2019

I am getting these warnings since i moved the cameras from generic to uvc:

2019-09-09 10:02:42 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.no1 () took 0.417 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-09-09 10:02:42 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.no2 () took 0.434 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2019-09-09 10:07:43 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.no3 () took 0.509 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Silverridge on 9 Sep 2019

Updating state for weather.dark_sky () took 0.421 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Hass.io 0.98.5 Rpi3

gsotiriou on 17 Sep 2019

Updating state for switch.13333211840d8e626fd8 () took 0.668 seconds. Please report platform to the developers at https://goo.gl/Nvioub

fnxpt on 17 Sep 2019

Updating state for sensor.energy_daily (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) took 1.254 seconds.

HA 0.98.5; RPi2

maxwroc on 19 Sep 2019

Home Assistant 0.99.0 (HASSIO) running in QNAP and VM enviroment

2019-09-20 17:56:46 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.rpi_ups_battery_runtime (<class 'homeassistant.components.nut.sensor.NUTSensor'>) took 5.007 seconds. Please report platform to the developers at https://goo.gl/Nvioub

salvq on 20 Sep 2019

homeassistant.components.arlo.camera.ArloCam taking ~13.5, 77.9, and 2.225 sec. Others mention Arlo but I'll add this again.

Here is one:

2019-09-24 17:18:56 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.front () took 77.922 seconds. Please report platform to the developers at https://goo.gl/Nvioub

brannonvann on 24 Sep 2019

2019-09-25 23:04:53 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.remote_ui () took 0.481 seconds.

HASS.IO 0.99.3
Pentium NUC

jerobins on 29 Sep 2019

2019-10-03 20:06:42 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.energia_consumata () took 0.807 seconds.

homeassistant/home-assistant 0.99.2 docker image

fakezeta on 3 Oct 2019

Updating state for remote.xiaomi_miio_192_168_xx_xx () took 0.614 seconds. Please report platform to the developers at https://goo.gl/Nvioub

hass installed by this manual: https://www.home-assistant.io/docs/installation/raspberry-pi/

yaroslavyaroslav on 9 Oct 2019

Same as yaroslavyaroslav
Updating state for remote.xiaomi_miio_192_168_x_xx () took 5.005 seconds.

It starts after update to 0.100.1 and several restarts

dobriys on 11 Oct 2019

homeassistant.helpers.entity warning report:
Home Assistant version: 0.100.2
platform: media_player
product: Samsung TV QLED Q7F
entity_id: media_player.samsung_tv_remote
class 'custom_components.samsungtv_custom.media_player.SamsungTVDeviceQLED'

warming message: "WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.samsung_tv_remote () took 9.900 seconds. Please report platform to the developers at https://goo.gl/Nvioub"

krishuang92 on 18 Oct 2019

Mon Oct 21 2019 14:33:05 GMT-0500 (Central Daylight Time)
Updating state for binary_sensor.remote_ui () took 0.496 seconds. Please report platform to the developers at https://goo.gl/Nvioub

txwindsurfer on 21 Oct 2019

Home Assistant 0.100.3 on rpi3b+

Updating state for sensor.xiaomi_aqara_magic_cube_action () took 1.605 seconds. Please report platform to the developers at https://goo.gl/Nvioub

and

Updating state for sensor.xiaomi_temp_sensor_pressure () took 0.410 seconds. Please report platform to the developers at https://goo.gl/Nvioub

SelcouthGuy on 23 Oct 2019

Home Assistant 0.100.3 on Synology DS918+ Docker:

Updating state for remote.xiaomi_remotev2 () took 0.635 seconds. Please report platform to the developers at https://goo.gl/Nvioub

truebit on 26 Oct 2019

Hassio 0.100.2 running on a Ubuntu VM, if that matters. Started getting alot more delays and what not since last upgrade.

2019-10-31 23:14:27 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.altandorr_tvrum (<class 'homeassistant.components.verisure.binary_sensor.VerisureDoorWindowSensor'>) took 1.224 seconds. Please report platform to the developers at https://goo.gl/Nvioub

I also get alot of that message for my Hue hub, but without the report part..

[homeassistant.components.light] Updating hue light took longer than the scheduled update interval 0:00:05

phk-r on 31 Oct 2019

Updating state for light.xiaomi_gateway () took 2.854 seconds. Please report platform to the developers at https://goo.gl/Nvioub

SelcouthGuy on 1 Nov 2019

Got another one today:

[homeassistant.helpers.entity] Updating state for switch.dafang1_blue_led (<class 'homeassistant.components.mqtt.switch.MqttSwitch'>) took 0.412 seconds. Please report platform to the developers at https://goo.gl/Nvioub

phk-r on 1 Nov 2019

Here is one

Updating state for camera.chicken_camera () took 1.986 seconds.

dapowers87 on 5 Nov 2019

👍1

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for media_player.masterbedroomspeaker () took 0.738 seconds. Please report platform to the developers at https://goo.gl/Nvioub

westerncanada on 9 Nov 2019

Updating state for sensor.database_size () took 1.080 seconds. Please report platform to the developers at https://goo.gl/Nvioub

sermayoral on 10 Nov 2019

Ubiquiti Unifi Cameras are showing this error. Specifically the UVC G3 Micro but I am sure all Unifi NVR cameras are showing this error.

Updating state for camera.outside_back_door (<class 'homeassistant.components.uvc.camera.UnifiVideoCamera'>) took 2.878 seconds. Please report platform to the developers at https://goo.gl/Nvioub

dcplaya on 10 Nov 2019

my sensor that shows uptime gave me this warning so as it says - I'm reporting that here :)

2019-11-10 04:00:45 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.sns_uptime_ha (<class 'homeassistant.components.template.sensor.SensorTemplate'>) took 0.459 seconds. Please report platform to the developers at https://goo.gl/Nvioub

pejotigrek on 11 Nov 2019

Owntracks:
<class 'homeassistant.components.owntracks.device_tracker.OwnTracksEntity'>) took 0.655 seconds.

Home Assistant
0.100.2

Running in a docker container.

Nornode on 13 Nov 2019

2019-11-21 16:04:19 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.condizionatore_camera () took 0.450 seconds. Please report platform to the developers at https://goo.gl/Nvioub

It seems started from 0.101.3 and it is also in the 0.102

claudiosala80 on 21 Nov 2019

Hello,
since yesterday I'm getting this on my ha log file

Updating state for device_tracker.mom_phone_gps () took 0.431 seconds

It's started with 0.102.1 and still present on 0.102.2

ThePirat91 on 25 Nov 2019

Hello,
Updating state for media_player.tv () took 0.587 seconds

0.102.2

stsybizov on 29 Nov 2019

Hello,
reporting SpotifyMediaPlayer

Updating state for media_player.spotify (<class 'homeassistant.components.spotify.media_player.SpotifyMediaPlayer'>) took 0.598 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Home Assistant 0.102.3

pasleto on 7 Dec 2019

Reporting for DSMR (Dutch Smart Meter p1)

2019-12-07 17:06:25 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.power_consumption_low () took 0.642 seconds. Please report platform to the developers at https://goo.gl/Nvioub

DaPlague on 7 Dec 2019

I'm seeing this in the meross-homeassistant plugin from @albertogeniola.

Updating state for switch.bedroom_heater (<class 'custom_components.meross_cloud.switch.SwitchEntityWrapper'>) took 1.141 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Updating state for switch.bathroom_heater (<class 'custom_components.meross_cloud.switch.SwitchEntityWrapper'>) took 0.554 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Updating state for switch.kitchen_heater (<class 'custom_components.meross_cloud.switch.SwitchEntityWrapper'>) took 0.420 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Updating state for switch.smart_plug_mini (<class 'custom_components.meross_cloud.switch.SwitchEntityWrapper'>) took 0.943 seconds. Please report platform to the developers at https://goo.gl/Nvioub

skullydazed on 8 Dec 2019

👍1

Hello,
2019-12-25 14:41:15 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.remote_ui () took 0.442 seconds. Please report platform to the developers at https://goo.gl/Nvioub

This happened in Home Assistant version 0.103.4

ghost on 25 Dec 2019

Hi, just happened on 103.3 :

Updating state for weather.openweathermap () took 0.543 seconds. Please report platform to the developers at https://goo.gl/Nvioub

arpel on 27 Dec 2019

homeassistant.components.arlo.camera.ArloCam taking ~13.5, 77.9, and 2.225 sec. Others mention Arlo but I'll add this again.

Here is one:

2019-09-24 17:18:56 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.front () took 77.922 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Adding my report to this one as well...

Updating state for camera.living_area () took 48.387 seconds. Please report platform to the developers at https://goo.gl/Nvioub

asthypar on 28 Dec 2019

Ditto the above.

Log Details (WARNING)
Mon Dec 30 2019 10:44:14 GMT+0000 (Greenwich Mean Time)
Updating state for camera.arlo_kitchen () took 17.069 seconds. Please report platform to the developers at https://goo.gl/Nvioub
Connection lost. Reconnecting…

Chillywasher on 30 Dec 2019

Updating state for light.yeelight_ceiling1_34ce008dd64a () took 0.972 seconds. Please report platform to the developers at https://goo.gl/Nvioub

lfliess on 30 Dec 2019

Уровень: WARNING
Wed Jan 01 2020 11:58:28 GMT+0300 (Москва, стандартное время)
Updating state for remote.xiaomi_miio_192_168_1_225 () took 0.413 seconds. Please report platform to the developers at https://goo.gl/Nvioub

LeshiyGS on 1 Jan 2020

Home Assistant 0.103.5

Updating state for sensor.garage_1_temperature () took 23.165 seconds. Please report platform to the developers at https://goo.gl/Nvioub

pasleto on 1 Jan 2020

Home Assistant 0.103.4

Another one for Arlo:-

Updating state for camera.garden () took 1.922 seconds

DrCamel9000 on 1 Jan 2020

Hassio 0.103.6

Updating state for light.livingroom_2 () took 0.650 seconds. Please report platform to the developers at https://goo.gl/Nvioub

magidel on 9 Jan 2020

Updating state for lock.zuhause () took 10.913 seconds.

mmmente on 10 Jan 2020

another one for the list...

platform: mobile_app
time: 1.391 sec

Updating state for device_tracker.oneplus_7t (<class 'homeassistant.components.mobile_app.device_tracker.MobileAppEntity'>) took 1.391 seconds. Please report platform to the developers at https://goo.gl/Nvioub

nelbs on 12 Jan 2020

👍1

Updating state for sensor.eaton3s_load (<class 'homeassistant.components.nut.sensor.NUTSensor'>) took 0.683 seconds. Please report platform

quazzie on 14 Jan 2020

platform enigma2
hassio 104.1
other things clearly visible :-)

Updating state for media_player.xtrend_et7500 () took 1.250 seconds.

tstoykov on 17 Jan 2020

hassio 0.103.6

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for weather.wth_darksky () took 13.938 seconds.

pejotigrek on 17 Jan 2020

hass docker 104.1:

2020-01-18 11:18:17 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for zwave.zwaveme_zme_uzb1_usb_stick (<class 'homeassistant.components.zwave.node_entity.ZWaveNodeEntity'>) took 1.673 seconds. Please report platform to the developers at https://goo.gl/Nvioub

I have never had this error before and I have been using zwave for years now

jurgenweber on 18 Jan 2020

Just see the log for homeassistant.components.meteo_france.weather.MeteoFranceWeather

2020-01-18 08:59:27 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for weather.aurade (<class 'homeassistant.components.meteo_france.weather.MeteoFranceWeather'>) took 0.506 seconds. Please report platform to the developers at https://goo.gl/Nvioub

oncleben31 on 18 Jan 2020

Running Hass 0.104.3
Updating state for light.quarto (<class 'homeassistant.components.yeelight.light.YeelightColorLight'>) took 0.433 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Matcheryt on 28 Jan 2020

Got a warning about Nut but it actually looks fine.

bdraco on 3 Feb 2020

Running Hass 0.104.3
Updating state for media_player.samsung_tv_remote_2 () took 9.817 seconds.

jackkitley on 4 Feb 2020

👍1

Running Hass 0.105.2 | HassOS 3.8
Updating state for camera.aarlo_camera2 () took 0.687 seconds.

friendodevil on 10 Feb 2020

Came from custom component DreamScreen:

Updating state for dreamscreen.dream_screen () took 0.839 seconds.

HA Core: 0.105.2

guice on 10 Feb 2020

I'm getting the warning from the custom meross component :

2020-02-14 21:33:02 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.power_2_e805 (<class 'custom_compo
nents.meross_cloud.switch.SwitchEntityWrapper'>) took 0.545 seconds. Please report platform to the developers at https://goo.gl/Nvio
ub
2020-02-14 21:33:03 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.power_5_e043 (<class 'custom_compo
nents.meross_cloud.switch.SwitchEntityWrapper'>) took 0.684 seconds. Please report platform to the developers at https://goo.gl/Nvio
ub
2020-02-14 21:33:04 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.power_1 (<class 'custom_components
.meross_cloud.switch.SwitchEntityWrapper'>) took 0.550 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2020-02-14 21:33:04 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.power_4_e039 (<class 'custom_components.meross_cloud.switch.SwitchEntityWrapper'>) took 0.688 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2020-02-14 21:33:05 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.power_3_e29d (<class 'custom_components.meross_cloud.switch.SwitchEntityWrapper'>) took 0.709 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2020-02-14 21:33:06 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for switch.power_6_e2f7 (<class 'custom_components.meross_cloud.switch.SwitchEntityWrapper'>) took 0.944 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Additionally and maybe related I get this traceback in the meross stuff:

2020-02-15 02:14:06 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.power_6_e2f7 fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 459, in async_device_update
    await self.async_update()
  File "/config/custom_components/meross_cloud/sensor.py", line 42, in async_update
    sensor_info = self._device.get_electricity()
  File "/usr/local/lib/python3.7/site-packages/meross_iot/cloud/devices/power_plugs.py", line 144, in get_electricity
    return self._get_electricity()['electricity']
  File "/usr/local/lib/python3.7/site-packages/meross_iot/cloud/devices/power_plugs.py", line 21, in _get_electricity
    return self.execute_command("GET", ELECTRICITY, {})
  File "/usr/local/lib/python3.7/site-packages/meross_iot/cloud/device.py", line 126, in execute_command
    return self.__cloud_client.execute_cmd(self.uuid, command, namespace, payload, callback=callback, timeout=timeout)
  File "/usr/local/lib/python3.7/site-packages/meross_iot/cloud/client.py", line 302, in execute_cmd
    raise CommandTimeoutException("A timeout occurred while waiting for the ACK: %d" % timeout)
meross_iot.cloud.exceptions.CommandTimeoutException.CommandTimeoutException: A timeout occurred while waiting for the ACK: 10

$ ha core info
arch: amd64
boot: true
custom: false
image: homeassistant/intel-nuc-homeassistant
ip_address: 172.30.32.1
last_version: 0.105.3
machine: intel-nuc
port: 8123
ssl: true
version: 0.105.2
wait_boot: 600
watchdog: true

HTH

cabletie on 15 Feb 2020

@cabletie that's a problem with the custom component. It's doing I/O inside async_update. Please report it to the author of the custom component.

balloob on 15 Feb 2020

Updating state for media_player.samsung_tv (<class 'custom_components.samsungtv_custom.media_player.SamsungTVDevice'>) took 0.976 seconds. Please report platform to the developers at https://goo.gl/Nvioub

twsl on 17 Feb 2020

Component: Envisalink
Issue: Update State for Binary Sensor
Time: 0.704 seconds

Log:
2020-02-18 13:22:52 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.mud_room_door () took 0.704 seconds.

grahamr on 18 Feb 2020

Component: DSMR Sensor (Dutch smart electrical/gass smart meter):
Updating state for sensor.power_consumption_normal () took 0.531 seconds.
This message first showed up after updating to 0.105.5

EelcoAV on 18 Feb 2020

Updating state for remote.kitchen_remote (<class 'homeassistant.components.xiaomi_miio.remote.XiaomiMiioRemote'>) took 0.415 seconds. Please report platform to the developers at https://goo.gl/Nvioub

anonim-no on 19 Feb 2020

2020-02-21 11:50:58 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for zone.laid_back_key_west () took 1.989 seconds. Please report platform to the developers at https://goo.gl/Nvioub

toddsantoro on 21 Feb 2020

Updating state for remote.xiaomi_miio_192_168_1_113 () took 0.767 seconds. Please report platform to the developers at https://goo.gl/Nvioub

RasPi4 with Hassio installed from the Hass site

iluhis on 21 Feb 2020

Component: VerisureThermometer
Platform: Sensor
Time to update: 0.567 s

Updating state for sensor.garage_temperature () took 0.567 seconds. Please report platform to the developers at https://goo.gl/Nvioub

Raspberry Pi 3B, docker

JakeTheSnake on 22 Feb 2020

2020-02-23 22:21:30 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.voltage_sags_phase_l3 () took 2.699 seconds. Please report platform to the developers at https://goo.gl/Nvioub

jcassee on 23 Feb 2020

2020-02-25 20:40:59 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.ytterdorr () took 23.405 seconds. Please report platform to the developers at https://goo.gl/Nvioub

hbylow on 25 Feb 2020

got one for mobile app running on a Moto G7:

Updating state for device_tracker.xxx_phone (<class 'homeassistant.components.mobile_app.device_tracker.MobileAppEntity'>) took 0.984 seconds. Please report platform to the developers at https://goo.gl/Nvioub

ffcruz85 on 26 Feb 2020

As requested - one for the bom weather sensor:
“Updating state for weather.bom_home () took 0.527 seconds. Please report platform to the developers at https://goo.gl/Nvioub”

Cobertizo on 27 Feb 2020

2020-03-11 23:13:43 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.motion_detected_entity_ago_bathroom_stdev_statistics () took 0.887 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2020-03-11 23:23:24 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for binary_sensor.motion_annotated_bathroom () took 0.456 seconds. Please report platform to the developers at https://goo.gl/Nvioub

dcmartin on 12 Mar 2020

Since 0.109.0.dev i got a message related to the synology camera integration (Currently run 0.109.0.dev20200419):
2020-04-19 13:44:15 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue for synology doing I/O at homeassistant/components/synology/camera.py, line 53: timeout=timeout,
2020-04-19 13:44:17 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue for synology doing I/O at homeassistant/components/synology/camera.py, line 53: timeout=timeout,
2020-04-19 13:44:18 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue for synology doing I/O at homeassistant/components/synology/camera.py, line 53: timeout=timeout,
2020-04-19 13:44:19 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue for synology doing I/O at homeassistant/components/synology/camera.py, line 53: timeout=timeout,
2020-04-19 13:44:19 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue for synology doing I/O at homeassistant/components/synology/camera.py, line 53: timeout=timeout,
2020-04-19 13:44:20 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue for synology doing I/O at homeassistant/components/synology/camera.py, line 53: timeout=timeout,
2020-04-19 13:44:20 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue for synology doing I/O at homeassistant/components/synology/camera.py, line 53: timeout=timeout,

S-Przybylski on 19 Apr 2020

👍1

Dear @balloob
The event loop message Synology camera module do not appear any longer! Semms to be fixed by that! Thanks!

S-Przybylski on 21 Apr 2020

Log Details (WARNING)
Version: 0.109.0b0
Logger: homeassistant.util.async_
Source: util/async_.py:120
First occurred: 7:29:41 (1 occurrences)
Last logged: 7:29:41
Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for smartir doing I/O at custom_components/smartir/__init__.py, line 68: request = requests.get(MANIFEST_URL.format(branch), stream=True, timeout=10)

nhok3296 on 23 Apr 2020

@nhok3296 please report this to the author of the custom component that you are using, as per the message.

balloob on 23 Apr 2020

👍1

Ok

nhok3296 on 23 Apr 2020

May I ask, when you have an inital update that may take some time to complete, what is the best way to do this? for example intial call to update function may take 10sec and after that <1 sec. Is there an override to stop the warnings, or another way?

mcc05 on 14 Jun 2020

This issue is overdue. A lot of fixes have been implemented or not tracked in here anymore.

The log message in Home Assistant has been adjusted a while back and now requests to create a separate issue (which we can assign to the specific integration or codeowner). This is more productive at this point compared to this issue.

So, if you run into an issue as described here, please open up a new, separate issue.

Thanks 👍

frenck on 11 Aug 2020

Core: Platforms that do I/O inside properties

Backstory

Most helpful comment

All 371 comments

Xiaomi temperature and humidity sensor

Platform

Device

Full warning

Execution time: 0.443 seconds

Related issues