Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aqara Magic Cube Z2M 2.0.0 #7

Closed
Dillton opened this issue Jan 4, 2025 · 5 comments · Fixed by #8
Closed

Aqara Magic Cube Z2M 2.0.0 #7

Dillton opened this issue Jan 4, 2025 · 5 comments · Fixed by #8

Comments

@Dillton
Copy link

Dillton commented Jan 4, 2025

Blueprint filename

zigbee2mqtt_aqara_magic_cube.yaml

The problem

Hi @golles
So I have updated my system to Z2M 2.0.0 and all remains to migrate is the Magic Cube.
When I create new automation based on the new blueprint the Cube device is not found.
image

But the device is in HA recognized.
image

Is there anything else to do or change in the blueprint?

Currently I have enabled the legacy actions which gives the backward compatibility and it works but it would be nice to not use it.
I guess at some point all legacy stuff will be romoved from Z2M.

What version of Home Assistant Core has the issue?

2025.1

Home Assistant log

No response

Additional information

No response

@golles
Copy link
Owner

golles commented Jan 4, 2025

Hi, thanks for letting me know.
It looks like all selectors for my Blueprints are broken, let me see what is going on here...

@Dillton
Copy link
Author

Dillton commented Jan 4, 2025

I guess I found the problem with device. My cube reports model only as "Cube" and not "Cube (MFKZQ01LM)".
So I have adjusted this in blueprint and now the device is found.

I am going to try now some actions to see if everything works.

@golles
Copy link
Owner

golles commented Jan 4, 2025

It should indeed be Cube. Let me also double check all other Blueprint selectors

@golles golles linked a pull request Jan 4, 2025 that will close this issue
@golles golles closed this as completed in #8 Jan 4, 2025
@golles
Copy link
Owner

golles commented Jan 4, 2025

I guess this is due to Z2M 2.0, I've updated the Blueprints.
Thanks again for letting me know - and good luck with the migration!

@Dillton
Copy link
Author

Dillton commented Jan 4, 2025

Thanks for quick reaction.
Cube is now tested and working flawlessly again.

FYI this was the last one missing. Other than that I had to just replace some entity_ids in automations where I am still using device triggers because some of them changed but in total I think two hours of adjustments and everything is updated and working. So no big deal for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants