Aqara Cube ZHA - Simplified face-based device control

[richlee91 (Rich Lee)]

That would be why, I’ll upgrade to 2022.2.

[richlee91 (Rich Lee)]

Works great with 2022.2. Thank you!

[queelyte]

FINALLY!! A ZHA cube blueprint that works!! Thank you!!

[mouth4war]

Can you use the angle of rotation in ZHA or is that only available in Z2MQTT?

[EdwardTFN (Edward Firmo)]

Angle is also available on ZHA.
What is your use case? Maybe I can adjust this Blueprint to use the angle.

[mouth4war]

Want to use rotation to dim lights/control volume. I think the angle can act as a multiplier for the dimming value.

Aqara cube rotate automation to brighten or dim lights

I wanted to control the percentage of brightness adjustment so that, for example if I turn the cube too much the lights will dim at greater values etc. I’m using zigbee2mqtt to pair my Aqara Cube, and in the entity attributes it tells you the angle of rotation: [image] So I created an automation which reads the changes in the angle and translates it in brightness step percentage: id: '1601415207224' alias: dim light from cube description: '' trigger: - platform: state entity…

[EdwardTFN (Edward Firmo)]

@EdwardTFN

- variables:
    command: '{{ trigger.event.data.command }}'
    value: '{{ trigger.event.data.args.value | default(0) }}'
    flip_degrees: '{{ trigger.event.data.args.flip_degrees | default(0) }}'
    ...

If you see in this Blueprint, the flip_degrees is available as a local variable. The Blueprint was made to support any action (not only light), so angle is not used as a parameter.
In order to use this, a new Blueprint (or automation) will be needed, with small modification.

Do you have any experience with building your own automation with YAML or do you wanna help building it?

[EdwardTFN (Edward Firmo)]

By the way, I’ve used increase/decrease brightness as actions and it works fine. It’s probably better than using degree as you don’t have to calibrate it.

[EdwardTFN (Edward Firmo)]

Also, I cannot test right now, but most likely the Blueprint that I’ve created will work as it is if you select “call a service” as an action for one of the turning sides and then adding the variable as a template in YAML mode:

EDIT on 2022-05-07: Use relative_degrees or trigger.event.data.args.relative_degrees instead of flip_degrees.

[mouth4war]

I’ve tried both in automations before and prefer the one using degrees as a multiplier. If you set it right, you can get finer control over the adjustment. Low angle = low change in brightness/volume. High angle = high change. Versus a static X% no matter how much the turn angle.

[Anto79-ops]

hi thanks for your blueprint!

I have 3 of these cubes and they control various thongs like blids, fans, lights, etc. I’m currently using the 51 action blueprint one now, besides geting erros messages in the my log files when I rotate the cube:

Template variable warning: 'dict object' has no attribute 'flip_degrees' when rendering '{{ trigger.event.data.args.flip_degrees }}'

2:24:17 PM – (WARNING) helpers/template.py - message first occurred at 2:24:06 PM and shows up 28 times

just curious what your blueprint does that is better than the 51 action one? I’d be happy to change to this!

[EdwardTFN (Edward Firmo)]

Have you tried using flip_degrees as in my last example?

[EdwardTFN (Edward Firmo)]

Hi @Anto79-ops,
I don’t know which Blueprint you are talking about. Please share the link here and I can try to identify the difference between them.
By the way, this is not a competition between blueprints.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

It’s the wrong zigbee flavor, but if you are able to get the angle into my template, this template logic I suggest for angle actions should work for you… (This is a link to the dimmer control section)

At that level, it’s just an action. You would need to pass the angle in. Z2M gives me pos angles for CW and negative angles for CCW, so the template doesn’t change and called script gets used for multiple sensors.

I also provide in there a scheme to set the R, G, & B Colors using rotation, and another section to use a short rotation for a short press and a larger rotation as a long press. These are all template things you can do regardless of the Zigbee flavor as long as you can get the angle out of the Integrations Data Attributes.

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…

[Anto79-ops]

@EdwardTFN thanks!

Here’s what im using now, its in your OP

Aqara Magic Cube ZHA (51 actions)

Blueprint to support the Xiaomi Cube Controller using ZHA. Thanks to @bergstrom for this inspiration. All has been tested. Supported actions Slide Knock Flip 90 degress Flip 180 degress Shake Drop Wake Rotate clockwise Rotate counter-clockwise Blueprint Click the badge to import this Blueprint: (needs Home Assistant Core 2021.3 or higher) [Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.] blueprint: name: Aqara Magic Cube …

I tried your blue-print, and it acutally fixes that error in logs that I posted above! so that is great news.

With your blue-print, how does one:

1. set a command to fire when, for example, something is flipped from side 1 to side 2

[Anto79-ops]

@Sir_Goodenough

its sounds like things are greener over at the Z2M side, in terms of features. I’m slowly building up momentum to make the switch. That’s an impressive blue-print for the cube!

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

That is simply an action sensor called by te zigbee stuff. It’s a Home Assistant script.

If ZHA has the angle as an attribute, that is the input and the rest should be close.

[EdwardTFN (Edward Firmo)]

I was about to try Z2M when I got this cube and couldn’t find so much material, but in the end I invested a bit more time to learn a bit more on how to work with events and discovered I can have very similar capabilities with ZHA, with an smoother user experience, so I decided to stay.

Maybe I can help you here… What you want is that Blueprint converted for ZHA?

[EdwardTFN (Edward Firmo)]

On my Blueprint I don’t take in account the “from” side, I just use the side the needed showing up after each action.

[Anto79-ops]

@EdwardTFN @Sir_Goodenough

Sometimes simplicity the best solultion, I can guarantee you that if I start talking about angles to control devices with my wife, she is going to through that cube out the window.

I think in my household, I will be using both your blueprints

thanks again for your awesome dev work here!!