Unfortunately, SmartThings has made the decision to discontinue hosting a public groovy cloud, so that type of custom code will no longer work by the end of this year, and the IDE itself is going away. . They have announced a general timeline for this.
So we don’t really know what the options are going to be as far as custom code for hub connected devices going forward.
I guess they have one chance to impress me. While I said “pretty easy” honestly I have never been a big fan of “groovy”. I don’t know java so groovy is even worse for me, but I can still mad-lib the templates they provide.
It mentions moving to an API as a replacement. I’m not sure how this will be implemented, but if done correctly, would allow you to write custom automations until your heart is content in whatever language you prefer.
Honestly though, I’m expecting an overly restrictive API and no way for an average Joe to turn some ordinary device into a “smart” device. Their claim of optimizing for Java bothers me too. Can we please stop using java already?? If they were trying to modernize, they would be moving to Python. Maybe I’m just being pessimistic but they’ve given me no reason not to be.
They might as well have just added the implied statements at the end that says “in the meantime, we don’t give a ?!&& if your lights stop working or you can no longer do certain things”.
If anyone has any further information in this API model, who will be able to program what, whether there will be any ability to implement say a raspberry pi or a Arduino etc, I’d be interested. I’m going to have to decide soon whether to continue down this path, or to switch to one of the open source hubs or one of the competitive products.
They put out a lot already on how smart apps will work. You can write them in any language you want, but you have to host them yourself. And there is a quite robust API which is published that tells you how to communicate to the smartthings account. So that part seems to be OK as long as you’re willing to put up with doing your own hosting.
They’ve also published a lot on cloud to cloud integrations for DTHs, so again, that part seems pretty clear, but again you have to do your own hosting.
What we don’t have details on yet on how custom DTHs for hub connected devices are going to work.
Details on what has been documented so far is all on the developers site… Note that the “rules API“ is different from the API for communicating from your own smartapp or for communicating as a cloud to cloud DTH.
Just noticed in this post the link to the “rules api” forum. I will look through here and see if I can make some sense out of how to get started with it and what it can do. Just browsing the first few posts is not really inspiring my confidence so far…
DTH is “Device type Handler.“ One of smartthings’ many names for a Device driver.
They are also called “device handlers“, “Device types”, and a couple of other things.
The following community FAQ explains the terminology and the concepts. It was written for the 2015 version of the smartthings app so some of the publishing steps are out of date, but it’s a good basic read anyway as far as understanding the approach for adding custom code to the groovy cloud. (The topic title is a clickable link.)
And for giving you some of the terminology that will still be used with the new platform.
Got it…yes I just found it as well. Guess I should’ve searched “SmartThings DTH” instead. I do know what a DTH is and have created/ modified a few myself (working on one for esp8266 & wled very soon actually). I guess I have just not spent enough time in these forums to pick up on the acronyms.
Thanks for the links and helping me find the gradual wakeup “experimental” smartapp.
Samsung honestly still has some proving to do to me at this point. I honestly hope they are able to pull this together and expose an interface that works the way it should.
This “host it yourself” and authentication model talk is interesting. It’s confusing to try to understand whether this is in the context of “I as a device manufacturer” or “I as a consumer” (or maybe both) guess I have some reading to do.
Security.modes are used with smartthings Home Monitor. The values are now Arm (away), Arm (Stay) and Disarmed.
Location.modes are used in automations as a “behavioral filter.“ When you first set up a smartthings account, the values are Home, Away, and Night. But you can add more location that modes if you want. For example, many people add Guest mode or Vacation mode or even Party mode. Your choice.
Location.modes don’t do anything by themselves. You have to create automations to set them and then act on those settings.
Location.mode is not shown under the LIFE tab, but Security.mode is.
You have to drill down a couple of levels from the main menu to find location.mode, I’m not sure why, it’s useful information.
I’m with you. Samsung is more interested in adding new but rarely needed features such as integration with their smart appliances (oven for example) instead of fixing known bugs!
Fed up and frustrated users can’t get reliable basics.
Why are all my sunrise sunset time based automations suddenly stopped working?
Why are all my zigbee devices suddenly disconnected and I had to physically reconnect them?
I don’t know what to do. I got 3 WiFi hubs invested with over 50 devices and countless automations and scenes. There are many occasions I was about to abandon SmartThings and willing to move to another platform.
There is a home icon alongside a curiously inert location name on all the pages that use the new UI. So not the menu page It, not device details, not automations. It only ever handles the same location related stuff.
“Samsung is more interested in adding new but rarely needed features such as integration with their smart appliances (oven for example) instead of fixing known bugs!”
Haha! I forgot about this one. Yes while trying to figure out why my gradual ramp up was no longer working, I was presented with the option to add a smart app to curate custom recipes to use with my smart stove.
so bizarre and ridiculous. I always make this joke about toilets in the future that will twitter #1 or #2 and weight volume etc when flushed.
I think Samsung actually thinks this is the right direction. Great now they are going to make it and add a BM tracker smart app that integrates with the custom recipe suggestion app to improve BM quality.
Meanwhile I still cant find the settings to get my lights working right again.
I have done that in the past. And support told me they only support US customers and I need to contact Australian Samsung support. Australian has literally no support for SmartThings and no one bother getting back to me at all…