I’m glad this has been useful to so many people!
The side with “Aqara” is 1.
The side opposite that is 4.
If you position the cube so that Aqara is on the top, and facing you so you can read it, the remaining sides are:
Up: 3
Left: 5
Right: 2
Down: 6
If you want to check for yourself, go to Developer Tools → Events. Start listening to zha_event, and the event data will have an activated_face variable. That’s the side that’s up.
Some of the gestures do send the activated face (flip, slide, knock). Others don’t (drop, shake, rotate).
The information sent by the cube doesn’t include the side that’s up during a rotation. It would be possible to track that in an input_number helper, but I’m not sure how to generalize that for a blueprint without hardcoding a name of a helper (maybe possible, but if so I don’t know how yet). Also, there are many things that can happen that would get that out of sync, like tossing the cube in the air. Very easy for the side that’s actually up to be different than the last reported activated side.
It seems that a single tap doesn’t send an event at all. Any number of multiple taps in quick succession (I tested 2-6) send a single knock event.