🧯 Zigbee2MQTT - Xiaomi Cube Controller

Sir_Goodenough · July 27, 2023, 4:14pm

I have tons of documentation and examples listed with my blueprint. Plus a script blueprint to do the code for you.

SirGoodenough/HA_Blueprints/blob/c0399777dad1d1c3df2932baba024320fb720e78/Automations/Zigbee2MQTT-Xiaomi_Cube_Controller_MQTT_Triggered.md

(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

* **2022-03-01-A**: Beef-up the note not to use spaces and non alpha in MQTT topics.
* **2023-03-01**: Add Author Tag. Bump HA required Version to 2023-3-0
* **2022-12-28**: Code cleanup.
* * Add note to fix configuration conflict template error:
* * Update angle configuration text to help with config errors. No Code Change.
* *  **Error while executing automation automation.friendly_name_automations: TemplateError: Must provide a device or entity ID**
* **2022-12-22**: Change instances of the attribute ```angle``` to ```action_angle``` to fix non-legacy bug.
* * Add note not to use spaces and non alpha in MQTT topics.
* **2022-12-12**: Add Update Method Note, minor code change.
* * Name of Blueprint may have changed meaning you have to re-download with a new link.
* * If name changed, it is similar. Variables have not changed.
* **2022-12-04**: Re-did the backend to use MQTT instead of the Z2M Legacy configuration.
* * This removes the legacy trigger requirement and makes it respond much faster.
* * Old version Deprecated and available on the original Github link but will be no longer supported.
* * Old Github link still works if you need it for something...
* **2022-05-05**: Updated for 2022.5.0 HA. Added Markdown to !input Descriptions plus shortcut or.

This file has been truncated. show original

Code Examples are found in the Yaml file here
If you want to create the script file using a script BluePrint, I have that for you right here: Dimmer Control BluePrint

Plus if you look above, I just came up with a volume control script blueprint as well.

DS_DV · July 27, 2023, 7:34pm

Thank you <3

The video solved my “problem”

i somehow did not understand that i need to call the dimmer script with the trigger blueprint.
i don’t know why but i assumed that it worked as standalone.

now i got my dimming to work just fine and thanks to your work just in a few clicks!

You are awesome! thank you so much!

geidorei · August 10, 2023, 11:39am

Any suggestions…

All setup, no issues, no spaces in name ‘AqaraCube’ and can see under MQTT logbook for the Aqara Cube that the actions are shown. Nothing in main log either.

Have just one automation (double tap) and that is to turn a bulb on, have tried other as well, but nothing happens.

I am obviously doing something wrong, any help appreciated.

After some digging… I am getting the following in the log. I have also the HA SkyConnect installed, but nothing is on ZHA, waiting for ‘matter’ to come through.

2023-08-10 12:41:06.725 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities number.aqaracube_last_side are missing or not currently available

Could this be some kind of conflict?

Further update: have disabled ZHA, still the same…

Sir_Goodenough · August 10, 2023, 3:51pm

I really have nothing to go on here, other than it don’t work and it can’t find the last_side entity the BluePrint creates.
Did you follow the troubleshooting in the documentation? (top post here or the guide file in GitHub) Did you create the sensor to help you see what the BP is seeing when you preform actions with the cube? Since this is the BP for the old style cube, are you using the old style cube? If this is the T1 Pro style cube, there is a different BP for that.

https://community.home-assistant.io/t/zigbee2mqtt-aqara-magic-cube-t1-pro-ctp-r01-xiaomi-lumi-cagl02/525111

geidorei · August 10, 2023, 3:55pm

Hi - thanks for reply, I will go thru docs again. Yes, it is the old cube (original). As a note, tried to setup automations via MQTT and not working their either.

Sir_Goodenough · August 10, 2023, 4:15pm

Sounds like you should verify that the cube is there as well. Under the MQTT integration, select devices, can you find it there? When you action the cube is HA responding in the HA log on the right?

geidorei · August 10, 2023, 4:18pm

Hi - yes its showing in MQTT, and logs show the action, but the bulb or whatever I device I choose does nothing.

Sir_Goodenough · August 10, 2023, 4:52pm

Keep in mind that for every time an action is detected, a clear last event action also happens as seen by the log above. There are also wake-ups and none’s and other things the BP does not act on. So many actions are screened out in the BP condition statement as not relevant to the BP.
Activate the cube’s tap or whatever one you have programmed to do the light then look in the traces. Find the trace that the initial condition passed. What did it try to do?

This might be a matter of finding the right side of the cube…

Have you tried an action in the ‘any side’ section to see if you can get something to work? The drop is a good one to use for initial testing, where you drop the cube from one hand to the other.

geidorei · August 10, 2023, 11:02pm

Going Miss Marple, will post after the investigation…

Sir_Goodenough · August 11, 2023, 12:58am

2023-08-07: Updates for Home Assistant 2023.8
- LOOK THIS LINK FOR IMPORTANT UPDATE INSTRUCTIONS
- Selector syntax change
- Condition Selector addition (where applicable)
- MQTT Discovery name changes (where applicable)
- Clean-up code formatting

geidorei · August 13, 2023, 4:02pm

Did what you said and it sort of works but is very intermittent. Tap for example has to be very quick…

Devices will toggle on and off, but when using ‘Call Service’ to toggle a switch (Sonoff mains plug) nothing happens.

Any ideas? Thanks for your help.

Sir_Goodenough · August 13, 2023, 5:41pm

I have a video up on how to tap in my instructions. Quick and fairly aggressive. Those cube actions are often misunderstood. Also please know you need a second or 2 between actions or the too soon action will not register. This is a de-bounce thing so that you don’t get unintended double actions on say a light, causing it to flash instead of go on or off.

Does the service call work when called from developer tools - services?
Does the Blueprint trace show that it’s trying to do it?
Does the diagnostic sensor register the action you think that you did?
Did you do the action on the same cube side you added the service call to?

These are physical actions sent to the BP the way you configured it. There is no way for me to troubleshoot this. That is why I built the diag sensor tool to help you know what side you are physically activating.

This is like me telling you I turned the key on my car and the radio works but it makes a noise and nothing happens. Please fix it for me. ( over chat )

I’m glad to help where I can, but some things are up to you.

geidorei · August 13, 2023, 11:42pm

Update: found out that when using call service with the cube turning on/off an entity all works perfectly fine, but toggle just doesn’t want to know.

Thanks for all your help.

DS_DV · August 15, 2023, 9:40am

hello Sir_Goodenough (:
i have a question regarding the dimmer script.
I got it to work but every so often it somehow breaks the dimmer switch i use.

I made the following observations:

i mostly happens when i try to get to the lowest dimming point
when i try to get low dimming the dimmer shuts off
when i am in tasmota web ui i can dimm everything from 1 - 100
in tasmota webui it does not shut down when set to 1

i wonder if i can turn off the automatic shutoff when turning the dimmer to low values.
(in hope it might solve my problem).

The workaround is to unplug the main power from the dimmer to reset it.

with kind regards

Sir_Goodenough · August 16, 2023, 12:06am

You could remove this section. It is intended to force off if the setting ends up below 5%,

        {% if new_brightness < 5 %}
          {# If it gets really low set to 0. Adjust if needed for your lights. #}
          0

You could either remove those lines or set this to 10 or whatever the lowest you want it to go.

DS_DV · August 16, 2023, 8:09am

thank you ill try that (:

as a note tho: since you wrote to set the script value for minimum brightness higher as low values might cause bugs i already have set mine to 15. But it also shuts off if you dim to low.

Sir_Goodenough · August 16, 2023, 8:28am

There is the minimum where it should stay on that you can pick, and I also set if it got below 5% it should shut off. This disables the shut off part, which appears to be causing you grief.

Taking that section out should assure the final setting to the light is the minimum level you set in the inputs.

DS_DV · August 16, 2023, 8:31am

i now set it to

  {% if new_brightness < 5 %}
          {# If it gets really low set to 0. Adjust if needed for your lights. #}
          1

which solves the shutting down part (:

but when its set to 0 it also shuts down if Minimum Brighness in the blueprint is set to 15
maybe my setup is bugged o.o

Sir_Goodenough · August 16, 2023, 8:52am

1% might still be off to the bulb. just take those lines out.

DS_DV · August 16, 2023, 9:02am

1 works great (:
it works in tasmota web ui and it now works with the cube