Error turning on the yeelight bedside lamp d2 after a long period of inactivity

Pro100x3mal commented 4 months ago

The problem

I have automation configured. Every morning at 8.00 the yeelight bedside lamp d2 is turned on with a brightness setting of 5 and a gradual increase to 255. So sometimes the automation doesn’t work and gives an error

2024-02-24 08:00:30.393 ERROR (MainThread) [homeassistant.components.automation.svetovoi_budilnik] Ночник. Световой будильник: Error executing script. Error for call_service at pos 2: Timed out when calling _async_turn_on for bulb Yeelight Bslamp3 0x1243c06d at 192.168.1.130: <class 'TimeoutError'>
2024-02-24 08:00:30.394 ERROR (MainThread) [homeassistant.components.automation.svetovoi_budilnik] Error while executing automation automation.svetovoi_budilnik: Timed out when calling _async_turn_on for bulb Yeelight Bslamp3 0x1243c06d at 192.168.1.130: <class 'TimeoutError'>

Also, after the yeelight device has not been used for a long time (not turned on/off), then when you press the button to turn on the device in HA, it does not turn on, freezes for a few seconds and only then can it be turned on and off. It is often in the "Unavailable" state

My automatization:

alias: Ночник. Световой будильник
description: ""
trigger:
  - platform: time
    at: input_datetime.nachalo_svetovogo_budilnika
condition:
  - condition: state
    entity_id: input_boolean.svetovoi_budilnik
    state: "on"
  - condition: state
    entity_id: light.yeelight_bslamp3_0x1243c06d
    state: "off"
    enabled: true
action:
  - service: automation.turn_off
    metadata: {}
    data:
      stop_actions: true
    target:
      entity_id:
        - automation.lights_yeelight
  - service: light.turn_on
    metadata: {}
    data:
      kelvin: 4000
      brightness_pct: 1
    target:
      entity_id: light.yeelight_bslamp3_0x1243c06d
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - repeat:
      sequence:
        - service: light.turn_on
          metadata: {}
          data:
            kelvin: 4000
            brightness_step: 5
          target:
            entity_id: light.yeelight_bslamp3_0x1243c06d
        - delay:
            hours: 0
            minutes: 0
            seconds: 5
            milliseconds: 0
      until:
        - condition: or
          conditions:
            - condition: state
              entity_id: light.yeelight_bslamp3_0x1243c06d
              state: "off"
              enabled: true
            - condition: template
              value_template: >-
                {{(state_attr('light.yeelight_bslamp3_0x1243c06d',
                'brightness')|int) == 255 }}
          enabled: true
    enabled: true
  - service: automation.turn_on
    metadata: {}
    data: {}
    target:
      entity_id: automation.lights_yeelight
mode: single

What version of Home Assistant Core has the issue?

2024.2.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 4 months ago

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

Code owner commands

Code owners of `yeelight` 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 yeelight` 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)}}

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

Pro100x3mal commented 4 months ago

Here is the detailed log:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:240
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 09:26:16 (1 occurrences)
Last logged: 09:26:16

[546866876736] Timed out when calling _async_turn_on for bulb Yeelight Bslamp3 0x1243c06d at 192.168.1.130: <class 'TimeoutError'>
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/yeelight/aio.py", line 101, in async_send_command
    response = await future
               ^^^^^^^^^^^^
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/yeelight/light.py", line 257, in _async_wrap
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/yeelight/light.py", line 776, in _async_turn_on
    await self._bulb.async_turn_on(
  File "/usr/local/lib/python3.12/site-packages/yeelight/aio.py", line 45, in wrapper
    cmd = await self.async_send_command(
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/yeelight/aio.py", line 100, in async_send_command
    async with asyncio_timeout(TIMEOUT):
  File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 240, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2279, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2316, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 892, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 962, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 628, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/usr/src/homeassistant/homeassistant/components/yeelight/light.py", line 796, in async_turn_on
    await self._async_turn_on(duration)
  File "/usr/src/homeassistant/homeassistant/components/yeelight/light.py", line 263, in _async_wrap
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Timed out when calling _async_turn_on for bulb Yeelight Bslamp3 0x1243c06d at 192.168.1.130: <class 'TimeoutError'>

aaronope commented 3 months ago

This sounds similar to this issue in the HA forums: https://community.home-assistant.io/t/yeelight-not-resposnse/703611

I'm having a similar issue with the Yeelight W1 GU10 White bulbs (non-rgb) - they are fine at first but become unresponsive after some time. I find that the issue can be resolved (temporarily) by triggering a reload via the integration. I've also found a way to trigger the unresponsive state but I'm not sure if it's related or a seperate issue. I'm on Core version 2024.3.0

Here is how I can trigger the unresponsive state:

Bulb is working OK, I can turn off/on fine.
Open Developer tools - Services, and set the following:
- Service: Yeelight: Set mode
- Targets: Choose entity - Bedroom Right (the name I gave my bulb)
- Mode: Moonlight
Select CALL SERVICE
Bulb is now unresponsive
Go to Yeelight Integration, and Reload the integration entry for the bulb
Bulb is now working OK again

I went through the above steps whilst debug logging was enabled in the integration - log attached.

home-assistant_yeelight_2024-03-14T21-12-52.856Z.log

Apologies if this is not the same issue.

Orneeman commented 3 months ago

Hi , I have the same issue ( I am the one who opened the thread in HA community ). I attached my log , looks like the integration got an exception and can not recover .\

Orneeman commented 3 months ago

anyone can help ?

Pro100x3mal commented 3 months ago

@aaronope I confirm. The Yeelight bedside lamp D2 has the same problem. I checked through Services - the problem was confirmed

m4dm4xi commented 2 months ago

I suddenly have this problem as well. The Yeelight ceiling has been working fine for ~4 years and suddenly I am not able to control it via hoimeassistant anymore. There were no changes on the network, I restarted the lamp, I restarted the router. I am not able to bring it back to life...

Logger: homeassistant.components.websocket_api.http.connection Quelle: components/websocket_api/commands.py:239 Integration: Home Assistant WebSocket API (Dokumentation, > Probleme) Erstmals aufgetreten: 16:14:52 (3 Vorkommnisse) Zuletzt protokolliert: 16:41:32

[546767784768] Timed out when calling _async_turn_on for bulb Yeelight Ceiling3 0x5eb901a at 192.168.xxx.xxx: <class 'TimeoutError'> [546932896448] Timed out when calling _async_turn_on for bulb Yeelight Ceiling3 0x5eb901a at 192.168.xxx.xxx: <class 'TimeoutError'> Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/yeelight/aio.py", line 101, in async_send_command response = await future ^^^^^^^^^^^^ asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/yeelight/light.py", line 257, in _async_wrap return await func(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/yeelight/light.py", line 776, in _async_turn_on await self._bulb.async_turn_on( File "/usr/local/lib/python3.12/site-packages/yeelight/aio.py", line 45, in wrapper cmd = await self.async_send_command( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/yeelight/aio.py", line 100, in async_send_command async with asyncio_timeout(TIMEOUT): File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in aexit raise TimeoutError from exc_val TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 239, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2543, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2580, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/adaptive_lighting/hass_utils.py", line 62, in service_func_proxy await existing_service.job.target(call) File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 971, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1043, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 631, in async_handle_light_on_service await light.async_turn_on(**filter_turn_on_params(light, params)) File "/usr/src/homeassistant/homeassistant/components/yeelight/light.py", line 796, in async_turn_on await self._async_turn_on(duration) File "/usr/src/homeassistant/homeassistant/components/yeelight/light.py", line 263, in _async_wrap raise HomeAssistantError( homeassistant.exceptions.HomeAssistantError: Timed out when calling _async_turn_on for bulb Yeelight Ceiling3 0x5eb901a at 192.168.xxx.xxx: <class 'TimeoutError'>

ilvi80 commented 2 months ago

I confirm the problem. Yeelight GU10 Smart Bulb (Multicolor) lamps have stopped responding (reacting) in HA. At the same time, they work through the Yeelight application.

This problem did not exist before; the equipment configuration did not change. Core 2024.4.3 Supervisor 2024.04.0 Operating System 12.2 User interface 20240404.2

Orneeman commented 2 months ago

`2024-04-26 17:21:17.008 DEBUG (MainThread) [homeassistant.components.yeelight.light] Calling <function YeelightBaseLight._async_turn_off at 0x989ce398> with (350,) {} 2024-04-26 17:21:17.010 DEBUG (MainThread) [homeassistant.components.yeelight.light] Calling <function YeelightBaseLight._async_turn_off at 0x989ce398> with (350,) {} 2024-04-26 17:21:17.015 DEBUG (MainThread) [homeassistant.components.yeelight.light] Calling <function YeelightBaseLight._async_turn_off at 0x989ce398> with (350,) {} 2024-04-26 17:21:17.017 DEBUG (MainThread) [homeassistant.components.yeelight.light] Calling <function YeelightBaseLight._async_turn_off at 0x989ce398> with (350,) {} 2024-04-26 17:21:17.025 DEBUG (MainThread) [homeassistant.components.yeelight.light] Calling <function YeelightBaseLight._async_turn_off at 0x989ce398> with (350,) {} 2024-04-26 17:21:25.073 DEBUG (MainThread) [homeassistant.components.yeelight.device] Received callback: {'power': 'off', 'connected': True} 2024-04-26 17:21:32.011 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall light.turn_off (c:01HWDCFW5EN8BPRNXXNAZ2FCD1): entity_id=['light.yeelight_monob_0x1b41c622'], params=> Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/yeelight/aio.py", line 101, in async_send_command response = await future ^^^^^^^^^^^^ asyncio.exceptions.CancelledError