Zigbee Home Automation (ZHA) - Aqara T1 Pro Cube - Only Shake and Rotate Events Triggering #84301
Comments
|
Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
|
can you please share your diagnostic info for the device? The one I have is working:
|
|
Attached please find my device info, ZHA events, and logbook |
|
Can you please share the diagnostic file from the device page. It’s in the 3 dots menu |
|
Also, wake the device up by shaking it and try the reconfiguration in the 3 dots menu as well |
|
Hi- Here is the file you requested. I also tried reconfiguration which showed green but still did not activate the flips, slide, knock actions. SD { |
|
Same here :( |
|
I'm also having a similar issue. In my case, my log book is empty but shaking and rotating instead turn on and off all the zigbee connected devices without any automation instructions. { |
|
I also have the same problem. { |
|
I will post diagnostics here as well if needed but just wanted to chime in that I'm having the same problem. However, I can only register device shaken events. Battery is "unknown" as well, not sure if that matters.. |
|
I recently bought an Aqara Cube T1Pro, and mine seems to have even fewer clusters, and the signature doesn't even match the signature: {
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0103",
"in_clusters": [
"0x0000",
"0x0003",
"0x0006"
],
"out_clusters": [
"0x0000",
"0x0003"
]
}
},
"manufacturer": "LUMI",
"model": "lumi.remote.cagl02",
"class": "zigpy.device.Device"
}diagnostics: {
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2022.12.8",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.10.7",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Amsterdam",
"os_name": "Linux",
"os_version": "5.15.76-v8",
"supervisor": "2022.12.1",
"host_os": "Home Assistant OS 9.4",
"docker_version": "20.10.19",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"auto_backup": {
"version": "1.3.0",
"requirements": []
},
"lightwave": {
"version": "2.2.0",
"requirements": [
"lightwave==0.20"
]
},
"hacs": {
"version": "1.29.0",
"requirements": [
"aiogithubapi>=22.10.1"
]
}
},
"integration_manifest": {
"domain": "zha",
"name": "Zigbee Home Automation",
"config_flow": true,
"documentation": "https://www.home-assistant.io/integrations/zha",
"requirements": [
"bellows==0.34.5",
"pyserial==3.5",
"pyserial-asyncio==0.6",
"zha-quirks==0.0.89",
"zigpy-deconz==0.19.2",
"zigpy==0.52.3",
"zigpy-xbee==0.16.2",
"zigpy-zigate==0.10.3",
"zigpy-znp==0.9.2"
],
"usb": [
{
"vid": "10C4",
"pid": "EA60",
"description": "*2652*",
"known_devices": [
"slae.sh cc2652rb stick"
]
},
{
"vid": "1A86",
"pid": "55D4",
"description": "*sonoff*plus*",
"known_devices": [
"sonoff zigbee dongle plus v2"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "*sonoff*plus*",
"known_devices": [
"sonoff zigbee dongle plus"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "*tubeszb*",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "*tubeszb*",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "*zigstar*",
"known_devices": [
"ZigStar Coordinators"
]
},
{
"vid": "1CF1",
"pid": "0030",
"description": "*conbee*",
"known_devices": [
"Conbee II"
]
},
{
"vid": "10C4",
"pid": "8A2A",
"description": "*zigbee*",
"known_devices": [
"Nortek HUSBZB-1"
]
},
{
"vid": "0403",
"pid": "6015",
"description": "*zigate*",
"known_devices": [
"ZiGate+"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "*zigate*",
"known_devices": [
"ZiGate"
]
},
{
"vid": "10C4",
"pid": "8B34",
"description": "*bv 2010/10*",
"known_devices": [
"Bitron Video AV2010/10"
]
}
],
"codeowners": [
"@dmulcahey",
"@adminiuga",
"@puddly"
],
"zeroconf": [
{
"type": "_esphomelib._tcp.local.",
"name": "tube*"
},
{
"type": "_zigate-zigbee-gateway._tcp.local.",
"name": "*zigate*"
},
{
"type": "_zigstar_gw._tcp.local.",
"name": "*zigstar*"
}
],
"dependencies": [
"file_upload"
],
"after_dependencies": [
"onboarding",
"usb",
"zeroconf"
],
"iot_class": "local_polling",
"loggers": [
"aiosqlite",
"bellows",
"crccheck",
"pure_pcapy3",
"zhaquirks",
"zigpy",
"zigpy_deconz",
"zigpy_xbee",
"zigpy_zigate",
"zigpy_znp"
],
"is_built_in": true
},
"data": {
"ieee": "**REDACTED**",
"nwk": 55359,
"manufacturer": "LUMI",
"model": "lumi.remote.cagl02",
"name": "LUMI lumi.remote.cagl02",
"quirk_applied": false,
"quirk_class": "zigpy.device.Device",
"manufacturer_code": 4447,
"power_source": "Battery or Unknown",
"lqi": 207,
"rssi": -68,
"last_seen": "2023-01-03T11:32:09",
"available": true,
"device_type": "EndDevice",
"signature": {
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0103",
"in_clusters": [
"0x0000",
"0x0003",
"0x0006"
],
"out_clusters": [
"0x0000",
"0x0003"
]
}
}
},
"active_coordinator": false,
"entities": [
{
"entity_id": "button.lumi_lumi_remote_cagl02_identify",
"name": "LUMI lumi.remote.cagl02"
},
{
"entity_id": "switch.lumi_lumi_remote_cagl02_switch",
"name": "LUMI lumi.remote.cagl02"
}
],
"neighbors": [],
"routes": [],
"endpoint_names": [
{
"name": "ON_OFF_LIGHT_SWITCH"
}
],
"user_given_name": null,
"device_reg_id": "6f9251be0d6c6861aa68d65c430e1744",
"area_id": "roberts_kamer",
"cluster_details": {
"1": {
"device_type": {
"name": "ON_OFF_LIGHT_SWITCH",
"id": 259
},
"profile_id": 260,
"in_clusters": {
"0x0000": {
"endpoint_attribute": "basic",
"attributes": {
"0x0004": {
"attribute_name": "manufacturer",
"value": "LUMI"
},
"0x0005": {
"attribute_name": "model",
"value": "lumi.remote.cagl02"
}
},
"unsupported_attributes": {}
},
"0x0003": {
"endpoint_attribute": "identify",
"attributes": {},
"unsupported_attributes": {}
},
"0x0006": {
"endpoint_attribute": "on_off",
"attributes": {},
"unsupported_attributes": {}
}
},
"out_clusters": {
"0x0000": {
"endpoint_attribute": "basic",
"attributes": {},
"unsupported_attributes": {}
},
"0x0003": {
"endpoint_attribute": "identify",
"attributes": {},
"unsupported_attributes": {}
}
}
}
}
}
} |
|
I am also having similar issues with the T1 Pro cube. |
|
Same thing with mine as well, described above. |
|
Did you see zigpy/zha-device-handlers#1975 (comment)? |
|
Yah but I can't that fix to work. Need more context on how to do it. Do you remove device and then add back in, etc. |
|
Same problem here, also the responsiveness and the accuracy of the event is not really accurate. |
|
Same here. Shake is the only consistent event. I also noticed that using developer tools or node red to look at zha_events, even when turn events show in the log book, nothing comes through in the dev tools. |
|
I left it alone overnight... now all the events are coming through in Node Red. Fun times... |
|
I can't get my cube to expose any entities except the identify button and battery sensor. |
Are you using ZHA? Could you please check integration logs if events are available there? Thanks! |
|
Yes, I'm using ZHA and if you are referring to the Log Book, yes they are. |
Not for me :( |
I solved the problem, I found into another thread that the cube can operate in 2 different modes. To switch those modes, just to press fast 5 times the cube pairing button (no blink or other notification) but immediately the cube started to work as expected and to send events to HA. Only the battery indicator is still unknown. |
|
Yeah, I tried that several times. It seemed very non-deterministic. I saw no immediate change in events from the cube. In fact sometimes, the cube stopped responding at all! I'm sure doing something like that ultimately caused it to work properly, but I can't tell you exactly what it was. |
I noted that operating the cube on sofa (not really a flat solid surface) the cube doesn’t work while on a desk, flat and solid surface, all the commands are quite responsive at the moment. I’ll keep posted if the device goes in sleep mode in the next days/hours. Maybe this is not the case but it looks that internal sensors/algorithm are not capable to interpret more than on trigger at the same time like rotation on a slant surface). |
That works for me too. Thanks! |
This does not appear to be working; at least not for me. I press the pairing button 5 times, at different "fast" tempos, but the cube does not seem to change its operation mode or start sending data to the zha_event listener. Also after each 5 presses, shaking the cube continues to turn off and on all of the ZigBee lights/plugs/switches connected to the controller and does not send data to ZHA. There are no Zigbee Groups setup with this Cube as a member. The cube does not show that is bound (binding) to any specific device or group. I can't find any documentation on pressing the button 5 times changing the operation mode. Only information I'm able to find indicates that it has to be done via the Aqara App, and only way to get the cube into the Aqara App is via an Aqara Hub. Well, not going to buy a hub just to switch the mode. I don't see a benefit in the T1 Cube vs the original version; since you can't use the different operation modes in Home Assistant. Also the cube sides appear to be in a difference sequence. On the original cube (non T1), Side 2 was to the right, and Side 5 is to the left of the side with the "Aqara" logo w/ Side 4 having the access door to the battery/button. On the T1 Cube, Sides 4 & 3 are to the left/right of the "Aqara" logo, w/ Side 6 having the access door. At this point the cube is nothing more than an overpriced "Kill Switch" to turn off every light/switch/plug in the house at once.... |
|
For anyone having trouble, try updating your ZigBee coordinator firmware. See my comment here. |
|
Same problem here. The Cube is recognised as an On/Off switch (see config) "data": { |
|
Thanks! I did find your posts. Good point - I didn't include the hub - it's a Conbee II stick. Updating the firmware sounds like a real pain but I might give it try but I'm all Mac here and from what I've read updating on the Pi is fraught with danger. Or maybe I'll just buy a Sonoff. Or an M2 hub. You can never have enough hubs! |
|
I don't have a Conbee stick nor am I familiar with the drivers/software but this guy updates the firmware on a Conbee stick directly on a Pi without much difficulty. If you do attempt this from the Pi, ensure you stop ALL services that might be using the Conbee stick (ex: HomeAssistant, Zigbee2MQTT) before starting the update process. |
|
Hello, i did not read the whole post here but i would like to change the mode form the Cube. I read something like push the reset button 5x times but it seems that i does not work for me. What i miss are triggers for the new scene mode like flip90 or flip180. Is there a solution how to change the mode? |
|
Same for me. Click 5 times and an update of Sonoff Zigbee Dongle-E does not help =( Diagnostics |
|
I updated my ConBee II from an older firmware to 0x26780700 on my Windows PC, and did the 5 quick clicks, and after it was working. Thanks to zigpy/zha-device-handlers#1975 (comment) |
|
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. |
issue-triage-workflows
bot
closed this as not planned
and others
The problem
The Aqara T1 Pro Cube supports multiple actions/modes. When added into Aqara app I can verify that is detects all events: knock, flip, rotate, slide, shake. However, when I delete from app and add device via ZHA....it will bind it but only detect a subset of events. In the logbook on the device page in HA I can see the rotate and shake events trigger but not the flip event. I confirmed this in developer tools by attempting to listen to ZHA events.
What version of Home Assistant Core has the issue?
2022.12.7
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
ZHA
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?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: