CLI: How to Install and Use

[JDRoberts]

The IDE is part of the old pre-2022 SmartThings architecture. It does not display accurate information for devices which are using Edge Drivers, which are part of the new architecture.

You can get some equivalent information by using the CLI (command level interface), a developer tool which is part of the new architecture. This information includes device IDs and event logs.

Using it is quite different than using the IDE. The IDE was just a webpage with information about your account. The CLI is a program that you have to download to a computer and then run. (Those like myself who just use a tablet are currently out of luck. )

@Mariano_Colmenarejo , a community developer, has written up instructions for how to download and use the CLI on a windows pc.

Edge Driver or Device Handeler for a TUYA (Zemismart) Zigbee plug with energy mesurment capabilities - #18 by Mariano_Colmenarejo

Hopefully ST will provide an official feature which is easier to use in the future when the transition to the new architecture is complete, but no promises.

A few more links on the transition:

FAQ: I have no idea what Edge is. Is that a new developer tool? (2022)
.

FAQ: Why does the IDE list “placeholder” for my device? Can I change that?
.
FAQ: How do I access Smartapps, Devices, etc. from web (the old IDE information)

And here Mariano has a very detailed post on setting up the environment on a pc to write your own custom Edge Drivers for those interested in that aspect:

Setting Up Edge Development Environment - #9 by Mariano_Colmenarejo

Tagging @TAustin @ygerlovin @Automated_House @orangebucket in case they have any more to add.

[Automated_House (Jimmy)]

I believe @nayelyz has instructions posted for installing the CLI on any computer

(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

Hi, if, by offline you mean that it shows the cloud icon like in this picture you shared: This means the capabilities weren’t initialized and your device is not reporting new values, this could be because: The joining process wasn’t completed (you need to wait in the “scan nearby” page a few seconds after the device is found) There was an error during the joining process. (you can verify this in the Hub logs) Initialize the Hub logging Download the latest release of the CLI and save it in a specific folder Open that folder in the terminal and run a simple command such as smartthings devices This will open a browser page where you have to log in to your account and authorize the access. Once it says “you can close this window”, run the command smartthings edge:drivers:logcat. It …

I’ve also taken to calling the current/old IDE the “Groovy IDE” specifically to distinguish that it should only be used for legacy Groovy purposes.

[JDRoberts]

@Automated_House

I believe @nayelyz has instructions posted for installing the CLI on any computer
(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices - #335 by nayelyz

She did, but since she wrote that post the link to the IDE has changed out so the one in her post takes you to the wrong place and can be confusing, particularly for newfolk.

[homeagain]

Is there any where beyond the legacy IDE where you can add/remove location modes? Does CLI give you this?

[JDRoberts]

@homeagain

Is there any where beyond the legacy IDE where you can add/remove location modes? Does CLI give you this?

I don’t think it’s in the CLI, but I don’t know the answer to your question. @jkp might.

[nayelyz (SmartThings Developer Support)]

@JDRoberts

but since she wrote that post the link to the IDE has changed out

Thanks, @JDRoberts. I just edited that post.

About the location modes, @homeagain
The CLI doesn’t have those endpoints but the API has some:

1. GET modes:
   https://api.smartthings.com/v1/locations/locationID/modes
   Try the POST and DELETE versions of this endpoint to add/remove one
2. GET current mode:
   https://api.smartthings.com/v1/locations/locationID/modes/current
3. PUT to modify the current mode:
   https://api.smartthings.com/v1/locations/locationID/modes/current
   Body:

{
    "modeId": "mode-id"
}

Got this info from this post:

SmartThings API: Listing location mode

Have you tried this? https://api.smartthings.com/v1/locations/{locationId}/modes You also need the proper scopes on your token (modes)

[JDRoberts]

@nayelyz

About the location modes, @homeagain

Does that allow you to create new custom modes like you can in the IDE?

For example, at our house we have the following modes:

Home
Away
Night
Sleeping
Guest
Party
Test

The custom modes were added through the IDE:

[nayelyz (SmartThings Developer Support)]

@nayelyz

Try the POST and DELETE versions of this endpoint to add/remove one

These options allow you to create/remove modes.

1. Create (POST):
   https://api.smartthings.com/v1/locations/locationID/modes
   Body:

{
    "label": "test",
    "name": "test"
}

2. Remove (DELETE):
   https://api.smartthings.com/v1/locations/locationID/modes/custom-mode-id

[Bloodtick_Jones]

@nayelyz

Have a curious permission problem/question with Modes.

In order to ‘set’ the mode you need “x:location:*” permission or get a “status code: 403, reason phrase: Forbidden”

However, the SmartThings Developer Workspace doesn’t allow SmartApps to have that permission.

BUT…

Grabbing a PAT allows that permission and doing a HTTP PUT set command works fine. Any idea why this exists? and can the developer workspace smartapp be updated?

[nayelyz (SmartThings Developer Support)]

@Bloodtick_Jones

can the developer workspace smartapp be updated?

Those scopes can be modified using the API, here is an example:

SmartThings SDK Subscribing to Devices Dynamically

He meant you to add it manually through the SmartThings API. What we do, is: Get the current scopes of the SmartApp. [oauth_config] Copy the result, add the r:hubs:* scope, and save the new configuration. [save_oauth_config] You should see this permission on the Authorization page. [hub_scope] Note: Every time you make a change to the project in the Developer Workspace, URL, display name, etc. you’ll need to repeat those steps.

In the meantime, I’ll check with the team more details about this.