[Device Support Request] Aqara T1 LED Strip

[jaredhamilton]

Problem description

Light strip is available to add via ZHA directly, however you cannot control the length of the strip. When using extensions on the light strip, standard color temperatures will illuminate the entire strip, however using RGB colors will only illuminate the original strip length, minus the extensions.

It should be noted that there are reports of this strip working with Z2M, though the attributes need to be configured through MQTT. See this thread: https://community.home-assistant.io/t/unable-to-turn-on-extensions-for-aqara-t1-led-strip-zha/650487/4

Solution description

Develop a quirk that includes the strip length attribute.

Screenshots/Video

No response

Device signature

No response

Diagnostic information

No response

Logs

No response

Custom quirk

No response

Additional information

No response

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[lindhe]

I'd love to see this not be stale. I have a T1 LED strip, is there anything I can do to help?

[benjaml4]

I to have a T1 LED strip. Unfortunately I don't have any knowledge of programming quirks. Can someone please take a look at the Zigbee2MQTT handler and see if we can map this to ZHA? It would make it so much better removing my Aqara E1 hub as it's causing interference with my default ZHA hub.

[Menelmacar]

Same here, I've attached two images to illustrate the issue. White Leds work, but the color led doesn't for the extention

[skypyxis]

It would be great to have the ability to use scenes and effects, but these don't appear to be supported with ZHA

[skypyxis]

Additionally: what is the purpose of the 'Transition' setting? It doesn't appear to have any effect. Shouldn't it be used to fade one color into another?

[Ros-One]

Same issue.

Is there anything that can be done to set the device length other than using an Aqara hub or using z2m? I installed the zha-toolkit, but didn't manage to figure it out. I expected to be able to send some write_command and set the length to 3m.

[gafderks]

@Ros-One I managed to get this working.

1. Install ZHA Toolkit in HACS
2. In the Developer Tools run action "ZHA 🧰 Toolkit: Write Attribute" with the following YAML config:

action: zha_toolkit.attr_write
data:
  ieee: [entity]
  attribute: 0x51b
  cluster: 0xfcc0
  manf: 4447
  endpoint: 1
  attr_val: 15

Here, attr_val is the number of segments that the led strip has, which is 10 for the base strip and 5 additional per extension strip.

Edited to note that I found the cluster and the attribute in the zigbee-herdsman-converters repository. There, also the attributes for audio, audio sensitivity, as well as some others are listed, I did not test those.

[gmeye]

@Ros-One I managed to get this working.

1. Install ZHA Toolkit in HACS
2. In the Developer Tools run action "ZHA 🧰 Toolkit: Write Attribute" with the following YAML config:

action: zha_toolkit.attr_write data: ieee: [entity] attribute: 0x51b cluster: 0xfcc0 manf: 4447 endpoint: 1 attr_val: 15 Here, attr_val is the number of segments that the led strip has, which is 10 for the base strip and 5 additional per extension strip.

Edited to note that I found the cluster and the attribute in the zigbee-herdsman-converters repository. There, also the attributes for audio, audio sensitivity, as well as some others are listed, I did not test those.

Can you explain how you got that action to run?

I have ZHA toolkit installed, when I go into developer tools and try to run that action I get the following error: Action zha_toolkit.attr_write not found.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Menelmacar]

Contribute