Concerns about Direction of Developer Workspace

That’s how I feel as well. They are going away from their core community and gearing it up to play only with the big boys - who BTW have their own game and ST doesn’t stand a chance - Alexa already has a zigbee radio and if it adds z-wave, why would my cousin want to buy ST; she just wants things to work. Point being their new strategy is neither here or there. It’s not in the big leagues and they will lose their base by making life difficult.

Has been the OAuth method implemented yet? I’m really curious about how long it will take to release a version for doing this.

Also can you please explain the way to submit an app available for all smartthing users?

Oauth in is currently the active item under development so it’s release should not be in the too distant future.

Depends on the kind of app/device/integration. For simple API apps the current thinking is that it will be instantly available to everyone. For things that push code into the mobile app or add/change UI there will be a review process. For devices we have rebuilt the certification process from the ground up. If you intend to publish a device or solution visit this page to get started

https://smartthings.developer.samsung.com/participate

1 Like

doesnt sound very promising for home users like me… only companies that want to publish device types for their products… no more open api with anyone pushing code?

No. It’s not limited only to companies. If you want to have a device certified to Work With SmartThings (WWST), you will need to go through a certification process and you don’t need to be a company. Anyone can submit a device for publication and you will still be able to self-publish your own custom stuff without any sort of approval. The API is open and fully documented.

  1. What if someone wants to publish a “Virtual Device” (to be used with a publishable SmartApp)… e.g., TrendSetter, or Weather, or various types of Virtual Switches and so on?

  2. Will one brand / model of device be allowed to have different DH’s provided by different developers? (e.g., Ecobee, Nest, …)

2 Likes

Simple API apps seem to have the same issue. In the new platform when you submit an Automation the status is “self-published” so I assume that it’s not accesible for everyone. Am I missing something?

What about the rest of us that are not developers, or basic programmers that benefit from other members hard work? Are we going to be left with out these benefits that others so nicely provide? Who is SamrtThings going to be for? I for one choose SmartThings just because of the great community that helps so many.

3 Likes

Correct. Self published means that it is not available to anyone but you. See my previous comment about different types of apps needing different types of review.

Virtual Devices are supported.

Custom device profiles will still be possible. There is also the concept of a device plugin that extends/enhances and existing device.

I guess it’s almost time for the SmartThings to Connect to Samsung Account to SmartThings migration to be completed? :grinning:

SmartThings is full of makers, hobbyists, and tinkerers. I might be doing this full time but I still “tinker” around with SmartThings in my spare time. It’s not about pushing hobbyist old timers out the back door at all. There is a problem that needed to be addressed, while our original tools were great for a weekend hobby project, they were never going to scale into a solution capable of service millions of people.

I fully believe that our new API will open doors to people who could never have developed for SmartThings before.

You can now develop a SmartApp that runs at your home on a raspberry pi and do it in javascript, or java, or groovy, or any language you want. All you need is a basic understanding of how restful API’s work and you are off to the races. This is a big win for developers of every skill level, not a step back.

What about the rest of us that are not developers, or basic programmers that benefit from other members hard work? Are we going to be left with out these benefits that others so nicely provide? Who is SamrtThings going to be for? I for one choose SmartThings just because of the great community that helps so many.

5 Likes

Absolutely…the community here was a key reason I bought into SmartThings, and a key source of some of the best experiences that are available on this platform.

3 Likes

I tried this some time back. I use a dyndns service to know my home IP address. But if I tried to enter ****.dyndns.org in the ST development it kept telling me it was an invalid IP address. Maybe that’s been fixed by now. I haven’t tried it lately.

I agree with @anon36505037. Something needs to be done to maintain accessibility to smartapps (Webcore and others) and custom DTH’s or I’m out!

3 Likes

And those of us not using a Raspberry Pi? What then?

1 Like

I am a pretty new ST-user and I must say I’m concerned about what I have read here. The reason I bought ST is because of all different custom device handlers. Also, I am using webcore for all my automations.

Will my user experience be affected? Will my devices and automations stop working or have I missed something?

1 Like

Absolutely Not.

Raspberry pi was just one example. When you publish code via the IDE today it’s being “hosted” by someone (SmartThings). We need to stop looking at this through the lenses of how this worked in the past. For the non-coders, we are trying to build a platform that does not force you to use code. For the developers we are trying to build a platform that will allow you reach more people in a published and controlled way without needing to pass around the source code.

And lastly, No. We aren’t throwing anything in the bin overnight. There is going to be a long transition period before all of the new stuff is even fully in “production”. Then there will be some time while we main both the new system and legacy systems.

1 Like

It is required to be HTTPS

I just opened another thread about this problem of “https requirement” and the complexity of the new development model.

Am I missing something? From my point of view, I need to develop a network-hub-connected (UPNP&SSDP) device, but the documentation for hub-connected devices seems to specify it will be only zigbee and zwave… :frowning: