[ST Edge] Issues pairing a device with the driver

In that case it might simply be a case of adding that as a fingerprint. It rather depends on what differences there are between lumi.sensor_cube and lumi.sensor_cube.aqgl01 apart from the Zigbee model name itself.

“lumi sensor_cube” is added to the fingerprints

1 Like

It works for me now.

3 Likes

Can’t connect aqara cube using drivers.
Not appearing in device list.
Please help.
Can’t find this device in channels also other than yours.

do you have other edge devices running?
it’s hard to help without knowing what you have tried.
The Edge platform is in Beta now and is not intended for non-developers

First hold the button until LED goes off(about 3 seconds). It should flash once quickly. Then press it again. It should flash 3 times indicating it has connected to the hub. Continue pressing the pairing button between double flashes of the LED until the device shows up in the app. It will take a minute or so. If you’ve ever paired a universal tv remote without the code it’s similar to that.

2 Likes

Super it worked.
All functions working. Except connecting dimmer to lights of Aquara cube. Is there a way to use cube as dimmer. I can see in other platforms like home assistant people are using it to control light and volume.

I have not tried to use it as a dimmer.

Unfortunately the ST platform doesn’t support dimmers, there were option in ST SmartLights App but it doesn’t work with Edge devices .
But there are still two options:

  • use cloud Groovy app, there are plenty “Sync Dimming” apps around, I can publish my version which is stripped version of someone s code.
    It works with a significant delay but you can have a dimming proportional to the cube rotation

  • use Edge driver “Zigbee Light Multifunction MC”. There is a capability to increase dimming by constant value

it should work faster, but you have to rotate several times(steps) to get full brightness.

@veonua Actually SmartThings still support mirror in Smart Lighting. That’s how this can be done

the cube does not have “on/off” capability required for Smart Lighting.

I looked at that, but could not create a routine because the cube did not show up as a trigger

In case of no on/off, just button capability, i am using Mariano’s driver for light and temperature level. Works great any multi button devices

1 Like

For those interested in the mirror functionality, I shared in this post two examples using the Rules API, one for the Switch capability and the other for those capabilities that use commands with arguments to set the attribute’s value (in this case, switchLevel).

Feel free to post your doubts or thoughts. :grinning_face_with_smiling_eyes:

can you show us any successful use of the Rule API by users?

it seems like this API has no traction, only ST team is able to run basic rules, that can be created in the app within a couple of clicks.

1 Like

@nayelyz Or if we can join that Rule Builder tool, even if it is in Beta stage. Anyway Edge is in Beta too.
I am pretty sure any user input is good input.

I don’t have webCoRE installed.

I don’t have Smart Lighting installed.

I have 3 Routines in the app. Two of those are only because Notifications weren’t documented for the Rules API last time I checked and they are beyond my limited reverse engineering abilities (my abilities being limited to making guesses). The remaining one is to change a Location mode at a certain time and is only there because I need to enable and disable it easily.

I have 3 Scenes in the app. This bothers me. If Scenes could be created independently from the app I’d move them all immediately. Alternatively if there was a Rule to execute another Rule directly I’d be using that.

I only have in the region of 80 to 90 Rules as my needs are simple. It worries me that there is said to be a limit of 100 Rules. The minimum needs to be at least 500.

I’m afraid in this context you don’t count @orangebucket, you even have “Developer” in your tag. A “user” would be any regular user, that has only one hub, is not a developer, does not create device type handers, has an I.Q. less than 170, of which precisely zero are using the Rules API @nayelyz

1 Like

Here are two demo tools that can help you understand how to build a Rule and create/delete it.

  1. Crafting a Rule. This tool helps you build Rules using:
  • Time references to turn on/off a Switch
  • Turn on/off a device based on the temperature of another (above, below)
  • Turn on/off a device when presence is detected
  • Turn on/off a device when the location mode changes
  • Lock/unlock a device when an event lasts for x amount of minutes

Note: Please, avoid submitting a Rule from this tool unless you save its ID, this is because it won’t be listed on the other tool or in the request to the API (Rules endpoint) using a Personal Access Token (PAT).

  1. Listing, creating, and deleting Rules. This other tool helps you execute these actions on the selected location.
  • To create the Rule, you must paste a valid Rule in the Submit Rule tab and click on “Submit”. It can be one from the samples or one crafted in the other tool.
    Note: you can check how to change the commands/conditions to adapt it for other capabilities, also, you can get creative and combine them to form a more complex Rule.
  • To delete a Rule, you can list the existing ones in the “List Rules” tab, get its ID and use it on the “Delete Rule” tab

Note: Remember that all the Rules created here won’t be retrieved using a PAT, also, the ones created with this type of token won’t appear in the tool.

We also welcome anyone who is interested in building and maintaining an independent app on top of the API, we love seeing the Community members’ great ideas and skills and of course, I’ll be glad to help in case questions come up.

1 Like

Have these tools been updated? I checked this out a couple of years ago. I created a test rule in which a Xiaomi temp sensor turned on a ceiling fan at 72F. It worked but I don’t remember why Ii stopped using it. I remember I did have trouble deleting the rule, and had to delete the trigger to delete the rule.