Z2M - Xiaomi Cube Controller

[melistraza (Andrew Kuzmychov)]

Is it possible to remove this sub condition

- conditions: '{{ sub_event == 0 }}'
                sequence: []

I don’t want to add all scenarios for each side.
For me enaught just to rotate in any side.

[juventinio]

Im trying to configure blueprint, unfortunately in GUI i dont see device (magic_cube).
Im using Z2m with conbee II and i have aqara magic cube on the list, working properly.

Any idea?

[Groto]

Did you ever figure this out? I have the same issue.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

This would be a lot easier for your users to import and keep track of if you add an import link…
Simply fill this in and then add the markdown code to the original message…

Create a link – My Home Assistant

Like this:

Looks like this in Markdown…

[![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%2Fcommunity.home-assistant.io%2Ft%2Fz2m-xiaomi-cube-controller%2F263006)

As far as the Blueprint itself goes, it’s awesome and works perfectly.
You may want to add in the initial message ( or better yet the Description of ‘sensor to use’ inside the blueprint ) what sensor to use to get the is to work. I see people seem to be confused because all you need exported to HA to make this work is the sensor.##Device_Name##_action sensor and that is what you put in for the controller to use question. This may seem obvious, but not for everyone. The rest of the sensors can be hidden unless you want to watch battery or signal from diagnostics.

Z2M - Xiaomi Cube Controller

So I had a question about using this blueprint. What should the entity be that I look at? I see multiple sensor.magic_cube_action, sensor.magic_cube_action_angle, sensor.magic_cube_action_from_side, sensor.magic_cube_action_side, sensor.magic_cube_action_to_side, sensor.magic_cube_linkquality. I thought, it would one entity like sensor.magic_cube…

Z2M - Xiaomi Cube Controller

I am using the “sensor.magic_cube_action_side” and that is working fine.

Z2M - Xiaomi Cube Controller

I’ve just received my cube but can’t get either of the blueprints in this post to work. The trace gives an error of Error: UndefinedError: ‘dict object’ has no attribute ‘to_state’ The entities which have been created in HomeAssistant are: sensor.cube_action sensor.cube_action_angle sensor.cube_action_from_side sensor.cube_action_side sensor.cube_action_to_side sensor.cube_battery If I look at the mqtt package it looks something like this: {“action”:“rotate_right”,“action_angle”:…

Z2M - Xiaomi Cube Controller

I have the same issue, did you find a resolution? I just go my cube and connected to zigbee2mqtt. MQTT Explorer shows correct at first then publishs again and then shows null on everything… {"action":"flip90","action_angle":null,"action_from_side":3,"action_side":5,"action_to_side":5,"battery":38,"linkquality":57,"side":5,"voltage":2875} {"action":"","action_angle":null,"action_from_side":null,"action_side":null,"action_to_side":null,"battery":38,"linkquality":57,"side":5,"voltage":2875}

Thanks for the great code!!

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

@yourigh

The blueprint works well. I spent some time on an automation where the brightness will increase by action angle.

What about lowering the brightness?
Is it as simple as adding a negative sign in the template?

UPDATE…
I figured this out and put the new code in my ‘forked’ version of this blueprint.

CW is a positive angle and CCW is a negative angle, so don’t futz with the sign…

Thanks for the idea.

[Richi_Bowzer]

Thanks for this bud, works flawless for me and love that I can change scenes using the rotate clockwise and counter clockwise

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

I see a couple of other changes that I think should be made.
I believe I’m going to ‘fork’ off of this and start another version. The logging should not be on all the time, and I have a better way to display the last action to a sensor instead, so that you can troubleshoot and generate the actions easier.
That along with some of the descriptions I think a few tweaks like that would make this a lot better.
The basic code is sound and doesn’t need a thing.

Community link for my forked version of this blueprint:

Zigbee2MQTT - Xiaomi Cube Controller

(Hundreds of possible actions!!) Works with MQTT Directly bypassing both Legacy and non-Legacy trigger issues. Uses a Zigbee2MQTT built MQTT sensor to sort out the 38(+54) commands available from the Xiaomi Magic Cube. This gives you the ability to trigger actions using the remote. NOTICE: Using this Blueprint and example scripts, this cube can be triggered many ways, but only 38(+54) of them are unique… Changelog 2023-12-09: Stop log spamming leak. #32 2023-10-20: Enhancement A…

source_url from GitHub: https://github.com/SirGoodenough/HA_Blueprints/blob/master/Automations/Zigbee2MQTT%20-%20Xiaomi%20Cube%20Controller.yaml

Event Sensor in Action:

[Soepgroenten (Mathijs)]

Great Blueprint, I especially like the respect for which face is up functionality. Unfortunately I’m a Deconz user. Is this Blueprint coming for Deconz too?

[finder39 (Joe Neuman)]

I am also getting these issues. I see that if I change all of the trigger.to_state.attributes.action to trigger.to_state.state then shake will work, but the flip90’s won’t as the sub_event is never populated.

I wonder if something changed with how the action entities are set/updated?

Looks like that states are no longer in the main action’s attributes. I’m running HA 2022.3.1, and Zigbee2MQTT 20211217. Maybe something changed in an update?

EDIT:

On further testing, it seems I can get it to work with the blueprint as-is IF I enable “Home Assistant legacy entity attributes” & “Home Assistant legacy triggers”.

[ServiceXp (RJ)]

Did you ever get it working without setting homeassistant: false in configuration (which caused problems when HAOS is restarted)

If I have is set to true, I just keep getting flashes, and ’ ’ as the final action payload in HA, and I can’t seem to catch the first payload.

[scetu]

Thanks! You’ve saved me a big headache - when after few hours I was unable to get the cube working.

[C.G.B.Spender]

Hi,
I’m looking for sort of a “reality check” on what I’m trying to do with my cube. I would like to be somehow able to detect the direction of 1side flip.

Basically what I was trying to do before getting stuck in the “well how the hell would that work” phase is to make the cube work as arrow keys. I already use it for many media controls when watching kodi and was thinking if I could just flip the cube left/right/up/down (where “top” would be the face which was on top at the time of 1st flip).

Would something like this be possible in any (however elaborate) way?

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

If you pick a starting point, you know where it is. on that starting side draw an arrow up so you know how to position it. Then each flip is from that side to one of the other 4 sides. The cube will tell you the from and the to.
Don’t know if this blueprint will do it or not, but mine would.

Z2M - Xiaomi Cube Controller

I see a couple of other changes that I think should be made. I believe I’m going to ‘fork’ off of this and start another version. The logging should not be on all the time, and I have a better way to display the last action to a sensor instead, so that you can troubleshoot and generate the actions easier. That along with some of the descriptions I think a few tweaks like that would make this a lot better. The basic code is sound and doesn’t need a thing. Community link for my forked version…

[adamch (Adam)]

Just installed this blueprint but cannot get it working with HA 2022.10.

The device works fine but the blueprint is never triggered.

alias: Cube living room
description: ""
use_blueprint:
  path: SirGoodenough/Zigbee2MQTT - Xiaomi Cube Controller.yaml
  input:
    remote: sensor.cube_living_room_action
    slide_face_0:
      - service: light.turn_off
        data: {}
      - service: switch.turn_off
        data: {}
        target:
          entity_id: switch.kitchen_light_outlet_local
    rotate_cw_face_0:
      - service: media_player.volume_up
        data: {}
        target:
          entity_id: media_player.sony_ke_48a9
    rotate_ccw_face_0:
      - service: media_player.volume_down
        data: {}
        target:
          entity_id: media_player.sony_ke_48a9

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

Change your legacy settings on your device.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

I have all the set-up and configuration options that you are looking for in my version of the cube controller…

Zigbee2MQTT - Xiaomi Cube Controller

(Hundreds of possible actions!!) Works with MQTT Directly bypassing both Legacy and non-Legacy trigger issues. Uses a Zigbee2MQTT built MQTT sensor to sort out the 38(+54) commands available from the Xiaomi Magic Cube. This gives you the ability to trigger actions using the remote. NOTICE: Using this Blueprint and example scripts, this cube can be triggered many ways, but only 38(+54) of them are unique… Changelog 2023-12-09: Stop log spamming leak. #32 2023-10-20: Enhancement A…

[hroman (Roman)]

Anyone knows how to download any of blueprints discussed there? links don’t work anymore.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

Mine works just above…
@hroman

@hroman

Anyone knows how to download any of blueprints discussed there? links don’t work anymore.

[Himdola]

same here, how an i download the latest version of the blueprint?

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

It’s possible the code is abandoned. Haven’t heard from the author in a while.
If that’s the case and the link does not work, you will have to copy it over manually and take your chances.