šŸ§Æ ZHA - Xiaomi Cube Controller

Blueprints Exchange
, , ,
38

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

image
image801Ɨ621 34.5 KB

39

If you would like to read my instructions again, Iā€™m sure this is the problemā€¦

https://github.com/SirGoodenough/HA_Blueprints/blob/241faf3e5f7438eeeb9af0e9c1cc0eda53180f08/Automations/ZHA-Xiaomi_Cube_Controller.md#--hardware-versions.

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
40

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

image
image1143Ɨ533 20.2 KB

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

41

šŸ§Æ ZHA - Xiaomi Cube Controller.

Direct link

42

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 -

image
image915Ɨ1241 96.6 KB

43

And the event log, due to new-user upload limits:
image

44

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.

45

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.
image

image
image871Ɨ411 45.8 KB

46

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.

47

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

state unavailable what do I need to do to fix this sensor code

48

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.

49

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

Developer_Tools_ā€“_Home_Assistant
Developer_Tools_ā€“_Home_Assistant1092Ɨ700 75.7 KB

50

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.

51

Just wanted to type out an appreciation for this helper/automation. Worked great, really enjoy.

Thank you for this.

1 Like
52

NEW VERSION available today

:bookmark_tabs: Changelog

  • 2024-06-04: Blueprint Input Sections for enhanced Descriptions.
53

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

2 Likes
54

Like @inghaj mentioned, the Cube T1 Pro has dice face number markings printed on to each face of the cube.
image
These markings are different to the face numbers defined in this blueprint. This easily leads to confusion when setting up automations with this blueprint and the Cube T1 Pro, since all the side number actions have to be translated from the blueprintā€™s number to the cubeā€™s printed number.

It would be great if this blueprint could be updated to support the correct face numbers as marked on the Cube T1 Pro. I imagine this would need to be a configuration to optionally enable alternate cube face numbering, so that existing automations are unaffected.

The faces on the cube are marked like this:

Cube T1 Pro Marking Blueprint Face Number
Logo (1) 0
2 1
3 2
4 3
5 4
6 5

Iā€™ve raised this as an issue on your GitHub repo too for tracking.

55

This is on my list of fix items, Or I think it is.
Feel free to add an issue in my GitHub for it if it isnā€™t, as I plan to look at it.
Then I canā€™t forget it (again) and during a major overhaul is the time.

2 Likes
56

Hi there, this page has been very handy, thank you! I have managed to get the cube paired, Iā€™ve changed mode so that rotate, slide etc work. Iā€™ve using blueprint and dimmer script to have side 0 (with logo) control a light group or individual light (I selected the entity but did try area and other ways to pick the lights).

The dimmer does work when I rotate counter clockwise but it also dims when I rotate clockwise. So, it just ends up turning the lights offā€¦ any suggestions?

Other actions like Knock seem to turn on and off lights etc just fine but increasing brightness with a clockwise rotation using your brightness script doesnā€™t seem to work for me.

Thanks in advance!

57

Hello ganonderp,
Welcome to the Home Assistant Forum and Thanks for choosing my Blueprint.

Show me the cw and ccw inputs you built in your automation for these commands (or your whole automation is fine as well). Please use the ā€˜</>ā€™ stuff in the editor to designate code blocks so I can read it. If you are not familiar, you can find the YAML to share using the edit as YAML in the top right menu.

I know my blueprint code so if you didnā€™t change that donā€™t include any if that.