I’ve never noticed either of mine flash the blue LED after pairing. I take it you’re pairing using the catchall method? in which case are you absolutely certain you got the correct network ID? i’ve had issues before when I picked the wrong part of the catchall…
Here’s what a small section of my device events log looks like, using the simple mode:
2019-02-24 7:54:50.867 PM GMT
3 days ago DEVICE battery 62 Bedroom Cube battery is 62%
2019-02-24 7:11:36.202 PM GMT
3 days ago DEVICE button pushed Bedroom Cube detected 90 degree flip
2019-02-24 7:08:10.822 PM GMT
3 days ago DEVICE button pushed Bedroom Cube detected slide motion.
2019-02-24 7:08:10.785 PM GMT
3 days ago DEVICE button pushed Bedroom Cube detected 90 degree flip
2019-02-24 7:08:09.885 PM GMT
3 days ago DEVICE button pushed Bedroom Cube was rotated right.
2019-02-24 7:06:44.337 PM GMT
3 days ago DEVICE button pushed Bedroom Cube detected 90 degree flip
2019-02-24 7:06:35.374 PM GMT
3 days ago DEVICE button pushed Bedroom Cube detected 90 degree flip
2019-02-24 7:06:27.384 PM GMT
3 days ago DEVICE button pushed Bedroom Cube detected 90 degree flip
2019-02-24 6:58:24.737 PM GMT
3 days ago DEVICE battery 62 Bedroom Cube battery is 62%
And a section from the cube using advanced mode:
2019-02-23 8:29:21.163 AM GMT
4 days ago DEVICE battery 66 White Cube battery is 66%
2019-02-23 7:51:50.095 AM GMT
4 days ago DEVICE button pushed White Cube was knocked with face # 2 up
2019-02-23 7:39:01.137 AM GMT
4 days ago DEVICE battery 70 White Cube battery is 70%
2019-02-23 6:48:07.690 AM GMTOne of the first tries used the catchall and I think I got the right ID. Trying another time I saw the catchall but at the same time the cube actually showed up in the SmartThings app add device screen so I added it. IIRC the ID matched the catchall so I thought I was good.
Thanks for the info, I’ll try again tonight.
I just wanted to add since I couldn’t bring it up on the search function, the newer Aqara cube is working with this just fine for me, basic functions worked with the built in device options but WebCore would also work, for the moment I have the 7 basic functions mapped out with the Advanced Button Controller smart app. Took maybe ten mins to work out which function was ‘button 1, button 2’ and there’s no option to rename them, but it’s working well, thank you heaps to the legends that wrote the handlers and apps!
I did have to use the catch-all method to pair it and then manually define the device type, there is probably a good newbie step by step (I’m very new to this) but I muddled my way through the IDE to find the right option and caught the device address after a few tries - it threw me as it was 4 numbers, no letters, but it works.
Hey guys, just got aqara cube and installed it in smartthings. It seems fine, but in smartthings app everything is shown as “pressed”. In web interface, I see movements properly registered. What kind of app are you using?
Also buttons are not shown in the device as in screenshots in this thread - guess this is due to new app. Any update on this?
Ok, i’ve quickly added support for rest of the actions. basically all that needs to be done is change button event value not to be “pushed” with all the actions, but select some from this list:
then automation can be created with any of the button presses 
looking into creating custom capability, so the naming matching the actions
@PiTRiS did you upload your fixes somewhere? I got a cube too and I’d like to use it to make automations in the new app, since the old one is going away soon.
Hey, as most of people here, I also bought the Aqara Cube and it seems that most actions were supported in the old app by DTH itself. Howver using SteveTheGeekHA : Magic Cube Button Controller SmartApp even on the new SmartThings seems to be the closest you can get to make it work. The only problem is that it only works as a switch, so no slider dimming, but all the original input actions are supported.
@PiTRiS I am not sure how your added changes work, but it seems that most of the events are categorized the same, so it only acts as a press on any state change.
I think , rewriting the SmartApp by Steve to support more output actions would be the closest way of getting a full integration on the new SmartThings app.
Interesting, I didn’t know about this Magic Cube Button Controller smartapp. I just started using the ABC button control smartapp, which is a general purpose smartapp for button devices.
Well as it seems that something changed yesterday and my config in the smart app seems to no longer work.
What about your SmartApp how much of control were you able to get out of it? Do thinga like slide/rotate dimming work? Honestly even basic flips would be good right now.
So I’m using the Advanced DTH from this thread in the most basic 7-button mode. Within the ABC smartapp I can see the action each button press corresponds to (flip, shake, etc) which is good, and when the cube works, it works great.
The only issues I’ve had so far are the cube not properly detecting actions, and sometimes half dropping off. It could be some kind of sleep issue from not being used for a few days. To ‘wake’ it up, I just switched the mode of the device to the 7 button mode again and that got it responding again.
This all works within the new app BTW.
Thank you so much, that really did it for me! Now I am able to leverage the full cube controls with all my SmartThings connected devices. Usually when searching for the integration with Aquara Cube, this app is not within the scope of things to show up on the search results. This is awesome!
You’re very welcome! The ABC smartapp is a very powerful and good one to have anyway, because it allows for increasing/decreasing bulb brightness by a set amount instead of the usual “turn on and set level” features that Smart lighting allows for. There’s lots of other things it can do too, of course.
Really loving that it has the full feature set indeed. Some settings need some tweaking on my end to make them work as I would like to, already tested the Increase/Decrease dimming by adding all my existing yeelight light to be dimmed at the same time via the rotational movements. Will do some experimenting with Color Temps maybe later on as well.
Hi all,
Hope you don’t mind me reviving this old topic 
I got my first cube just recently, and I’m using this fantastic DTH that gives me plethora of options in Webcore.
However, there is one issue/bug? I can’t seem to resolve, number of buttons in Webcore. It is always 32, while I need 36 to utilize the full functionality of Advanced mode.
As per my understanding, DTH is reporting number of buttons (36 in case of Advanced mode) and Webcore should act accordingly and increase the number of available buttons to 36, but that is not happening!
It is always 32! I made sure I’m using cube as a physical device, I tried changeing/re-publishing DTH, switch between cube modes, removing/re-adding cube from Webcore … nothing really seem to help.
Any ideas?
In case you didnt fix your issue Kunjila this might help. I was having the same issue as you but I was initailly using the DHT version available in paul sheldon repo for the ABC app and no matter what it stayed limited at 32 buttons in WebCore (be it a virtual or physical device). I compared both codes and it seems there is some slight modifications made between the two DHT. When i tried directly the DHT by ClassicGod i got the 36 button again in WebCore.
In a hope that this will be seen . 
The commands i have to choose from aren’t "numbered "
but this ;
pushed
held
double pushed_2x
pushed_3x
pushed_4x
pushed_5x
pushed_6x
down
down_2x
down_3x
down_4x
down_5x
down_6x
down_hold
up
up _2x
up 3x
up 4x
up _5x
up _6x
up_hold
swipe_up
swipe_down
swipe_left
swipe_right
this make no sence to me and i cant get the cube to make a simple switch in color with a hue lamp - no matter what i set as “button rule”
- when looking in the api.smartthings is quite clear displays whats been done with the cube like “knocked on face 1”…
show me the light - please
Any hope to see this as a Edge driver?