Thank you @EdwardTFN this is brilliantly simple! (Not to dismiss the work from other template contributors, but I can only keep up to a certain level of complexity ).
Is there a reason why you didn’t bring ‘shake’ and ‘drop’ commands? I was actually to add ‘shake’ without success, but that may just be my limited blueprints skills…
Model is: MFKZQ01LM
Firmware would be a bit tricky as it is only in HA, I don’t have an Aqara hub so unless someone can give me an idea of where to look for the F/W version I can’t help I’m afraid.
Can I just add that both you and @EdwardTFN have been magnificent in continuing to look into this. I get frustrated when people say things that aren’t helpful and tend to give up for periods. I’m very technical but this is not my field of expertise so appreciate the tenacity of you both, thank you.
Got my cube a couple days ago was very excited to find this. Unfortunately the last face helper doesn’t work because it only ever uses the activated face to the time of change which is always the current face.
Set up some extra helpers to do some maths from the automation and was getting the active face information NOT the deactivated face. Roll from 3 to 1 and was getting last face as 1 not 3. This immediately screwed my initial use so I’ve expanded your wonderful work @EdwardTFN to make that a possibility.
However, I’d prefer to not upload it as my own as its yours apart from deactivated and activated face storing correctly.
I added this to the inputs:
current_face_input:
name: Current face up numeric helper
description: Please select a Numeric Helper to be used to record the last face
up.
selector:
entity:
domain:
- input_number
multiple: false
And this above activated face:
deactivated_face: '{{iif((command == ''slide'' or command == ''knock'' or command == ''flip''), trigger.event.data.args.deactivated_face, states(temp_last_face_input)) | int(0) }}'
And changed this bit to cope with the last face being last face and current being the current:
Should trigger any and all things your cube does.
It is the basis of most Cube Blueprints if you want further reference. But it will give you a lot of traffic, so you may want to condition that down a bit to cut out some noise.
Perhaps just taking control of someones blueprint is a better way to start what you are asking (or just using their blueprint).
This thread is about a specific blueprint someone is sharing that happens to control the cube, not writing your own automation to control the cube. A new post in Configuration - Home Assistant Community would be the place for that.
Hi @EdwardTFN I have tried to use @Sir_goodenough blueprint but his writing is very confusing and his replies seem to be intentionally holding info. I am going to use other blueprints as this is a waste of time.
I have multiple aqara cube. Where can I define which one to select for an automation? In sir_goodenough blueprint this step is not clear. Is this done inside the blueprint for you or outside somewhere?
That is ok. No worries. But you don’t know what I tried or not so saying I should try before reaching out is not something you know. If your responses are clear and pointing to a specific part of your guide then yes it is correct, if not, then I don’t know what your intention is as it wastes my time and everyone else’s who inquires. People inquire because you encourage to inquire.
Anyhow, thanks. I have posted so others know which blueprint to work with in an efficient manner. Did not mean any ill intention.
My question remains for anyone who can answer. Thanks