ZHA - Aqara Magic Cube (69 actions)

rvaidya · October 18, 2021, 11:31pm

Blueprint to automate the Aqara Magic Cube using ZHA.
Based on Mikkelmoller’s 51-action blueprint.
as well as brent’s 57-action blueprint.

This blueprint adds support for rotating the cube per specific side, by using an Input Number helper to track the side that was last activated by a side-specific action (flip, slide, knock).

Note that since this blueprint uses an input number helper to track which side is active, it will only register side changes from valid side actions (again, flip/knock/slide). If you lift the cube, rotate it freely, and then place it down on a different side, this is not registered as a valid action and the tracking variable won’t be updated.

The input number helper will need to be created independently in HomeAssistant, by going to Configuration → Helpers in the UI and adding a new Number helper.

Supported actions

Slide
Knock
Flip 90 degress
Flip 180 degress
Flip to specific side
Shake
Drop
Wake
Rotate clockwise
Rotate counter-clockwise
Rotate per side

Here’s a sample automation that will call out the side using Alexa media player TTS when flipped, and will adjust brightness of office lights based on the relative degree of the rotation (thanks brent!) but only for face 1:

- id: '1634593050891'
  alias: 'Master: Aqara Magic Cube'
  description: ''
  use_blueprint:
    path: rvaidya/aqara_magic_cube.yaml
    input:
      remote: 3243d34
      active_face: input_number.aqara_magic_cube_active_face
      flip_any: true
      cube_flip_1:
      - service: notify.alexa_media
        data:
          message: One
          target: media_player.user_s_echo_dot
          data:
            type: tts
      cube_flip_2:
      - service: notify.alexa_media
        data:
          message: Two
          target: media_player.user_s_echo_dot
          data:
            type: tts
      cube_flip_3:
      - service: notify.alexa_media
        data:
          message: Three
          target: media_player.user_s_echo_dot
          data:
            type: tts
      cube_flip_4:
      - service: notify.alexa_media
        data:
          message: Four
          target: media_player.user_s_echo_dot
          data:
            type: tts
      cube_flip_5:
      - service: notify.alexa_media
        data:
          message: Five
          target: media_player.user_s_echo_dot
          data:
            type: tts
      cube_flip_6:
      - service: notify.alexa_media
        data:
          message: Six
          target: media_player.user_s_echo_dot
          data:
            type: tts
      rotate_left_side_1:
      - service: light.turn_on
        target:
          area_id: office
        data_template:
          brightness_step: '{{ relative_degrees | float }}'
      rotate_right_side_1:
      - service: light.turn_on
        target:
          area_id: office
        data_template:
          brightness_step: '{{ relative_degrees | float }}'

krystm · October 27, 2021, 9:59pm

Hey this looks like it will do exactly what I am looking for. I am however very new to HA and was wondering if you could just give me an example how the number helper would work. What lines were required etc. I am a once I see it I can understand how to do the rest but the big thing is tracking the sides which is the big functionality.

Really Appreciate it and looks great!

dimitri.bellini · October 28, 2021, 1:22pm

Thanks very great work!
I have tested for rotate face and it works but if try to use knock face option seems to not work.
There is some special flag to use “knock” face feature?
Thanks so much

rvaidya · November 6, 2021, 8:57pm

You can create an input number helper in HomeAssistant’s UI. Just go to Configuration → Helpers and create a “Number” helper. You can then reference this in the automation in the UI.

rvaidya · November 6, 2021, 8:58pm

The knock detection on the cube is kind of flaky - I find that I have to pick up the cube and then hit it against the desk 3 times to trigger it somewhat consistently.

dimitrior · November 6, 2021, 11:09pm

Excellent work! Thank you!

dimitri.bellini · November 9, 2021, 4:18pm

Yes you are right, now if pick up and then i hit it it works!! So thanks so much and sorry…!

richlee91 · December 22, 2021, 1:02pm

Any reason that an action can’t go against an entity instead of a device. I have some zigbee groups that I would like to use this on. But can’t get the action down. Thanks

rvaidya · January 3, 2022, 7:01am

As far as I can tell, the cube doesn’t expose entities that can be used for automations when added to ZHA.

dimitri.bellini · January 3, 2022, 10:42am

Dear Rahul,
from some time (i can not be sure…sorry) the feature of “Slide - Side X up” seems not working as we expected.
If we look on “active_face_entity” (the helper entity) i can see the right side but as soon i slide the cube the active_face_entity will change with a different number for instance: if i’m on face n.2 and i slide the cube the “active_face_entity” will be n.5.
Maybe something is changed on homeassistant release (i’m in 2021.12.7).
Thanks so much for your help

richlee91 · January 3, 2022, 3:31pm

Thank you for your reply, Rahul. I am looking for a way for the blueprint to perform an action on any entity. So in my case I have the cube and the blueprint, and I want to turn on a zigbee group. There doesn’t seem to be a way for me to define the zigbee group (which is an entity) in the Blueprint. AmI missing something?

Thank you!

dimitri.bellini · January 4, 2022, 11:08am

I have fixed my problem with a change to those Blueprint lines (bold value):

activated_face: |

    {% if command == "slide" or command == "knock" %}

      {% if trigger.event.data.args.activated_face == 1 %} 1

      {% elif trigger.event.data.args.activated_face == 2 %} **2**

      {% elif trigger.event.data.args.activated_face == 3 %} **3**

      {% elif trigger.event.data.args.activated_face == 4 %} 4

      {% elif trigger.event.data.args.activated_face == 5 %} **5**

      {% elif trigger.event.data.args.activated_face == 6 %} **6**

Now it seems to work as expected but why?
Thanks so much

miguellobato84 · January 8, 2022, 5:45pm

Hi, by using this blueprint I develop my one in a much simpler approach (only 24 actions, 6 sides * [rotate, flip, knock and slide])

ZHA - Aqara Magic Cube (24 actions)

maehmann · February 24, 2022, 7:55pm

Hey,

First of all thank you for providing this blueprint. I’m still not sure what different actions I will program because it will be hard to remember them all

I’m trying to use the rotate left and right actions to change the color temperature of a light (like dimming). This is the YAML that I tried

      rotate_left_side_1:
      - service: light.turn_on
        data_template:
          color_temp: "{{ state_attr('light.glas', 'color_temp') - 20 }}"
        target:
          device_id: bd2742b4f7d475d7e876ca73bc305d74

Unfortunately this isn’t working. Any ideas why?

Thanks.

queelyte · April 2, 2022, 7:38pm

when creating the input helper, do I only need to give it a name and save it with all the other default values?

chuckned · July 20, 2022, 9:37pm

@rvaidya Amazing blueprint! I love it! I ran into a bug though. If I create a new automation from the blueprint it works perfectly. However if I try and edit the automation later the toggle switches won’t save if I change them (slide any, rotate any, etc.). Am I doing something wrong?

Sir_Goodenough · July 21, 2022, 3:06am

That is an HA Bug I believe…
There is an issue for that.

github.com/home-assistant/frontend

Blueprint boolean selectors not prompting to save and also not saving in blueprint editor

opened 12:33PM - 15 Jul 22 UTC

aderusha

### The problem There are two issues I've noticed with boolean selectors in b…lueprints: 1) If you edit a blueprint with one or more booleans, toggling the state of the boolean does not bring up the "save" button. You have to edit some other selector in order for the "save" button to be presented. 2) If you save a blueprint after toggling the state of a boolean selector, the updated selector state is not persisted to disk. Here is an example, dummy blueprint that offers a text selector and two booleans: https://gist.github.com/aderusha/e4348da4790af6d0875d2b3baa1762ac ## Process to replicate 1. Import and deploy blueprint: [![Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.](https://my.home-assistant.io/badges/blueprint_import.svg)](https://my.home-assistant.io/redirect/blueprint_import/?blueprint_url=https%3A%2F%2Fgist.github.com%2Faderusha%2Fe4348da4790af6d0875d2b3baa1762ac) 2. Create automation from blueprint 3. Toggle one of the booleans, observe that the "save" button appears. 4. Press "save" and exit out of automation editor 5. Go back to the new automation in the automation editor 6. Toggle one of the booleans, observe that the "save" button does **not** appear. 7. Change the text field 8. Observe that the "save" button now appears 9. Press save and exit out of automation editor. 10. Go back to the automation in the automation editor and observe that the new value for the boolean you changed has not been saved, while the value for the text selector has been saved. 11. Open `automations.yaml` and observe that the updated boolean has not been saved, while the value for the text selector has been saved. ### What version of Home Assistant Core has the issue? Home Assistant 2022.7.5 ### 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 _No response_ ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml blueprint: name: "Test blueprint toggle saving" domain: automation input: text: name: "Text 01" default: "Text to save" selector: text: toggle1: name: "Toggle 01" default: false selector: boolean: toggle2: name: "Toggle 02" default: false selector: boolean: variables: text: !input text toggle1: !input toggle1 toggle2: !input toggle2 trigger: [] action: [] ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

chuckned · July 21, 2022, 6:50pm

Good to know, thanks!

sunny1 · August 2, 2022, 2:16am

FYI: I was struggling to get this automation blueprint for my aqara cube working after a recent HA update (currently running 2022.7.7) . I finally realized I didn’t need the blueprint anymore because the cube device now generates events that can be used for automation without the blueprint.

Sir_Goodenough · August 6, 2022, 4:48pm

Yes, it always did that. Otherwise the Blueprints would not work.