Platforms that do I/O inside properties #4210
Comments
|
Fixed via #4219 Thanks @pvizeli 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. |
|
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.
|
|
Seeing this behaviour as well with the media_player.sonos component, reporting as requested:
|
|
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 |
|
Here you go - reporting per log request: |
|
Which platform is this? On Sat, Nov 5, 2016, 20:56 olines notifications@github.com wrote:
|
|
I'm getting when connecting to my Honeywell thermostat API. |
|
I´m getting 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 what platform is the lamp? |
|
I am getting the warning on cover.garage_door - it is the "myq" platform, from: http://pastebin.com/qVszax1t |
|
@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 |
|
@balloob It´s a tellstick (not Net) switch |
|
I have a huge number of KNX switches and I'm getting following in the error log (truncated): |
|
@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. |
|
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 |
|
I am getting the warning message on the dark sky weather platform |
|
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 |
|
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' |
|
@bestlibre could you try against #4298 ? |
|
Got a warning about Nut but it actually looks fine. |
|
Running Hass 0.104.3 |
|
Running Hass 0.105.2 | HassOS 3.8 |
|
Came from custom component DreamScreen: Updating state for dreamscreen.dream_screen (<class 'custom_components.dreamscreen.DreamScreenEntity'>) took 0.839 seconds. HA Core: 0.105.2 |
|
I'm getting the warning from the custom meross component : Additionally and maybe related I get this traceback in the meross stuff: HTH |
|
@cabletie that's a problem with the custom component. It's doing I/O inside |
|
|
|
Component: Envisalink Log: |
|
Component: DSMR Sensor (Dutch smart electrical/gass smart meter): |
|
|
|
2020-02-21 11:50:58 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for zone.laid_back_key_west (<class 'homeassistant.components.zone.Zone'>) took 1.989 seconds. Please report platform to the developers at https://goo.gl/Nvioub |
|
Updating state for remote.xiaomi_miio_192_168_1_113 (<class 'homeassistant.components.xiaomi_miio.remote.XiaomiMiioRemote'>) took 0.767 seconds. Please report platform to the developers at https://goo.gl/Nvioub RasPi4 with Hassio installed from the Hass site |
|
Component: VerisureThermometer Updating state for sensor.garage_temperature (<class 'homeassistant.components.verisure.sensor.VerisureThermometer'>) took 0.567 seconds. Please report platform to the developers at https://goo.gl/Nvioub Raspberry Pi 3B, docker |
|
2020-02-23 22:21:30 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.voltage_sags_phase_l3 (<class 'homeassistant.components.dsmr.sensor.DSMREntity'>) took 2.699 seconds. Please report platform to the developers at https://goo.gl/Nvioub |
|
2020-02-25 20:40:59 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.ytterdorr (<class 'homeassistant.components.arlo.camera.ArloCam'>) took 23.405 seconds. Please report platform to the developers at https://goo.gl/Nvioub |
|
got one for mobile app running on a Moto G7:
|
|
As requested - one for the bom weather sensor: |
|
2020-03-11 23:13:43 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.motion_detected_entity_ago_bathroom_stdev_statistics (<class 'homeassistant.components.statistics.sensor.StatisticsSensor'>) took 0.887 seconds. Please report platform to the developers at https://goo.gl/Nvioub |
|
Since 0.109.0.dev i got a message related to the synology camera integration (Currently run 0.109.0.dev20200419): |
|
Dear @balloob |
|
Log Details (WARNING) |
|
@nhok3296 please report this to the author of the custom component that you are using, as per the message. |
|
Ok |
|
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? |
|
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 👍 |
Uh oh!
There was an error while loading. Please reload this page.
If you came here because of a warning in your Home Assistant logs, please check if it is in the list below. If it is not, please add a reply with the brand of the product / platform and the time that it took to execute. Thanks
Platforms that have been reported as slow:
Reported but no suspicious behavior found:
Backstory
When we moved to async we started writing the state of entities to the state machine from within the event loop. This can only work correctly if no platforms or components do any I/O within any property of an entity. Instead, that work should be done inside the update method.
Bad
Good
Although we cannot detect directly if I/O is happening inside a property, we can measure the time it takes us to fetch the properties. If this takes too long, it's probably bad and needs more research. In #4208 I implemented this warning which will redirect users to this issue.
The text was updated successfully, but these errors were encountered: