-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
Hi, thanks for letting me know. |
I guess I found the problem with device. My cube reports model only as "Cube" and not "Cube (MFKZQ01LM)". I am going to try now some actions to see if everything works. |
It should indeed be |
I guess this is due to Z2M 2.0, I've updated the Blueprints. |
Thanks for quick reaction. 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. |
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.
But the device is in HA recognized.
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
The text was updated successfully, but these errors were encountered: