ZB-CL01 Bulbs with ZHA - constantly reconnecting

jane-t · June 23, 2023, 8:19am

I am running 2023.6.2 with a SkyConnect for Zigbee
I have just purchased a pack of 3 ZB-CL01eWeLink light blubs.
They are all behaving in the same way when connected. Turning them on they flash and can easily be added to Skyconnect. They work for around 5-10 minutes, then flash again drop the connection to HA and then reconnect but will not respond to commands, eventually they will drop off completely.

It is almost as if they are not holding the connection and reverting to connection mode.

I found an old closed issue, which seems similar, but it did not have a resolution.

github.com/home-assistant/core

ewelight ZB-CL01 bulb will not turn off

opened 08:24PM - 10 Sep 22 UTC

closed 11:06PM - 03 Jan 23 UTC

arfletcher

integration: zha stale

### The problem I have 3 ewelight ZB-CL01 bulbs that will no longer turn off vi…a the zha integration. It used to work a few months ago. The only changes are Home Assistant updates. I have the bulbs listed in a panel on my dashboard. Click the button to tuen if off...... and at the next poll the button turns again correctly indicating that the buld state never changed. I have connected one bulb to zigbee2mqtt and the bulb acts correctly. I have sent custom ZigBee commands via ZHA and, again, the bulbs turn off: alias: turn off lamp post sequence: - service: zha.issue_zigbee_cluster_command data: ieee: 00:12:4b:00:22:1d:aa:33 endpoint_id: 1 cluster_id: 6 cluster_type: in command: 0 command_type: server I use the Silicon Labs combo HUSBZB-1 USB stick. See logs below ### What version of Home Assistant Core has the issue? 2022.8.1 ### What was the last working version of Home Assistant Core? 2022.5.1 ### What type of installation are you running? Home Assistant Container ### Integration causing the issue zha ### Link to integration documentation on our website https://www.home-assistant.io/integrations/zha/ ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt In the homeasssiatnt.log I see 2022-09-10 16:05:15.546 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0500]: failed to get attributes '['zone_state']' on 'ias_zone' cluster: 2022-09-10 16:05:15.546 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0500]: async_initialize: all attempts have failed: [DeliveryError('[0x160e:1:0x0500]: Message send failure'), DeliveryError('[0x160e:1:0x0500]: Message send failure'), DeliveryError('[0x160e:1:0x0500]: Message send failure'), TimeoutError()] 2022-09-10 16:05:16.393 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0702]: failed to get attributes '['instantaneous_demand', 'current_summ_delivered', 'status']' on 'smartenergy_metering' cluster: 2022-09-10 16:05:16.393 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('[0x160e:1:0x0702]: Message send failure'), DeliveryError('[0x160e:1:0x0702]: Message send failure'), DeliveryError('[0x160e:1:0x0702]: Message send failure'), TimeoutError()] 2022-09-10 16:05:16.395 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0006]: 'async_initialize' stage succeeded 2022-09-10 16:05:16.395 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0008]: 'async_initialize' stage succeeded 2022-09-10 16:05:16.396 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0702]: 'async_initialize' stage succeeded 2022-09-10 16:05:16.396 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0003]: 'async_initialize' stage succeeded 2022-09-10 16:05:16.396 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0000]: 'async_initialize' stage succeeded 2022-09-10 16:05:16.396 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0500]: 'async_initialize' stage succeeded 2022-09-10 16:05:16.396 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x160E:1:0x0019]: 'async_initialize' stage succeeded 2022-09-10 16:05:16.396 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x160E](E13-N11): power source: Mains 2022-09-10 16:05:16.396 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x160E](E13-N11): completed initialization 2022-09-10 16:05:17.165 DEBUG (MainThread) [homeassistant.components.zha.entity] light.ewelight_zb_cl01_01_level_light_color_on_off: setting transitioning flag to True 2022-09-10 16:05:17.226 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x6B2F:1:0x0008]: executed 'move_to_level_with_on_off' command with args: '(0, 0)' kwargs: '{}' result: Default_Response(command_id=4, status=<Status.INVALID_VALUE: 135>) 2022-09-10 16:05:17.227 DEBUG (MainThread) [homeassistant.components.zha.entity] light.ewelight_zb_cl01_01_level_light_color_on_off: starting transitioning timer for 0.25 2022-09-10 16:05:17.227 DEBUG (MainThread) [homeassistant.components.zha.entity] light.ewelight_zb_cl01_01_level_light_color_on_off: turned off: Default_Response(command_id=4, status=<Status.INVALID_VALUE: 135>) 2022-09-10 16:05:17.478 DEBUG (MainThread) [homeassistant.components.zha.entity] light.ewelight_zb_cl01_01_level_light_color_on_off: transition complete - future attribute reports will write HA state ``` ### Additional information _No response_

Any ideas before I return them?

Nick4 · June 23, 2023, 8:23am

Hi, do you have other zigbee devices and are those working well?

jane-t · June 23, 2023, 9:52am

Thanks for replying.

Yes, the other 20 or so devices work fine. I am reasonably sure it is just these bulbs, but am not sure how to go about tracking the problem, or just send them back and try another brand.

kp1602 · August 16, 2023, 10:13am

I have 2 of these devices too, with the exact same behaviour. Did you manage to find any resolution?

jane-t · August 16, 2023, 1:21pm

Sent them back for a refund.