class 'homeassistant.components.ibeacon.sensor.IBeaconSensorEntity' took 1.928 seconds. Please create a bug report

tedrudie commented 8 months ago

The problem

My home assistant locks up daily. I suspect it has something to do with traccar. But, reading through the log.1file, I find this (probably unrelated) message:

2024-02-04 10:17:45.504 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.gvh5075_8c12_estimated_distance (<class 'homeassistant.components.ibeacon.sensor.IBeaconSensorEntity'>) took 1.928 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+ibeacon%22 2024-02-04 10:26:50.663 WARNING (Thread-2 (_thread_main)) [homeassistant.components.mqtt.client] Disconnected from MQTT server 192.168.20.25:1883 (16)

These are the final lines in homeassistant.log.1 before crashing.

What version of Home Assistant Core has the issue?

core-2024.1.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

unknown

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-02-04 03:30:05.506 INFO (MainThread) [custom_components.hacs] Loading known repositories
2024-02-04 06:00:00.077 INFO (MainThread) [homeassistant.components.automation.morning_lights] Morning Lights: Running automation actions
2024-02-04 06:00:00.078 INFO (MainThread) [homeassistant.components.automation.morning_lights] Morning Lights: Executing step call service
2024-02-04 06:48:03.719 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.samsung_6_series_50 is taking over 10 seconds
2024-02-04 06:48:03.721 WARNING (MainThread) [homeassistant.components.media_player] Updating samsungtv media_player took longer than the scheduled update interval 0:00:10
2024-02-04 07:38:12.151 INFO (MainThread) [homeassistant.components.automation.morning_off] Morning Off: Running automation actions
2024-02-04 07:38:12.151 INFO (MainThread) [homeassistant.components.automation.morning_off] Morning Off: Executing step call service
2024-02-04 07:38:12.153 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities light.back_porch_light are missing or not currently available
2024-02-04 09:30:00.439 INFO (MainThread) [homeassistant.components.automation.roomba_run] Roomba Run: Running automation actions
2024-02-04 09:30:00.439 INFO (MainThread) [homeassistant.components.automation.roomba_run] Roomba Run: Executing step device automation
2024-02-04 09:30:00.446 INFO (MainThread) [homeassistant.components.automation.roomba_run] Roomba Run: Executing step delay 1:30:00
2024-02-04 09:30:05.507 INFO (MainThread) [custom_components.hacs] Loading known repositories
2024-02-04 09:30:06.382 INFO (MainThread) [homeassistant.components.analytics] Submitted analytics to Home Assistant servers. Information submitted includes {'uuid': 'a60d8fda24e247bdbd7fcd4690ec1530', 'version': '2024.1.6', 'installation_type': 'Home Assistant Supervised', 'supervisor': {'healthy': True, 'supported': True, 'arch': 'aarch64'}, 'certificate': False, 'integrations': ['camera', 'automation', 'input_text', 'logger', 'mqtt', 'govee_ble', 'zone', 'default_config', 'scene', 'dlna_dms', 'stream', 'timer', 'http', 'venstar', 'sun', 'notify', 'frontend', 'mobile_app', 'input_number', 'ibeacon', 'roomba', 'hassio', 'person', 'bluetooth', 'icloud', 'script', 'input_boolean', 'unifi', 'input_select', 'device_tracker', 'samsungtv', 'dlna_dmr'], 'custom_integrations': [{'domain': 'hacs', 'version': <AwesomeVersion SemVer '1.34.0'>}, {'domain': 'webrtc', 'version': <AwesomeVersion SemVer '3.5.1'>}, {'domain': 'frigate', 'version': <AwesomeVersion SemVer '5.0.0'>}], 'addons': [{'slug': 'ccab4aaf_frigate-proxy', 'protected': True, 'version': '1.4', 'auto_update': False}, {'slug': 'core_mosquitto', 'protected': True, 'version': '6.4.0', 'auto_update': False}, {'slug': 'core_ssh', 'protected': True, 'version': '9.8.1', 'auto_update': False}, {'slug': 'c7657554_double-take-proxy', 'protected': True, 'version': '1.0.0', 'auto_update': False}, {'slug': 'core_mariadb', 'protected': True, 'version': '2.6.1', 'auto_update': False}, {'slug': 'a0d7b954_traccar', 'protected': True, 'version': '0.25.0', 'auto_update': False}], 'energy': {'configured': False}, 'recorder': {'engine': 'sqlite', 'version': <AwesomeVersion SimpleVer '3.41.2'>}}
2024-02-04 09:35:39.451 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take kitchen, sending update
2024-02-04 09:39:21.369 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take kitchen, sending update
2024-02-04 09:41:44.620 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.samsung_6_series_50 is taking over 10 seconds
2024-02-04 09:41:44.620 WARNING (MainThread) [homeassistant.components.media_player] Updating samsungtv media_player took longer than the scheduled update interval 0:00:10
2024-02-04 09:47:10.193 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: device_tracker double-take ted, sending update
2024-02-04 09:47:10.199 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take ted, sending update
2024-02-04 09:47:10.207 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take kitchen, sending update
2024-02-04 09:49:09.066 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take kitchen, sending update
2024-02-04 09:55:27.259 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take kitchen, sending update
2024-02-04 09:55:45.869 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take kitchen, sending update
2024-02-04 09:59:55.786 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take kitchen, sending update
2024-02-04 10:02:48.653 WARNING (Thread-3 (_thread_main)) [roombapy.roomba] Unexpectedly disconnected from Roomba 192.168.20.27, code The connection was lost
2024-02-04 10:02:53.075 INFO (Thread-3 (_thread_main)) [roombapy.roomba] Connecting to Roomba 192.168.20.27
2024-02-04 10:05:15.909 WARNING (MainThread) [async_upnp_client.profiles.profile] Failed subscribing to service: UpnpConnectionError('ClientConnectorError(ConnectionKey(host=\'192.168.20.57\', port=9197, is_ssl=False, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=4313332024716888740), ConnectionRefusedError(111, "Connect call failed (\'192.168.20.57\', 9197)"))', None)
2024-02-04 10:12:50.505 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: device_tracker double-take ted, sending update
2024-02-04 10:12:50.511 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take ted, sending update
2024-02-04 10:12:50.518 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take kitchen, sending update
2024-02-04 10:17:45.504 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.gvh5075_8c12_estimated_distance (<class 'homeassistant.components.ibeacon.sensor.IBeaconSensorEntity'>) took 1.928 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+ibeacon%22
2024-02-04 10:26:50.663 WARNING (Thread-2 (_thread_main)) [homeassistant.components.mqtt.client] Disconnected from MQTT server 192.168.20.25:1883 (16)

Additional information

No response

home-assistant[bot] commented 8 months ago

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (ibeacon) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `ibeacon` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign ibeacon` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

ibeacon documentation ibeacon source _{^{(message by IssueLinks)}}

bdraco commented 5 months ago

Its likely you have an integration blocking the event loop

Install profiler integration https://my.home-assistant.io/redirect/config_flow_start/?domain=profiler
Enable asyncio debug service as soon as possible after startup https://www.home-assistant.io/integrations/profiler/#service-profilerset_asyncio_debug
Watch logs for RuntimeError: Non-thread-safe operation and long asyncio delays
Download and post logs with full trace

For 2024.5.x and later Home Assistant debug mode can also be enabled in configuration.yaml

homeassistant:
  debug: true

bdraco commented 2 months ago

Closing due to no response

home-assistant / core