I would do this paired and with my event sensor running so that you know what mode itās in, but this instruction is what the manual says for the cube and has always worked for meā¦
https://github.com/SirGoodenough/HA_Blueprints/blob/06da5f1a0fe0a6bcbc4cafcd60d58dc6b1d9bd33/Automations/ZHA-Xiaomi_Cube_Controller.md#--hardware-versions.
thanks for the fast answer. I found the Solution. You need to first give up 
After sync, i just let the cube alone for half an hour. Then i pressed the button shortly. Pretty sure that this was not important. I think the soulution is to wait a long while after sync. 5 Mins was for sure not enough.
1 Like
Hi!
I have the Cube T1 Pro (connceted with ZHA and skyconncet).
My aqara can shake and rotate, filp, slide but canāt knock.
I should be in the right mode (if i change mode i can only rotate and shake).
Sometimes if you don.t delay long enough between moves, the move wonāt register. make sure there is a 1 or 2 second pause right before the knock.
Plus you have to be doing the knock right. Thereās a video above of how to do it.
Finally id you add the event sensor and put the sensor entity on your dashboard, you will see what the blueprint thinks your move was. That will help with training.
Foe ZHA figuring out the mode is a pain. Yoyu probably have to look at the zha events or in the lohistory for the device to see if scene or action mode.
thanks for your advices.
Iāve try to wait but i canāt still knock.
Iāve also try to update the firmware of skyconnect but nothing changed.
Is it normal that i see all the move in the regiter as āface anyā. It canāt detect (for example) slice face 1, slice face 2, ecc.
I could try buing another dice but i think is my configuration the problem
If you would like to read my instructions again, Iām sure this is the problemā¦
Put it into action mode, it is the only mode that works properly on ZHA and the people that set-up the zigpy device registry have not made a proper interview device for this cube. Complaints would need to be registered thereā¦
(It all works fine in Z2M, BTW)
The T1 pro Cube is missing new functions that are available in the device. Ā· Issue #2145 Ā· zigpy/zha-device-handlers Ā· GitHub. to thumb up this to possibly get this fixedā¦
1 Like
Thank you again. I thought that listening the event from ZHA was fine.
In the dev tool i see the face of the dice and i was able to see a knock too
But only one (i wasnāt able to repruduce it).
I havenāt find the video that show how to knock the dice (iāll try again).
Thanks again
I was looking at @Hybrego 's issue - and mine sounds very similar. I believe Iāve swapped to Action mode, as triggering 5 presses alters the behavior - no flips will register in the events.
Iāve re-read your comments, but my understanding is that Scene mode would only reflect rotate & knock, not the slide/flip which we currently see?
Iāve also posted to the subreddit, if the signature would be hlepful. https://www.reddit.com/r/homeassistant/comments/18u86ke/aqara_t1_cube_faces/
When I view the trace -
And the event log, due to new-user upload limits:
Are you using my blueprint? Those logbook entries donāt look familiar.
Also I recommend only the action mode for ZHA. The interview profile is too far off for the scene mode to be functional in ZHA. There is a link above to the zigpy issue asking for this to be fixed and I would appreciate everyone giving it a thumbs up or finding someone that can figure out how to change the interview for this cube. Scene mode on this cube is broken, and the action mode is handicapped with a couple of functions missing and a couple of others not available.
It really only works properly in Z2M.
Well, feeling dumb. User Error.
I was 100% using your blueprint at the end - but I had loaded at least 4-5 others during testing of various issues. Reloading my configs, issue resolved - yours fires events as set up.
The Logbook still only shows the āface anyā event, but the correct changes occur.
As the docs say, you can add the template sensor and pull that sensor to the dashboard to see what the blueprint thinks is happening real time. It helps a lot when setting things up.
I canāt get tis working
template:
- trigger:
- platform: event
event_type: cube_last_action - platform: event
event_type: zha_cube_last_action
sensor: - name: āCube Last Actionā
unique_id: cubelastaction
icon: mdi:eye-refresh-outline
attributes:
friendly_name: āCube Actionā
state: >
{{ trigger.event.data.friendly_name }} -
{{ trigger.event.data.action }} -
{{ trigger.event.data.side }} frm
{{ trigger.event.data.last_side }}Preformatted text
- platform: event
state unavailable what do I need to do to fix this sensor code
Perhaps could you edit that for me do lit looks like it does on your screen?
It may be a matter of indenting or something.
How to help us help you - or How to ask a good question.
It should be looking exactly like this, and Iām thinking you have sensor: indented wrong.
HA_Blueprints/Samples/Cube_Last_Action_Template_Trigger_SAMPLE.yaml at c05d6fb431c1d84cb145c7d6dd5ffe5a60b1d9e2 Ā· SirGoodenough/HA_Blueprints Ā· GitHub.
thanks but I tried to put that code in my templates.yaml and got errors so I download your yaml file and uploaded it to home assistant folder it creates sensor but still says unavailable ill keep trying I would love this working maybe ive miss something
According to what you have above, you did not copy it correctly. The indentation is off, and this is very important.
See what mine in my working config file looks like:
Home-Assistant-Config/templates/trigger/ZHA Cube Last Action.yaml at d0068d87b4036406bb6a19d257bf6cf695331c85 Ā· SirGoodenough/Home-Assistant-Config Ā· GitHub.
I canāt help you id you donāt copy the stuff I give you correctly.
Just wanted to type out an appreciation for this helper/automation. Worked great, really enjoy.
Thank you for this.
1 Like
NEW VERSION available today
Changelog
- 2024-06-04: Blueprint Input Sections for enhanced Descriptions.
Hi
First a HUGE thank you to you Sir_Goodenough for all the time & effort you have put in and for sharing this great blueprint!
Second, Im not sure if its me, but the blueprint lists actions for faces 0 to 5ā¦ it took me a long time to realise that my cube is numbered like a dice : 1 through 6ā¦ so I was testing with an automation on āside 5ā and nothing was workingā¦ but then realised in fact āside 5ā in the blueprint actually refers to my cube with dice number 6!! Hope this may help someone in the futureā¦
Thanks
James
1 Like