ver. 2.1.0 2023/07/15 1:14 PM - the first published experimental version.
ver. 1.0.1 2023/07/16 4:54 PM - (dev. branch) - sideUp # event is now sent before the flipToSide action; added second fingerprint; skipped duplicated 'sideUp' events; added 'throw' action;
You may need several pairing attempts until the cube starts to send action updates to HE .
An indicator of the successful pairing is when the parent router NWK is shown in the State Variables ( you need to press F5 in the browser to update the device web page ) :
I am excited to see someone working on a driver for the Pro Cube. I had similar issues with my C-8 even using the 2 alternative Zigbee pairing methods suggested by Hubitat. I was able to get it to pair to my C-5 hub but the health status doesn't show the parentNWK information:
@stephen_nutt when you hold the pairing button down and the pairing process starts after 3 short blinks of the LED, you can continue pressing shortly the button for a few more seconds, this keeps the device awake.
Second tip: pressing quickly 5 (five) times the button inside the cube switches between the new 'scene' mode and the old 'action' mode (the old mode is not supported yet).
If you successfully change the operation mode, you will see a new state :
I have tried a few times pairing close to hub. "Action" and "operationMode" don't show up in my Current States. When it does pair, it always pairs as a "Device" and I have to change it to use the Cube driver. Yes, I do hit the Configure button afterwards.
Your model seems to be the same as mine, but by some reason it didn't pair successfully on the first time and the inClusters list is wrong.
You must click on the 'REMOVE DEVICE' red button at the bottom of the device web page and pair it again.
The 'Aqara Cube T1 Pro' driver must be automatically selected during the pairing process, otherwise the device will not work.
The specific Aqara initialization 'voodoo' works only when the device is still in Zigbee pairing mode during the initial inclusion, so the automatic selection of this driver is a must.
When you first remove the device and then pair it as a new one, you will have the 'Device Info' button/hyperlink on the HE Zigbee pairing screen. Please make a screenshot of it.
Update: I have published version 2.1.1 were I ave added a second fingerprint matching yours.
The C-3 has probably different Zigbee radio than the C-7 model, so there may be differences...
I was having same issues initially when trying to pair to my C-7 also. It would pair as a "Device". I installed your updated driver on C-7 and it's working!!!! Nice job! Thanx.
There is still a lot of work to be done to complete the driver, but the very good news is that it is working in at least one other environment, different than the development system! : )
'Pushed' - when the cube is flipped on side 3, the color bulb will flash once, denoting that the Cube is in control of this particular device (GLEDOPTO RGBW light strip)
'DoubleTapped' - when the cube is shaken, the light will be toggled on/off
'Held' - start ramping the lights down, wait for 1 second, then stop
'Released' - start ramping the lights up, wait for 1 second, then stop
I will publish my test use scenarios in a day or two, but as I have the Cube only for a few days, it will be interesting to hear from others that have a longer experience.
)
